draft-ietf-mmusic-ice-sip-sdp-29.txt   draft-ietf-mmusic-ice-sip-sdp-30.txt 
MMUSIC M. Petit-Huguenin MMUSIC M. Petit-Huguenin
Internet-Draft Impedance Mismatch Internet-Draft Impedance Mismatch
Obsoletes: 5245 (if approved) S. Nandakumar Obsoletes: 5245 (if approved) S. Nandakumar
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: November 30, 2019 A. Keranen Expires: December 3, 2019 A. Keranen
Ericsson Ericsson
May 29, 2019 June 1, 2019
Session Description Protocol (SDP) Offer/Answer procedures for Session Description Protocol (SDP) Offer/Answer procedures for
Interactive Connectivity Establishment (ICE) Interactive Connectivity Establishment (ICE)
draft-ietf-mmusic-ice-sip-sdp-29 draft-ietf-mmusic-ice-sip-sdp-30
Abstract Abstract
This document describes Session Description Protocol (SDP) Offer/ This document describes Session Description Protocol (SDP) Offer/
Answer procedures for carrying out Interactive Connectivity Answer procedures for carrying out Interactive Connectivity
Establishment (ICE) between the agents. Establishment (ICE) between the agents.
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 36 skipping to change at page 1, line 36
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 November 30, 2019. This Internet-Draft will expire on December 3, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 46 skipping to change at page 2, line 46
3.3.4. Concluding ICE . . . . . . . . . . . . . . . . . . . 10 3.3.4. Concluding ICE . . . . . . . . . . . . . . . . . . . 10
3.4. Subsequent Offer/Answer Exchanges . . . . . . . . . . . . 10 3.4. Subsequent Offer/Answer Exchanges . . . . . . . . . . . . 10
3.4.1. Sending Subsequent Offer . . . . . . . . . . . . . . 10 3.4.1. Sending Subsequent Offer . . . . . . . . . . . . . . 10
3.4.2. Sending Subsequent Answer . . . . . . . . . . . . . . 13 3.4.2. Sending Subsequent Answer . . . . . . . . . . . . . . 13
3.4.3. Receiving Answer for a Subsequent Offer . . . . . . . 15 3.4.3. Receiving Answer for a Subsequent Offer . . . . . . . 15
4. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1. "candidate" Attribute . . . . . . . . . . . . . . . . . . 16 4.1. "candidate" Attribute . . . . . . . . . . . . . . . . . . 16
4.2. "remote-candidates" Attribute . . . . . . . . . . . . . . 19 4.2. "remote-candidates" Attribute . . . . . . . . . . . . . . 19
4.3. "ice-lite" and "ice-mismatch" Attributes . . . . . . . . 19 4.3. "ice-lite" and "ice-mismatch" Attributes . . . . . . . . 19
4.4. "ice-ufrag" and "ice-pwd" Attributes . . . . . . . . . . 20 4.4. "ice-ufrag" and "ice-pwd" Attributes . . . . . . . . . . 20
4.5. "ice-pacing" Attribute . . . . . . . . . . . . . . . . . 20 4.5. "ice-pacing" Attribute . . . . . . . . . . . . . . . . . 21
4.6. "ice-options" Attribute . . . . . . . . . . . . . . . . . 21 4.6. "ice-options" Attribute . . . . . . . . . . . . . . . . . 21
5. Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . 22 5. Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. SIP Considerations . . . . . . . . . . . . . . . . . . . . . 22 6. SIP Considerations . . . . . . . . . . . . . . . . . . . . . 22
6.1. Latency Guidelines . . . . . . . . . . . . . . . . . . . 22 6.1. Latency Guidelines . . . . . . . . . . . . . . . . . . . 22
6.1.1. Offer in INVITE . . . . . . . . . . . . . . . . . . . 23 6.1.1. Offer in INVITE . . . . . . . . . . . . . . . . . . . 23
6.1.2. Offer in Response . . . . . . . . . . . . . . . . . . 24 6.1.2. Offer in Response . . . . . . . . . . . . . . . . . . 24
6.2. SIP Option Tags and Media Feature Tags . . . . . . . . . 24 6.2. SIP Option Tags and Media Feature Tags . . . . . . . . . 24
6.3. Interactions with Forking . . . . . . . . . . . . . . . . 24 6.3. Interactions with Forking . . . . . . . . . . . . . . . . 24
6.4. Interactions with Preconditions . . . . . . . . . . . . . 25 6.4. Interactions with Preconditions . . . . . . . . . . . . . 25
6.5. Interactions with Third Party Call Control . . . . . . . 25 6.5. Interactions with Third Party Call Control . . . . . . . 25
skipping to change at page 7, line 7 skipping to change at page 7, line 7
few exceptions noted below: few exceptions noted below:
1. The presence of certain application layer gateways MAY modify the 1. The presence of certain application layer gateways MAY modify the
transport address information as described in Section 8.2.2. The transport address information as described in Section 8.2.2. The
behavior of the responding agent in such a situation is behavior of the responding agent in such a situation is
implementation defined. Informally, the responding agent MAY implementation defined. Informally, the responding agent MAY
consider the mismatched transport address information as a consider the mismatched transport address information as a
plausible new candidate learnt from the peer and continue its ICE plausible new candidate learnt from the peer and continue its ICE
processing with that transport address included. Alternatively, processing with that transport address included. Alternatively,
the responding agent MAY include an "a=ice-mismatch" attribute in the responding agent MAY include an "a=ice-mismatch" attribute in
its answer and MAY also omit "a=candidate" attributes for such its answer for such data streams. If agent chooses to include an
data streams. "a=ice-mismatch" attribute in its answer for a data stream, then
it MUST also omit "a=candidate" attributes, MUST terminate the
usage of ICE procedures and [RFC3264] procedures MUST be used
instead for this data stream.
2. The transport address from the peer for the default destination 2. The transport address from the peer for the default destination
correspond to IP address values "0.0.0.0"/"::" and port value of correspond to IP address values "0.0.0.0"/"::" and port value of
"9". This MUST not be considered as a ICE failure by the peer "9". This MUST not be considered as a ICE failure by the peer
agent and the ICE processing MUST continue as usual. agent and the ICE processing MUST continue as usual.
3. In some cases, controlling/initiator agent may receive the SDP 3. In some cases, controlling/initiator agent may receive the SDP
answer that may omit "a=candidate" attributes for the data answer that may omit "a=candidate" attributes for the data
stream, and instead include a media level "a=ice-mismatch" stream, and instead include a media level "a=ice-mismatch"
attribute. This signals to the offerer that the answerer attribute. This signals to the offerer that the answerer
skipping to change at page 19, line 50 skipping to change at page 19, line 50
The syntax of the "ice-lite" and "ice-mismatch" attributes, both of The syntax of the "ice-lite" and "ice-mismatch" attributes, both of
which are flags, is: which are flags, is:
ice-lite = "ice-lite" ice-lite = "ice-lite"
ice-mismatch = "ice-mismatch" ice-mismatch = "ice-mismatch"
"ice-lite" is a session-level attribute only, and indicates that an "ice-lite" is a session-level attribute only, and indicates that an
agent is a lite implementation. "ice-mismatch" is a media-level agent is a lite implementation. "ice-mismatch" is a media-level
attribute and only reported in the answer. It indicates that the attribute and only reported in the answer. It indicates that the
offer arrived with a default destination for a media component that offer arrived with a default destination for a media component that
didn't have a corresponding candidate attribute. didn't have a corresponding candidate attribute. Inclusion of
"a=ice-mismatch" attribute for a given data stream implies that even
though both agents support ICE, ICE procedures MUST not used for this
data stream and [RFC3264] procedures MUST be used instead.
4.4. "ice-ufrag" and "ice-pwd" Attributes 4.4. "ice-ufrag" and "ice-pwd" Attributes
The "ice-ufrag" and "ice-pwd" attributes convey the username fragment The "ice-ufrag" and "ice-pwd" attributes convey the username fragment
and password used by ICE for message integrity. Their syntax is: and password used by ICE for message integrity. Their syntax is:
ice-pwd-att = "ice-pwd:" password ice-pwd-att = "ice-pwd:" password
ice-ufrag-att = "ice-ufrag:" ufrag ice-ufrag-att = "ice-ufrag:" ufrag
password = 22*256ice-char password = 22*256ice-char
ufrag = 4*256ice-char ufrag = 4*256ice-char
 End of changes. 7 change blocks. 
8 lines changed or deleted 14 lines changed or added

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