draft-ietf-mmusic-ice-sip-sdp-01.txt   draft-ietf-mmusic-ice-sip-sdp-02.txt 
MMUSIC M. Petit-Huguenin MMUSIC M. Petit-Huguenin
Internet-Draft Jive Communications Internet-Draft Jive Communications
Intended status: Standards Track A. Keranen Intended status: Standards Track A. Keranen
Expires: July 14, 2014 Ericsson Expires: July 14, 2014 Ericsson
January 10, 2014 January 10, 2014
Using Interactive Connectivity Establishment (ICE) with Using Interactive Connectivity Establishment (ICE) with
Session Description Protocol (SDP) offer/answer and Session Description Protocol (SDP) offer/answer and
Session Initiation Protocol (SIP) Session Initiation Protocol (SIP)
draft-ietf-mmusic-ice-sip-sdp-01 draft-ietf-mmusic-ice-sip-sdp-02
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 13, line 23 skipping to change at page 13, line 23
characters. The upper limit allows for buffer sizing in characters. The upper limit allows for buffer sizing in
implementations. Its large upper limit allows for increased amounts implementations. Its large upper limit allows for increased amounts
of randomness to be added over time. For compatibility with the 512 of randomness to be added over time. For compatibility with the 512
character limitation for the STUN username attribute value and for character limitation for the STUN username attribute value and for
bandwidth conservation considerations, the ice-ufrag attribute MUST bandwidth conservation considerations, the ice-ufrag attribute MUST
NOT be longer than 32 characters when sending, but an implementation NOT be longer than 32 characters when sending, but an implementation
MUST accept up to 256 characters when receiving. MUST accept up to 256 characters when receiving.
8.5. "ice-options" Attribute 8.5. "ice-options" Attribute
The "ice-options" attribute is a session-level attribute. It The "ice-options" attribute is a session- and media-level attribute.
contains a series of tokens that identify the options supported by It contains a series of tokens that identify the options supported by
the agent. Its grammar is: the agent. Its grammar is:
ice-options = "ice-options" ":" ice-option-tag ice-options = "ice-options" ":" ice-option-tag
0*(SP ice-option-tag) 0*(SP ice-option-tag)
ice-option-tag = 1*ice-char ice-option-tag = 1*ice-char
9. Subsequent Offer/Answer Exchanges 9. Subsequent Offer/Answer Exchanges
Either agent MAY generate a subsequent offer at any time allowed by Either agent MAY generate a subsequent offer at any time allowed by
RFC 3264 [RFC3264]. The rules in Section 7 will cause the RFC 3264 [RFC3264]. The rules in Section 7 will cause the
skipping to change at page 33, line 21 skipping to change at page 33, line 21
Appropriate Values: See Section 8 of RFC XXXX. Appropriate Values: See Section 8 of RFC XXXX.
16.1.7. ice-options Attribute 16.1.7. ice-options Attribute
Contact Name: Jonathan Rosenberg, jdrosen@jdrosen.net. Contact Name: Jonathan Rosenberg, jdrosen@jdrosen.net.
Attribute Name: ice-options Attribute Name: ice-options
Long Form: ice-options Long Form: ice-options
Type of Attribute: session-level Type of Attribute: session- or media-level
Charset Considerations: The attribute is not subject to the charset Charset Considerations: The attribute is not subject to the charset
attribute. attribute.
Purpose: This attribute is used with Interactive Connectivity Purpose: This attribute is used with Interactive Connectivity
Establishment (ICE), and indicates the ICE options or extensions Establishment (ICE), and indicates the ICE options or extensions
used by the agent. used by the agent.
Appropriate Values: See Section 8 of RFC XXXX. Appropriate Values: See Section 8 of RFC XXXX.
 End of changes. 3 change blocks. 
4 lines changed or deleted 4 lines changed or added

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