IANA Registration for IAX Enumservice
draft-ietf-enum-iax-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 October 18, 2007.

Copyright Notice

Copyright © The IETF Trust (2007).

Abstract

This document registers the IAX2 (Inter-Asterisk eXchange Version 2) Enumservice using the URI scheme 'iax2:' as per the IANA registration process defined in the ENUM specification RFC3761.

Table of Contents

1.  Terminology
2.  Introduction
3.  IAX Service Registration
4.  Examples
    4.1.  Simple IAX Registration
    4.2.  Registration with Preference Order
    4.3.  Registration with an IAX context
    4.4.  IPv6 Registration
5.  Security Considerations
6.  IANA Considerations
7.  Acknowledgments
8.  Draft Changes
    8.1.  Changes since draft-ietf-enum-iax-01
    8.2.  Changes since draft-guy-iaxenum-00
9.  References
    9.1.  Normative References
    9.2.  Informative References
§  Author's Address
§  Intellectual Property and Copyright Statements

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] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

2.  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. This is accomplished in a decentralized manner with distributed management of the different levels in the lookup process.

IAX2 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, IAX2 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. IAX2 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. The registration is defined within the DDDS (Dynamic Delegation Discovery System [RFC3401] (Mealling, M., “Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS,” October 2002.) [RFC3402] (Mealling, M., “Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm,” October 2002.) [RFC3403] (Mealling, M., “Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database,” October 2002.) [RFC3404] (Mealling, M., “Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI),” October 2002.) ) hierarchy, for use with the "E2U" DDDS Application defined 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.)

3.  IAX Service Registration

Enumservice Name:

"IAX"

Enumservice Type:

"iax"

Enumservice Subtype:

iax2

URI Scheme:

"iax2"

Functional Specification:

The IAX Enumservice indicates that the resource identified by the associated URI scheme http://www.iana.org/assignments/uri-schemes/prov/iax2 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] (Spencer, M., Shumard, K., Capouch, B., and E. Guy, “IAX2: Inter-Asterisk eXchange Version 2,” October 2006.).

Security Considerations:

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

Intended Usage:

COMMON

Author:

Ed Guy (For contact detail, see the Authors' Address section below).

Any other information the author deems interesting:

None.

4.  Examples

4.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:iax2" "!^.*$!iax2:example.com/charlie!"

This contact information indicates that the domain 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX2 protocol at domain 'example.com' with the identifier 'charlie'.

4.2.  Registration with Preference Order

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!" .

4.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:iax2" "!^.*$!iax2: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 IAX2 protocol at domain 'example.com' with the identifier 'joe' in the context (or user partition) 'developers'.

4.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 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:iax2" "!^.*$!iax2:[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 IAX2 protocol at IPv6 address [2001:db8::1], port 4569with the identifier 'alice' in the context (or user partition) 'friends'.

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] (Eastlake, D., “Domain Name System Security Extensions,” March 1999.) is recommended to improve operational security.

6.  IANA Considerations

This document requests registration of the "iax" Enumservice with the 'iax2' 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 this document.

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-01

* Add reference to provisionally registered URI scheme.

* Separate normative and informative references.

* Minor grammatical edits.

* Added the IPv6 Example.

* Updated References.

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

9.2. Informative References

Author's Address

Full Copyright Statement

Copyright © 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).