Browse Prior Art Database

Mobility with Traversal Using Relays around NAT (TURN) (RFC8016) Disclosure Number: IPCOM000248253D
Original Publication Date: 2016-Nov-01
Included in the Prior Art Database: 2016-Nov-11
Document File: 26 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Reddy: AUTHOR [+3]


When moving between networks, the endpoint's IP address can change or, due to NAT, the endpoint's public IP address can change. Such a change of IP address breaks upper-layer protocols such as TCP and RTP. Various techniques exist to prevent this breakage, all tied to making the endpoint's IP address static (e.g., Mobile IP, Proxy Mobile IP, Locator/ID Separation Protocol (LISP)). Other techniques exist, which make the change in IP address agnostic to the upper- layer protocol (e.g., Stream Control Transmission Protocol (SCTP)). The mechanism described in this document is in that last category.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                          T. Reddy Request for Comments: 8016                                         Cisco Category: Standards Track                                        D. Wing ISSN: 2070-1721                                                                 P. Patil                                                             P. Martinsen                                                                    Cisco                                                            November 2016

          Mobility with Traversal Using Relays around NAT (TURN)


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Reddy, et al.                Standards Track                    [Page 1]
 RFC 8016                   Mobility with TURN              November 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described i...