[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: (draft-jennings-iptel-tel-reg) 00
01 02 03 04 05 06 RFC 5341
IPTEL WG C. Jennings
Internet-Draft Cisco Systems
Updates: 3966,AAAA,4694,4715,CCCC V. Gurbani
(if approved) Alcatel-Lucent
Expires: June 8, 2007 December 5, 2006
The Internet Assigned Number Authority (IANA) tel Uniform Resource
Identifier (URI) Parameter Registry
draft-ietf-iptel-tel-reg-04
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 8, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document creates an Internet Assigned Number Authority (IANA)
registry for tel Uniform Resource Identifier (URI) parameters and
their values. It populates the registry with the parameters defined
in the tel URI specification, along with the parameters in tel URI
extensions defined for number portability and trunk groups.
Jennings & Gurbani Expires June 8, 2007 [Page 1]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use of the Registry . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4.1 tel URI Parameters Registry . . . . . . . . . . . . . . . 4
4.2 Registration Policy for tel URI Parameters . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1 Normative References . . . . . . . . . . . . . . . . . . . 6
7.2 Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . 8
Jennings & Gurbani Expires June 8, 2007 [Page 2]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
1. Introduction
The tel URI, defined in RFC 3966 [1], defines a URI that can be used
to represent resources identified by telephone numbers. The tel URI,
like many other URIs, provides extensibility through the definition
of new URI parameters and new values for existing parameters.
However, RFC3966 did not specify an IANA registry where such
parameters and values can be listed and standardized. This
specification creates such a registry.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [3].
3. Use of the Registry
The tel URI parameters and values for these parameters MUST be
documented in a standards-track RFC in order to be registered by
IANA. This documentation MUST fully explain the syntax, intended
usage, and semantics of the parameter. The intent of this
requirement is to assure interoperability between independent
implementations, and to prevent accidental namespace collisions
between implementations of dissimilar features.
RFCs defining tel URI parameters or parameter values MUST register
them with IANA as described below.
Registered tel URI parameters and their values are to be considered
"reserved words". In order to preserve interoperability, registered
parameters MUST be used in a manner consistent with that described in
their defining RFC. Implementations MUST NOT utilize "private" or
"locally defined" URI parameters that conflict with registered
parameters.
Some tel URI parameters only accept a set of predefined parameter
values while others can take any value. There are also parameters
that do not have any value; they are used as flags.
Those URI parameters that take on predefined values typically take on
a large number of values. Registering each of those values, or
creating a sub-registry for each such parameter is not not
appropriate. Instead, we have chosen to register URI parameter
values by reference. That is, the entry in the URI parameter
registry for a given URI parameter contains references to the RFCs
defining new values of that parameter.
Jennings & Gurbani Expires June 8, 2007 [Page 3]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
Accordingly, the tel URI parameter registry contains a column that
indicates whether or not each parameter only accepts a set of
predefined values. The column can contain "Yes", or "No". A value
of "Yes" in the column implies that certain predefined values exist
for this parameter and the accompanying RFC should be consulted to
find out the accepted set of values. A value of "No" in the column
implies that the parameter is used either as a flag, or does not have
a set of predefined values. The accompanying RFC should provide more
information on the semantics of the parameter.
4. IANA Considerations
The specification creates a new IANA registry named "tel URI
Parameters".
4.1 tel URI Parameters Registry
New tel URI parameters and new values for existing tel URI parameters
MUST be registered by IANA.
When registering a new tel URI parameter the following information
MUST be provided:
o Name of the parameter.
o Whether the parameter only accepts a set of predefined values.
o Reference to the RFC defining the parameter and to any RFC that
defines new values for the parameter.
When registering a new value for an existing tel URI parameter the
following information MUST be provided:
o Name of the parameter.
o Reference to the RFC providing the new value.
Note to IANA editor: When a new value for an existing tel URI
parameter is standardized, the Reference column of Table 1 (below)
corresponding to the parameter name must be updated to include the
new RFC number.
Table 1 contains the initial values for this registry.
Jennings & Gurbani Expires June 8, 2007 [Page 4]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
Parameter Name Predefined Values Reference
-------------- ----------------- ---------
isub Yes [RFC 3966]
isub-encoding Yes [RFC 4715]
ext Yes [RFC 3966]
phone-context Yes [RFC 3966]
enumdi No [RFC AAAA]
npdi No [RFC 4694]
rn Yes [RFC 4694]
rn-context Yes [RFC 4694]
cic Yes [RFC 4694]
cic-context Yes [RFC 4694]
tgrp Yes [RFC CCCC]
trunk-context Yes [RFC CCCC]
Table 1: IANA tel URI parameter registry
Note to RFC Editor: Please replace AAAA with the RFC number for [7].
Please replace CCCC with the RFC number for [5].
4.2 Registration Policy for tel URI Parameters
As per the terminology in RFC 2434 [4], the registration policy for
tel URI parameters shall be "Standards Action". For the purposes of
this registry, the parameter for which IANA registration is requested
MUST be defined by a standards-track RFC.
5. Security Considerations
The registry in this document does not in itself have security
considerations. However, as mentioned in RFC 3427 [2], an important
reason for the IETF to manage the extensions of SIP is to ensure that
all extensions and parameters are able to provide secure usage. The
supporting RFC publications for parameter registrations described
this specification MUST provide detailed security considerations for
them.
6. Acknowledgments
The bulk of this document comes from RFC 3969 [8] written by Gonzalo
Camarillo. Jonathan Rosenberg provided substantive comments that
have improved this document.
7. References
Jennings & Gurbani Expires June 8, 2007 [Page 5]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
7.1 Normative References
[1] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966,
December 2004.
[2] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J., and B.
Rosen, "Change Process for the Session Initiation Protocol
(SIP)", RFC 3427, December 2002.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[4] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[5] Jennings, C. and V. Gurbani, "Representing trunk groups in tel/
sip Uniform Resource Identifiers (URIs)",
draft-ietf-iptel-trunk-group-09 (work in progress),
December 2005.
[6] Yu, J., "New Parameters for the "tel" URI to Support Number
Portability", draft-ietf-iptel-tel-np-09 (work in progress),
July 2005.
[7] Stastny, R., "The ENUM Dip Indicator parameter for the "tel"
URI", draft-ietf-iptel-tel-enumdi-05 (work in progress),
April 2005.
7.2 Informative References
[8] Camarillo, G., "The Internet Assigned Number Authority (IANA)
Uniform Resource Identifier (URI) Parameter Registry for the
Session Initiation Protocol (SIP)", BCP 99, RFC 3969,
December 2004.
Authors' Addresses
Cullen Jennings
Cisco Systems
170 West Tasman Drive
Mailstop SJC-21/2
San Jose, CA 95134
USA
Phone: +1 408 902-3341
Email: fluffy@cisco.com
Jennings & Gurbani Expires June 8, 2007 [Page 6]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
Vijay K. Gurbani
Alcatel-Lucent
2701 Lucent Lane
Room 9F-546
Lisle, IL 60532
USA
Phone: +1 630 224-0216
Email: vkg@alcatel-lucent.com
Jennings & Gurbani Expires June 8, 2007 [Page 7]
Internet-Draft IANA Registry for TEL URI Parameters December 2006
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Jennings & Gurbani Expires June 8, 2007 [Page 8]
Html markup produced by rfcmarkup 1.127, available from
https://tools.ietf.org/tools/rfcmarkup/