One document matched: draft-ietf-enum-iax-05.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY rfc2026 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2026.xml'>
    <!ENTITY rfc2535 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2535.xml'>
    <!ENTITY rfc3762 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3762.xml'>
    <!ENTITY rfc3764 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3764.xml'>
    <!ENTITY rfc3978 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3978.xml'>
    <!ENTITY rfc3979 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3979.xml'>
    <!ENTITY rfc3761 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3761.xml'>
    <!ENTITY rfc1034 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml'>
    <!ENTITY rfc3401 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3401.xml'>
    <!ENTITY rfc3402 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3402.xml'>
    <!ENTITY rfc3403 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3403.xml'>
    <!ENTITY rfc3404 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3404.xml'>
    <!ENTITY rfc3986 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml'>
    <!ENTITY rfc4035 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4035.xml'>
    <!ENTITY rfc3833 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3833.xml'>
]>

<!---    < ! ENTITY rfc5456 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5456.xml'> -->


<rfc category="info" ipr="trust200811" docName='draft-ietf-enum-iax-05'>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes" ?>

    <front>
        <title>IANA Registration for IAX Enumservice</title>

<author initials="E.T." surname="Guy" fullname="Ed Guy">
<organization>Truphone</organization>
<address>
<postal>
<street>12 Williams Rd</street>
<city>Chatham</city> <region>NJ</region> <code>07928</code>
<country>US</country>
</postal>
<phone>+1 973 437 4519</phone>
<email>edguy@emcsw.com</email>
<uri>http://www.TruPhone.com/</uri>
</address>
</author>

        <date month="February" year="2009"/>

<!-- <area ...>  "Applications", "General", "Internet", "Management", "Operations", "Routing", "Security", "Transport", or "User" -->
<area>Transport</area>
<workgroup>Telephone Number Mapping</workgroup>
<!-- <keyword ...> -->
<!-- <keyword ...> -->

        <abstract><t>

This document registers the IAX 
Enumservice using the URI scheme 'iax:' as per the IANA
registration process defined in the ENUM specification RFC3761.
	
	</t></abstract>
<!-- <note ...>  -->
    </front>

    <middle>
<section title="Introduction"> 
<t>
The E.164 to Uniform Resource Identifiers (URI) <xref target="RFC3986" />
Dynamic Delegation Discovery System (DDDS) Application (ENUM)
<xref target="RFC3761"/> transforms E.164 <xref target="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.  
<vspace blankLines='1' />
IAX (Inter-Asterisk eXchange) <xref target="ID-IAX" /> 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.
<vspace blankLines='1' />
This document registers the IAX Enumservice according to the guidelines
given in RFC3761 <xref target="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.  
</t> </section>


<section anchor="sec.reg" title="Enumservice Registration - IAX">
<t>
<list style='empty'>
<t> Enumservice Name: "IAX" 
   <vspace blankLines='1' />
</t>
<t> Enumservice Type: "iax" 
   <vspace blankLines='1' />
</t>
<t> URI Scheme: 	"iax" 
   <vspace blankLines='1' />
</t>
<t> Functional Specification: 
  <list style='empty'>
  <t>
   <vspace blankLines='0' />
      The IAX Enumservice indicates that the resource identified by the
      associated URI scheme 
      <!-- TODO EDITOR: UPDATE EREF to Perm -->
      <eref target="http://www.iana.org/assignments/uri-schemes/prov/iax" /> is capable of being contacted using the 
      IAX protocol to provide a
      communication session.
  </t>
  <t>
   <vspace blankLines='0' />
      A client selecting this NAPTR needs to be able to support   
      call origination utilizing the IAX protocol <xref target="ID-IAX"/>.
   <vspace blankLines='1' />
  </t>
  </list>
</t>
<t> Security Considerations: 
<list style='empty'>
<t>
   <vspace blankLines='1' />
There are no specific security issues with this Enumservice.
However, the general considerations of <xref target="Security"/> apply.
   <vspace blankLines='1' />
</t>
</list>
</t>
<t> Intended Usage: COMMON 
   <vspace blankLines='1' />
</t>
<t> Author: Ed Guy <edguy@emcsw.com>
   <vspace blankLines='1' />
	</t>
<t>
	Any other information the author deems interesting:
	      None.
</t>
	</list>
	</t>
		</section>



<section title="Examples"> 
<section title="Simple IAX Registration"> <t>

  The following is an example of the use of the Enumservice registered
     by this document in a NAPTR resource record.

<figure>
<artwork><![CDATA[
  $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!" .   
]]></artwork>
</figure>

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

