[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] [IPR]

Versions: (draft-guy-enumiax) 00 01 02 03 04 05 06 07 08 09 10 RFC 6315

Telephone Number Mapping                                          E. Guy
Internet-Draft                                                  TruPhone
Intended status: Standards Track                               June 2007
Expires: December 3, 2007


                 IANA Registration for IAX Enumservice
                         draft-ietf-enum-iax-03

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 3, 2007.

Copyright Notice

   Copyright (C) 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.








Guy                     Expires December 3, 2007                [Page 1]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


Table of Contents

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





























Guy                     Expires December 3, 2007                [Page 2]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


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


2.  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.
   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].  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] [RFC3402] [RFC3403] [RFC3404] ) hierarchy,
   for use with the "E2U" DDDS Application defined in RFC3761.
   [RFC3761]


3.  IAX Service Registration

   Enumservice Name:  "IAX"
   Enumservice Type:  "iax"
   Enumservice Subtype:  iax2
   URI Scheme:  "iax2"







Guy                     Expires December 3, 2007                [Page 3]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


   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 needs to be able to support call
      origination 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.


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

   This contact information indicates that service identified by the
   "+442079460148" E.164 number can be accessed using the IAX2 protocol
   to domain 'example.com.' with the identifier 'chas'.

4.2.  Registration with Multiple Priorities

   The next example demonstrates that service identified by the
   "+441632960083" E.164 number is preferably accessed by IAX2, secondly
   via SIP [RFC3764] , and then H.323 [RFC3764] for voice, and lastly by
   SMTP for messaging.  Note that the tokens "iax", "sip", and "h323"
   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.




Guy                     Expires December 3, 2007                [Page 4]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


   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 iax2, 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" "!^.*$!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!" .

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 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: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 4569 with 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 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] and RFC



Guy                     Expires December 3, 2007                [Page 5]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


   3822 [RFC3833].

   The use of DNSSEC [RFC4035] 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] 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-02

   * Clarifications suggested by Peter Koch.

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



Guy                     Expires December 3, 2007                [Page 6]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


   * Context example added.


9.  References

9.1.  Normative 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, "IAX2:
              Inter-Asterisk eXchange Version 2", draft-guy-iax-03 Work
              In Progress, October 2006.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

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

9.2.  Informative References

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

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, January 2005.




Guy                     Expires December 3, 2007                [Page 7]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


   [RFC4035]  Arends, R., Austein, R., Larson, M., Massey, D., and S.
              Rose, "Protocol Modifications for the DNS Security
              Extensions", RFC 4035, March 2005.


Author's Address

   Ed Guy
   TruPhone
   235 Main Street, STE 253
   Madison, NJ  07940
   US

   Phone: +1 973 437 4519
   Email: edguy@emcsw.com
   URI:   http://www.TruPhone.com/



































Guy                     Expires December 3, 2007                [Page 8]

Internet-Draft    IANA Registration for IAX Enumservice        June 2007


Full Copyright Statement

   Copyright (C) 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).





Guy                     Expires December 3, 2007                [Page 9]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/