API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 4561
[ACTIVE]

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

Metadata

Publisher
IETF
Doc Type
Standard
Pages
10
Abstract
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]
Publication Date
2006-06-01
Status Note
Proposed Standard
DOI
10.17487/RFC4561
Link
https://doi.org/10.17487/RFC4561
Author(s)
JP Vasseur
Zafar Ali
Siva Sivabalan
Keyword(s)
MPLS-TE, PLR, IGP, Autonomous System, ABR, ASBR
Latest version of IETF RFC 4561

Document Versions — IETF RFC 4561

  • ▶ IETF RFC 4561 (2006-06-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Farrel, A., Vasseur, J.-P., and J. Ash, "A Path Computation Element (PCE) Based Architecture", Work in Progress, April 2006. EXTERNAL
  • IETF RFC 4105 [Active*]
  • IETF RFC 4216 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4561.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 4561, Definition of a Record Route Object (RRO) Node-Id Sub-Object. Available at https://doi.org/10.17487/RFC4561
Snippet:
IETF RFC 4561, Definition of a Record Route Object (RRO) Node-Id Sub-Object. Available at https://doi.org/10.17487/RFC4561

HTML (ISO 690 compliant)

Preview:
IETF RFC 4561, Definition of a Record Route Object (RRO) Node-Id Sub-Object. Available at https://doi.org/10.17487/RFC4561
Snippet:
<span class="citation"><cite>IETF RFC 4561</cite>, Definition of a Record Route Object (RRO) Node-Id Sub-Object. Available at <a href="https://doi.org/10.17487/RFC4561" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4561</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 4561, Definition of a Record Route Object (RRO) Node-Id Sub-Object
doi: 10.17487/RFC4561
url: https://doi.org/10.17487/RFC4561
Snippet:
<li>
<cite id="bib-rfc4561">IETF RFC 4561</cite>, Definition of a Record Route Object (RRO) Node-Id Sub-Object
<span class="doi">10.17487/RFC4561</span>
</li>

Referenced By