idnits 2.17.1 draft-petithuguenin-behave-turn-uri-bis-02.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 ([TURN-RESOLV]), 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, 2010) is 5037 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 July 10, 2010 5 Expires: January 11, 2011 7 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers 8 draft-petithuguenin-behave-turn-uri-bis-02 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 [TURN-RESOLV]. 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 January 11, 2011. 33 Copyright Notice 35 Copyright (c) 2010 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-02 and 62 petithuguenin-01 . . . . . . . . . . . . . . . . . . . . . 6 63 A.2. Modifications between petithuguenin-01 and 64 petithuguenin-00 . . . . . . . . . . . . . . . . . . . . . 6 65 A.3. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 6 66 A.4. Running Code Considerations . . . . . . . . . . . . . . . . 7 67 A.5. TODO List . . . . . . . . . . . . . . . . . . . . . . . . . 7 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 1. Introduction 72 [TURN-RESOLV] defines a resolution mechanism to convert a secure 73 flag, an host name or IP address, a eventually empty port, and an 74 eventually empty transport to a list of IP address, port, and TURN 75 transport tuples. 77 To simplify the provisioning of TURN clients, this document defines a 78 TURN and a TURNS URI scheme that can carry the four components needed 79 for the resolution mechanism. 81 2. Syntax of a TURN or TURNS URI 83 A TURN/TURNS URI has the following ABNF syntax [RFC5234]: 85 turnURI = scheme ":" turn-host [ ":" turn-port ] 86 [ "?transport=" transport ] 87 scheme = "turn" / "turns" 88 transport = "udp" / "tcp" / transport-ext 89 transport-ext = 1*unreserved 90 turn-host = IP-literal / IPv4address / reg-name 91 turn-port = *DIGIT 92 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 93 IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) 94 IPv6address = 6( h16 ":" ) ls32 95 / "::" 5( h16 ":" ) ls32 96 / [ h16 ] "::" 4( h16 ":" ) ls32 97 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 98 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 99 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 100 / [ *4( h16 ":" ) h16 ] "::" ls32 101 / [ *5( h16 ":" ) h16 ] "::" h16 102 / [ *6( h16 ":" ) h16 ] "::" 103 h16 = 1*4HEXDIG 104 ls32 = ( h16 ":" h16 ) / IPv4address 105 IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet 106 dec-octet = DIGIT ; 0-9 107 / %x31-39 DIGIT ; 10-99 108 / "1" 2DIGIT ; 100-199 109 / "2" %x30-34 DIGIT ; 200-249 110 / "25" %x30-35 ; 250-255 111 reg-name = *( unreserved / pct-encoded / sub-delims ) 113 , , and are specified in 114 [RFC3986]. 116 is equal to false is is equal to "turn" and equal 117 to false if is equal to "turns". 119 3. Security Considerations 121 Security considerations for the resolution mechanism are discussed in 122 [TURN-RESOLV]. 124 The "turn" and "turns" URI schemes do not introduce any specific 125 security issues beyond the security considerations discussed in 126 [RFC3986]. 128 4. IANA Considerations 130 This section contains the registration information for the "turn" and 131 "turns" URI Schemes (in accordance with [RFC4395]). 133 4.1. TURN URI Registration 135 URI scheme name: turn 137 Status: permanent 139 URI scheme syntax: See Section 2. 141 URI scheme semantics: See [TURN-RESOLV]. 143 Encoding considerations: There are no encoding considerations beyond 144 those in [RFC3986]. 146 Applications/protocols that use this URI scheme name: 148 The "turn" URI scheme is intended to be used by applications that 149 might need access to a TURN server. 151 Interoperability considerations: N/A 153 Security considerations: See Section 3. 155 Contact: Marc Petit-Huguenin 157 Author/Change controller: Marc Petit-Huguenin 159 References: This document. 161 [Note to RFC Editor: Replace "This document" with reference to this 162 document] 164 4.2. TURNS URI Registration 166 URI scheme name: turns 168 Status: permanent 170 URI scheme syntax: See Section 2. 172 URI scheme semantics: See [TURN-RESOLV]. 174 Encoding considerations: There are no encoding considerations beyond 175 those in [RFC3986]. 177 Applications/protocols that use this URI scheme name: 179 The "turns" URI scheme is intended to be used by applications that 180 might need access to a TURN server. 182 Interoperability considerations: N/A 184 Security considerations: See Section 3. 186 Contact: Marc Petit-Huguenin 188 Author/Change controller: Marc Petit-Huguenin 190 References: This document. 192 [Note to RFC Editor: Replace "This document" with reference to this 193 document] 195 5. Acknowledgements 197 Thanks to Margaret Wasserman, Magnus Westerlund, Juergen 198 Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. 199 Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes, and Jim Kleck for 200 their comments, suggestions and questions that helped to improve this 201 document. 203 The and ABNF productions have been copied 204 from the and ABNF productions from [RFC3986]. 206 This document was written with the xml2rfc tool described in 207 [RFC2629]. 209 6. References 210 6.1. Normative References 212 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 213 Resource Identifier (URI): Generic Syntax", STD 66, 214 RFC 3986, January 2005. 216 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 217 Specifications: ABNF", STD 68, RFC 5234, January 2008. 219 [TURN-RESOLV] 220 Petit-Huguenin, M., "Traversal Using Relays around NAT 221 (TURN) Resolution Mechanism", 222 draft-ietf-behave-turn-uri-10 (work in progress), 223 February 2010. 225 6.2. Informative References 227 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 228 June 1999. 230 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 231 Registration Procedures for New URI Schemes", BCP 35, 232 RFC 4395, February 2006. 234 Appendix A. Release notes 236 This section must be removed before publication as an RFC. 238 A.1. Modifications between petithuguenin-02 and petithuguenin-01 240 o Nits. 242 A.2. Modifications between petithuguenin-01 and petithuguenin-00 244 o Shorten I-D references. 246 A.3. Design Notes 248 o is not used in the URIs because it is deprecated. 249 is not used in the URIs because it is not used to guide 250 the resolution mechanism. 251 o As discussed in Dublin, there is no generic parameters in the URI 252 to prevent compatibity issues. 254 A.4. Running Code Considerations 256 o Reference Implementation of TURN URI parser and resolver 257 (). Marc Petit- 258 Huguenin. Implements version -00 260 A.5. TODO List 262 (Empty) 264 Author's Address 266 Marc Petit-Huguenin 267 Unaffiliated 269 Email: petithug@acm.org