⌕ Поиск по атласу

IETF · RFC · RFC8016

RFC8016 · Mobility with Traversal Using Relays around NAT (TURN)

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.

Официальная английская аннотация

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-01

Полные импортированные сведения карточки
{
  "id": "RFC8016",
  "number": 8016,
  "title_en": "Mobility with Traversal Using Relays around NAT (TURN)",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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.",
  "authors": [
    "T. Reddy",
    "D. Wing",
    "P. Patil",
    "P. Martinsen"
  ],
  "organizations": [],
  "publication_date": "2016-11-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "tsv",
  "area_ru": "Транспорт",
  "working_group": "tram",
  "source_draft": "draft-ietf-tram-turn-mobility-09",
  "page_count": 13,
  "doi": "10.17487/RFC8016",
  "keywords": [
    "IP Address Mobility",
    "VoIP",
    "ICE",
    "STUN",
    "RTP",
    "TUNNEL"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8016/",
    "html": "https://www.rfc-editor.org/rfc/rfc8016.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8016.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8016/"
  }
}