Traversal Using Relays around NAT (TURN) Uniform Resource IdentifiersImpedance Mismatchpetithug@acm.orgCisco Systems170 West Tasman DriveSan JoseCA95134USsnandaku@cisco.comCisco Systems7200-12 Kit Creek RoadResearch Triangle ParkNC27709USgsalguei@cisco.comCisco Systems7025 Kit Creek RoadResearch Triangle ParkNC27709USpaulej@packetizer.com
TSV
BEHAVE
This document specifies the syntax of Uniform Resource Identifier (URI) schemes for the Traversal Using Relays around NAT (TURN) protocol.
It defines two URI schemes to
provision the TURN Resolution
Mechanism (RFC 5928).
This document specifies the syntax and semantics of the Uniform Resource Identifier (URI) scheme for the Traversal Using Relays around NAT (TURN) protocol.
The TURN protocol is a specification allowing hosts behind NAT to control the operation of a relay server.
The relay server allows hosts to exchange packets with its peers.
The peers themselves may also be behind NATs.
RFC 5766 defines the specifics of the TURN protocol.
The "turn" and "turns" URI schemes are used to designate a TURN server (also known as a relay) on Internet hosts accessible using the TURN protocol.
With the advent of standards such as WebRTC , we anticipate a plethora of endpoints and web applications to be able to identify and communicate with such a TURN server to carry out the TURN protocol.
This implies that endpoints and/or applications must be provisioned
with the appropriate configuration to identify the TURN server.
Having an inconsistent syntax adds ambiguity and can result in
non-interoperable solutions and
implementation limitations. The "turn" and "turns" URI schemes help
alleviate most of these issues by providing a consistent way to
describe, configure, and exchange the information identifying a TURN
server.
defines a resolution mechanism to convert a secure flag, a host name or IP address, a potentially empty port, and a potentially empty transport to a list of IP address, port, and TURN transport tuples.To simplify the provisioning of TURN clients, this document defines the "turn" and "turns" URI schemes that can carry the four components needed for the resolution mechanism.
The key words "MUST", "MUST NOT", "REQUIRED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in when they appear in ALL CAPS.
When these words are not in ALL CAPS (such as "should" or "Should"), they have their usual English meanings, and are not to be interpreted as RFC 2119 key words.
The "turn" and "turns" URIs have the following formal ABNF syntax :
<host> and <port> are specified in .
While these two ABNF productions are defined in as components of the generic hierarchical URI, this does not imply that the "turn" and "turns" schemes are hierarchical URIs.
Developers MUST NOT use a generic hierarchical URI parser to parse a "turn" or "turns" URI.
The <host>, <port>, and <transport> components are passed without modification to the algorithm.
<secure> is set to false if <scheme> is equal to "turn", and set to true if <scheme> is equal to "turns" and passed to the algorithm with the other components.
The "turn" and "turns" URI schemes are used to designate a TURN server (also known as a relay) on Internet hosts accessible using the TURN protocol.
The TURN protocol supports sending messages over UDP, TCP, or TLS-over-TCP.
The "turns" URI scheme MUST be used when TURN is run over TLS-over-TCP (or, in the future, DTLS-over-UDP), and the "turn" scheme MUST be used otherwise.
The required <host> part of the "turn" URI denotes the TURN server host.
As specified in and , the <port> part, if present, denotes the port on which the TURN server is awaiting connection requests.
If it is absent, the default port is 3478 for both UDP and TCP.
The default port for TURN over TLS is 5349.
Security considerations for the resolution mechanism are discussed in Section 5 of .
Note that this section contains normative text defining authentication procedures to be followed by turn clients when TLS is used.
The "turn" and "turns" URI schemes do not introduce any specific security issues beyond the security considerations discussed in .
Although a "turn" or "turns" URI does not itself include the username or password that will be used to authenticate the TURN client, in certain environments, such as WebRTC, the username and password will almost certainly be provisioned remotely by an external agent at the same time as a "turns" URI is sent to that client.
Thus, in such situations, if the
username and password were received in
the clear, there would be little or no benefit to using a "turns" URI.
For this reason, a TURN client MUST ensure that the username, password, "turns" URI, and any other security-relevant parameters are received with equivalent security before using the "turns" URI.
Receiving those parameters over another TLS session can provide the appropriate level of security, if both TLS sessions are similarly parameterised, e.g., with commensurate strength ciphersuites.
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 with a need to identify a TURN server to be used for NAT traversal.Interoperability considerations: N/ASecurity considerations: See .Contact: Marc Petit-Huguenin <petithug@acm.org>Author/Change controller: The IESGReferences: RFC 7065URI 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 with a need to identify a TURN server to be used for NAT traversal over a secure connection.Interoperability considerations: N/ASecurity considerations: See .Contact: Marc Petit-Huguenin <petithug@acm.org>Author/Change controller: The IESGReferences: RFC 7065Thanks 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 the comments,
suggestions, and questions that helped improve
"Traversal Using Relays around NAT (TURN) Uniform Resource
Identifiers" by M. Petit-Huguenin
(October 2011).
Many thanks to Cullen Jennings for his
detailed review and thoughtful comments on
"URI Scheme for Traversal Using Relays around
NAT (TURN) Protocol" by S. Nandakumar, et al. (October 2011).Thanks to Bjoern Hoehrmann, Dan Wing, Russ Housley, S. Moonesamy, Graham Klyne, Harald Alvestrand, Hadriel Kaplan, Tina Tsou, Spencer Dawkins, Ted Lemon, Barry Leiba, Pete Resnick, and Stephen Farrell for the comments, suggestions, and questions that helped improve this document.
The authors would also like to express their gratitude to Dan Wing for his assistance in shepherding this document.
We also want to thank Gonzalo
Camarillo, the Real-time Applications
and Infrastructure Area Director, for
sponsoring this document as well as his careful reviews.
Key words for use in RFCs to Indicate Requirement LevelsHarvard University1350 Mass. Ave.CambridgeMA 02138- +1 617 495 3864sob@harvard.edu
General
keyword
In many standards track documents several words are used to signify
the requirements in the specification. These words are often
capitalized. This document defines these words as they should be
interpreted in IETF documents. Authors who follow these guidelines
should incorporate this phrase near the beginning of their document:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119.
Note that the force of these words is modified by the requirement
level of the document in which they are used.
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: ABNFTraversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Traversal Using Relays around NAT (TURN) Resolution MechanismGuidelines and Registration Procedures for New URI SchemesWebRTC 1.0: Real-time Communication Between Browsers shows how the <secure>, <port>, and <transport> components are populated from various URIs.
For all these examples, the <host> component is populated with "example.org".
URI<secure><port><transport>turn:example.orgfalseturns:example.orgtrueturn:example.org:8000false8000turn:example.org?transport=udpfalseUDPturn:example.org?transport=tcpfalseTCPturns:example.org?transport=tcptrueTLS
One recurring comment
was to stop using the
suffix "s" on the URI scheme, and to move the secure option to a parameter (e.g. ";proto=tls").
We decided against this idea because the STUN URI does not have a ";proto=" parameter and we would have lost the symmetry between the TURN and STUN URIs.
Following the advice of Section 2.2
of RFC 4395, and because the TURN URI does not describe a hierarchical structure, the TURN URIs are opaque URIs.
<password> is not used in the URIs because it is deprecated .
<username> and <auth> are not used in the URIs because they do not guide the resolution mechanism.
As discussed at IETF 72 in Dublin, there are no generic parameters in the URI to prevent compatibility issues.