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

IETF · RFC · RFC7050

RFC7050 · Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis

Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis

This document describes a method for detecting the presence of DNS64 and for learning the IPv6 prefix used for protocol translation on an access network. The method depends on the existence of a well-known IPv4-only fully qualified domain name "ipv4only.arpa.". The information learned enables nodes to perform local IPv6 address synthesis and to potentially avoid NAT64 on dual-stack and multi-interface deployments.

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

This document describes a method for detecting the presence of DNS64 and for learning the IPv6 prefix used for protocol translation on an access network. The method depends on the existence of a well-known IPv4-only fully qualified domain name "ipv4only.arpa.". The information learned enables nodes to perform local IPv6 address synthesis and to potentially avoid NAT64 on dual-stack and multi-interface deployments.

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

updated_by: RFC8880

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

Полные импортированные сведения карточки
{
  "id": "RFC7050",
  "number": 7050,
  "title_en": "Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis",
  "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 a method for detecting the presence of DNS64 and for learning the IPv6 prefix used for protocol translation on an access network. The method depends on the existence of a well-known IPv4-only fully qualified domain name \"ipv4only.arpa.\". The information learned enables nodes to perform local IPv6 address synthesis and to potentially avoid NAT64 on dual-stack and multi-interface deployments.",
  "authors": [
    "T. Savolainen",
    "J. Korhonen",
    "D. Wing"
  ],
  "organizations": [],
  "publication_date": "2013-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": "behave",
  "source_draft": "draft-ietf-behave-nat64-discovery-heuristic-17",
  "page_count": 22,
  "doi": "10.17487/RFC7050",
  "keywords": [
    "NAT64",
    "DNS64",
    "464XLAT",
    "Pref64::/n"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8880"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7050/",
    "html": "https://www.rfc-editor.org/rfc/rfc7050.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7050.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7050/"
  }
}