Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers(Unaffiliated)petithug@acm.orgThis document defines two URI schemes that can be used to provision the configuration values needed by the resolution mechanism defined in . defines a resolution mechanism to convert a secure flag, an host name or IP address, a eventually empty port, and an eventually empty transport to a list of IP address, port and TURN transport tuples.To simplify the provisioning of TURN clients, this document defines a TURN and a TURNS URI scheme that can carry the four components needed for the resolution mechanism.A TURN/TURNS URI has the following ABNF syntax :<unreserved>, <sub-delims> and <pct-encoded> are specified in .<secure> is equal to false is <scheme> is equal to "turn" and equal to false if <scheme> is equal to "turns".Security considerations for the resolution mechanism are discussed in .The "turn" and "turns" URI schemes do not introduce any specific security issues beyond the security considerations discussed in .This section contains the registration information for the "turn" and "turns" URI Schemes (in accordance with ).URI scheme name: turnStatus: permanentURI scheme syntax: See .URI scheme semantics: See .Encoding considerations: There are no encoding considerations beyond those in .Applications/protocols that use this URI scheme name:The "turn" URI scheme is intended to be used by applications that might need access to a TURN server.Interoperability considerations: N/ASecurity considerations: See .Contact: Marc Petit-Huguenin <petithug@acm.org>Author/Change controller: Marc Petit-Huguenin <petithug@acm.org>References: This document.URI scheme name: turnsStatus: permanentURI scheme syntax: See .URI scheme semantics: See .Encoding considerations: There are no encoding considerations beyond those in .Applications/protocols that use this URI scheme name:The "turns" URI scheme is intended to be used by applications that might need access to a TURN server.Interoperability considerations: N/ASecurity considerations: See .Contact: Marc Petit-Huguenin <petithug@acm.org>Author/Change controller: Marc Petit-Huguenin <petithug@acm.org>References: This document.Thanks to Margaret Wasserman, Magnus Westerlund, Juergen Schoenwaelder, Sean Turner, Ted Hardie, Dave Thaler, Alfred E. Heggestad, Eilon Yardeni, Dan Wing, Alfred Hoenes and Jim Kleck for their comments, suggestions and questions that helped to improve this document.The <turn-port> and <turn-host> ABNF productions have been copied from the <port> and <host> ABNF productions from .This document was written with the xml2rfc tool described in .Uniform Resource Identifier (URI): Generic SyntaxWorld Wide Web ConsortiumMassachusetts Institute of Technology77 Massachusetts AvenueCambridgeMA02139USA+1-617-253-5702+1-617-258-5999timbl@w3.orghttp://www.w3.org/People/Berners-Lee/Day Software5251 California Ave., Suite 110IrvineCA92617USA+1-949-679-2960+1-949-679-2972fielding@gbiv.comhttp://roy.gbiv.com/Adobe Systems Incorporated345 Park AveSan JoseCA95110USA+1-408-536-3024LMM@acm.orghttp://larry.masinter.net/
Applications
uniform resource identifierURIURLURNWWWresource
A Uniform Resource Identifier (URI) is a compact sequence of characters
that identifies an abstract or physical resource. This specification
defines the generic URI syntax and a process for resolving URI references
that might be in relative form, along with guidelines and security
considerations for the use of URIs on the Internet.
The URI syntax defines a grammar that is a superset of all valid URIs,
allowing an implementation to parse the common components of a URI
reference without knowing the scheme-specific requirements of every
possible identifier. This specification does not define a generative
grammar for URIs; that task is performed by the individual
specifications of each URI scheme.
Augmented BNF for Syntax Specifications: ABNFInternet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS TRACK]Traversal Using Relays around NAT (TURN) Resolution MechanismThis document defines a resolution mechanism to generate a list of server transport addresses that can be tried to create a Traversal Using Relays around NAT (TURN) allocation.Writing I-Ds and RFCs using XMLInvisible Worlds, Inc.660 York StreetSan FranciscoCA94110US+1 415 695 3975mrose@not.invisible.nethttp://invisible.net/
General
RFCRequest for CommentsI-DInternet-DraftXMLExtensible Markup LanguageThis memo presents a technique for using XML
(Extensible Markup Language)
as a source format for documents in the Internet-Drafts (I-Ds) and
Request for Comments (RFC) series.Guidelines and Registration Procedures for New URI SchemesThis document provides guidelines and recommendations for the definition of Uniform Resource Identifier (URI) schemes. It also updates the process and IANA registry for URI schemes. It obsoletes both RFC 2717 and RFC 2718. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.This section must be removed before publication as an RFC.
<password> is not used in the URIs because it is deprecated.
<username> is not used in the URIs because it is not used to guide the resolution mechanism.
As discussed in Dublin, there is no generic parameters in the URI to prevent compatibity issues.
Reference Implementation of TURN URI parser and resolver (<http://ietf.implementers.org/turn-uri-0.3.zip>).
Marc Petit-Huguenin.
Implements version -00
(Empty)