Skip to main content

Mobility with Traversal Using Relays around NAT (TURN)
RFC 8016

Revision differences

Document history

Date By Action
2023-04-13
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'It is desirable to minimize traffic disruption caused by changing IP address during a mobility event. …
Received changes through RFC Editor sync (changed abstract to '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.')
2016-11-10
(System)
Received changes through RFC Editor sync (created alias RFC 8016, changed title to 'Mobility with Traversal Using Relays around NAT (TURN)', changed abstract to …
Received changes through RFC Editor sync (created alias RFC 8016, changed title to 'Mobility with Traversal Using Relays around NAT (TURN)', changed abstract to '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.', changed pages to 13, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2016-11-10, changed IESG state to RFC Published)
2016-11-10
(System) RFC published