idnits 2.17.1 draft-petithuguenin-behave-turn-uri-bis-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. 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 ([I-D.ietf-behave-turn-uri]), 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 (November 25, 2009) is 5265 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-05 -- 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 November 25, 2009 5 Expires: May 29, 2010 7 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers 8 draft-petithuguenin-behave-turn-uri-bis-00 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on May 29, 2010. 33 Copyright Notice 35 Copyright (c) 2009 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 in effect on the date of 40 publication of this document (http://trustee.ietf.org/license-info). 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. 44 Abstract 46 This document defines two URI schemes that can be used to provision 47 the configuration values needed by the resolution mechanism defined 48 in [I-D.ietf-behave-turn-uri]. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Syntax of a TURN or TURNS URI . . . . . . . . . . . . . . . . . 3 54 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 55 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 56 4.1. TURN URI Registration . . . . . . . . . . . . . . . . . . . 4 57 4.2. TURNS URI Registration . . . . . . . . . . . . . . . . . . 5 58 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 61 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 62 Appendix A. Release notes . . . . . . . . . . . . . . . . . . . . 6 63 A.1. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 6 64 A.2. Running Code Considerations . . . . . . . . . . . . . . . . 6 65 A.3. TODO List . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 68 1. Introduction 70 [I-D.ietf-behave-turn-uri] defines a resolution mechanism to convert 71 a secure flag, an host name or IP address, a eventually empty port, 72 and an eventually empty transport to a list of IP address, port and 73 TURN transport tuples. 75 To simplify the provisioning of TURN clients, this document defines a 76 TURN and a TURNS URI scheme that can carry the four components needed 77 for the resolution mechanism. 79 2. Syntax of a TURN or TURNS URI 81 A TURN/TURNS URI has the following ABNF syntax [RFC5234]: 83 turnURI = scheme ":" turn-host [ ":" turn-port ] 84 [ "?transport=" transport ] 85 scheme = "turn" / "turns" 86 transport = "udp" / "tcp" / transport-ext 87 transport-ext = 1*unreserved 88 turn-host = IP-literal / IPv4address / reg-name 89 turn-port = *DIGIT 90 IP-literal = "[" ( IPv6address / IPvFuture ) "]" 91 IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) 92 IPv6address = 6( h16 ":" ) ls32 93 / "::" 5( h16 ":" ) ls32 94 / [ h16 ] "::" 4( h16 ":" ) ls32 95 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 96 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 97 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 98 / [ *4( h16 ":" ) h16 ] "::" ls32 99 / [ *5( h16 ":" ) h16 ] "::" h16 100 / [ *6( h16 ":" ) h16 ] "::" 101 h16 = 1*4HEXDIG 102 ls32 = ( h16 ":" h16 ) / IPv4address 103 IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet 104 dec-octet = DIGIT ; 0-9 105 / %x31-39 DIGIT ; 10-99 106 / "1" 2DIGIT ; 100-199 107 / "2" %x30-34 DIGIT ; 200-249 108 / "25" %x30-35 ; 250-255 109 reg-name = *( unreserved / pct-encoded / sub-delims ) 111 , and are specified in 112 [RFC3986]. 114 is equal to false is is equal to "turn" and equal 115 to false if is equal to "turns". 117 3. Security Considerations 119 Security considerations for the resolution mechanism are discussed in 120 [I-D.ietf-behave-turn-uri]. 122 The "turn" and "turns" URI schemes do not introduce any specific 123 security issues beyond the security considerations discussed in 124 [RFC3986]. 126 4. IANA Considerations 128 This section contains the registration information for the "turn" and 129 "turns" URI Schemes (in accordance with [RFC4395]). 131 4.1. TURN URI Registration 133 URI scheme name: turn 135 Status: permanent 137 URI scheme syntax: See Section 2. 139 URI scheme semantics: See [I-D.ietf-behave-turn-uri]. 141 Encoding considerations: There are no encoding considerations beyond 142 those in [RFC3986]. 144 Applications/protocols that use this URI scheme name: 146 The "turn" URI scheme is intended to be used by applications that 147 might need access to a TURN server. 149 Interoperability considerations: N/A 151 Security considerations: See Section 3. 153 Contact: Marc Petit-Huguenin 155 Author/Change controller: Marc Petit-Huguenin 157 References: This document. 159 4.2. TURNS URI Registration 161 URI scheme name: turns 163 Status: permanent 165 URI scheme syntax: See Section 2. 167 URI scheme semantics: See [I-D.ietf-behave-turn-uri]. 169 Encoding considerations: There are no encoding considerations beyond 170 those in [RFC3986]. 172 Applications/protocols that use this URI scheme name: 174 The "turns" URI scheme is intended to be used by applications that 175 might need access to a TURN server. 177 Interoperability considerations: N/A 179 Security considerations: See Section 3. 181 Contact: Marc Petit-Huguenin 183 Author/Change controller: Marc Petit-Huguenin 185 References: This document. 187 5. Acknowledgements 189 Thanks to Margaret Wasserman, Magnus Westerlund, Juergen 190 Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. 191 Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes and Jim Kleck for 192 their comments, suggestions and questions that helped to improve this 193 document. 195 The and ABNF productions have been copied 196 from the and ABNF productions from [RFC3986]. 198 This document was written with the xml2rfc tool described in 199 [RFC2629]. 201 6. References 202 6.1. Normative References 204 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 205 Resource Identifier (URI): Generic Syntax", STD 66, 206 RFC 3986, January 2005. 208 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 209 Specifications: ABNF", STD 68, RFC 5234, January 2008. 211 [I-D.ietf-behave-turn-uri] 212 Petit-Huguenin, M., "Traversal Using Relays around NAT 213 (TURN) Resolution Mechanism", 214 draft-ietf-behave-turn-uri-05 (work in progress), 215 November 2009. 217 6.2. Informative References 219 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 220 June 1999. 222 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 223 Registration Procedures for New URI Schemes", BCP 35, 224 RFC 4395, February 2006. 226 Appendix A. Release notes 228 This section must be removed before publication as an RFC. 230 A.1. Design Notes 232 o is not used in the URIs because it is deprecated. 233 is not used in the URIs because it is not used to guide 234 the resolution mechanism. 235 o As discussed in Dublin, there is no generic parameters in the URI 236 to prevent compatibity issues. 238 A.2. Running Code Considerations 240 o Reference Implementation of TURN URI parser and resolver 241 (). Marc Petit- 242 Huguenin. Implements version -00 244 A.3. TODO List 246 (Empty) 248 Author's Address 250 Marc Petit-Huguenin 251 (Unaffiliated) 253 Email: petithug@acm.org