draft-ietf-mmusic-ice-sip-sdp-07.txt   draft-ietf-mmusic-ice-sip-sdp-08.txt 
MMUSIC M. Petit-Huguenin MMUSIC M. Petit-Huguenin
Internet-Draft Impedance Mismatch Internet-Draft Impedance Mismatch
Intended status: Standards Track A. Keranen Intended status: Standards Track A. Keranen
Expires: April 21, 2016 Ericsson Expires: September 19, 2016 Ericsson
S. Nandakumar S. Nandakumar
Cisco Systems Cisco Systems
October 19, 2015 March 18, 2016
Using Interactive Connectivity Establishment (ICE) with Using Interactive Connectivity Establishment (ICE) with
Session Description Protocol (SDP) offer/answer and Session Initiation Session Description Protocol (SDP) offer/answer and Session Initiation
Protocol (SIP) Protocol (SIP)
draft-ietf-mmusic-ice-sip-sdp-07 draft-ietf-mmusic-ice-sip-sdp-08
Abstract Abstract
This document describes how Interactive Connectivity Establishment This document describes how Interactive Connectivity Establishment
(ICE) is used with Session Description Protocol (SDP) offer/answer (ICE) is used with Session Description Protocol (SDP) offer/answer
and Session Initiation Protocol (SIP). and Session Initiation Protocol (SIP).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 21, 2016. This Internet-Draft will expire on September 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 6, line 19 skipping to change at page 6, line 19
username fragment and password are exchanged in the ice-ufrag and username fragment and password are exchanged in the ice-ufrag and
ice-pwd attributes, respectively. ice-pwd attributes, respectively.
If an agent is a lite implementation, it MUST include an "a=ice-lite" If an agent is a lite implementation, it MUST include an "a=ice-lite"
session-level attribute in its SDP to indicate this. If an agent is session-level attribute in its SDP to indicate this. If an agent is
a full implementation, it MUST NOT include this attribute. a full implementation, it MUST NOT include this attribute.
The default candidates are added to the SDP as the default The default candidates are added to the SDP as the default
destination for media. For streams based on RTP, this is done by destination for media. For streams based on RTP, this is done by
placing the IP address and port of the RTP candidate into the "c=" placing the IP address and port of the RTP candidate into the "c="
and "m=" lines, respectively. If the agent is utilizing RTCP, it and "m=" lines, respectively. If the agent is utilizing RTCP and if
MUST encode the RTCP candidate using the a=rtcp attribute as defined RTCP candidate is present and is not equal to the same address and
in RFC 3605 [RFC3605]. If RTCP is not in use, the agent MUST signal the next higher port number of the RTP candidate, the agent MUST
encode the RTCP candidate using the a=rtcp attribute as defined in
RFC 3605 [RFC3605]. If RTCP is not in use, the agent MUST signal
that using b=RS:0 and b=RR:0 as defined in RFC 3556 [RFC3556]. that using b=RS:0 and b=RR:0 as defined in RFC 3556 [RFC3556].
The transport addresses that will be the default destination for The transport addresses that will be the default destination for
media when communicating with non-ICE peers MUST also be present as media when communicating with non-ICE peers MUST also be present as
candidates in one or more a=candidate lines. candidates in one or more a=candidate lines.
ICE provides for extensibility by allowing an offer or answer to ICE provides for extensibility by allowing an offer or answer to
contain a series of tokens that identify the ICE extensions used by contain a series of tokens that identify the ICE extensions used by
that agent. If an agent supports an ICE extension, it MUST include that agent. If an agent supports an ICE extension, it MUST include
the token defined for that extension in the ice-options attribute. the token defined for that extension in the ice-options attribute.
skipping to change at page 35, line 22 skipping to change at page 35, line 22
Some of the text in this document was taken from RFC 6336, authored Some of the text in this document was taken from RFC 6336, authored
by Magnus Westerlund and Colin Perkins. by Magnus Westerlund and Colin Perkins.
Thanks to Thomas Stach for the text in Section 10.3 Thanks to Thomas Stach for the text in Section 10.3
19. References 19. References
19.1. Normative References 19.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
DOI 10.17487/RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <http://www.rfc-editor.org/info/rfc3261>.
[RFC3262] Rosenberg, J. and H. Schulzrinne, "Reliability of [RFC3262] Rosenberg, J. and H. Schulzrinne, "Reliability of
Provisional Responses in Session Initiation Protocol Provisional Responses in Session Initiation Protocol
(SIP)", RFC 3262, DOI 10.17487/RFC3262, June 2002, (SIP)", RFC 3262, DOI 10.17487/RFC3262, June 2002,
<http://www.rfc-editor.org/info/rfc3262>. <http://www.rfc-editor.org/info/rfc3262>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264, DOI
DOI 10.17487/RFC3264, June 2002, 10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>. <http://www.rfc-editor.org/info/rfc3264>.
[RFC3312] Camarillo, G., Ed., Marshall, W., Ed., and J. Rosenberg, [RFC3312] Camarillo, G., Ed., Marshall, W., Ed., and J. Rosenberg,
"Integration of Resource Management and Session Initiation "Integration of Resource Management and Session Initiation
Protocol (SIP)", RFC 3312, DOI 10.17487/RFC3312, October Protocol (SIP)", RFC 3312, DOI 10.17487/RFC3312, October
2002, <http://www.rfc-editor.org/info/rfc3312>. 2002, <http://www.rfc-editor.org/info/rfc3312>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>. July 2003, <http://www.rfc-editor.org/info/rfc3550>.
[RFC3556] Casner, S., "Session Description Protocol (SDP) Bandwidth [RFC3556] Casner, S., "Session Description Protocol (SDP) Bandwidth
Modifiers for RTP Control Protocol (RTCP) Bandwidth", Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC
RFC 3556, DOI 10.17487/RFC3556, July 2003, 3556, DOI 10.17487/RFC3556, July 2003,
<http://www.rfc-editor.org/info/rfc3556>. <http://www.rfc-editor.org/info/rfc3556>.
[RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute
in Session Description Protocol (SDP)", RFC 3605, in Session Description Protocol (SDP)", RFC 3605, DOI
DOI 10.17487/RFC3605, October 2003, 10.17487/RFC3605, October 2003,
<http://www.rfc-editor.org/info/rfc3605>. <http://www.rfc-editor.org/info/rfc3605>.
[RFC4032] Camarillo, G. and P. Kyzivat, "Update to the Session [RFC4032] Camarillo, G. and P. Kyzivat, "Update to the Session
Initiation Protocol (SIP) Preconditions Framework", Initiation Protocol (SIP) Preconditions Framework", RFC
RFC 4032, DOI 10.17487/RFC4032, March 2005, 4032, DOI 10.17487/RFC4032, March 2005,
<http://www.rfc-editor.org/info/rfc4032>. <http://www.rfc-editor.org/info/rfc4032>.
[RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network [RFC4091] Camarillo, G. and J. Rosenberg, "The Alternative Network
Address Types (ANAT) Semantics for the Session Description Address Types (ANAT) Semantics for the Session Description
Protocol (SDP) Grouping Framework", RFC 4091, Protocol (SDP) Grouping Framework", RFC 4091, DOI
DOI 10.17487/RFC4091, June 2005, 10.17487/RFC4091, June 2005,
<http://www.rfc-editor.org/info/rfc4091>. <http://www.rfc-editor.org/info/rfc4091>.
[RFC4092] Camarillo, G. and J. Rosenberg, "Usage of the Session [RFC4092] Camarillo, G. and J. Rosenberg, "Usage of the Session
Description Protocol (SDP) Alternative Network Address Description Protocol (SDP) Alternative Network Address
Types (ANAT) Semantics in the Session Initiation Protocol Types (ANAT) Semantics in the Session Initiation Protocol
(SIP)", RFC 4092, DOI 10.17487/RFC4092, June 2005, (SIP)", RFC 4092, DOI 10.17487/RFC4092, June 2005,
<http://www.rfc-editor.org/info/rfc4092>. <http://www.rfc-editor.org/info/rfc4092>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>. July 2006, <http://www.rfc-editor.org/info/rfc4566>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/
DOI 10.17487/RFC5234, January 2008, RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <http://www.rfc-editor.org/info/rfc5234>.
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing, [RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
"Session Traversal Utilities for NAT (STUN)", RFC 5389, "Session Traversal Utilities for NAT (STUN)", RFC 5389,
DOI 10.17487/RFC5389, October 2008, DOI 10.17487/RFC5389, October 2008,
<http://www.rfc-editor.org/info/rfc5389>. <http://www.rfc-editor.org/info/rfc5389>.
[RFC5768] Rosenberg, J., "Indicating Support for Interactive [RFC5768] Rosenberg, J., "Indicating Support for Interactive
Connectivity Establishment (ICE) in the Session Initiation Connectivity Establishment (ICE) in the Session Initiation
Protocol (SIP)", RFC 5768, DOI 10.17487/RFC5768, April Protocol (SIP)", RFC 5768, DOI 10.17487/RFC5768, April
2010, <http://www.rfc-editor.org/info/rfc5768>. 2010, <http://www.rfc-editor.org/info/rfc5768>.
[RFC6679] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P., [RFC6679] Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P.,
and K. Carlberg, "Explicit Congestion Notification (ECN) and K. Carlberg, "Explicit Congestion Notification (ECN)
for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August
2012, <http://www.rfc-editor.org/info/rfc6679>. 2012, <http://www.rfc-editor.org/info/rfc6679>.
[RFC7092] Kaplan, H. and V. Pascual, "A Taxonomy of Session [RFC7092] Kaplan, H. and V. Pascual, "A Taxonomy of Session
Initiation Protocol (SIP) Back-to-Back User Agents", Initiation Protocol (SIP) Back-to-Back User Agents", RFC
RFC 7092, DOI 10.17487/RFC7092, December 2013, 7092, DOI 10.17487/RFC7092, December 2013,
<http://www.rfc-editor.org/info/rfc7092>. <http://www.rfc-editor.org/info/rfc7092>.
[ICE-BIS] Keranen, A. and J. Rosenberg, "Interactive Connectivity [ICE-BIS] Keranen, A. and J. Rosenberg, "Interactive Connectivity
Establishment (ICE): A Protocol for Network Address Establishment (ICE): A Protocol for Network Address
Translator (NAT) Traversal for Offer/Answer Protocols", Translator (NAT) Traversal for Offer/Answer Protocols",
draft-ietf-ice-rfc5245bis-00 (work in progress), March draft-ietf-ice-rfc5245bis-00 (work in progress), March
2015. 2015.
19.2. Informative References 19.2. Informative References
skipping to change at page 37, line 40 skipping to change at page 37, line 40
Control (3pcc) in the Session Initiation Protocol (SIP)", Control (3pcc) in the Session Initiation Protocol (SIP)",
BCP 85, RFC 3725, DOI 10.17487/RFC3725, April 2004, BCP 85, RFC 3725, DOI 10.17487/RFC3725, April 2004,
<http://www.rfc-editor.org/info/rfc3725>. <http://www.rfc-editor.org/info/rfc3725>.
[RFC3960] Camarillo, G. and H. Schulzrinne, "Early Media and Ringing [RFC3960] Camarillo, G. and H. Schulzrinne, "Early Media and Ringing
Tone Generation in the Session Initiation Protocol (SIP)", Tone Generation in the Session Initiation Protocol (SIP)",
RFC 3960, DOI 10.17487/RFC3960, December 2004, RFC 3960, DOI 10.17487/RFC3960, December 2004,
<http://www.rfc-editor.org/info/rfc3960>. <http://www.rfc-editor.org/info/rfc3960>.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Congestion Control Protocol (DCCP)", RFC 4340, Congestion Control Protocol (DCCP)", RFC 4340, DOI
DOI 10.17487/RFC4340, March 2006, 10.17487/RFC4340, March 2006,
<http://www.rfc-editor.org/info/rfc4340>. <http://www.rfc-editor.org/info/rfc4340>.
[RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed., [RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed.,
"Managing Client-Initiated Connections in the Session "Managing Client-Initiated Connections in the Session
Initiation Protocol (SIP)", RFC 5626, Initiation Protocol (SIP)", RFC 5626, DOI 10.17487/
DOI 10.17487/RFC5626, October 2009, RFC5626, October 2009,
<http://www.rfc-editor.org/info/rfc5626>. <http://www.rfc-editor.org/info/rfc5626>.
[RFC5898] Andreasen, F., Camarillo, G., Oran, D., and D. Wing, [RFC5898] Andreasen, F., Camarillo, G., Oran, D., and D. Wing,
"Connectivity Preconditions for Session Description "Connectivity Preconditions for Session Description
Protocol (SDP) Media Streams", RFC 5898, Protocol (SDP) Media Streams", RFC 5898, DOI 10.17487/
DOI 10.17487/RFC5898, July 2010, RFC5898, July 2010,
<http://www.rfc-editor.org/info/rfc5898>. <http://www.rfc-editor.org/info/rfc5898>.
Appendix A. Examples Appendix A. Examples
For the example shown in Section 13 of [ICE-BIS] the resulting offer For the example shown in Section 13 of [ICE-BIS] the resulting offer
(message 5) encoded in SDP looks like: (message 5) encoded in SDP looks like:
v=0 v=0
o=jdoe 2890844526 2890842807 IN IP4 $L-PRIV-1.IP o=jdoe 2890844526 2890842807 IN IP4 $L-PRIV-1.IP
s= s=
 End of changes. 17 change blocks. 
30 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.44. The latest version is available from http://tools.ietf.org/tools/rfcdiff/