RFC4561 · Definition of a Record Route Object (RRO) Node-Id Sub-Object

{
  "id": "RFC4561",
  "number": 4561,
  "title_en": "Definition of a Record Route Object (RRO) Node-Id Sub-Object",
  "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 the context of MPLS TE Fast Reroute, the Merge Point (MP) address is required at the Point of Local Repair (PLR) in order to select a backup tunnel intersecting a fast reroutable Traffic Engineering Label Switched Path (TE LSP) on a downstream Label Switching Router (LSR). However, existing protocol mechanisms are not sufficient to find an MP address in multi-domain routing networks where a domain is defined as an Interior Gateway Protocol (IGP) area or an Autonomous System (AS). Hence, the current MPLS Fast Reroute mechanism cannot be used in order to protect inter-domain TE LSPs from a failure of an Area Border Router (ABR) or Autonomous System Border Router (ASBR). This document specifies the use of existing Record Route Object (RRO) IPv4 and IPv6 sub-objects (with a new flag defined) thus defining the node-id sub-object in order to solve this issue. The MPLS Fast Reroute mechanism mentioned in this document refers to the \"Facility backup\" MPLS TE Fast Reroute method. [STANDARDS-TRACK]",
  "authors": [
    "J.-P. Vasseur",
    "Z. Ali",
    "S. Sivabalan"
  ],
  "organizations": [],
  "publication_date": "2006-06-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": "mpls",
  "source_draft": "draft-ietf-mpls-nodeid-subobject-07",
  "page_count": 10,
  "doi": "10.17487/RFC4561",
  "keywords": [
    "multiprotocol label switching traffic engineering",
    "plr",
    "point of local repair",
    "igp",
    "interior gateway protocol",
    "as",
    "autonomous system",
    "abr",
    "area border router",
    "asbr",
    "autonomous system border router"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4561/",
    "html": "https://www.rfc-editor.org/rfc/rfc4561.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4561.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4561/"
  }
}