RFC 8016: Mobility with Traversal Using Relays around NAT (TURN)
In plain English — editorial summary, not part of the RFC
It is desirable to minimize traffic disruption caused by changing IP address during a mobility event. One mechanism to minimize disruption is to expose a shorter network path to the mobility event so that only the local network elements are aware of the changed IP address and the remote peer is unaware of the changed IP address. This document provides such an IP address mobility solution using Traversal Using Relays around NAT (TURN). This is achieved by allowing a client to retain an allocation on the TURN server when the IP address of the client changes.
Document record
- Document ID
- RFC8016
- Published
- November 2016
- Authors
- T. Reddy; D. Wing; P. Patil; P. Martinsen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 9392Sending RTP Control Protocol (RTCP) Feedback for Congestion Control in Interactive Multimedia ConferencesCurrent
April 2023
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?