idnits 2.17.1 draft-petithuguenin-behave-turn-uri-bis-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 (January 13, 2010) is 5209 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-10) exists of draft-ietf-behave-turn-uri-06 -- 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: 2 errors (**), 0 flaws (~~), 2 warnings (==), 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 13, 2010 5 Expires: July 17, 2010 7 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers 8 draft-petithuguenin-behave-turn-uri-bis-01 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 to IETF 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), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 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 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on July 17, 2010. 39 Copyright Notice 41 Copyright (c) 2010 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Syntax of a TURN or TURNS URI . . . . . . . . . . . . . . . . . 3 58 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 60 4.1. TURN URI Registration . . . . . . . . . . . . . . . . . . . 4 61 4.2. TURNS URI Registration . . . . . . . . . . . . . . . . . . 5 62 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 63 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 64 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 65 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 66 Appendix A. Release notes . . . . . . . . . . . . . . . . . . . . 6 67 A.1. Modifications between petithuguenin-01 and 68 petithuguenin-00 . . . . . . . . . . . . . . . . . . . . . 6 69 A.2. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 6 70 A.3. Running Code Considerations . . . . . . . . . . . . . . . . 6 71 A.4. TODO List . . . . . . . . . . . . . . . . . . . . . . . . . 7 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 1. Introduction 76 [TURN-RESOLV] defines a resolution mechanism to convert a secure 77 flag, an host name or IP address, a eventually empty port, and an 78 eventually empty transport to a list of IP address, port and TURN 79 transport tuples. 81 To simplify the provisioning of TURN clients, this document defines a 82 TURN and a TURNS URI scheme that can carry the four components needed 83 for the resolution mechanism. 85 2. Syntax of a TURN or TURNS URI 87 A TURN/TURNS URI has the following ABNF syntax [RFC5234]: 89 turnURI = scheme ":" turn-host [ ":" turn-port ] 90 [ "?transport=" transport ] 91 scheme = "turn" / "turns" 92 transport = "udp" / "tcp" / transport-ext 93 transport-ext = 1*unreserved 94 turn-host = IP-literal / IPv4address / reg-name 95 turn-port = *DIGIT 96 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 97 IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) 98 IPv6address = 6( h16 ":" ) ls32 99 / "::" 5( h16 ":" ) ls32 100 / [ h16 ] "::" 4( h16 ":" ) ls32 101 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 102 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 103 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 104 / [ *4( h16 ":" ) h16 ] "::" ls32 105 / [ *5( h16 ":" ) h16 ] "::" h16 106 / [ *6( h16 ":" ) h16 ] "::" 107 h16 = 1*4HEXDIG 108 ls32 = ( h16 ":" h16 ) / IPv4address 109 IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet 110 dec-octet = DIGIT ; 0-9 111 / %x31-39 DIGIT ; 10-99 112 / "1" 2DIGIT ; 100-199 113 / "2" %x30-34 DIGIT ; 200-249 114 / "25" %x30-35 ; 250-255 115 reg-name = *( unreserved / pct-encoded / sub-delims ) 117 , and are specified in 118 [RFC3986]. 120 is equal to false is is equal to "turn" and equal 121 to false if is equal to "turns". 123 3. Security Considerations 125 Security considerations for the resolution mechanism are discussed in 126 [TURN-RESOLV]. 128 The "turn" and "turns" URI schemes do not introduce any specific 129 security issues beyond the security considerations discussed in 130 [RFC3986]. 132 4. IANA Considerations 134 This section contains the registration information for the "turn" and 135 "turns" URI Schemes (in accordance with [RFC4395]). 137 4.1. TURN URI Registration 139 URI scheme name: turn 141 Status: permanent 143 URI scheme syntax: See Section 2. 145 URI scheme semantics: See [TURN-RESOLV]. 147 Encoding considerations: There are no encoding considerations beyond 148 those in [RFC3986]. 150 Applications/protocols that use this URI scheme name: 152 The "turn" URI scheme is intended to be used by applications that 153 might need access to a TURN server. 155 Interoperability considerations: N/A 157 Security considerations: See Section 3. 159 Contact: Marc Petit-Huguenin 161 Author/Change controller: Marc Petit-Huguenin 163 References: This document. 165 [Note to RFC Editor: Replace "This document" with reference to this 166 document] 168 4.2. TURNS URI Registration 170 URI scheme name: turns 172 Status: permanent 174 URI scheme syntax: See Section 2. 176 URI scheme semantics: See [TURN-RESOLV]. 178 Encoding considerations: There are no encoding considerations beyond 179 those in [RFC3986]. 181 Applications/protocols that use this URI scheme name: 183 The "turns" URI scheme is intended to be used by applications that 184 might need access to a TURN server. 186 Interoperability considerations: N/A 188 Security considerations: See Section 3. 190 Contact: Marc Petit-Huguenin 192 Author/Change controller: Marc Petit-Huguenin 194 References: This document. 196 [Note to RFC Editor: Replace "This document" with reference to this 197 document] 199 5. Acknowledgements 201 Thanks to Margaret Wasserman, Magnus Westerlund, Juergen 202 Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. 203 Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes and Jim Kleck for 204 their comments, suggestions and questions that helped to improve this 205 document. 207 The and ABNF productions have been copied 208 from the and ABNF productions from [RFC3986]. 210 This document was written with the xml2rfc tool described in 211 [RFC2629]. 213 6. References 214 6.1. Normative References 216 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 217 Resource Identifier (URI): Generic Syntax", STD 66, 218 RFC 3986, January 2005. 220 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 221 Specifications: ABNF", STD 68, RFC 5234, January 2008. 223 [TURN-RESOLV] 224 Petit-Huguenin, M., "Traversal Using Relays around NAT 225 (TURN) Resolution Mechanism", 226 draft-ietf-behave-turn-uri-06 (work in progress), 227 January 2010. 229 6.2. Informative References 231 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 232 June 1999. 234 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 235 Registration Procedures for New URI Schemes", BCP 35, 236 RFC 4395, February 2006. 238 Appendix A. Release notes 240 This section must be removed before publication as an RFC. 242 A.1. Modifications between petithuguenin-01 and petithuguenin-00 244 o Shorten I-D references. 246 A.2. 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.3. Running Code Considerations 256 o Reference Implementation of TURN URI parser and resolver 257 (). Marc Petit- 258 Huguenin. Implements version -00 260 A.4. TODO List 262 (Empty) 264 Author's Address 266 Marc Petit-Huguenin 267 (Unaffiliated) 269 Email: petithug@acm.org