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

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

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY rfc1035 PUBLIC '' 'bibxml/reference.RFC.1035.xml'>
    <!ENTITY rfc2026 PUBLIC '' 'bibxml/reference.RFC.2026.xml'>
    <!ENTITY rfc2535 PUBLIC '' 'bibxml/reference.RFC.2535.xml'>
    <!ENTITY rfc3762 PUBLIC '' 'bibxml/reference.RFC.3762.xml'>
    <!ENTITY rfc3764 PUBLIC '' 'bibxml/reference.RFC.3764.xml'>
    <!ENTITY rfc3978 PUBLIC '' 'bibxml/reference.RFC.3978.xml'>
    <!ENTITY rfc3979 PUBLIC '' 'bibxml/reference.RFC.3979.xml'>
    <!ENTITY rfc1034 PUBLIC '' 'bibxml/reference.RFC.1034.xml'>
    <!ENTITY rfc3401 PUBLIC '' 'bibxml/reference.RFC.3401.xml'>
    <!ENTITY rfc3402 PUBLIC '' 'bibxml/reference.RFC.3402.xml'>
    <!ENTITY rfc3403 PUBLIC '' 'bibxml/reference.RFC.3403.xml'>
    <!ENTITY rfc3404 PUBLIC '' 'bibxml/reference.RFC.3404.xml'>
    <!ENTITY rfc3986 PUBLIC '' 'bibxml/reference.RFC.3986.xml'>
    <!ENTITY rfc4033 PUBLIC '' 'bibxml/reference.RFC.4033.xml'>
    <!ENTITY rfc3833 PUBLIC '' 'bibxml/reference.RFC.3833.xml'>
    <!ENTITY rfc5456 PUBLIC '' 'bibxml/reference.RFC.5456.xml'>
    <!ENTITY rfc6116 PUBLIC '' 'bibxml/reference.RFC.6116.xml'>
    <!ENTITY rfc6117 PUBLIC '' 'bibxml/reference.RFC.6117.xml'>
]>

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


<rfc category="info" ipr="pre5378Trust200902" docName='draft-ietf-enum-iax-10'>

<?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 Enumservice 'iax'</title>

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

<author initials="K." surname="Darilion" fullname="Klaus Darilion">
<organization>nic.at</organization>
<address>
<postal>
<street>Karlsplatz 1/2/9</street>
<city>1010 Wien</city>
<country>Austria</country>
</postal>
<phone>+43 1 5056416 36</phone>
<email>klaus.darilion@nic.at</email>
<uri>http://www.nic.at/</uri>
</address>
</author>

        <date year="2011"/> 

<!-- <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 an Enumservice for the IAX protocol 
according to the guidelines given in RFC 6117.
</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="RFC6116"/> transforms E.164 <xref target="E164"/> numbers into 
URIs using the Domain Name System (DNS) <xref target="RFC1035"/>.
<vspace blankLines='1' />
IAX (Inter-Asterisk eXchange) <xref target="RFC5456" /> is an "all in one" protocol for handling multimedia in IP networks. It combines both control and media services in the same protocol.
<vspace blankLines='1' />
This document registers an Enumservice for the IAX <xref target="RFC5456" /> protocol according to the guidelines 
given in <xref target="RFC6117"/>.
</t> </section>


<section anchor="sec.reg" title="IANA Registration">

<t> [Note for RFC-Editor: Please replace any instance of rfcTHIS with
 the RFC number of this document before publication]</t>

<figure><artwork><![CDATA[
      <record>
       <!-- iax -->
       <class>Protocol-Based</class>
       <type>iax</type>
       <!-- No subtype -->
       <urischeme>iax</urischeme>
       <functionalspec>
         <paragraph>
           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 <xref target="RFC5456"/>.
         </paragraph>
         <paragraph>
           A client selecting this NAPTR needs to be able to support 
           communication utilizing the IAX protocol.
         </paragraph>
       </functionalspec>
       <security>
         See <xref type="rfc" data="rfcTHIS"/>, Section 4.
       </security>
       <usage>COMMON</usage>
       <registrationdocs>
         <xref type="rfc" data="rfcTHIS"/>
       </registrationdocs>
       <requesters>
         <xref type="person" data="Ed_Guy"/>
         <xref type="person" data="Klaus_Darilion"/>
       </requesters>
     </record>

     <people>
       <person id="Ed_Guy">
         <name>Ed Guy</name>
         <org>CleverSpoke, Inc</org>
         <uri>mailto:edguy@CleverSpoke.com</uri>
         <updated>2010-11-01</updated>
       </person>
       <person id="Klaus_Darilion">
         <name>Klaus Darilion</name>
         <org>nic.at</org>
         <uri>mailto:klaus.darilion@nic.at</uri>
         <updated>2011-03-24</updated>
       </person>
     </people>
]]></artwork></figure>
</section>
<section title="Examples">

<t> The following examples are just for illustrative purposes and will in no way limit the usage
of the 'iax' Enumservice to other usage scenarios.
</t>

<section title="Simple IAX URI"> <t>

  The following NAPTR resource record is an example of the 'iax' Enumservice.

<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/alice!" . )
]]></artwork>
</figure>

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

</t>
</section> 
<section title="IAX URI with a context"> <t>

  The following is an example of the 'iax' Enumservice using an IPv6 destination address
  and 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:[2001:db8::1]:4569/alice?friends!" . )
]]></artwork> </figure>
<t>
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 <xref target="RFC5456"/>.

</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 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 <xref target="RFC3833" />.

<vspace blankLines='1' />
The use of DNSSEC <xref target="RFC4033" /> is recommended to improve operational 
security.

<vspace blankLines='1' />
For security considerations that apply to all Enumservices please refer to 
RFC 6116, Section 7.
</t> 

</section>
        <section title="IANA Considerations"> <t>
This document requests registration of the 'iax' Enumservice according to
the guidelines and specifications in 
<xref target="RFC6117"/> and the definitions
in <xref target='sec.reg' />
in this document.
	
</t> </section>
<section title="DNS Considerations"> <t>
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. 
</t> </section>
<section title="Acknowledgments"> <t>
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.
</t> </section>

    </middle>

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

	&rfc3986;
	&rfc5456;
	&rfc6116;
	&rfc6117;
	</references>
<references title="Informative References">
	&rfc1035;
	&rfc3833;
	&rfc4033;
<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>