Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
RFC 7065
Document | Type |
RFC - Proposed Standard
(November 2013; No errata)
Was draft-petithuguenin-behave-turn-uris (individual in rai area)
|
|
---|---|---|---|
Authors | Marc Petit-Huguenin , Suhas Nandakumar , Gonzalo Salgueiro , Paul Jones | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Dan Wing | ||
Shepherd write-up | Show (last changed 2013-09-16) | ||
IESG | IESG state | RFC 7065 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Gonzalo Camarillo | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) M. Petit-Huguenin Request for Comments: 7065 Impedance Mismatch Category: Standards Track S. Nandakumar ISSN: 2070-1721 G. Salgueiro P. Jones Cisco Systems November 2013 Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers Abstract 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). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7065. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Petit-Huguenin, et al. Standards Track [Page 1] RFC 7065 TURN URIs November 2013 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Definitions of the "turn" and "turns" URI . . . . . . . . . . 4 3.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 4 3.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5.1. "turn" URI Registration . . . . . . . . . . . . . . . . . 5 5.2. "turns" URI Registration . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . 7 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 8 Appendix B. Design Notes . . . . . . . . . . . . . . . . . . . . 8 Petit-Huguenin, et al. Standards Track [Page 2] RFC 7065 TURN URIs November 2013 1. Introduction 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 [RFC5766] 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 [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. [RFC5928] defines a resolution mechanism to convert a secure flag, a host name or IP address, a potentially empty port, and a potentiallyShow full document text