</t>
</section> 
<section title="Registration with Multiple Priorities"> <t>
The next example demonstrates that service identified by the "+441632960083" E.164 number
is
preferably accessed by IAX, secondly via SIP <xref target="RFC3764"/> , and then H.323 <xref target="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.
<vspace blankLines='1' />
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).

	</t> 
<figure>
<artwork><![CDATA[
  $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!" .
]]></artwork>
</figure>

	</section>
<section title="Registration with an IAX context"> <t>

  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'.
     </t>
<figure><artwork><![CDATA[
  $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!"    
]]></artwork> </figure>
<t>
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 
<!-- TODO EDITOR:  check final xref -->
Section 2 of <xref target="ID-IAX"/>.

</t>
</section> 
<section title="IPv6 Registration"> <t>

  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.
</t>
<figure><artwork><![CDATA[
$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!"  .
]]></artwork> </figure>
<t>
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'. 
</t>
</section> 



</section>
<section title="Security Considerations" anchor="Security"> <t>
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 <xref target="RFC4035" />
and RFC 3822 <xref target="RFC3833" />.

<vspace blankLines='1' />
The use of DNSSEC <xref target="RFC4035" /> is recommended to improve operational 
security.
	</t> 
</section>
        <section title="IANA Considerations"> <t>
This document requests registration of the "iax" Enumservice with
the 'iax' sub-type according to
the guidelines and specifications in RFC 3761 <xref target="RFC3761"/> and the definitions
in <xref target='sec.reg' />
in this document.
	
</t> </section>
<section title="Acknowledgments"> <t>
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.
</t> </section>
<section title="Draft Changes">
<t>[Note to Editor: This section is to be removed before publishing. Xml source is available upon request.]</t>
<section title="Changes since draft-ietf-enum-iax-04"> 
<t>
<vspace blankLines='1' />
* Removed the 'iax2' subtype per AD request.
<vspace blankLines='1' />
* Change from standards track to informational track.
<vspace blankLines='1' />
* Added citation to second paragraph.
</t></section>
<section title="Changes since draft-ietf-enum-iax-03"> 
<t>
* Removed version number '2' from scheme name.
<vspace blankLines='1' />
* IDNITS: removed terminology section. 
<vspace blankLines='1' />
* Various rewordings per Alex Mayrhofer and idnits review. 
<vspace blankLines='1' />
* Added E2U+email:mailto example to match text,
</t>
</section>
<section title="Changes since draft-ietf-enum-iax-02"> <t>
* Clarifications suggested by Peter Koch.
</t>
</section>
<section title="Changes since draft-ietf-enum-iax-01"> <t>
* Add reference to provisionally registered URI scheme.
<vspace blankLines='1' />
* Separate normative and informative references.
<vspace blankLines='1' />
* Minor grammatical edits.
<vspace blankLines='1' />
* Added the IPv6 Example.
<vspace blankLines='1' />
* Updated References.
</t></section>
<section title="Changes since draft-guy-iaxenum-00"> <t>
* Minor grammatical edits.
<vspace blankLines='1' />
* Added the 'iax2' subtype at WG request.
<vspace blankLines='1' />
* The Examples section was split into subsections for each example.
<vspace blankLines='1' />
* Context example added.


</t> </section>
</section>

    </middle>

    <back>
<references title="Normative References">

	&rfc3761; 
	&rfc3986;
	<reference anchor="ID-IAX">
		<front>
		<title abbrev="IAX Protocol">IAX: Inter-Asterisk eXchange Version 2</title>

		<author initials="M." surname="Spencer" fullname="Mark Spencer"> <organization>Digium</organization></author>
		<author initials="B." surname="Capouch" fullname="Brian Capouch"> <organization>Saint Joseph's College</organization></author>
		<author initials="E.T." surname="Guy" fullname="Ed Guy" role="editor"> <organization>Truphone</organization></author>
		<author initials="F." surname="Miller"> <organization>Cornfed
		Systems, LLC</organization></author>
		<author initials="K." surname="Shumard" fullname="Kenneth Shumard"> <organization>Digium</organization></author>

		<date month="February" year="2009"/>
		</front>
		<seriesInfo name="draft-guy-iax-05" value="Work In Progress"/>
	</reference>


	</references>
<references title="Informative References">
	&rfc3762;
	&rfc3764;
	&rfc4035;
	&rfc3833;
<reference anchor="E164">
	<front>
	<title abbrev="E.164">The International Public Telecommunication Number Plan</title>
	
	<author> <organization>ITU-T</organization></author>
	<date year="1997" month="May"/>
	</front>
	<seriesInfo name="" value="Recommendation E.164"/>
</reference>

	</references>
	
    </back>

</rfc>