Telephone Number Mapping E. Guy Internet-Draft CleverSpoke Intended status: Informational K. Darilion Expires: August 25, 2011 nic.at February 21, 2011 IANA Registration for Enumservice 'iax' draft-ietf-enum-iax-09 Abstract [Note for RFC-Editor: Please replace any instance of RFC XXXX with the RFC number of draft-ietf-enum-enumservices-guide before publication] This document registers an Enumservice for the IAX protocol according to the guidelines given in RFC XXXX. 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 August 25, 2011. Copyright Notice Copyright (c) 2011 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 Guy & Darilion Expires August 25, 2011 [Page 1] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 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 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 . . . . . . . . . . . . . . . . . . . . . . 3 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Simple IAX URI . . . . . . . . . . . . . . . . . . . . . . 5 3.2. IAX URI with a context . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. DNS Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 8. Draft Changes . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Changes since draft-ietf-enum-iax-08 . . . . . . . . . . . 6 8.2. Changes since draft-ietf-enum-iax-07 . . . . . . . . . . . 6 8.3. Changes since draft-ietf-enum-iax-06 . . . . . . . . . . . 7 8.4. Changes since draft-ietf-enum-iax-05 . . . . . . . . . . . 8 8.5. Changes since draft-ietf-enum-iax-04 . . . . . . . . . . . 8 8.6. Changes since draft-ietf-enum-iax-03 . . . . . . . . . . . 8 8.7. Changes since draft-ietf-enum-iax-02 . . . . . . . . . . . 9 8.8. Changes since draft-ietf-enum-iax-01 . . . . . . . . . . . 9 8.9. Changes since draft-guy-iaxenum-00 . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Guy & Darilion Expires August 25, 2011 [Page 2] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 1. Introduction The E.164 to Uniform Resource Identifiers (URI) [RFC3986] Dynamic Delegation Discovery System (DDDS) Application (ENUM) [I-D.ietf-enum-3761bis] transforms E.164 [E164] numbers into Uniform Resource Identifiers (URIs) using the Domain Name System (DNS) [RFC1035]. 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. This document registers an Enumservice for the IAX [RFC5456] protocol according to the guidelines given in draft-ietf-enum-enumservices-guide [I-D.ietf-enum-enumservices-guide]. 2. IANA Registration [Note for RFC-Editor: Please replace any instance of rfcTHIS with the RFC number of this document before publication] Guy & Darilion Expires August 25, 2011 [Page 3] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 Protocol-Based iax iax The 'iax' Enumservice is used to map E.164 numbers to IAX URIs. Such URIs identify resources capable of being contacted to provide a communication session using the IAX protocol . A client selecting this NAPTR needs to be able to support communication 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 3. Examples The following examples are just for illustrative purposes and will in no way limit the usage of the 'iax' Enumservice to other usage scenarios. Guy & Darilion Expires August 25, 2011 [Page 4] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 3.1. Simple IAX URI The following NAPTR resource record is an example of the 'iax' Enumservice. $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/alice!" . ) This contact information indicates that the party addressed by the E.164 number +442079460148 can be contacted using the IAX protocol to domain 'example.com'. The called party, service, or program on that domain is identified by 'alice'. 3.2. IAX URI with a context The following is an example of the 'iax' Enumservice using an IPv6 destination address and 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:[2001:db8::1]:4569/alice?friends!" . ) This NAPTR resource record indicates that +442079460149 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'. For further usage of IAX URIs see Section 2 of [RFC5456]. 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 [RFC3833]. The use of DNSSEC [RFC4033] is recommended to improve operational security. 5. IANA Considerations This document requests registration of the 'iax' Enumservice according to the guidelines and specifications in Guy & Darilion Expires August 25, 2011 [Page 5] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 draft-ietf-enum-enumservices-guide [I-D.ietf-enum-enumservices-guide] and the definitions in Section 2 in this document. 6. DNS Considerations 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. 7. Acknowledgments This work was supported by Internet Foundation Austria. In addition, thanks to Michael Haberler, Bernie Hoeneisen and Richard Stastny for their support and guidance in writing this document. 8. Draft Changes [Note to RFC-Editor: This section is to be removed before publishing. XML source is available upon request.] 8.1. Changes since draft-ietf-enum-iax-08 * KD: Changed the wording of the functionalspec 8.2. Changes since draft-ietf-enum-iax-07 * KD: Changed DNSSEC reference from RFC4035 to RFC4033, which gives an overview about DNSSEC * KD: in first example renamed "chas" to "alice" as it is IMO a more common and meaningful used term in examples * KD: Removed the example with priorities (this RFC is about the Enumservice registration and not about ENUM itself). Remove the example with the context as the IPv6 example also uses a context. Changed description and title of remaining examples. * KD: Added introducery text to Examples section * KD: DNS considerations: removed reference to SIP ENUM RFC as the SIP ENUM RFC does not have a DNS Consideration section. * KD: ordered names in acknowledge section alphabetical Guy & Darilion Expires August 25, 2011 [Page 6] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 * KD: removed RFC3762 and RFC3764 from references, as they are not referenced in the text 8.3. Changes since draft-ietf-enum-iax-06 * KD: Changed title from "IANA Registration for IAX Enumservice" to "IANA Registration for Enumservice 'iax'" as the service type is in small letters * KD: Changed introduction (ENUM maps to URIs, not domains) - used wording from Enumservices draft [I-D.ietf-enum-enumservices-guide]. * KD: Changed introduction: shortened IAX description - this RFC is not about IAX but about the ENUM service. * KD: Changed introduction: shortend description (the service field actually does not describe the class of functionality, but is mostly a pointer to supported communication protocols) * KD: Use the same wording in abstract and introduction: The Enumservice is not IAX but iax, thus used different wording. * KD: Fixed double-spaces * KD: IANA Registration: changed functional description: fixed wording, use 'communication' instead of 'call origination' * KD: IANA Registration: remove reference to URI registry (no clean way to reference) and moved reference to [RFC5456] one paragraph up * KD: Todo: Fix references "thisRFC" in IANA Registration * KD: Registration with multiple priorities: write "SIP", "H323" for the tokens, instead of "sip", "h323" and add 'mailto' to the protocols * KD: Examples: replaced "This contact information indicates that the domain 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted" with "This contact information indicates that +442079460149 may be contacted" as a domain is not contacted (although the previous text was from the ENUM RFC) * KD: Examples: Write IPv6 address in text without [] as the port is mentioned separately * KD: IANA Considerations: removed the sub-type as we do not register a sub-type Guy & Darilion Expires August 25, 2011 [Page 7] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 * KD: DNS Considerations: removed "Since IAX is typically deployed in a proxy configuration" as there is no "proxy" configuration in IAX * KD: DNS Considerations: removed reference to [RFC4759] as IMO it does not solve the loop problem on DNS changes and chached data (it does not even contain the word 'loop') * KD: Security Considerations: removed reference to RFC 4035 regarding "unwanted communication" as DNSSEC is here not relevant. * KD: as suggested by Bernie: fixed references to RFC3761bis and draft-ietf-enum-enumservices-guide * KD: as suggested by Bernie: verified that all example numbers are UK drama numbers (http://stakeholders.ofcom.org.uk/telecoms/ numbering/guidance-tele-no/numbers-for-drama) and 2001:db8::1 is a "documentation" IPv6 address * KD: as suggested by Bernie: replaced "Editor" with "RFC-Editor" * KD: Acknowledgments: added Bernie 8.4. 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. 8.5. 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.6. Changes since draft-ietf-enum-iax-03 * Removed version number '2' from scheme name. * IDNITS: removed terminology section. Guy & Darilion Expires August 25, 2011 [Page 8] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 * Various rewordings per Alex Mayrhofer and idnits review. * Added E2U+email:mailto example to match text, 8.7. Changes since draft-ietf-enum-iax-02 * Clarifications suggested by Peter Koch. 8.8. 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.9. 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 9.1. Normative References [I-D.ietf-enum-3761bis] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", draft-ietf-enum-3761bis-09 (work in progress), June 2010. [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. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Guy & Darilion Expires August 25, 2011 [Page 9] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 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. [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987. [RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name System (DNS)", RFC 3833, August 2004. [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "DNS Security Introduction and Requirements", RFC 4033, March 2005. [RFC4759] Stastny, R., Shockey, R., and L. Conroy, "The ENUM Dip Indicator Parameter for the "tel" URI", RFC 4759, December 2006. Authors' Addresses 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 & Darilion Expires August 25, 2011 [Page 10] Internet-Draft IANA Registration for Enumservice 'iax' February 2011 Klaus Darilion nic.at Karlsplatz 1/2/9 1010 Wien Austria Phone: +43 1 5056416 36 Email: klaus.darilion@nic.at URI: http://www.nic.at/ Guy & Darilion Expires August 25, 2011 [Page 11]