RFC 6315

IANA Registration for Enumservice 'iax'

📅 published July 2011, from ietf

RFC 6315: IANA Registration for Enumservice 'iax' 🎀

okay bestie, this is the header info 📋. RFC 6315 is titled "IANA Registration for Enumservice 'iax'" 💖. E. Guy from CleverSpoke and K. Darilion from nic.at wrote it 🫶. It's Informational 🌸, ISSN 2070-1721, and it came out in July 2011 🦋. The title block doesn't list anything it obsoletes or updates ✨.

Abstract ✨

this doc registers an Enumservice for the Inter-Asterisk eXchange (IAX) protocol, following the guidelines in RFC 6117 💅.

Status of This Memo 🧚

this is not an Internet Standards Track spec. it's published just for info 🌈.

it's a product of the Internet Engineering Task Force (IETF) 👑. it reflects consensus from the IETF community, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG). not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 5741 🙈.

for current status, errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc6315 🍓.

Copyright Notice 💜

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stand on the publication date. read those carefully, because they spell out your rights and restrictions for this doc 📜. Code Components pulled out of this doc must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as described in the Simplified BSD License 🛠️.

this doc may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. the people controlling the copyright in some of that material may not have given the IETF Trust permission to allow modifications outside the IETF Standards Process. without an adequate license from them, this doc may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process. the exceptions are formatting it for publication as an RFC or translating it into languages other than English 🌸.

Table of Contents 🗂️

1. Introduction ....................................................2
2. IANA Registration ...............................................3
3. Examples ........................................................4
   3.1. Simple IAX URI .............................................4
   3.2. IAX URI with a Context .....................................4
4. Security Considerations .........................................4
5. IANA Considerations .............................................5
6. DNS Considerations ..............................................5
7. Acknowledgments .................................................5
8. References ......................................................5
   8.1. Normative References .......................................5
   8.2. Informative References .....................................6

1. Introduction 🦋

okay so the E.164 to Uniform Resource Identifiers (URIs) [RFC3986] Dynamic Delegation Discovery System (DDDS) Application (ENUM) [RFC6116] turns E.164 [E164] numbers into URIs using the Domain Name System (DNS) [RFC1035] 🌈.

IAX (Inter-Asterisk eXchange) [RFC5456] is an "all-in-one" protocol for handling multimedia on IP networks 🎧. it does control AND media in the same protocol, which is literally so efficient 😭🔥.

this doc registers an Enumservice for the IAX [RFC5456] protocol, following the guidelines in [RFC6117] 💖.

2. IANA Registration 📝

here's the record, verbatim 💅:

      <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="6315"/>, Section 4.
       </security>
       <usage>COMMON</usage>
       <registrationdocs>
         <xref type="rfc" data="6315"/>
       </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>

the 'iax' Enumservice maps E.164 numbers to IAX URIs 🍓. those URIs point at resources you can contact to set up a communication session over IAX 📞. a client picking this NAPTR has to be able to support IAX, full stop 💜.

3. Examples 🧁

these examples are only for illustration. they don't limit the 'iax' Enumservice to other usage scenarios 🌸.

3.1. Simple IAX URI 🎀

here's a Naming Authority Pointer (NAPTR) resource record showing the 'iax' Enumservice 💅:

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

so this contact info says the party at E.164 number +442079460148 can be reached over IAX at domain 'example.com'. the called party, service, or program on that domain is 'alice' 🦋.

3.2. IAX URI with a Context 🌈

here's the 'iax' Enumservice with an IPv6 destination address and 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"
            "!^.*$!iax:[2001:db8::1]:4569/alice?friends!" . )

this NAPTR says +442079460149 can be contacted over IAX at IPv6 address 2001:db8::1, port 4569, with the called party 'alice' in the context (or user partition) 'friends' 👑. for more on IAX URIs, see Section 5 of [RFC5456] 🫶.

4. Security Considerations 🔐

the 'iax' Enumservice doesn't add new security issues beyond the ones already in the ENUM, DNS, and IAX protocols. the catch is that this Enumservice allows disclosure of information that may make an attack or a violation of user privacy easier. the main result of these exploits is unwanted communications 🚨. these issues are covered in more detail in [RFC3833] 😭.

using DNS Security (DNSSEC) [RFC4033] is recommended to improve operational security 🛡️.

for security considerations that apply to all Enumservices, see RFC 6116, Section 7 🙏.

5. IANA Considerations 📋

this doc registers the 'iax' Enumservice following the guidelines and specs in [RFC6117] and the definitions in Section 2 of this doc 💖.

6. DNS Considerations 🌐

misconfigurations or delays in zone changes can cause call loops, maybe across different protocols or networks 🔄. implementations should take care to make sure these loops can be detected without interrupting other services, including SIP-based, IAX-based, and DNS itself 💀.

7. Acknowledgments 🫶

this work was supported by Internet Foundation Austria 🇦🇹. thanks also to Michael Haberler, Bernie Hoeneisen, and Richard Stastny for their support and guidance in writing this doc 🌸.

8. References 📚

8.1. Normative References 🔥

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC5456] Spencer, M., Capouch, B., Guy, E., Ed., Miller, F., and K. Shumard, "IAX: Inter-Asterisk eXchange Version 2", RFC 5456, February 2010.
[RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 6116, March 2011.
[RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA Registration of Enumservices: Guide, Template, and IANA Considerations", RFC 6117, March 2011.

8.2. Informative References 🧚

[E164] ITU-T, "The International Public Telecommunication Numbering Plan", Recommendation E.164, May 1997.
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain Name System (DNS)", RFC 3833, August 2004.
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, "DNS Security Introduction and Requirements", RFC 4033, March 2005.

Authors' Addresses 🏡

Ed Guy
CleverSpoke
12 Williams Road
Chatham, NJ  07928
US

Phone: +1 973 437 4519
EMail: edguy@CleverSpoke.com
URI:   http://www.cleverspoke.com/


Klaus Darilion
nic.at
Karlsplatz 1/2/9
1010 Wien
Austria

Phone: +43 1 5056416 36
EMail: klaus.darilion@nic.at
URI:   http://www.nic.at/

that's the whole doc, bestie 🌈💖✨

📦 where this page comes from

ietf: rfc6315 2011-07
💖 girlified by claude-haiku-5-5 on 2026-10-17: a language model's rewrite of the original, under its terms