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

IETF · RFC · RFC9756

RFC9756 · Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes

Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes

This document updates the registration procedure within the IANA "Path Computation Element Protocol (PCEP) Numbers" registry group. This specification changes some of the registries with Standards Action to IETF Review as defined in RFC 8126 and thus updates RFCs 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 8779, 8780, 8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604. Designating "experimental use" sub-ranges within codepoint registries is often beneficial for protocol experimentation in controlled environments. Although the registries for PCEP messages, objects, and TLV types have sub-ranges assigned for Experimental Use, the registry for PCEP Error-Types and Error-values currently does not. This document updates RFC 5440 by designating a specific range of PCEP Error-Types for Experimental Use.

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

This document updates the registration procedure within the IANA "Path Computation Element Protocol (PCEP) Numbers" registry group. This specification changes some of the registries with Standards Action to IETF Review as defined in RFC 8126 and thus updates RFCs 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 8779, 8780, 8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604. Designating "experimental use" sub-ranges within codepoint registries is often beneficial for protocol experimentation in controlled environments. Although the registries for PCEP messages, objects, and TLV types have sub-ranges assigned for Experimental Use, the registry for PCEP Error-Types and Error-values currently does not. This document updates RFC 5440 by designating a specific range of PCEP Error-Types for Experimental Use.

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

updates: RFC5440, RFC8231, RFC8233, RFC8281, RFC8623, RFC8664, RFC8685, RFC8697, RFC8733, RFC8745, RFC8779, RFC8780, RFC8800, RFC8934, RFC9050, RFC9059, RFC9168, RFC9357, RFC9504, RFC9603, RFC9604

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

Полные импортированные сведения карточки
{
  "id": "RFC9756",
  "number": 9756,
  "title_en": "Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes",
  "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 updates the registration procedure within the IANA \"Path Computation Element Protocol (PCEP) Numbers\" registry group. This specification changes some of the registries with Standards Action to IETF Review as defined in RFC 8126 and thus updates RFCs 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 8779, 8780, 8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604. Designating \"experimental use\" sub-ranges within codepoint registries is often beneficial for protocol experimentation in controlled environments. Although the registries for PCEP messages, objects, and TLV types have sub-ranges assigned for Experimental Use, the registry for PCEP Error-Types and Error-values currently does not. This document updates RFC 5440 by designating a specific range of PCEP Error-Types for Experimental Use.",
  "authors": [
    "D. Dhody",
    "A. Farrel"
  ],
  "organizations": [],
  "publication_date": "2025-03-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": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "pce",
  "source_draft": "draft-ietf-pce-iana-update-03",
  "page_count": 11,
  "doi": "10.17487/RFC9756",
  "keywords": [],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5440",
      "RFC8231",
      "RFC8233",
      "RFC8281",
      "RFC8623",
      "RFC8664",
      "RFC8685",
      "RFC8697",
      "RFC8733",
      "RFC8745",
      "RFC8779",
      "RFC8780",
      "RFC8800",
      "RFC8934",
      "RFC9050",
      "RFC9059",
      "RFC9168",
      "RFC9357",
      "RFC9504",
      "RFC9603",
      "RFC9604"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9756/",
    "html": "https://www.rfc-editor.org/rfc/rfc9756.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9756.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9756/"
  }
}