分享
 
 
 

RFC3266 - Support for IPv6 in Session Description Protocol (SDP)

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group S. Olson

Request for Comments: 3266 Microsoft

Updates: 2327 G. Camarillo

Category: Standards Track EriCsson

A. B. Roach

dynamicsoft

June 2002

Support for IPv6 in Session Description Protocol (SDP)

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2002). All Rights Reserved.

Abstract

This document describes the use of Internet Protocol Version 6 (IPv6)

addresses in conjunction with the Session Description Protocol (SDP).

Specifically, this document clarifies existing text in SDP with

regards to the syntax of IPv6 addresses.

1. IntrodUCtion

SDP is intended for describing multimedia sessions for the purposes

of session announcement, session invitation, and other forms of

multimedia session initiation. It is a text format description that

provides many details of a multimedia session including: the

originator of the session, a URL related to the session, the

connection address for the session media(s), and optional attributes

for the session media(s). Each of these pieces of information may

involve one or more IPv6 addresses. The ABNF for IP addresses in SDP

currently leaves the syntax for IPv6 addresses undefined. This

document attempts to complete the ABNF to include IPv6 addresses.

Accordingly, the address type "IP6" indicating an IPv6 address,

should be allowed in the connection field, "c=", of the SDP. The

ABNF already reflects this, though the "Connection Data" text under

section 6 of RFC2328 currently only defines the "IP4" address type.

2. Terminology

The key Words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in RFC2119 [5].

3. Syntax

RFC2373 [1] gives an ABNF for the text representation of IPv6

addresses in Appendix B. RFC2732 [3] covers the text representation

of IPv6 addresses when used within a URL. Using the ABNF described

in these documents, the following updated ABNF for SDP is proposed.

uri = ; defined in RFC1630 and RFC2732

multicast-address = IP4-multicast / IP6-multicast

IP4-multicast = m1 3*( "." decimal-uchar )

"/" ttl [ "/" integer ]

; 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 ))

IP6-multicast = heXPart

; IPv6 address starting with FF

addr = FQDN / unicast-address

FQDN = 4*(alpha-numeric/"-"/".")

; fully qualified domain name as specified

; in RFC1035

unicast-address = IP4-address / IP6-address

IP4-address = b1 3*("." decimal-uchar) / "0.0.0.0"

b1 = decimal-uchar

; less than "224"; not "0" or "127"

; The following is from RFC2373 Appendix B. It is a direct copy.

IP6-address = hexpart [ ":" IP4-address ]

hexpart = hexseq / hexseq "::" [ hexseq ] /

"::" [ hexseq ]

hexseq = hex4 *( ":" hex4)

hex4 = 1*4HEXDIG

4. Example SDP description with IPv6 addresses

The following is an example SDP description using the above ABNF for

IPv6 addresses. In particular, the origin and connection fields

contain IPv6 addresses.

v=0

o=nasa1 971731711378798081 0 IN IP6 2201:056D::112E:144A:1E24

s=(Almost) live video feed from Mars-II satellite

p=+1 713 555 1234

c=IN IP6 FF1E:03AD::7F2E:172A:1E24

t=3338481189 3370017201

m=audio 6000 RTP/AVP 2

a=rtpmap:2 G726-32/8000

m=video 6024 RTP/AVP 107

a=rtpmap:107 H263-1998/90000

5. Note for implementors

An implementation may receive an SDP session description with an IPv6

address whose format [1] is internally that of an IPv4 mapped

address. Note that such an address is actually the address of an

IPv4-only node, and implementors are warned to interpret IPv4 mapped

addresses as equivalent to IP4.

6. IANA Considerations

This document updates the definition of the IP6 addrtype parameter

found in RFC2327.

7. Security Considerations

No additional considerations above what is stated in section 7 of RFC

2327.

8. References

[1] Hinden, R. and S. Deering, "IP Version 6 Addressing

Architecture", RFC2373, July 1998.

[2] Handley, M. and V. Jacobson, "SDP: Session Description

Protocol", RFC2327, April 1998.

[3] Hinden, R., Carpenter, B. and L. Masinter, "Format for Literal

IPv6 Addresses in URL's", RFC2732, December 1999.

[4] Crocker, D. and P. Overell, "Augmented BNF for Syntax

Specifications: ABNF", RFC2234, November 1997.

[5] Bradner, S., "Key words for Use in RFCs to Indicate Requirement

Levels", BCP 14, RFC2119, March 1997.

9. Authors' Addresses

Sean Olson

Microsoft

One Microsoft Way

Redmond, WA 98052

USA

EMail: seanol@microsoft.com

Gonzalo Camarillo

Ericsson

Advanced Signalling Research Lab.

FIN-02420 Jorvas

Finland

Phone: +358 9 299 3371

Fax: +358 9 299 3118

EMail: Gonzalo.Camarillo@ericsson.com

Adam Roach

dynamicsoft

5100 Tennyson Parkway

Suite 1200

Plano, TX 75024

USA

EMail: adam@dynamicsoft.com

Voice: <sip:adam@dynamicsoft.com>

10. Full Copyright Statement

Copyright (C) The Internet Society (2002). All Rights Reserved.

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.

Acknowledgement

Funding for the RFCEditor function is currently provided by the

Internet Society.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有