{
  "number": 8016,
  "title": "Mobility with Traversal Using Relays around NAT (TURN)",
  "authors": [
    "T. Reddy",
    "D. Wing",
    "P. Patil",
    "P. Martinsen"
  ],
  "published": "2016-11",
  "status": "Proposed Standard",
  "stream": "IETF",
  "area": "tsv",
  "working_group": "tram",
  "pages": 13,
  "formats": [
    "TXT",
    "HTML"
  ],
  "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.\n\nThis 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.",
  "keywords": [
    "IP Address Mobility",
    "VoIP",
    "ICE",
    "STUN",
    "RTP",
    "TUNNEL"
  ],
  "draft": "draft-ietf-tram-turn-mobility-09",
  "doi": "10.17487/RFC8016",
  "errata_url": "https://www.rfc-editor.org/errata/rfc8016",
  "urls": {
    "html": "https://rfc.dk/rfc8016/",
    "text": "https://rfc.dk/rfc8016.txt",
    "rfc_editor": "https://www.rfc-editor.org/rfc/rfc8016",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8016/"
  },
  "text_modified": "2016-11-10T21:39:44.948403392Z"
}