IANA Registration for IAX Enumservice
draft-ietf-enum-iax-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 December 20, 2008.

Abstract

This document registers the IAX Enumservice using the URI scheme 'iax:' as per the IANA registration process defined in the ENUM specification RFC3761.

Table of Contents

1.  Introduction
2.  Enumservice Registration - IAX
3.  Examples
    3.1.  Simple IAX Registration
    3.2.  Registration with Multiple Priorities
    3.3.  Registration with an IAX context
    3.4.  IPv6 Registration
4.  Security Considerations
5.  IANA Considerations
6.  Acknowledgments
7.  Draft Changes
    7.1.  Changes since draft-ietf-enum-iax-03
    7.2.  Changes since draft-ietf-enum-iax-02
    7.3.  Changes since draft-ietf-enum-iax-01
    7.4.  Changes since draft-guy-iaxenum-00
8.  References
    8.1.  Normative References
    8.2.  Informative References
§  Author's Address
§  Intellectual Property and Copyright Statements

1.  Introduction

The E.164 to Uniform Resource Identifiers (URI) [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.) Dynamic Delegation Discovery System (DDDS) Application (ENUM) [RFC3761] (Faltstrom, P. and M. Mealling, “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM),” April 2004.) transforms E.164 [E164] (ITU-T, “The International Public Telecommunication Number Plan,” May 1997.) 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) 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] (Faltstrom, P. and M. Mealling, “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM),” April 2004.). 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.

2.  Enumservice Registration - IAX

Enumservice Name: "IAX"

Enumservice Type: "iax"

Enumservice Subtype: "iax"

URI Scheme: "iax"

Functional Specification:

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 [ID‑IAX] (Spencer, M., Shumard, K., Capouch, B., and E. Guy, “IAX: Inter-Asterisk eXchange Version 2,” October 2006.).

Security Considerations:

There are no specific security issues with this Enumservice. However, the general considerations of Section 4 (Security Considerations) apply.

Intended Usage: COMMON

Author: Ed Guy <edguy@emcsw.com>

Any other information the author deems interesting: None.

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" \
               "!^.*$!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] (Peterson, J., “enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record,” April 2004.) , and then H.323 [RFC3762] (Levin, O., “Telephone Number Mapping (ENUM) Service Registration for H.323,” April 2004.) 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"     \
              "!^.*$!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!" .

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"    \
               "!^.*$!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 [ID‑IAX] (Spencer, M., Shumard, K., Capouch, B., and E. Guy, “IAX: Inter-Asterisk eXchange Version 2,” October 2006.).

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"    \
               "!^.*$!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 another fact, visible to anyone anonymously, that may be harvested and possibly exploited. The primary result of these exploits is unwanted communications. These issues are discussed in further detail in RFC 4035 [RFC4035] (Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, “Protocol Modifications for the DNS Security Extensions,” March 2005.) and RFC 3822 [RFC3833] (Atkins, D. and R. Austein, “Threat Analysis of the Domain Name System (DNS),” August 2004.).

The use of DNSSEC [RFC4035] (Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, “Protocol Modifications for the DNS Security Extensions,” March 2005.) is recommended to improve operational security.

5.  IANA Considerations

This document requests registration of the "iax" Enumservice with the 'iax' sub-type according to the guidelines and specifications in RFC 3761 [RFC3761] (Faltstrom, P. and M. Mealling, “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM),” April 2004.) and the definitions in Section 2 (Enumservice Registration - IAX) in this document.

6.  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.

7.  Draft Changes

[Note to Editor: This section is to be removed before publishing. Xml source is available upon request.]

7.1.  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,

7.2.  Changes since draft-ietf-enum-iax-02

* Clarifications suggested by Peter Koch.

7.3.  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.

7.4.  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.

8.  References

8.1. Normative References

8.2. Informative References

Author's Address

Full Copyright Statement

Copyright © The IETF Trust (2008).

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.