Definition of an RRO node-id subobject
draft-vasseur-mpls-nodeid-subobject-00

Document Type Expired Internet-Draft (individual)
Last updated 2003-02-10
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-vasseur-mpls-nodeid-subobject-00.txt

Abstract

In the context of MPLS TE Fast Reroute ([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 protected Traffic Engineering LSP on a downstream LSR. However, existing protocol mechanisms are not sufficient to find MP address multi-areas or multi- domain routing network. Hence, the current MPLS Fast Reroute mechanism cannot be used to protect inter-area or inter-AS TE LSPs from a failure of an ABR (Area Border Router) or ASBR (Autonomous System Border Router) respectively. This document specifies the use of existing RRO IPv4 and IPv6 subobjects (with a new flag defined) to define the node- id subobject in order to solve this issue.

Authors

Zafar Ali (zali@cisco.com)
Siva Sivabalan (msiva@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)