idnits 2.17.1 draft-petithuguenin-behave-turn-uri-bis-04.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 (July 10, 2011) is 4673 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 July 10, 2011 5 Expires: January 11, 2012 7 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers 8 draft-petithuguenin-behave-turn-uri-bis-04 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 January 11, 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-04 and 65 petithuguenin-03 . . . . . . . . . . . . . . . . . . . . . 6 66 A.2. Modifications between petithuguenin-03 and 67 petithuguenin-02 . . . . . . . . . . . . . . . . . . . . . 6 68 A.3. Modifications between petithuguenin-02 and 69 petithuguenin-01 . . . . . . . . . . . . . . . . . . . . . 6 70 A.4. Modifications between petithuguenin-01 and 71 petithuguenin-00 . . . . . . . . . . . . . . . . . . . . . 6 72 A.5. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 6 73 A.6. Running Code Considerations . . . . . . . . . . . . . . . . 7 74 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 76 1. Introduction 78 [RFC5928] defines a resolution mechanism to convert a secure flag, an 79 host name or IP address, a eventually empty port, and an eventually 80 empty transport to a list of IP address, port, and TURN transport 81 tuples. 83 To simplify the provisioning of TURN clients, this document defines a 84 TURN and a TURNS URI scheme that can carry the four components needed 85 for the resolution mechanism. 87 2. Syntax of a TURN or TURNS URI 89 A TURN/TURNS URI has the following ABNF syntax [RFC5234]: 91 turnURI = scheme ":" turn-host [ ":" turn-port ] 92 [ "?transport=" transport ] 93 scheme = "turn" / "turns" 94 transport = "udp" / "tcp" / transport-ext 95 transport-ext = 1*unreserved 96 turn-host = IP-literal / IPv4address / reg-name 97 turn-port = *DIGIT 98 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 99 IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) 100 IPv6address = 6( h16 ":" ) ls32 101 / "::" 5( h16 ":" ) ls32 102 / [ h16 ] "::" 4( h16 ":" ) ls32 103 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 104 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 105 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 106 / [ *4( h16 ":" ) h16 ] "::" ls32 107 / [ *5( h16 ":" ) h16 ] "::" h16 108 / [ *6( h16 ":" ) h16 ] "::" 109 h16 = 1*4HEXDIG 110 ls32 = ( h16 ":" h16 ) / IPv4address 111 IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet 112 dec-octet = DIGIT ; 0-9 113 / %x31-39 DIGIT ; 10-99 114 / "1" 2DIGIT ; 100-199 115 / "2" %x30-34 DIGIT ; 200-249 116 / "25" %x30-35 ; 250-255 117 reg-name = *( unreserved / pct-encoded / sub-delims ) 119 , , and are specified in 120 [RFC3986]. 122 is equal to false is is equal to "turn" and equal 123 to false if is equal to "turns". 125 3. Security Considerations 127 Security considerations for the resolution mechanism are discussed in 128 [RFC5928]. 130 The "turn" and "turns" URI schemes do not introduce any specific 131 security issues beyond the security considerations discussed in 132 [RFC3986]. 134 4. IANA Considerations 136 This section contains the registration information for the "turn" and 137 "turns" URI Schemes (in accordance with [RFC4395]). 139 4.1. TURN URI Registration 141 URI scheme name: turn 143 Status: permanent 145 URI scheme syntax: See Section 2. 147 URI scheme semantics: See [RFC5928]. 149 Encoding considerations: There are no encoding considerations beyond 150 those in [RFC3986]. 152 Applications/protocols that use this URI scheme name: 154 The "turn" URI scheme is intended to be used by applications that 155 might need access to a TURN server. 157 Interoperability considerations: N/A 159 Security considerations: See Section 3. 161 Contact: Marc Petit-Huguenin 163 Author/Change controller: Marc Petit-Huguenin 165 References: This document. 167 [Note to RFC Editor: Replace "This document" with reference to this 168 document] 170 4.2. TURNS URI Registration 172 URI scheme name: turns 174 Status: permanent 176 URI scheme syntax: See Section 2. 178 URI scheme semantics: See [RFC5928]. 180 Encoding considerations: There are no encoding considerations beyond 181 those in [RFC3986]. 183 Applications/protocols that use this URI scheme name: 185 The "turns" URI scheme is intended to be used by applications that 186 might need access to a TURN server. 188 Interoperability considerations: N/A 190 Security considerations: See Section 3. 192 Contact: Marc Petit-Huguenin 194 Author/Change controller: Marc Petit-Huguenin 196 References: This document. 198 [Note to RFC Editor: Replace "This document" with reference to this 199 document] 201 5. Acknowledgements 203 Thanks to Margaret Wasserman, Magnus Westerlund, Juergen 204 Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. 205 Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes, and Jim Kleck for 206 their comments, suggestions and questions that helped to improve this 207 document. 209 The and ABNF productions have been copied 210 from the and ABNF productions from [RFC3986]. 212 This document was written with the xml2rfc tool described in 213 [RFC2629]. 215 6. References 216 6.1. Normative References 218 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 219 Resource Identifier (URI): Generic Syntax", STD 66, 220 RFC 3986, January 2005. 222 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 223 Specifications: ABNF", STD 68, RFC 5234, January 2008. 225 [RFC5928] Petit-Huguenin, M., "Traversal Using Relays around NAT 226 (TURN) Resolution Mechanism", RFC 5928, August 2010. 228 6.2. Informative References 230 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 231 June 1999. 233 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 234 Registration Procedures for New URI Schemes", BCP 35, 235 RFC 4395, February 2006. 237 Appendix A. Release notes 239 This section must be removed before publication as an RFC. 241 A.1. Modifications between petithuguenin-04 and petithuguenin-03 243 o Fixed references code link. 245 A.2. Modifications between petithuguenin-03 and petithuguenin-02 247 o Updated RFC references. 249 A.3. Modifications between petithuguenin-02 and petithuguenin-01 251 o Nits. 253 A.4. Modifications between petithuguenin-01 and petithuguenin-00 255 o Shorten I-D references. 257 A.5. Design Notes 259 o is not used in the URIs because it is deprecated. 260 is not used in the URIs because it is not used to guide 261 the resolution mechanism. 263 o As discussed in Dublin, there is no generic parameters in the URI 264 to prevent compatibity issues. 266 A.6. Running Code Considerations 268 o Reference Implementation of TURN URI parser and resolver 269 (). Marc Petit- 270 Huguenin. Implements version -04 272 Author's Address 274 Marc Petit-Huguenin 275 Unaffiliated 277 Email: petithug@acm.org