Telephone Number Mapping E. Guy Internet-Draft E-MC Software Expires: April 20, 2006 October 17, 2005 IANA Registration for IAX Enumservice draft-guy-enumiax-00 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 20, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document registers the IAX2 Enumservice using the URI scheme 'iax2:' as per the IANA registration process defined in the ENUM specification RFC3761. Guy Expires April 20, 2006 [Page 1] Internet-Draft IANA Registration for IAX Enumservice October 2005 Table of Contents 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. IAX2 Service Registration . . . . . . . . . . . . . . . . . . 5 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 Intellectual Property and Copyright Statements . . . . . . . . . . 11 Guy Expires April 20, 2006 [Page 2] Internet-Draft IANA Registration for IAX Enumservice October 2005 1. 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 [RFC2119]. Guy Expires April 20, 2006 [Page 3] Internet-Draft IANA Registration for IAX Enumservice October 2005 2. Introduction The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) [RFC3761] transforms E.164 [E164] numbers into DNS names and the use of DNS services like delegation through NS records, and use of NAPTR records in DNS. Using this system, one can look up what services are available for a specific domain name in a decentralized way with distributed management of the different levels in the lookup process. IAX [ID-IAX] is an "all in one" protocol for handling streaming media in Internet Protocol (IP) networks. IAX combines both control and media services in the same stream which decreases bandwidth usage and allows for Network Address Translation (NAT) transparency. These design decisions have made IAX accel at handling Internet telephony. The 'iax2:' URI scheme is also defined in the IAX protocol document. This document registers the IAX2 Enumservice according to the guidelines given in RFC3761 [RFC3761] to be used for provisioning in the services field of a NAPTR resource record to indicate what class of functionality a given end point offers. The registration is defined within the DDDS (Dynamic Delegation Discovery System [RFC3401] [RFC3402] [RFC3403] [RFC3404] ) hierarchy, for use with the "E2U" DDDS Application defined in RFC3761. [RFC3761] Guy Expires April 20, 2006 [Page 4] Internet-Draft IANA Registration for IAX Enumservice October 2005 3. IAX2 Service Registration Enumservice Name: "IAX2" Enumservice Type: "iax" Enumservice Subtype: N/A URI Scheme: "iax2:" Functional Specification: The IAX2 Enumservice indicates that the resource identified by the associated URI scheme is capable of being contacted using the IAX2 protocol to provide a communication session. A client selecting this NAPTR will have support for originating a call utilizing the IAX2 protocol [ID-IAX]. Security Considerations: There are no specific security issues with this Enumservice. However, the general considerations of Section 5 apply. Intended Usage: COMMON Author: Ed Guy (For contact detail, see the Authors' Address section below) Any other information the author deems interesting: None Guy Expires April 20, 2006 [Page 5] Internet-Draft IANA Registration for IAX Enumservice October 2005 4. Examples The following is an example of the use of the enumservice registered by this document in a NAPTR resource record. $ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. @ IN NAPTR 10 100 "u" "E2U+iax" "!^.*$!iax2:example.com/charlie!" The next example demonstrates that the domain 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. is preferably contacted by IAX2, secondly via SIP, and then H.323 for voice, and lastly by SMTP for messaging. Note that the tokens "iax", "sip", "h323", and "msg" are Types registered (or to be registered) with IANA, and they have no implicit connection with the protocols or URI schemes with the same names. In each case, the next step in the resolution process is to use the resolution mechanism appropriate to each of the protocols, (specified by the URI schemes iax, sip, h323 and mailto). $ORIGIN 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. @ IN NAPTR 10 100 "u" "E2U+iax" "!^.*$!iax2:example.com/mccarthy!" . @ IN NAPTR 10 101 "u" "E2U+sip" "!^.*$!sip:mccarthy@example.com!" . @ IN NAPTR 10 101 "u" "E2U+h323" "!^.*$!h323:mccarthy@example.com!" . @ IN NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:mccarthy@example.com!" . Guy Expires April 20, 2006 [Page 6] Internet-Draft IANA Registration for IAX Enumservice October 2005 5. Security Considerations The IAX Enumservice does not introduce any new security issues beyond any already present in the DNS and IAX protocols except that this Enumservice provides another fact that may be harvested and possibly exploited. The use of DNSSEC [RFC2535] is recommended to improve operational security. Guy Expires April 20, 2006 [Page 7] Internet-Draft IANA Registration for IAX Enumservice October 2005 6. IANA Considerations This document requests registration of the "iax" Enumservice with no sub-types according to the guidelines and specifications in RFC 3761 [RFC3761] and the definitions in this document. Guy Expires April 20, 2006 [Page 8] Internet-Draft IANA Registration for IAX Enumservice October 2005 7. Acknowledgements Thanks to Michael Haberler and Richard Stastny for their support and guidance in writing this document. 8. References [E164] ITU-T, "The International Public Telecommunication Number Plan", Recommendation E.164, May 1997. [ID-IAX] Spencer, M., Shumard, K., Capouch, B., and E. Guy, "IAX: Inter-Asterisk eXchange Version 2", Work In Progress, November 2005. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2535] Eastlake, D., "Domain Name System Security Extensions", RFC 2535, March 1999. [RFC3401] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS", RFC 3401, October 2002. [RFC3402] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm", RFC 3402, October 2002. [RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002. [RFC3404] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)", RFC 3404, October 2002. [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004. Guy Expires April 20, 2006 [Page 9] Internet-Draft IANA Registration for IAX Enumservice October 2005 Author's Address Ed Guy E-MC Software 235 Main Street, STE 253 Madison, NJ 07940 US Phone: +1 973 437 4519 Email: edguy@emcsw.com URI: http://www.emcsw.com/ Guy Expires April 20, 2006 [Page 10] Internet-Draft IANA Registration for IAX Enumservice October 2005 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 (2005). 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. Guy Expires April 20, 2006 [Page 11]