Mobility with TURN
draft-wing-tram-turn-mobility-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Dan Wing , Prashanth Patil , Tirumaleswar Reddy.K , Paal-Erik Martinsen | ||
Last updated | 2015-11-07 (Latest revision 2015-05-06) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 only the local network elements are aware of the changed IP address but the remote peer is unaware of the changed IP address. This draft 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.
Authors
Dan Wing
Prashanth Patil
Tirumaleswar Reddy.K
Paal-Erik Martinsen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)