Resilient MPLS Rings
draft-kompella-spring-rmr-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SPRING                                                       K. Kompella
Internet-Draft                                               A. Deshmukh
Intended status: Standards Track                                R. Torvi
Expires: April 25, 2019                           Juniper Networks, Inc.
                                                        October 22, 2018

                          Resilient MPLS Rings
                      draft-kompella-spring-rmr-00

Abstract

   This document describes the use of the SPRING MPLS data plane for
   Resilient MPLS Rings.  It describes how to create the bidirectional
   ring LSPs with SPRING, and how protection works.

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 April 25, 2019.

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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Kompella, et al.         Expires April 25, 2019                 [Page 1]
Internet-Draft            Resilient MPLS Rings              October 2018

   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
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Installing Primary LFIB Entries . . . . . . . . . . . . .   5
     3.2.  Installing Protection LFIB Entries  . . . . . . . . . . .   5
     3.3.  Protection  . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Rings are a very common topology in transport networks.  A ring is
   the simplest topology offering link and node resilience.  Rings are
   nearly ubiquitous in access and aggregation networks.  As MPLS
   increases its presence in such networks, and takes on a greater role
   in transport, it is imperative that MPLS handles rings well;
   [I-D.ietf-mpls-rmr] shows how this can be done.
   [I-D.ietf-teas-rsvp-rmr-extension] shows how RSVP-TE [RFC3209] can be
   used to signal RMR ring LSPs.  [I-D.ietf-mpls-ldp-rmr-extensions]
   shows how LDP [RFC5036] can be used to signal RMR LSPs.  This
   document shows how SPRING SID bindings can be used to create RMR
   LSPs, how the basic bidirectional LSPs are set up, and how protection
   works.

   While RMR looks at rings potentially with "express links", this
   document focuses on simple rings.  These are most common in access
   networks.  Future revisions will look at more general rings.

1.1.  Definitions

   A (directed) graph G = (V, E) consists of a set of vertices (or
   nodes) V and a set of edges (or links) E.  An edge is an ordered pair
   of nodes (a, b), where a and b are in V.  (In this document, the
   terms node and link will be used instead of vertex and edge.)

Kompella, et al.         Expires April 25, 2019                 [Page 2]
Internet-Draft            Resilient MPLS Rings              October 2018

   A ring is a subgraph of G.  A ring consists of a subset of n nodes
   {R_i, 0 <= i < n} of V.  The directed edges {(R_i, R_i+1) and (R_i+1,
Show full document text