IGP Extensions for Resilient MPLS Rings
draft-kompella-isis-ospf-rmr-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
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)
IS-IS OSPF                                                   K. Kompella
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                        October 30, 2016
Expires: May 3, 2017

                IGP Extensions for Resilient MPLS Rings
                    draft-kompella-isis-ospf-rmr-00

Abstract

   This document describes the use of IS-IS and OSPF for discovering
   Resilient MPLS Rings (RMR).  RMR relies on the IGP for discovery of
   the ring elements and properties, as well as subsequent changes to
   the ring topology.  Details of auto-discovery and operation are given
   in the RMR architecture document; this document simply describes the
   formats of RMR-related constructs in IS-IS and OSPF.

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 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 May 3, 2017.

Copyright Notice

   Copyright (c) 2016 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

Kompella                   Expires May 3, 2017                  [Page 1]
Internet-Draft   IGP Extensions for Resilient MPLS Rings    October 2016

   (http://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
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Provisioning  . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Announcement  . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

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; this is
   not the case today.  The RMR architecture document
   [I-D.ietf-mpls-rmr] describes the motivations and operation of RMR.

   RMR uses protocols such as IS-IS [RFC5305] and OSPF[RFC3630] for
   auto-discovery, and RSVP-TE [RFC3209] and LDP [RFC5036] for signaling
   LSPs.  This document gives the specifics of Type-Length-Value (TLV)
   formats for IS-IS and OSPF.

1.1.  Definitions

   For a more detailed description, see [I-D.ietf-mpls-rmr].

   A ring is a subgraph of a given graph G = (V, E), consisting of a
   subset of n nodes {R_i, 0 <= i < n}.  The directed edges {(R_i,
   R_i+1) and (R_i+1, R_i), 0 <= i < n-1} must be a subset of E (note
   that index arithmetic is done modulo n).  We define the direction
   from node R_i to R_i+1 as "clockwise" (CW) and the reverse direction
   as "anticlockwise" (AC).  As there may be several rings in a graph,
   we number each ring with a distinct ring ID RID.
Show full document text