datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

Definition of a Record Route Object (RRO) Node-Id Sub-Object
draft-ietf-mpls-nodeid-subobject-07

RFC
Document Stream: IETF
Last updated: 2005-12-01
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (mpls)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 4561
Responsible AD: Alex Zinin
Send notices to: loa@pi.se, swallow@cisco.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-mpls-nodeid-subobject.

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]

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)