draft-ietf-mmusic-sdp-ipv6-01.txt   draft-ietf-mmusic-sdp-ipv6-02.txt 
Internet Engineering Task Force Sean Olson Internet Engineering Task Force Sean Olson
Internet draft Adam Roach Internet draft Gonzalo Camarillo
Gonzalo Camarillo <draft-ietf-mmusic-sdp-ipv6-02.txt> Ericsson
Ericsson February 2002
January 2002 Expires: August 2002 Adam Roach
Expires July 2002 dynamicsoft
<draft-ietf-mmusic-sdp-ipv6-01.txt>
Support for IPv6 in SDP Support for IPv6 in SDP
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at line 34
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document describes the use of IPv6 addresses [1] in conjunction This document describes the use of IPv6 addresses [1] in conjunction
with the Session Description Protocol (SDP) [2]. Specifically, this with the Session Description Protocol (SDP) [2]. Specifically, this
document clarifies existing text in SDP with regards to the syntax of document clarifies existing text in SDP with regards to the syntax
IPv6 addresses. of IPv6 addresses.
Olson/Camarillo/Roach 1
Support for IPv6 in SDP
1. Introduction 1. Introduction
SDP is intended for describing multimedia sessions for the purposes of SDP is intended for describing multimedia sessions for the purposes
session announcement, session invitation, and other forms of multimedia of session announcement, session invitation, and other forms of
session initiation. It is a text format description that provides multimedia session initiation. It is a text format description that
many details of a multimedia session including: the originator of the provides many details of a multimedia session including: the
session, a URL related to the session, the connection address for the originator of the session, a URL related to the session, the
session media(s), and optional attributes for the session media(s). connection address for the session media(s), and optional attributes
Each of these pieces of information may involve one or more IPv6 for the session media(s). Each of these pieces of information may
addresses. The ABNF for IP addresses in SDP currently leaves the syntax involve one or more IPv6 addresses. The ABNF for IP addresses in SDP
for IPv6 addresses undefined. This Internet-Draft attempts to complete currently leaves the syntax for IPv6 addresses undefined. This
the ABNF to include IPv6 addresses. addresses.
Accordingly, the address type "IP6" indicating an IPv6 address, should Accordingly, the address type "IP6" indicating an IPv6 address,
be allowed in the connection field, "c=", of the SDP. The ABNF already should be allowed in the connection field, "c=", of the SDP. The
reflects this, though the "Connection Data" text under section 6 of ABNF already reflects this, though the "Connection Data" text under
RFC2328 currently only defines the "IP4" address type. section 6 of RFC2328 currently only defines the "IP4" address type.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
"OPTIONAL" in this document are to be interpreted as described in this document are to be interpreted as described in RFC 2119.
RFC 2119.
3. Syntax 3. Syntax
RFC2373 [1] gives an ABNF for the text representation of IPv6 addresses in RFC2373 [1] gives an ABNF for the text representation of IPv6
Appendix B. RFC2732 [3] covers the text representation of IPv6 addresses addresses in Appendix B. RFC2732 [3] covers the text representation
when used within a URL. Using the ABNF described in these documents, the of IPv6 addresses when used within a URL. Using the ABNF described
following updated ABNF for SDP is proposed. in these documents, the following updated ABNF for SDP is proposed.
uri = ; defined in RFC1630 and RFC2732 uri = ; defined in RFC1630 and RFC2732
multicast-address = IP4-multicast | IP6-multicast multicast-address = IP4-multicast | IP6-multicast
IP4-multicast = m1 3*( "." decimal-uchar ) "/" ttl [ "/" integer ] IP4-multicast = m1 3*( "." decimal-uchar )
; IPv4 multicast addresses may be in the range "/" ttl [ "/" integer ]
; 224.0.0.0 to 239.255.255.255 ; IPv4 multicast addresses may be in the
; range 224.0.0.0 to 239.255.255.255
m1 = ("22" ("4"|"5"|"6"|"7"|"8"|"9")) | ("23" DIGIT )) m1 = ("22" ("4"|"5"|"6"|"7"|"8"|"9")) |
("23" DIGIT ))
IP6-multicast = hexpart [ ":" IP4-multicast ] IP6-multicast = hexpart "/" ttl [ "/" integer ]
"/" ttl [ "/" integer ] ; IPv6 address starting with FF
; IPv6 address starting with FF00
addr = FQDN | unicast-address addr = FQDN | unicast-address
FQDN = 4*(alpha-numeric|"-"|".") FQDN = 4*(alpha-numeric|"-"|".")
; fully qualified domain name as specified in ; fully qualified domain name as specified
; RFC1035 ; in RFC1035
unicast-address = IP4-address | IP6-address unicast-address = IP4-address | IP6-address
IP4-address = b1 "." decimal-uchar "." decimal-uchar "." b4 Olson/Camarillo/Roach 2
| "0.0.0.0" Support for IPv6 in SDP
IP4-address = b1 "." decimal-uchar "." decimal-uchar
"." b4 | "0.0.0.0"
b1 = decimal-uchar b1 = decimal-uchar
; less than "224"; not "0" or "127" ; less than "224"; not "0" or "127"
b4 = decimal-uchar b4 = decimal-uchar
; not "0" ; not "0"
IP6-address = *( HEXDIGIT | "." | ":" ) ; The following is from RFC2373 Appendix B. It is a direct copy.
; As defined in the IPv6 addressing architecture IP6-address = hexpart [ ":" IP4-address ]
4. Additional IPv6 Issues in SDP
4.1 IPv6 Addresses with Embedded IPv4 Addresses
RFC2373 defines two ways in which an IPv4 address may be
encoded in an IPv6 address. In both forms, the lower 32 bits
of the IPv6 address contain the IPv4 address. The first form is an
"IPv4 compatible IPv6 address" and it has the format:
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+
The second form of address is used to represent the addresses of hexpart = hexseq | hexseq "::" [ hexseq ] |
IPv4-only nodes (those that *do not* support IPv6) as IPv6 addresses. "::" [ hexseq ]
This type of address is termed an "IPv4-mapped IPv6 address" and has
the format:
| 80 bits | 16 | 32 bits | hexseq = hex4 *( ":" hex4)
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+
The difference in format is significant and MAY be treated hex4 = 1*4HEXDIG
differently in SDP implementations.
5. Example SDP description with IPv6 addresses 4. Example SDP description with IPv6 addresses
The following is an example SDP description using the above ABNF The following is an example SDP description using the above ABNF for
for IPv6 addresses. In particular, the origin, URI, and connection IPv6 addresses. In particular, the origin, URI, and connection
fields contain IPv6 addresses. The URI contains an IPv4 compatible fields contain IPv6 addresses.
IPv6 address.
v=0 v=0
o=nasa1 971731711378798081 0 IN IP6 2201:056D::112E:144A:1E24 o=nasa1 971731711378798081 0 IN IP6 2201:056D::112E:144A:1E24
s=(Almost) live video feed from Mars-II sattelite s=(Almost) live video feed from Mars-II sattelite
u=http://[::FFFF:10.2.12.126]/marsII u=http://[1080::8:800:200C:417A]/marsII
p=+1 713 555 1234 p=+1 713 555 1234
c=IN IP6 FF00:03AD::7F2E:172A:1E24 c=IN IP6 FF00:03AD::7F2E:172A:1E24/127
t=3338481189 3370017201 t=3338481189 3370017201
m=audio 6000 RTP/AVP 2 m=audio 6000 RTP/AVP 2
a=rtpmap:2 G726-32/8000 a=rtpmap:2 G726-32/8000
m=video 6024 RTP/AVP 107 m=video 6024 RTP/AVP 107
a=rtpmap:107 H263-1998/90000 a=rtpmap:107 H263-1998/90000
5. Note for implementors
An implementation might receive an SDP session description with an
IPv6 address that contains an IPv4-mapped address. Such an address
MUST be treated the same as an IPv4 address.
6. IANA Considerations 6. IANA Considerations
This document updates the definition of the IP6 addrtype parameter This document updates the definition of the IP6 addrtype parameter
found in RFC2327. found in RFC2327.
7. Security Considerations 7. Security Considerations
No additional considerations above what is stated in section 7 of No additional considerations above what is stated in section 7 of
Olson/Camarillo/Roach 3
Support for IPv6 in SDP
RFC2327. RFC2327.
8. References 8. References
[1] R. Hinden and S. Deering, "IP Version 6 Addressing Architecture", [1] R. Hinden and S. Deering, "IP Version 6 Addressing
RFC2373, IETF. Architecture", RFC2373, IETF.
[2] M. Handley and V. Jacobson, "Session Description Protocol", [2] M. Handley and V. Jacobson, "Session Description Protocol",
RFC2327, IETF. RFC2327, IETF.
[3] R. Hinden, et. al., "Format for Literal IPv6 Addresses in URL's", [3] R. Hinden, et. al., "Format for Literal IPv6 Addresses in
RFC2732, IETF. URL's", RFC2732, IETF.
[4] D. Crocker and P. Overell, [4] D. Crocker and P. Overell, "Augmented BNF for Syntax
"Augmented BNF for Syntax Specifications: ABNF", Specifications: ABNF", RFC2234, IETF.
RFC2234, IETF.
[5] S. Bradner, "Key words for use in RFCs to Indicate Requirement [5] S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC2119, IETF. Levels", RFC2119, IETF.
9. Author's Addresses 9. Authors's Addresses
Sean Olson Sean Olson
Richardson, Texas Richardson, Texas
USA USA
Email: seancolson@yahoo.com Email: seancolson@yahoo.com
Gonzalo Camarillo Gonzalo Camarillo
Ericsson Ericsson
Advanced Signalling Research Lab. Advanced Signalling Research Lab.
FIN-02420 Jorvas FIN-02420 Jorvas
Finland Finland
Phone: +358 9 299 3371 Phone: +358 9 299 3371
Fax: +358 9 299 3118 Fax: +358 9 299 3118
Email: Gonzalo.Camarillo@ericsson.com Email: Gonzalo.Camarillo@ericsson.com
Adam Roach Adam Roach
Ericsson dynamicsoft
Richardson, Texas 5100 Tennyson Parkway
Suite 1200
Plano, TX 75024
USA USA
Phone: +1 972 583 7594 E-Mail: <adam@dynamicsoft.com>
Fax: +1 972 669 0154 Voice: <sip:adam@dynamicsoft.com>
Email: Adam.Roach@ericsson.com
Full Copyright Statement
Copyright (c) The Internet Society (2001). All Rights Reserved.
Olson/Camarillo/Roach 4
Support for IPv6 in SDP
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Olson/Camarillo/Roach 5
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/