One document matched: draft-ietf-enum-iax-07.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 rfc4035 PUBLIC '' 'bibxml/reference.RFC.4035.xml'>
<!ENTITY rfc4759 PUBLIC '' 'bibxml/reference.RFC.4759.xml'>
<!ENTITY rfc3833 PUBLIC '' 'bibxml/reference.RFC.3833.xml'>
<!ENTITY rfc5456 PUBLIC '' 'bibxml/reference.RFC.5456.xml'>
<!ENTITY draft-ietf-enum-3761bis PUBLIC '' 'bibxml3/reference.I-D.draft-ietf-enum-3761bis-09.xml'>
<!ENTITY draft-ietf-enum-enumservices-guide PUBLIC '' 'bibxml3/reference.I-D.draft-ietf-enum-enumservices-guide-22.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-07'>
<?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>
[Note for RFC-Editor: Please replace any instance of RFC XXXX with
the RFC number of draft-ietf-enum-enumservices-guide before
publication]
</t>
<t>
This document registers an Enumservice for the IAX protocol
according to the guidelines given in RFC XXXX.
</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="I-D.ietf-enum-3761bis"/> transforms E.164 <xref target="E164"/> numbers into Uniform Resource Identifiers (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 draft-ietf-enum-enumservices-guide <xref target="I-D.ietf-enum-enumservices-guide"/>.
</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 indicates that the resource
identified by the associated URI scheme is capable
of being contacted using the IAX protocol
<xref target="RFC5456"/> to provide a communication
session.
</paragraph>
<paragraph>
A client selecting this NAPTR needs to be able to support
communication utilizing the IAX protocol.
</paragraph>
</functionalspec>
<security>
There are no specific security issues with this Enumservice.
However, the general considerations of
<xref type="rfc" data="rfcTHIS"/> Section 4 apply.
</security>
<usage>COMMON</usage>
<registrationdocs>
<xref type="rfc" data="rfcTHIS"/>
</registrationdocs>
<requesters>
<xref type="person" data="Ed_Guy"/>
</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>
</people>
]]></artwork></figure>
</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"/>, thirdly by 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, h323, and mailto).
</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 +442079460149 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 2 of <xref target="RFC5456"/>.
</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 +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'.
</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="RFC4035" /> is recommended to improve operational
security.
</t>
</section>
<section title="IANA Considerations"> <t>
This document requests registration of the 'iax' Enumservice according to
the guidelines and specifications in draft-ietf-enum-enumservices-guide <xref target="I-D.ietf-enum-enumservices-guide"/> and the definitions
in <xref target='sec.reg' />
in this document.
</t> </section>
<section title="DNS Considerations"> <t>
DNS considerations related to the 'iax' Enumservice are similar to those of the 'SIP' Enumservice.
</t><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, Richard Stastny and Bernie Hoeneisen for their support and guidance
in writing this document.
</t> </section>
<section title="Draft Changes">
<t>[Note to RFC-Editor: This section is to be removed before publishing. XML source is available upon request.]</t>
<section title="Changes since draft-ietf-enum-iax-06">
<t>
* KD: Changed title from "IANA Registration for IAX Enumservice" to "IANA Registration for Enumservice 'iax'" as the service type is in small letters
<vspace blankLines='1' />
* KD: Changed introduction (ENUM maps to URIs, not domains) - used wording from Enumservices draft <xref target="I-D.ietf-enum-enumservices-guide"/>.
<vspace blankLines='1' />
* KD: Changed introduction: shortened IAX description - this RFC is not about IAX but about the ENUM service.
<vspace blankLines='1' />
* KD: Changed introduction: shortend description (the service field actually does not describe the class of functionality, but is mostly a pointer to supported communication protocols)
<vspace blankLines='1' />
* KD: Use the same wording in abstract and introduction: The Enumservice is not IAX but iax, thus used different wording.
<vspace blankLines='1' />
* KD: Fixed double-spaces
<vspace blankLines='1' />
* KD: IANA Registration: changed functional description: fixed wording, use 'communication' instead of 'call origination'
<vspace blankLines='1' />
* KD: IANA Registration: remove reference to URI registry (no clean way to reference) and moved reference to <xref target="RFC5456"/> one paragraph up
<vspace blankLines='1' />
* KD: Todo: Fix references "thisRFC" in IANA Registration
<vspace blankLines='1' />
* KD: Registration with multiple priorities: write "SIP", "H323" for the tokens, instead of "sip", "h323" and add 'mailto' to the protocols
<vspace blankLines='1' />
* KD: Examples: replaced "This contact information indicates that the domain 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted" with "This contact information indicates that +442079460149 may be contacted" as a domain is not contacted (although the previous text was from the ENUM RFC)
<vspace blankLines='1' />
* KD: Examples: Write IPv6 address in text without [] as the port is mentioned separately
<vspace blankLines='1' />
* KD: IANA Considerations: removed the sub-type as we do not register a sub-type
<vspace blankLines='1' />
* KD: DNS Considerations: removed "Since IAX is typically deployed in a proxy configuration" as there is no "proxy" configuration in IAX
<vspace blankLines='1' />
* KD: DNS Considerations: removed reference to <xref target="RFC4759" /> as IMO it does not solve the loop problem on DNS changes and chached data (it does not even contain the word 'loop')
<vspace blankLines='1' />
* KD: Security Considerations: removed reference to RFC 4035 regarding "unwanted communication" as DNSSEC is here not relevant.
<vspace blankLines='1' />
* KD: as suggested by Bernie: fixed references to RFC3761bis and draft-ietf-enum-enumservices-guide
<vspace blankLines='1' />
* KD: as suggested by Bernie: verified that all example numbers are UK drama numbers (http://stakeholders.ofcom.org.uk/telecoms/numbering/guidance-tele-no/numbers-for-drama) and 2001:db8::1 is a "documentation" IPv6 address
<vspace blankLines='1' />
* KD: as suggested by Bernie: replaced "Editor" with "RFC-Editor"
<vspace blankLines='1' />
* KD: Acknowledgments: added Bernie
</t></section>
<section title="Changes since draft-ietf-enum-iax-05">
<t>
* Changed to be compatible with <xref target="I-D.ietf-enum-enumservices-guide"/>.
<vspace blankLines='1' />
* Added DNS Considerations section.
<vspace blankLines='1' />
* Per Dan Harkin's review, improved language in security considerations section
and fixed typo.
<vspace blankLines='1' />
* Per Peter Koch's review, change DNS continuation character from \ to ( ) form.
</t></section>
<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">
&rfc3986;
&rfc5456;
&draft-ietf-enum-3761bis;
&draft-ietf-enum-enumservices-guide;
</references>
<references title="Informative References">
&rfc1035;
&rfc3762;
&rfc3764;
&rfc3833;
&rfc4035;
&rfc4759;
<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>
| PAFTECH AB 2003-2026 | 2026-04-24 02:38:38 |