draft-westerlund-mmusic-ice-options-registry-00.txt   draft-westerlund-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: May 15, 2011 November 11, 2010 Expires: May 23, 2011 November 19, 2010
IANA Registry for Interactive Connectivity Establishment (ICE) Options IANA Registry for Interactive Connectivity Establishment (ICE) Options
draft-westerlund-mmusic-ice-options-registry-00 draft-westerlund-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) is missing a registry for ICE options. This document defines
this missing IANA registry. this missing IANA registry.
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 33 skipping to change at page 1, line 33
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 May 15, 2011. This Internet-Draft will expire on May 23, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
3.1. ICE Options . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. ICE Options . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
"Interactive Connectivity Establishment (ICE): A Protocol for Network "Interactive Connectivity Establishment (ICE): A Protocol for Network
Address Translator (NAT) Traversal for Offer/Answer" [RFC5245] Address Translator (NAT) Traversal for Offer/Answer" [RFC5245]
defines a concept of ICE Options. However, the ICE RFC fails to defines a concept of ICE Options. However, the ICE RFC fails to
create an IANA registry for ICE options. As there has come into create an IANA registry for ICE options. As there has come into
existence at least one ICE option, there is need to create the existence at least one ICE option, there is need to create the
registry. registry.
skipping to change at page 3, line 41 skipping to change at page 3, line 41
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 following ABNF [RFC5234] An ICE option identifier MUST fulfill the ABNF [RFC5234] syntax for
syntax: "ice-option-tag" as specified in [RFC5245]. This syntax is reproduce
here for simplicity, but the authoritative definition is 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 SHOULD NOT be longer than 20 charachters. ICE options are of unlimited length by the syntax, however they are
recommended to be no longer than 20 characters. This is to reduce
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
o Email and Address of the Contact person o Email and Address of the Contact person
o Organization having the change control o Organization or individuals having the change control
o The ICE option identifier o The ICE option identifier
o Short description of the ICE extension o Short description of the ICE extension
o Reference(s) to the specification defining the ICE option and the o Reference(s) to the specification defining the ICE option and the
related extensions related extensions
4. Security Considerations 4. Security Considerations
 End of changes. 7 change blocks. 
8 lines changed or deleted 12 lines changed or added

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