idnits 2.17.1 draft-ietf-enum-iax-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 28, 2011) is 4771 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Telephone Number Mapping E. Guy 3 Internet-Draft CleverSpoke 4 Intended status: Informational K. Darilion 5 Expires: September 29, 2011 nic.at 6 March 28, 2011 8 IANA Registration for Enumservice 'iax' 9 draft-ietf-enum-iax-10 11 Abstract 13 This document registers an Enumservice for the IAX protocol according 14 to the guidelines given in RFC 6117. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on September 29, 2011. 33 Copyright Notice 35 Copyright (c) 2011 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 This document may contain material from IETF Documents or IETF 49 Contributions published or made publicly available before November 50 10, 2008. The person(s) controlling the copyright in some of this 51 material may not have granted the IETF Trust the right to allow 52 modifications of such material outside the IETF Standards Process. 53 Without obtaining an adequate license from the person(s) controlling 54 the copyright in such materials, this document may not be modified 55 outside the IETF Standards Process, and derivative works of it may 56 not be created outside the IETF Standards Process, except to format 57 it for publication as an RFC or to translate it into languages other 58 than English. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. IANA Registration . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 3.1. Simple IAX URI . . . . . . . . . . . . . . . . . . . . . . 5 66 3.2. IAX URI with a context . . . . . . . . . . . . . . . . . . 5 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 69 6. DNS Considerations . . . . . . . . . . . . . . . . . . . . . . 6 70 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 72 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 73 8.2. Informative References . . . . . . . . . . . . . . . . . . 7 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 76 1. Introduction 78 The E.164 to Uniform Resource Identifiers (URI) [RFC3986] Dynamic 79 Delegation Discovery System (DDDS) Application (ENUM) [RFC6116] 80 transforms E.164 [E164] numbers into URIs using the Domain Name 81 System (DNS) [RFC1035]. 83 IAX (Inter-Asterisk eXchange) [RFC5456] is an "all in one" protocol 84 for handling multimedia in IP networks. It combines both control and 85 media services in the same protocol. 87 This document registers an Enumservice for the IAX [RFC5456] protocol 88 according to the guidelines given in [RFC6117]. 90 2. IANA Registration 92 [Note for RFC-Editor: Please replace any instance of rfcTHIS with the 93 RFC number of this document before publication] 94 95 96 Protocol-Based 97 iax 98 99 iax 100 101 102 The 'iax' Enumservice is used to map E.164 numbers to 103 IAX URIs. Such URIs identify resources capable of being 104 contacted to provide a communication session using the 105 IAX protocol . 106 107 108 A client selecting this NAPTR needs to be able to support 109 communication utilizing the IAX protocol. 110 111 112 113 See , Section 4. 114 115 COMMON 116 117 118 119 120 121 122 123 125 126 127 Ed Guy 128 CleverSpoke, Inc 129 mailto:edguy@CleverSpoke.com 130 2010-11-01 131 132 133 Klaus Darilion 134 nic.at 135 mailto:klaus.darilion@nic.at 136 2011-03-24 137 138 140 3. Examples 142 The following examples are just for illustrative purposes and will in 143 no way limit the usage of the 'iax' Enumservice to other usage 144 scenarios. 146 3.1. Simple IAX URI 148 The following NAPTR resource record is an example of the 'iax' 149 Enumservice. 151 $ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. 153 @ IN NAPTR ( 10 100 "u" "E2U+iax" 154 "!^.*$!iax:example.com/alice!" . ) 156 This contact information indicates that the party addressed by the 157 E.164 number +442079460148 can be contacted using the IAX protocol to 158 domain 'example.com'. The called party, service, or program on that 159 domain is identified by 'alice'. 161 3.2. IAX URI with a context 163 The following is an example of the 'iax' Enumservice using an IPv6 164 destination address and a destination 'context'. 166 $ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. 168 @ IN NAPTR ( 10 100 "u" "E2U+iax" 169 "!^.*$!iax:[2001:db8::1]:4569/alice?friends!" . ) 171 This NAPTR resource record indicates that +442079460149 may be 172 contacted by using the IAX protocol at IPv6 address 2001:db8::1, port 173 4569 with the called party 'alice' in the context (or user partition) 174 'friends'. For further usage of IAX URIs see Section 2 of [RFC5456]. 176 4. Security Considerations 178 The 'iax' Enumservice does not introduce any new security issues 179 beyond any already present in the ENUM, DNS and IAX protocols except 180 that this Enumservice provides for disclosure of information that may 181 facilitate an attack or a violation of user privacy in some way. The 182 primary result of these exploits is unwanted communications. These 183 issues are discussed in further detail in [RFC3833]. 185 The use of DNSSEC [RFC4033] is recommended to improve operational 186 security. 188 For security considerations that apply to all Enumservices please 189 refer to RFC 6116, Section 7. 191 5. IANA Considerations 193 This document requests registration of the 'iax' Enumservice 194 according to the guidelines and specifications in [RFC6117] and the 195 definitions in Section 2 in this document. 197 6. DNS Considerations 199 Misconfiguration or delays in zone changes can result in call loops, 200 perhaps with different protocols or networks. Implementations should 201 take care to ensure such loops can be detected without interrupting 202 other services including SIP-based, IAX-based, and DNS itself. 204 7. Acknowledgments 206 This work was supported by Internet Foundation Austria. In addition, 207 thanks to Michael Haberler, Bernie Hoeneisen and Richard Stastny for 208 their support and guidance in writing this document. 210 8. References 212 8.1. Normative References 214 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 215 Resource Identifier (URI): Generic Syntax", STD 66, 216 RFC 3986, January 2005. 218 [RFC5456] Spencer, M., Capouch, B., Guy, E., Miller, F., and K. 219 Shumard, "IAX: Inter-Asterisk eXchange Version 2", 220 RFC 5456, February 2010. 222 [RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to 223 Uniform Resource Identifiers (URI) Dynamic Delegation 224 Discovery System (DDDS) Application (ENUM)", RFC 6116, 225 March 2011. 227 [RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA 228 Registration of Enumservices: Guide, Template, and IANA 229 Considerations", RFC 6117, March 2011. 231 8.2. Informative References 233 [E164] ITU-T, "The International Public Telecommunication Number 234 Plan", Recommendation E.164, May 1997. 236 [RFC1035] Mockapetris, P., "Domain names - implementation and 237 specification", STD 13, RFC 1035, November 1987. 239 [RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain 240 Name System (DNS)", RFC 3833, August 2004. 242 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 243 Rose, "DNS Security Introduction and Requirements", 244 RFC 4033, March 2005. 246 Authors' Addresses 248 Ed Guy 249 CleverSpoke 250 12 Williams Road 251 Chatham, NJ 07928 252 US 254 Phone: +1 973 437 4519 255 Email: edguy@CleverSpoke.com 256 URI: http://www.cleverspoke.com/ 258 Klaus Darilion 259 nic.at 260 Karlsplatz 1/2/9 261 1010 Wien 262 Austria 264 Phone: +43 1 5056416 36 265 Email: klaus.darilion@nic.at 266 URI: http://www.nic.at/