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

IETF · RFC · RFC8683

RFC8683 · Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks

Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks

This document describes how Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64) (including 464XLAT) can be deployed in an IPv6 network -- whether it's cellular ISP, broadband ISP, or enterprise -- and the possible optimizations. This document also discusses issues to be considered when having IPv6-only connectivity, such as: a) DNS64, b) applications or devices that use literal IPv4 addresses or non-IPv6-compliant APIs, and c) IPv4-only hosts or applications.

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

This document describes how Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64) (including 464XLAT) can be deployed in an IPv6 network -- whether it's cellular ISP, broadband ISP, or enterprise -- and the possible optimizations. This document also discusses issues to be considered when having IPv6-only connectivity, such as: a) DNS64, b) applications or devices that use literal IPv4 addresses or non-IPv6-compliant APIs, and c) IPv4-only hosts or applications.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8683",
  "number": 8683,
  "title_en": "Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks",
  "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": "This document describes how Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64) (including 464XLAT) can be deployed in an IPv6 network -- whether it's cellular ISP, broadband ISP, or enterprise -- and the possible optimizations. This document also discusses issues to be considered when having IPv6-only connectivity, such as: a) DNS64, b) applications or devices that use literal IPv4 addresses or non-IPv6-compliant APIs, and c) IPv4-only hosts or applications.",
  "authors": [
    "J. Palet Martinez"
  ],
  "organizations": [],
  "publication_date": "2019-11-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "v6ops",
  "source_draft": "draft-ietf-v6ops-nat64-deployment-08",
  "page_count": 38,
  "doi": "10.17487/RFC8683",
  "keywords": [
    "IPv6",
    "DNSSEC",
    "NAT64",
    "DNS64",
    "464XLAT",
    "CLAT",
    "NAT46",
    "PLAT"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8683/",
    "html": "https://www.rfc-editor.org/rfc/rfc8683.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8683.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8683/"
  }
}