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

IETF · RFC · RFC4548

RFC4548 · Internet Code Point (ICP) Assignments for NSAP Addresses

Internet Code Point (ICP) Assignments for NSAP Addresses

This document is intended to accomplish two highly inter-related tasks: to establish an "initial" Internet Code Point (ICP) assignment for each of IPv4 and IPv6 address encoding in Network Service Access Point (NSAP) Addresses, and to recommend an IANA assignment policy for currently unassigned ICP values. In the first task, this document is a partial replacement for RFC 1888 -- particularly for section 6 of RFC 1888. In the second task, this document incorporates wording and specifications from ITU-T Recommendation X.213 and further recommends that IANA use the "IETF consensus" assignment policy in making future ICP assignments. [STANDARDS-TRACK]

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

This document is intended to accomplish two highly inter-related tasks: to establish an "initial" Internet Code Point (ICP) assignment for each of IPv4 and IPv6 address encoding in Network Service Access Point (NSAP) Addresses, and to recommend an IANA assignment policy for currently unassigned ICP values. In the first task, this document is a partial replacement for RFC 1888 -- particularly for section 6 of RFC 1888. In the second task, this document incorporates wording and specifications from ITU-T Recommendation X.213 and further recommends that IANA use the "IETF consensus" assignment policy in making future ICP assignments. [STANDARDS-TRACK]

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

updates: RFC1888, RFC4048

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

Полные импортированные сведения карточки
{
  "id": "RFC4548",
  "number": 4548,
  "title_en": "Internet Code Point (ICP) Assignments for NSAP Addresses",
  "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 is intended to accomplish two highly inter-related tasks: to establish an \"initial\" Internet Code Point (ICP) assignment for each of IPv4 and IPv6 address encoding in Network Service Access Point (NSAP) Addresses, and to recommend an IANA assignment policy for currently unassigned ICP values. In the first task, this document is a partial replacement for RFC 1888 -- particularly for section 6 of RFC 1888. In the second task, this document incorporates wording and specifications from ITU-T Recommendation X.213 and further recommends that IANA use the \"IETF consensus\" assignment policy in making future ICP assignments. [STANDARDS-TRACK]",
  "authors": [
    "E. Gray",
    "J. Rutemiller",
    "G. Swallow"
  ],
  "organizations": [],
  "publication_date": "2006-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": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-gray-rfc1888bis-03",
  "page_count": 9,
  "doi": "10.17487/RFC4548",
  "keywords": [
    "network service access point"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC1888",
      "RFC4048"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4548/",
    "html": "https://www.rfc-editor.org/rfc/rfc4548.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4548.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4548/"
  }
}