Internet Engineering Task Force Y. Shen
Internet-Draft Juniper Networks
Intended status: Standards Track Y. Kamite
Expires: August 12, 2013 NTT Communications Corporation
February 8, 2013
RSVP Setup Protection
draft-shen-mpls-rsvp-setup-protection-02
Abstract
RFC 4090 specifies an RSVP facility-backup fast reroute mechanism for
protecting established LSPs against link and node failures. This
document extends the mechanism to provide so-called "setup
protection" for LSPs during their initial Path message signaling
time. In particular, it enables a router to reroute an LSP via an
existing bypass LSP, when there is a failure of the immediate
downstream link or node along the desired path. Therefore, it can be
used to reduce LSP setup time in such a situation, or allow LSPs with
strict paths to be established successfully when alternative paths
are unavailable in the network or unable to be computed by ingress.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 12, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
Shen & Kamite Expires August 12, 2013 [Page 1]
Internet-Draft RSVP Setup Protection February 2013
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Specification of Requirements . . . . . . . . . . . . . . . . 4
3. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 4
3.1. New RSVP Attribute Flag . . . . . . . . . . . . . . . . . 5
3.2. New RSVP Attributes TLVs . . . . . . . . . . . . . . . . . 5
3.2.1. Protected LSP Sender IPv4 Address TLV . . . . . . . . 6
3.2.2. Protected LSP Sender IPv6 Address TLV . . . . . . . . 6
3.3. PLR behavior . . . . . . . . . . . . . . . . . . . . . . . 7
3.4. MP behavior . . . . . . . . . . . . . . . . . . . . . . . 9
3.5. Local Revertive Mode . . . . . . . . . . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . . 10
7.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Shen & Kamite Expires August 12, 2013 [Page 2]
Internet-Draft RSVP Setup Protection February 2013
1. Introduction
In RSVP facility-backup fast reroute (FRR) [RFC 4090], the router at
a point of local repair (PLR) of an LSP can redirect traffic via a
bypass LSP upon a failure of the immediate downstream link or node.
Such protection is normally established after the LPS has been set
up. This is because the PLR must know the label and address of the
next-hop router (in the case of link protection) or those of the
next-next-hop router (in the case of node protection), before it can
select or signal a bypass LSP to protect the LSP. The information of
datatracker.ietf.org