RFC 8016

Mobility with Traversal Using Relays around NAT (TURN), November 2016

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Authors:
T. Reddy
D. Wing
P. Patil
P. Martinsen
Stream:
IETF
Source:
tram (tsv)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8016

Discuss this RFC: Send questions or comments to the mailing list tram@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8016


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search