1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Internet Engineering Task Force (IETF) E. Guy
Request for Comments: 6315 CleverSpoke
Category: Informational K. Darilion
ISSN: 2070-1721 nic.at
July 2011
<span class="h1">IANA Registration for Enumservice 'iax'</span>
Abstract
This document registers an Enumservice for the Inter-Asterisk
eXchange (IAX) protocol according to the guidelines given in <a href="./rfc6117">RFC</a>
<a href="./rfc6117">6117</a>.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6315">http://www.rfc-editor.org/info/rfc6315</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Guy & Darilion Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6315">RFC 6315</a> IANA Registration for Enumservice 'iax' July 2011</span>
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. IANA Registration ...............................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Examples ........................................................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Simple IAX URI .............................................<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. IAX URI with a Context .....................................<a href="#page-4">4</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. DNS Considerations ..............................................<a href="#page-5">5</a>
<a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-5">5</a>
<a href="#section-8">8</a>. References ......................................................<a href="#page-5">5</a>
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-5">5</a>
<a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The E.164 to Uniform Resource Identifiers (URIs) [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] Dynamic
Delegation Discovery System (DDDS) Application (ENUM) [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>]
transforms E.164 [<a href="#ref-E164" title=""The International Public Telecommunication Numbering Plan"">E164</a>] numbers into URIs using the Domain Name
System (DNS) [<a href="./rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>].
IAX (Inter-Asterisk eXchange) [<a href="./rfc5456" title=""IAX: Inter-Asterisk eXchange Version 2"">RFC5456</a>] is an "all-in-one" protocol
for handling multimedia in IP networks. It combines both control and
media services in the same protocol.
This document registers an Enumservice for the IAX [<a href="./rfc5456" title=""IAX: Inter-Asterisk eXchange Version 2"">RFC5456</a>] protocol
according to the guidelines given in [<a href="./rfc6117" title=""IANA Registration of Enumservices: Guide, Template, and IANA Considerations"">RFC6117</a>].
<span class="grey">Guy & Darilion Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6315">RFC 6315</a> IANA Registration for Enumservice 'iax' July 2011</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Registration</span>
<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="<a href="./rfc5456">RFC5456</a>"/>.
</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"/>, <a href="#section-4">Section 4</a>.
</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>
<span class="grey">Guy & Darilion Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6315">RFC 6315</a> IANA Registration for Enumservice 'iax' July 2011</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples</span>
The following examples are just for illustrative purposes and will in
no way limit the usage of the 'iax' Enumservice to other usage
scenarios.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Simple IAX URI</span>
The following Naming Authority Pointer (NAPTR) resource record is an
example of 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!" . )
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'.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. IAX URI with a Context</span>
The following is an example of the 'iax' Enumservice using 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 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 <a href="./rfc5456#section-5">Section 5
of [RFC5456]</a>.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
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
[<a href="./rfc3833" title=""Threat Analysis of the Domain Name System (DNS)"">RFC3833</a>].
<span class="grey">Guy & Darilion Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6315">RFC 6315</a> IANA Registration for Enumservice 'iax' July 2011</span>
The use of DNS Security (DNSSEC) [<a href="./rfc4033" title=""DNS Security Introduction and Requirements"">RFC4033</a>] is recommended to improve
operational security.
For security considerations that apply to all Enumservices, please
refer to <a href="./rfc6116#section-7">RFC 6116, Section 7</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
This document registers the 'iax' Enumservice according to the
guidelines and specifications in [<a href="./rfc6117" title=""IANA Registration of Enumservices: Guide, Template, and IANA Considerations"">RFC6117</a>] and the definitions in
<a href="#section-2">Section 2</a> in this document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. DNS Considerations</span>
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.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
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.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-RFC5456">RFC5456</a>] Spencer, M., Capouch, B., Guy, E., Ed., Miller, F., and K.
Shumard, "IAX: Inter-Asterisk eXchange Version 2",
<a href="./rfc5456">RFC 5456</a>, February 2010.
[<a id="ref-RFC6116">RFC6116</a>] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to
Uniform Resource Identifiers (URI) Dynamic Delegation
Discovery System (DDDS) Application (ENUM)", <a href="./rfc6116">RFC 6116</a>,
March 2011.
[<a id="ref-RFC6117">RFC6117</a>] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA
Registration of Enumservices: Guide, Template, and IANA
Considerations", <a href="./rfc6117">RFC 6117</a>, March 2011.
<span class="grey">Guy & Darilion Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6315">RFC 6315</a> IANA Registration for Enumservice 'iax' July 2011</span>
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-E164">E164</a>] ITU-T, "The International Public Telecommunication
Numbering Plan", Recommendation E.164, May 1997.
[<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.
[<a id="ref-RFC3833">RFC3833</a>] Atkins, D. and R. Austein, "Threat Analysis of the Domain
Name System (DNS)", <a href="./rfc3833">RFC 3833</a>, August 2004.
[<a id="ref-RFC4033">RFC4033</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements",
<a href="./rfc4033">RFC 4033</a>, March 2005.
Authors' Addresses
Ed Guy
CleverSpoke
12 Williams Road
Chatham, NJ 07928
US
Phone: +1 973 437 4519
EMail: edguy@CleverSpoke.com
URI: <a href="http://www.cleverspoke.com/">http://www.cleverspoke.com/</a>
Klaus Darilion
nic.at
Karlsplatz 1/2/9
1010 Wien
Austria
Phone: +43 1 5056416 36
EMail: klaus.darilion@nic.at
URI: <a href="http://www.nic.at/">http://www.nic.at/</a>
Guy & Darilion Informational [Page 6]
</pre>
|
