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

IETF · RFC · RFC6564

RFC6564 · A Uniform Format for IPv6 Extension Headers

A Uniform Format for IPv6 Extension Headers

In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the transport-layer header. There are a small number of such extension headers currently defined. This document describes the issues that can arise when defining new extension headers and discusses the alternate extension mechanisms in IPv6. It also provides a common format for defining any new IPv6 extension headers, if they are needed. [STANDARDS-TRACK]

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

In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the transport-layer header. There are a small number of such extension headers currently defined. This document describes the issues that can arise when defining new extension headers and discusses the alternate extension mechanisms in IPv6. It also provides a common format for defining any new IPv6 extension headers, if they are needed. [STANDARDS-TRACK]

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

updates: RFC2460

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

Полные импортированные сведения карточки
{
  "id": "RFC6564",
  "number": 6564,
  "title_en": "A Uniform Format for IPv6 Extension Headers",
  "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": "In IPv6, optional internet-layer information is encoded in separate headers that may be placed between the IPv6 header and the transport-layer header. There are a small number of such extension headers currently defined. This document describes the issues that can arise when defining new extension headers and discusses the alternate extension mechanisms in IPv6. It also provides a common format for defining any new IPv6 extension headers, if they are needed. [STANDARDS-TRACK]",
  "authors": [
    "S. Krishnan",
    "J. Woodyatt",
    "E. Kline",
    "J. Hoagland",
    "M. Bhatia"
  ],
  "organizations": [],
  "publication_date": "2012-04-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": "6man",
  "source_draft": "draft-ietf-6man-exthdr-06",
  "page_count": 6,
  "doi": "10.17487/RFC6564",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC2460"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6564/",
    "html": "https://www.rfc-editor.org/rfc/rfc6564.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6564.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6564/"
  }
}