draft-ietf-mmusic-ice-options-registry-00.txt   draft-ietf-mmusic-ice-options-registry-01.txt 
Network Working Group M. Westerlund Network Working Group M. Westerlund
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 5245 (if approved) C. Perkins Updates: 5245 (if approved) C. Perkins
Intended status: Standards Track University of Glasgow Intended status: Standards Track University of Glasgow
Expires: July 15, 2011 January 11, 2011 Expires: September 29, 2011 March 28, 2011
IANA Registry for Interactive Connectivity Establishment (ICE) Options IANA Registry for Interactive Connectivity Establishment (ICE) Options
draft-ietf-mmusic-ice-options-registry-00 draft-ietf-mmusic-ice-options-registry-01
Abstract Abstract
It has been identified that Interactive Connectivity Establishment It has been identified that Interactive Connectivity Establishment
(ICE) is missing a registry for ICE options. This document defines (ICE) RFC5245 is missing a registry for ICE options. This document
this missing IANA registry. defines this missing IANA registry and updates RFC5245.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 July 15, 2011. This Internet-Draft will expire on September 29, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 3, line 22 skipping to change at page 3, line 22
registry. registry.
RFC 5245 says: "ICE provides for extensibility by allowing an offer RFC 5245 says: "ICE provides for extensibility by allowing an offer
or answer to contain a series of tokens that identify the ICE or answer to contain a series of tokens that identify the ICE
extensions used by that agent. If an agent supports an ICE extensions used by that agent. If an agent supports an ICE
extension, it MUST include the token defined for that extension in extension, it MUST include the token defined for that extension in
the ice-options attribute." the ice-options attribute."
Thus, as future extensions are defined, these ICE options needs to be Thus, as future extensions are defined, these ICE options needs to be
registered with IANA to ensure non-conflicting identification. The registered with IANA to ensure non-conflicting identification. The
ICE options identifiers are used in signalling between the ICE end- ICE options identifiers are used in signalling between the ICE
points to negotiate extension support. RFC 5245 defines one method endpoints to negotiate extension support. RFC 5245 defines one
of signaling these ICE options, using SDP with Offer/Answer method of signalling these ICE options, using SDP with Offer/Answer
[RFC3264]. [RFC3264].
This document updates the ICE specification [RFC5245].
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. IANA Considerations 3. IANA Considerations
This document defines a registry for ICE options that can be used in This document defines a registry for ICE options that can be used in
SDP "ice-options" attribute or other signalling parameters carrying SDP "ice-options" attribute or other signalling parameters carrying
the ICE options. the ICE options.
3.1. ICE Options 3.1. ICE Options
An ICE option identifier MUST fulfill the ABNF [RFC5234] syntax for An ICE option identifier MUST fulfill the ABNF [RFC5234] syntax for
"ice-option-tag" as specified in [RFC5245]. This syntax is reproduce "ice-option-tag" as specified in [RFC5245]. This syntax is
here for simplicity, but the authoritative definition is in the ICE reproduced here for simplicity, but the authoritative definition is
RFC: in the ICE RFC:
ice-option-tag = 1*ice-char ice-option-tag = 1*ice-char
ice-char = ALPHA / DIGIT / "+" / "/" ice-char = ALPHA / DIGIT / "+" / "/"
ICE options are of unlimited length by the syntax, however they are ICE options are of unlimited length by the syntax, however they are
recommended to be no longer than 20 characters. This is to reduce RECOMMENDED to be no longer than 20 characters. This is to reduce
message sizes and allow for efficient parsing. message sizes and allow for efficient parsing.
Registration of an ICE option is done using the Specification Registration of an ICE option is done using the Specification
Required policy as defined in "Guidelines for Writing an IANA Required policy as defined in "Guidelines for Writing an IANA
Considerations Section in RFCs" [RFC5226]. Considerations Section in RFCs" [RFC5226].
A registration request MUST include the following information: A registration request MUST include the following information:
o Name of contact person for the registration o Name of contact person for the registration
 End of changes. 8 change blocks. 
12 lines changed or deleted 14 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/