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

IETF · RFC · RFC3519

RFC3519 · Mobile IP Traversal of Network Address Translation (NAT) Devices

Mobile IP Traversal of Network Address Translation (NAT) Devices

Mobile IP's datagram tunnelling is incompatible with Network Address Translation (NAT). This document presents extensions to the Mobile IP protocol and a tunnelling method which permits mobile nodes using Mobile IP to operate in private address networks which are separated from the public internet by NAT devices. The NAT traversal is based on using the Mobile IP Home Agent UDP port for encapsulated data traffic. [STANDARDS-TRACK]

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

Mobile IP's datagram tunnelling is incompatible with Network Address Translation (NAT). This document presents extensions to the Mobile IP protocol and a tunnelling method which permits mobile nodes using Mobile IP to operate in private address networks which are separated from the public internet by NAT devices. The NAT traversal is based on using the Mobile IP Home Agent UDP port for encapsulated data traffic. [STANDARDS-TRACK]

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

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

Полные импортированные сведения карточки
{
  "id": "RFC3519",
  "number": 3519,
  "title_en": "Mobile IP Traversal of Network Address Translation (NAT) Devices",
  "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": "Mobile IP's datagram tunnelling is incompatible with Network Address Translation (NAT). This document presents extensions to the Mobile IP protocol and a tunnelling method which permits mobile nodes using Mobile IP to operate in private address networks which are separated from the public internet by NAT devices. The NAT traversal is based on using the Mobile IP Home Agent UDP port for encapsulated data traffic. [STANDARDS-TRACK]",
  "authors": [
    "H. Levkowetz",
    "S. Vaarala"
  ],
  "organizations": [],
  "publication_date": "2003-05-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": "int",
  "area_ru": "Интернет",
  "working_group": "mobileip",
  "source_draft": "draft-ietf-mobileip-nat-traversal-07",
  "page_count": 34,
  "doi": "10.17487/RFC3519",
  "keywords": [
    "Internet Protocol",
    "datagram",
    "traffic",
    "Mobile IP",
    "NAT",
    "NAPT",
    "traversal",
    "tunnelling",
    "tunneling",
    "UDP",
    "private address space",
    "keepalives",
    "port 434",
    "MIP",
    "MIPv4",
    "network address translation"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3519/",
    "html": "https://www.rfc-editor.org/rfc/rfc3519.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3519.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3519/"
  }
}