Traversal Using Relays around NAT Extensions for TCP Allocations
RFC 6062, “Traversal Using Relays around NAT Extensions for TCP Allocations”, is a Proposed Standard document published in November 2010 by S. Perreault, J. Rosenberg. The canonical text is published by the RFC Editor.
Abstract
This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for Network Address Translator (NAT) traversal. This extension allows a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client\'s peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general-purpose servers from ports obtained from the TURN server. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6062 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6063 Dynamic Symmetric Key Provisioning Protocol
- RFC 6059 Simple Procedures for Detecting Network Attachment in IPv6
- RFC 6065 Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group Mappings
- RFC 6057 Comcast's Protocol-Agnostic Congestion Management System
- RFC 6067 BCP 47 Extension U
- RFC 6068 The 'mailto' URI Scheme
- RFC 6069 Making TCP More Robust to Long Connectivity Disruptions
- RFC 6054 Using Counter Modes with Encapsulating Security Payload and Authentication Header to Protect Group Traffic