idnits 2.17.1 draft-petithuguenin-behave-turn-uri-bis-03.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 : ---------------------------------------------------------------------------- ** 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 (January 10, 2011) is 4827 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 (==), 3 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 January 10, 2011 5 Expires: July 14, 2011 7 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers 8 draft-petithuguenin-behave-turn-uri-bis-03 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. 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 July 14, 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 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Syntax of a TURN or TURNS URI . . . . . . . . . . . . . . . . . 3 52 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 54 4.1. TURN URI Registration . . . . . . . . . . . . . . . . . . . 4 55 4.2. TURNS URI Registration . . . . . . . . . . . . . . . . . . 5 56 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 57 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 59 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 60 Appendix A. Release notes . . . . . . . . . . . . . . . . . . . . 6 61 A.1. Modifications between petithuguenin-03 and 62 petithuguenin-02 . . . . . . . . . . . . . . . . . . . . . 6 63 A.2. Modifications between petithuguenin-02 and 64 petithuguenin-01 . . . . . . . . . . . . . . . . . . . . . 6 65 A.3. Modifications between petithuguenin-01 and 66 petithuguenin-00 . . . . . . . . . . . . . . . . . . . . . 6 67 A.4. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 6 68 A.5. Running Code Considerations . . . . . . . . . . . . . . . . 7 69 A.6. TODO List . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 72 1. Introduction 74 [RFC5928] defines a resolution mechanism to convert a secure flag, an 75 host name or IP address, a eventually empty port, and an eventually 76 empty transport to a list of IP address, port, and TURN transport 77 tuples. 79 To simplify the provisioning of TURN clients, this document defines a 80 TURN and a TURNS URI scheme that can carry the four components needed 81 for the resolution mechanism. 83 2. Syntax of a TURN or TURNS URI 85 A TURN/TURNS URI has the following ABNF syntax [RFC5234]: 87 turnURI = scheme ":" turn-host [ ":" turn-port ] 88 [ "?transport=" transport ] 89 scheme = "turn" / "turns" 90 transport = "udp" / "tcp" / transport-ext 91 transport-ext = 1*unreserved 92 turn-host = IP-literal / IPv4address / reg-name 93 turn-port = *DIGIT 94 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 95 IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) 96 IPv6address = 6( h16 ":" ) ls32 97 / "::" 5( h16 ":" ) ls32 98 / [ h16 ] "::" 4( h16 ":" ) ls32 99 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 100 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 101 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 102 / [ *4( h16 ":" ) h16 ] "::" ls32 103 / [ *5( h16 ":" ) h16 ] "::" h16 104 / [ *6( h16 ":" ) h16 ] "::" 105 h16 = 1*4HEXDIG 106 ls32 = ( h16 ":" h16 ) / IPv4address 107 IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet 108 dec-octet = DIGIT ; 0-9 109 / %x31-39 DIGIT ; 10-99 110 / "1" 2DIGIT ; 100-199 111 / "2" %x30-34 DIGIT ; 200-249 112 / "25" %x30-35 ; 250-255 113 reg-name = *( unreserved / pct-encoded / sub-delims ) 115 , , and are specified in 116 [RFC3986]. 118 is equal to false is is equal to "turn" and equal 119 to false if is equal to "turns". 121 3. Security Considerations 123 Security considerations for the resolution mechanism are discussed in 124 [RFC5928]. 126 The "turn" and "turns" URI schemes do not introduce any specific 127 security issues beyond the security considerations discussed in 128 [RFC3986]. 130 4. IANA Considerations 132 This section contains the registration information for the "turn" and 133 "turns" URI Schemes (in accordance with [RFC4395]). 135 4.1. TURN URI Registration 137 URI scheme name: turn 139 Status: permanent 141 URI scheme syntax: See Section 2. 143 URI scheme semantics: See [RFC5928]. 145 Encoding considerations: There are no encoding considerations beyond 146 those in [RFC3986]. 148 Applications/protocols that use this URI scheme name: 150 The "turn" URI scheme is intended to be used by applications that 151 might need access to a TURN server. 153 Interoperability considerations: N/A 155 Security considerations: See Section 3. 157 Contact: Marc Petit-Huguenin 159 Author/Change controller: Marc Petit-Huguenin 161 References: This document. 163 [Note to RFC Editor: Replace "This document" with reference to this 164 document] 166 4.2. TURNS URI Registration 168 URI scheme name: turns 170 Status: permanent 172 URI scheme syntax: See Section 2. 174 URI scheme semantics: See [RFC5928]. 176 Encoding considerations: There are no encoding considerations beyond 177 those in [RFC3986]. 179 Applications/protocols that use this URI scheme name: 181 The "turns" URI scheme is intended to be used by applications that 182 might need access to a TURN server. 184 Interoperability considerations: N/A 186 Security considerations: See Section 3. 188 Contact: Marc Petit-Huguenin 190 Author/Change controller: Marc Petit-Huguenin 192 References: This document. 194 [Note to RFC Editor: Replace "This document" with reference to this 195 document] 197 5. Acknowledgements 199 Thanks to Margaret Wasserman, Magnus Westerlund, Juergen 200 Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. 201 Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes, and Jim Kleck for 202 their comments, suggestions and questions that helped to improve this 203 document. 205 The and ABNF productions have been copied 206 from the and ABNF productions from [RFC3986]. 208 This document was written with the xml2rfc tool described in 209 [RFC2629]. 211 6. References 212 6.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 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 219 Specifications: ABNF", STD 68, RFC 5234, January 2008. 221 [RFC5928] Petit-Huguenin, M., "Traversal Using Relays around NAT 222 (TURN) Resolution Mechanism", RFC 5928, August 2010. 224 6.2. Informative References 226 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 227 June 1999. 229 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 230 Registration Procedures for New URI Schemes", BCP 35, 231 RFC 4395, February 2006. 233 Appendix A. Release notes 235 This section must be removed before publication as an RFC. 237 A.1. Modifications between petithuguenin-03 and petithuguenin-02 239 o Updated RFC references. 241 A.2. Modifications between petithuguenin-02 and petithuguenin-01 243 o Nits. 245 A.3. Modifications between petithuguenin-01 and petithuguenin-00 247 o Shorten I-D references. 249 A.4. Design Notes 251 o is not used in the URIs because it is deprecated. 252 is not used in the URIs because it is not used to guide 253 the resolution mechanism. 254 o As discussed in Dublin, there is no generic parameters in the URI 255 to prevent compatibity issues. 257 A.5. Running Code Considerations 259 o Reference Implementation of TURN URI parser and resolver 260 (). Marc Petit- 261 Huguenin. Implements version -00 263 A.6. TODO List 265 (Empty) 267 Author's Address 269 Marc Petit-Huguenin 270 Unaffiliated 272 Email: petithug@acm.org