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

IETF · RFC · RFC8669

RFC8669 · Segment Routing Prefix Segment Identifier Extensions for BGP

Segment Routing Prefix Segment Identifier Extensions for BGP

Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions called "segments". A segment can represent any instruction, topological or service based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SIDs). Each SID represents a topological or service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An "SR domain" is defined as a single administrative domain for global SID assignment. This document defines an optional, transitive BGP attribute for announcing information about BGP Prefix Segment Identifiers (BGP Prefix-SIDs) and the specification for SR-MPLS SIDs.

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

Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions called "segments". A segment can represent any instruction, topological or service based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SIDs). Each SID represents a topological or service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An "SR domain" is defined as a single administrative domain for global SID assignment. This document defines an optional, transitive BGP attribute for announcing information about BGP Prefix Segment Identifiers (BGP Prefix-SIDs) and the specification for SR-MPLS SIDs.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8669",
  "number": 8669,
  "title_en": "Segment Routing Prefix Segment Identifier Extensions for BGP",
  "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": "Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions called \"segments\". A segment can represent any instruction, topological or service based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SIDs). Each SID represents a topological or service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An \"SR domain\" is defined as a single administrative domain for global SID assignment. This document defines an optional, transitive BGP attribute for announcing information about BGP Prefix Segment Identifiers (BGP Prefix-SIDs) and the specification for SR-MPLS SIDs.",
  "authors": [
    "S. Previdi",
    "C. Filsfils",
    "A. Lindem",
    "A. Sreekantiah",
    "H. Gredler"
  ],
  "organizations": [],
  "publication_date": "2019-12-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": "idr",
  "source_draft": "draft-ietf-idr-bgp-prefix-sid-27",
  "page_count": 15,
  "doi": "10.17487/RFC8669",
  "keywords": [
    "SR",
    "MPLS",
    "BGP",
    "Prefix-SID",
    "Label-Index",
    "SRGB"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8669/",
    "html": "https://www.rfc-editor.org/rfc/rfc8669.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8669.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8669/"
  }
}