idnits 2.17.1 draft-petithuguenin-behave-turn-uri-bis-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. 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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC5928]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 31, 2011) is 4533 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 4395 (Obsoleted by RFC 7595) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Petit-Huguenin 3 Internet-Draft Unaffiliated 4 Intended status: Informational October 31, 2011 5 Expires: May 3, 2012 7 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers 8 draft-petithuguenin-behave-turn-uri-bis-05 10 Abstract 12 This document defines two URI schemes that can be used to provision 13 the configuration values needed by the resolution mechanism defined 14 in [RFC5928]. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. This document may not be modified, 20 and derivative works of it may not be created, except to format it 21 for publication as an RFC or to translate it into languages other 22 than English. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on May 3, 2012. 36 Copyright Notice 38 Copyright (c) 2011 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Syntax of a TURN or TURNS URI . . . . . . . . . . . . . . . . . 3 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 57 4.1. TURN URI Registration . . . . . . . . . . . . . . . . . . . 4 58 4.2. TURNS URI Registration . . . . . . . . . . . . . . . . . . 5 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 62 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 63 Appendix A. Release notes . . . . . . . . . . . . . . . . . . . . 6 64 A.1. Modifications between petithuguenin-05 and 65 petithuguenin-04 . . . . . . . . . . . . . . . . . . . . . 6 66 A.2. Modifications between petithuguenin-04 and 67 petithuguenin-03 . . . . . . . . . . . . . . . . . . . . . 6 68 A.3. Modifications between petithuguenin-03 and 69 petithuguenin-02 . . . . . . . . . . . . . . . . . . . . . 6 70 A.4. Modifications between petithuguenin-02 and 71 petithuguenin-01 . . . . . . . . . . . . . . . . . . . . . 7 72 A.5. Modifications between petithuguenin-01 and 73 petithuguenin-00 . . . . . . . . . . . . . . . . . . . . . 7 74 A.6. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 7 75 A.7. Running Code Considerations . . . . . . . . . . . . . . . . 7 76 A.8. TODO List . . . . . . . . . . . . . . . . . . . . . . . . . 7 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 79 1. Introduction 81 [RFC5928] defines a resolution mechanism to convert a secure flag, an 82 host name or IP address, a eventually empty port, and an eventually 83 empty transport to a list of IP address, port, and TURN transport 84 tuples. 86 To simplify the provisioning of TURN clients, this document defines a 87 TURN and a TURNS URI scheme that can carry the four components needed 88 for the resolution mechanism. 90 2. Syntax of a TURN or TURNS URI 92 A TURN/TURNS URI has the following ABNF syntax [RFC5234]: 94 turnURI = scheme ":" turn-host [ ":" turn-port ] 95 [ "?transport=" transport ] 96 scheme = "turn" / "turns" 97 transport = "udp" / "tcp" / transport-ext 98 transport-ext = 1*unreserved 99 turn-host = IP-literal / IPv4address / reg-name 100 turn-port = *DIGIT 101 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 102 IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) 103 IPv6address = 6( h16 ":" ) ls32 104 / "::" 5( h16 ":" ) ls32 105 / [ h16 ] "::" 4( h16 ":" ) ls32 106 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 107 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 108 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 109 / [ *4( h16 ":" ) h16 ] "::" ls32 110 / [ *5( h16 ":" ) h16 ] "::" h16 111 / [ *6( h16 ":" ) h16 ] "::" 112 h16 = 1*4HEXDIG 113 ls32 = ( h16 ":" h16 ) / IPv4address 114 IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet 115 dec-octet = DIGIT ; 0-9 116 / %x31-39 DIGIT ; 10-99 117 / "1" 2DIGIT ; 100-199 118 / "2" %x30-34 DIGIT ; 200-249 119 / "25" %x30-35 ; 250-255 120 reg-name = *( unreserved / pct-encoded / sub-delims ) 122 , , and are specified in 123 [RFC3986]. 125 is equal to false if is equal to "turn" and equal 126 to false if is equal to "turns". 128 3. Security Considerations 130 Security considerations for the resolution mechanism are discussed in 131 [RFC5928]. 133 The "turn" and "turns" URI schemes do not introduce any specific 134 security issues beyond the security considerations discussed in 135 [RFC3986]. 137 4. IANA Considerations 139 This section contains the registration information for the "turn" and 140 "turns" URI Schemes (in accordance with [RFC4395]). 142 4.1. TURN URI Registration 144 URI scheme name: turn 146 Status: permanent 148 URI scheme syntax: See Section 2. 150 URI scheme semantics: See [RFC5928]. 152 Encoding considerations: There are no encoding considerations beyond 153 those in [RFC3986]. 155 Applications/protocols that use this URI scheme name: 157 The "turn" URI scheme is intended to be used by applications that 158 might need access to a TURN server. 160 Interoperability considerations: N/A 162 Security considerations: See Section 3. 164 Contact: Marc Petit-Huguenin 166 Author/Change controller: The IESG 168 References: This document. 170 [Note to RFC Editor: Replace "This document" with reference to this 171 document] 173 4.2. TURNS URI Registration 175 URI scheme name: turns 177 Status: permanent 179 URI scheme syntax: See Section 2. 181 URI scheme semantics: See [RFC5928]. 183 Encoding considerations: There are no encoding considerations beyond 184 those in [RFC3986]. 186 Applications/protocols that use this URI scheme name: 188 The "turns" URI scheme is intended to be used by applications that 189 might need access to a TURN server. 191 Interoperability considerations: N/A 193 Security considerations: See Section 3. 195 Contact: Marc Petit-Huguenin 197 Author/Change controller: The IESG 199 References: This document. 201 [Note to RFC Editor: Replace "This document" with reference to this 202 document] 204 5. Acknowledgements 206 Thanks to Margaret Wasserman, Magnus Westerlund, Juergen 207 Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. 208 Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes, and Jim Kleck for 209 their comments, suggestions and questions that helped to improve this 210 document. 212 The and ABNF productions have been copied 213 from the and ABNF productions from [RFC3986]. 215 This document was written with the xml2rfc tool described in 216 [RFC2629]. 218 6. References 219 6.1. Normative References 221 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 222 Resource Identifier (URI): Generic Syntax", STD 66, 223 RFC 3986, January 2005. 225 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 226 Specifications: ABNF", STD 68, RFC 5234, January 2008. 228 [RFC5928] Petit-Huguenin, M., "Traversal Using Relays around NAT 229 (TURN) Resolution Mechanism", RFC 5928, August 2010. 231 6.2. Informative References 233 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 234 June 1999. 236 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 237 Registration Procedures for New URI Schemes", BCP 35, 238 RFC 4395, February 2006. 240 [I-D.wood-tae-specifying-uri-transports] 241 Wood, L., "Specifying transport mechanisms in Uniform 242 Resource Identifiers", 243 draft-wood-tae-specifying-uri-transports-08 (work in 244 progress), May 2010. 246 Appendix A. Release notes 248 This section must be removed before publication as an RFC. 250 A.1. Modifications between petithuguenin-05 and petithuguenin-04 252 o Nits. 253 o Fixed schemes registration. 255 A.2. Modifications between petithuguenin-04 and petithuguenin-03 257 o Fixed references code link. 259 A.3. Modifications between petithuguenin-03 and petithuguenin-02 261 o Updated RFC references. 263 A.4. Modifications between petithuguenin-02 and petithuguenin-01 265 o Nits. 267 A.5. Modifications between petithuguenin-01 and petithuguenin-00 269 o Shorten I-D references. 271 A.6. Design Notes 273 o is not used in the URIs because it is deprecated. 274 is not used in the URIs because it is not used to guide 275 the resolution mechanism. 276 o As discussed in Dublin, there is no generic parameters in the URI 277 to prevent compatibity issues. 279 A.7. Running Code Considerations 281 o Reference Implementation of TURN URI parser and resolver 282 (). Marc Petit- 283 Huguenin. Implements version -05. 285 A.8. TODO List 287 o Instead of using a transport parameter perhaps a scheme prefix, as 288 proposed in [I-D.wood-tae-specifying-uri-transports] is better. 289 o Same thing for using a "+s" suffix instead of a "s" suffix for 290 security. 292 Author's Address 294 Marc Petit-Huguenin 295 Unaffiliated 297 Email: petithug@acm.org