RSVP Extensions for RMR
draft-deshmukh-teas-rsvp-rmr-extension-00
TEAS WG A. Deshmukh
Internet-Draft K. Kompella
Intended status: Standards Track Juniper Networks, Inc.
Expires: August 17, 2018 February 13, 2018
RSVP Extensions for RMR
draft-deshmukh-teas-rsvp-rmr-extension-00
Abstract
Rings are the most common topology in access and aggregation
networks. However, the use of MPLS as the transport protocol for
rings is very limited today. draft-ietf-mpls-rmr-02 describes a
mechanism to handle rings efficiently using MPLS. This document
describes the extensions to the RSVP protocol for signaling MPLS
label switched paths in rings.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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 https://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 17, 2018.
Copyright Notice
Copyright (c) 2018 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
Deshmukh & Kompella Expires August 17, 2018 [Page 1]
Internet-Draft RSVP Extensions for RMR February 2018
(https://trustee.ietf.org/license-info) in effect on the date of
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. RSVP Extensions . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Session Object . . . . . . . . . . . . . . . . . . . . . 4
3.2. SENDER_TEMPLATE,FILTER_SPEC Objects . . . . . . . . . . . 5
4. Ring Signaling Procedures . . . . . . . . . . . . . . . . . . 5
4.1. Differences from regular RSVP-TE LSPs . . . . . . . . . . 5
4.2. LSP signaling . . . . . . . . . . . . . . . . . . . . . . 5
4.2.1. Path Propagation for RMR . . . . . . . . . . . . . . 7
4.2.2. Resv Processing for RMR . . . . . . . . . . . . . . . 8
4.3. Protection . . . . . . . . . . . . . . . . . . . . . . . 9
4.4. Ring changes . . . . . . . . . . . . . . . . . . . . . . 10
4.5. Bandwidth management . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
This document extends RSVP-TE [RFC3209] to establish label-switched
path (LSP) tunnels in the ring topology. Rings are auto-discovered
using the mechanisms mentioned in the [draft-ietf-mpls-rmr-02].
Either IS-IS [RFC5305] or OSPF[RFC3630] can be used as the IGP for
auto-discovering the rings.
After the rings are auto-discovered, each ring node knows its
clockwise (CW) and anti-clockwise (AC) ring neighbors and its ring
links. All of the express links in the ring also get identified as
part of the auto-discovery process. At this point, every node in the
ring informs the RSVP protocol to begin the signaling of the ring
LSPs.
Deshmukh & Kompella Expires August 17, 2018 [Page 2]
Internet-Draft RSVP Extensions for RMR February 2018
Section 2 covers the terminology used in this document. Section 3
presents the RSVP protocol extensions needed to support MPLS rings.
Show full document text