ENUM -- Telephone Number Mapping B. Hoeneisen Working Group Switch Internet-Draft Oct 22, 2007 Expires: April 24, 2008 Registration of Enumservices for experimental, private or trial use draft-hoeneisen-enum-x-service-regs-02 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 April 24, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. Hoeneisen Expires April 24, 2008 [Page 1] Internet-Draft X-Enumservice Registrations Oct 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Required Sections and Information . . . . . . . . . . . . . . . 3 4. Expert Review . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . . 6 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 8 Hoeneisen Expires April 24, 2008 [Page 2] Internet-Draft X-Enumservice Registrations Oct 2007 1. Introduction This document provides a guide to the creation of new IANA registrations of X-Enumservices. This document aims to enhance section 3 of RFC 3761 [2], where the registration procedure for Enumservices was initially documented at a high level. It further complements the Guide and Template for IANA Registrations of Enumservices [3]. The X-Enumservice registration is intended to allow people to use the normal Enumservice template to describe what X-Enumservice strings exist in NAPTR Resource Records and to describe how they are used, but not (yet) to require a full IETF review and change control. This is needed as some trials use URL schemes that are not registered, and so cannot be used in Standards Track Enumservice registrations. Also, until trials have been completed, it may not be appropriate to produce a Standards Track document, as Enumservice syntax details, use and issues of security / privacy may not have been analyzed fully at that point. For the purpose of this document, 'registration document' and 'registration' refers to an Internet Draft proposing the IANA registration of an X-Enumservice following the procedures outlined above. 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 [1]. 3. Required Sections and Information A document for registration of an X-Enumservice is similar to a ordinary Enumservice registration as described in Guide and Template for IANA Registrations of Enumservices [3] except for the following: o Enumservice Name: The Enumservice Name MUST contain the prefix "X-". e.g. "X-Foo" Hoeneisen Expires April 24, 2008 [Page 3] Internet-Draft X-Enumservice Registrations Oct 2007 o Enumservice Type: The Type MUST be prefixed with "x-". To avoid confusion a name SHOULD be equal to type (but in lower case). e.g. "x-foo" o URI Schemes: The Uniform Resource Identifier (URI) [5] Schemes, which are used with an X-Enumservice do not necessarily need to be documented in an IETF document. If a publicly referenceable document is available it MUST be referenced in the registration document. In case there is no publicly referenceable document, the URI Scheme MUST be sufficiently described in the registration document. o Functional Specification: This section quite depends on how much publicly available documentation about the service already exists. o Intended Usage: For the Intended Usage RFC 3761 [2] is extended with "EXPERIMENTAL", "PRIVATE", and "TRIAL". One of those is to be used. e.g. "TRIAL" 4. Expert Review A new X-Enumservice MUST undergo Expert Review before publication. This expert review will include an initial evaluation of whether this specification will have issues in transferring to a Standards Track document (for example, if it uses an unregistered URL scheme, or that the security and privacy analysis is incomplete at this stage). It will also indicate whether the use of this X-Enumservice will clash with any other (X-)Enumservices or cause damage to other compliant ENUM components, and should be used only in private configurations where all involved components are aware of its use. The results of such an expert review SHOULD be appended to the registration document and will be recorded along with the specification itself. Hoeneisen Expires April 24, 2008 [Page 4] Internet-Draft X-Enumservice Registrations Oct 2007 However, the exact expert review process is to be defined. This process will be a simplified variant of the process for normal Enumservice registrations [3], which is still under specification. 5. Security Considerations Since this document does not introduce any technology or protocol, there are no security issues to be considered for this memo itself. 6. IANA Considerations This document introduces three new strings for Intended Usage as defined in RFC 3761 [2]. These new strings are: "EXPERIMENTAL", "PRIVATE", and "TRIAL". The revision of RFC 3761 [2] RFC3761bis [4] shall contain these new strings. Furthermore the dash in the 'X-' string needs to be put into the set of allowed characters in an Enumservice Type. In case the revision of RFC 3761 is not yet ready at publication time of this memo, an intermediary regime needs to be defined. An IANA Registry for X-Enumservices is to be defined. 7. Acknowledgements The author wishes to thank Alexander Mayrhofer and Lawrence Conroy for their contributions to this document. 8. References 8.1. Normative References [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [2] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004. [3] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "Guide and Template for IANA Registrations of Enumservices", draft-ietf-enum-enumservices-guide-05 (work in progress), October 2007. [4] Faltstrom, P., "The E.164 to Uniform Resource Identifiers (URI) Hoeneisen Expires April 24, 2008 [Page 5] Internet-Draft X-Enumservice Registrations Oct 2007 Dynamic Delegation Discovery System (DDDS) Application (ENUM)", draft-ietf-enum-3761bis-01 (work in progress), July 2007. 8.2. Informative References [5] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. Appendix A. Changes [RFC Editor: This section is to be removed before publication] draft-ietf-hoeneisen-enum-x-service-regs-02: o Name must have 'X-' prefix (Feedback L. Conroy) o Type should be equal to Name (Feedback L. Conroy) draft-ietf-hoeneisen-enum-x-service-regs-01: o added dash issue o introduced abbreviation X-Enumservice and used it throughout the document o clarified section URI Schemes o added to section Expert Review draft-ietf-hoeneisen-enum-x-service-regs-00: o Initial version Appendix B. Open Issues [RFC Editor: This section should be empty before publication] o Sync with RFC3761bis: e.g. Intended Usage "EXPERIMENTAL", "PRIVATE", and "TRIAL"; dash in 'X-' to allowed chars o Is there a need for "duration of Registration?" o Define process for Expert Review o Will there be an additional (IANA) Registry or just use the same IANA Registy as for ordinary Enumservice registrations? o Require a first Security analysis for trial registrations? Hoeneisen Expires April 24, 2008 [Page 6] Internet-Draft X-Enumservice Registrations Oct 2007 Author's Address Bernie Hoeneisen Switch Werdstrasse 2 CH-8004 Zuerich Switzerland Phone: +41 44 268 1515 Email: hoeneisen@switch.ch, b.hoeneisen@ieee.org URI: http://www.switch.ch/ Hoeneisen Expires April 24, 2008 [Page 7] Internet-Draft X-Enumservice Registrations Oct 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). 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. 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, THE IETF TRUST 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. Intellectual Property 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. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Hoeneisen Expires April 24, 2008 [Page 8]