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

IETF · RFC · RFC8489

RFC8489 · Session Traversal Utilities for NAT (STUN)

Session Traversal Utilities for NAT (STUN)

Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with NAT traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs and does not require any special behavior from them. STUN is not a NAT traversal solution by itself. Rather, it is a tool to be used in the context of a NAT traversal solution. This document obsoletes RFC 5389.

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

Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with NAT traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs and does not require any special behavior from them. STUN is not a NAT traversal solution by itself. Rather, it is a tool to be used in the context of a NAT traversal solution. This document obsoletes RFC 5389.

Связи документа

obsoletes: RFC5389

Официальный источник · 2020-02-01

Полные импортированные сведения карточки
{
  "id": "RFC8489",
  "number": 8489,
  "title_en": "Session Traversal Utilities for NAT (STUN)",
  "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": "Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with NAT traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs and does not require any special behavior from them. STUN is not a NAT traversal solution by itself. Rather, it is a tool to be used in the context of a NAT traversal solution. This document obsoletes RFC 5389.",
  "authors": [
    "M. Petit-Huguenin",
    "G. Salgueiro",
    "J. Rosenberg",
    "D. Wing",
    "R. Mahy",
    "P. Matthews"
  ],
  "organizations": [],
  "publication_date": "2020-02-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-stunbis-21",
  "page_count": 67,
  "doi": "10.17487/RFC8489",
  "keywords": [
    "SIPs"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC5389"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8489/",
    "html": "https://www.rfc-editor.org/rfc/rfc8489.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8489.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8489/"
  }
}