Telephone Number Mapping E. Guy Internet-Draft CleverSpoke Intended status: Informational November 8, 2010 Expires: May 12, 2011 IANA Registration for IAX Enumservice draft-ietf-enum-iax-06 Abstract This document registers the IAX Enumservice using the URI scheme 'iax:' as per the IANA registration process defined in the ENUM specification RFC3761. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on May 12, 2011. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Guy Expires May 12, 2011 [Page 1] Internet-Draft IANA Registration for IAX Enumservice November 2010 Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. IANA Registration . . . . . . . . . . . . . . . . . . . . . . . 4 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Simple IAX Registration . . . . . . . . . . . . . . . . . . 5 3.2. Registration with Multiple Priorities . . . . . . . . . . . 5 3.3. Registration with an IAX context . . . . . . . . . . . . . 6 3.4. IPv6 Registration . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 6. DNS Considerations . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Draft Changes . . . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Changes since draft-ietf-enum-iax-05 . . . . . . . . . . . 7 8.2. Changes since draft-ietf-enum-iax-04 . . . . . . . . . . . 8 8.3. Changes since draft-ietf-enum-iax-03 . . . . . . . . . . . 8 8.4. Changes since draft-ietf-enum-iax-02 . . . . . . . . . . . 8 8.5. Changes since draft-ietf-enum-iax-01 . . . . . . . . . . . 8 8.6. Changes since draft-guy-iaxenum-00 . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Guy Expires May 12, 2011 [Page 2] Internet-Draft IANA Registration for IAX Enumservice November 2010 1. Introduction The E.164 to Uniform Resource Identifiers (URI) [RFC3986] Dynamic Delegation Discovery System (DDDS) Application (ENUM) [RFC3761] transforms E.164 [E164] numbers into DNS names. Then, using DNS services like delegation through NS records and NAPTR records, one can look up what services are available for a specific domain name. IAX (Inter-Asterisk eXchange) [RFC5456] is an "all in one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol. In addition, IAX uses a single UDP data stream on a static port greatly simplifying Network Address Translation (NAT) gateway traversal, eliminating the need for other protocols to work around NAT, and simplifying network and firewall management. IAX employs a compact encoding which decreases bandwidth usage and is well suited for Internet telephony service. In addition, its open nature permits new payload types additions needed to support additional services. This document registers the IAX Enumservice according to the guidelines given in RFC3761 [RFC3761]. The IAX Enumservice is used in provisioning the services field of a NAPTR resource record. This field indicates what class of functionality a given end point offers. Guy Expires May 12, 2011 [Page 3] Internet-Draft IANA Registration for IAX Enumservice November 2010 2. IANA Registration Protocol-Based iax iax The IAX Enumservice indicates that the resource identified by the associated URI scheme < http://www.iana.org/assignments/uri-schemes/prov/iax" /> is capable of being contacted using the IAX protocol to provide a communication session. A client selecting this NAPTR needs to be able to support call origination utilizing the IAX protocol . There are no specific security issues with this Enumservice. However, the general considerations of Section 4 apply. COMMON Ed Guy CleverSpoke, Inc mailto:edguy@CleverSpoke.com 2010-11-01 Guy Expires May 12, 2011 [Page 4] Internet-Draft IANA Registration for IAX Enumservice November 2010 3. Examples 3.1. Simple IAX Registration 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" "!^.*$!iax:example.com/chas!" . ) This contact information indicates that service identified by the "+442079460148" E.164 number can be accessed using the IAX protocol to domain 'example.com.' The called party, service, or program on that domain is identified by 'chas'. 3.2. Registration with Multiple Priorities The next example demonstrates that service identified by the "+441632960083" E.164 number is preferably accessed by IAX, secondly via SIP [RFC3764] , and then H.323 [RFC3762] for voice and general commmunication, and lastly by SMTP for messaging. Note that the tokens "iax", "sip", "h323", and "email" are types 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, and h323). $ORIGIN 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. @ IN NAPTR ( 10 100 "u" "E2U+iax" "!^.*$!iax:example.com/mccarthy!" . ) @ IN NAPTR ( 10 101 "u" "E2U+SIP" "!^.*$!sip:mccarthy@example.com!" . ) @ IN NAPTR ( 10 102 "u" "E2U+H323" "!^.*$!h323:mccarthy@example.com!" . ) @ IN NAPTR ( 10 103 "u" "E2U+email:mailto" "!^.*$!mailto:mccarthy@example.com!" . ) Guy Expires May 12, 2011 [Page 5] Internet-Draft IANA Registration for IAX Enumservice November 2010 3.3. Registration with an IAX context The following is an example of the use of the Enumservice registered by this document in a NAPTR resource record that contains a destination 'context'. $ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. @ IN NAPTR ( 10 100 "u" "E2U+iax" "!^.*$!iax:example.com/joe?developers!" ) This contact information indicates that the domain 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX protocol at domain 'example.com' with the called party 'joe' in the context (or user partition) 'developers'. See Section Section 2 of [RFC5456]. 3.4. IPv6 Registration The following is an example of the use of the Enumservice registered by this document in a NAPTR resource record that contains an IPV6 destination address. $ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. @ IN NAPTR ( 10 100 "u" "E2U+iax" "!^.*$!iax:[2001:db8::1]:4569/alice?friends!" . ) This contact information indicates that the domain 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX protocol at IPv6 address [2001:db8::1], port 4569 with the called party 'alice' in the context (or user partition) 'friends'. 4. Security Considerations The IAX Enumservice does not introduce any new security issues beyond any already present in the ENUM, DNS and IAX protocols except that this Enumservice provides for disclosure of information that may facilitate an attack or a violation of user privacy in some way. The primary result of these exploits is unwanted communications. These issues are discussed in further detail in RFC 4035 [RFC4035] and RFC 3833 [RFC3833]. The use of DNSSEC [RFC4035] is recommended to improve operational security. Guy Expires May 12, 2011 [Page 6] Internet-Draft IANA Registration for IAX Enumservice November 2010 5. IANA Considerations This document requests registration of the "iax" Enumservice with the 'iax' sub-type according to the guidelines and specifications in RFC 3761bis [I-D.ietf-enum-enumservices-guide] and the definitions in Section 2 in this document. 6. DNS Considerations DNS considerations related to the IAX Enumservice are similar to those of the SIP enumservice. Since IAX is typically deployed in a proxy configuration, misconfiguration or delays in zone changes can result in call loops, perhaps with different protocols or networks. Implementations should take care to ensure such loops can be detected without interrupting other services including SIP-based, IAX-based, and DNS itself. [RFC4759] provides an example of a loop mitigation mechanism. 7. Acknowledgments This work was supported by Internet Foundation Austria. In addition, thanks to Michael Haberler and Richard Stastny for their support and guidance in writing this document. 8. Draft Changes [Note to Editor: This section is to be removed before publishing. Xml source is available upon request.] 8.1. Changes since draft-ietf-enum-iax-05 * Changed to be compatible with [I-D.ietf-enum-enumservices-guide]. * Added DNS Considerations section. * Per Dan Harkin's review, improved language in security considerations section and fixed typo. * Per Peter Koch's review, change DNS continuation character from \ to ( ) form. Guy Expires May 12, 2011 [Page 7] Internet-Draft IANA Registration for IAX Enumservice November 2010 8.2. Changes since draft-ietf-enum-iax-04 * Removed the 'iax2' subtype per AD request. * Change from standards track to informational track. * Added citation to second paragraph. 8.3. Changes since draft-ietf-enum-iax-03 * Removed version number '2' from scheme name. * IDNITS: removed terminology section. * Various rewordings per Alex Mayrhofer and idnits review. * Added E2U+email:mailto example to match text, 8.4. Changes since draft-ietf-enum-iax-02 * Clarifications suggested by Peter Koch. 8.5. Changes since draft-ietf-enum-iax-01 * Add reference to provisionally registered URI scheme. * Separate normative and informative references. * Minor grammatical edits. * Added the IPv6 Example. * Updated References. 8.6. Changes since draft-guy-iaxenum-00 * Minor grammatical edits. * Added the 'iax2' subtype at WG request. * The Examples section was split into subsections for each example. * Context example added. 9. References Guy Expires May 12, 2011 [Page 8] Internet-Draft IANA Registration for IAX Enumservice November 2010 9.1. Normative References [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. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC5456] Spencer, M., Capouch, B., Guy, E., Miller, F., and K. Shumard, "IAX: Inter-Asterisk eXchange Version 2", RFC 5456, February 2010. 9.2. Informative References [E164] ITU-T, "The International Public Telecommunication Number Plan", Recommendation E.164, May 1997. [I-D.ietf-enum-enumservices-guide] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA Registration of Enumservices: Guide, Template and IANA Considerations", draft-ietf-enum-enumservices-guide-22 (work in progress), October 2010. [RFC3762] Levin, O., "Telephone Number Mapping (ENUM) Service Registration for H.323", RFC 3762, April 2004. [RFC3764] Peterson, J., "enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record", RFC 3764, April 2004. [RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name System (DNS)", RFC 3833, August 2004. [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "Protocol Modifications for the DNS Security Extensions", RFC 4035, March 2005. [RFC4759] Stastny, R., Shockey, R., and L. Conroy, "The ENUM Dip Indicator Parameter for the "tel" URI", RFC 4759, December 2006. Guy Expires May 12, 2011 [Page 9] Internet-Draft IANA Registration for IAX Enumservice November 2010 Author's Address Ed Guy CleverSpoke 12 Williams Road Chatham, NJ 07928 US Phone: +1 973 437 4519 Email: edguy@CleverSpoke.com URI: http://www.cleverspoke.com/ Guy Expires May 12, 2011 [Page 10]