Traversal Using Relays around NAT (TURN) Server Auto Discovery
RFC 8155
Document | Type |
RFC - Proposed Standard
(April 2017; No errata)
Updates RFC 5766
|
|
---|---|---|---|
Last updated | 2018-12-20 | ||
Replaces | draft-patil-tram-turn-serv-disc | ||
Stream | IETF | ||
Formats | plain text pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Simon Perreault | ||
Shepherd write-up | Show (last changed 2016-07-13) | ||
IESG | IESG state | RFC 8155 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Spencer Dawkins | ||
Send notices to | "Simon Perreault" <sperreault@jive.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) P. Patil Request for Comments: 8155 T. Reddy Updates: 5766 Cisco Category: Standards Track D. Wing ISSN: 2070-1721 April 2017 Traversal Using Relays around NAT (TURN) Server Auto Discovery Abstract Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration. These are usually under the administrative control of the application or TURN service provider, and not the enterprise, ISP, or the network in which the client is located. Enterprises and ISPs wishing to provide their own TURN servers need auto-discovery mechanisms that a TURN client could use with minimal or no configuration. This document describes three such mechanisms for TURN server discovery. This document updates RFC 5766 to relax the requirement for mutual authentication in certain cases. 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 7841. 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/rfc8155. Patil, et al. Standards Track [Page 1] RFC 8155 TURN Server Auto Discovery April 2017 Copyright Notice Copyright (c) 2017 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Discovery Procedure . . . . . . . . . . . . . . . . . . . . . 4 4. Discovery Using Service Resolution . . . . . . . . . . . . . 5 4.1. Retrieving Domain Name . . . . . . . . . . . . . . . . . 5 4.1.1. DHCP . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1.2. From Own Identity . . . . . . . . . . . . . . . . . . 6 4.2. Resolution . . . . . . . . . . . . . . . . . . . . . . . 6 5. DNS Service Discovery . . . . . . . . . . . . . . . . . . . . 6 5.1. mDNS . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Discovery Using Anycast . . . . . . . . . . . . . . . . . . . 7 7. Deployment Considerations . . . . . . . . . . . . . . . . . . 8 7.1. Mobility and Changing IP Addresses . . . . . . . . . . . 8 7.2. Recursively Encapsulated TURN . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8.1. IPv4 Anycast . . . . . . . . . . . . . . . . . . . . . . 9 8.2. IPv6 Anycast . . . . . . . . . . . . . . . . . . . . . . 9 9. Security Considerations . . . . . . . . . . . . . . . . . . . 10 9.1. Service Resolution . . . . . . . . . . . . . . . . . . . 12 9.2. DNS Service Discovery . . . . . . . . . . . . . . . . . . 12 9.3. Anycast . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 15 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Patil, et al. Standards Track [Page 2] RFC 8155 TURN Server Auto Discovery April 2017 1. Introduction TURN [RFC5766] is a protocol that is often used to improve the connectivity of Peer-to-Peer (P2P) applications (as defined in Section 2.7 of [RFC5128]). TURN allows a connection to be established when one or both sides are incapable of a direct P2P connection. It is an important building block for interactive, real- time communication using audio, video, collaboration, etc.Show full document text