Separating Routing Planes using Segment Routing
draft-gulkohegde-routing-planes-using-sr-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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                                                          S. Hegde
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                                A. Gulko
Expires: September 14, 2017                              Thomson Reuters
                                                          March 13, 2017

            Separating Routing Planes using Segment Routing
              draft-gulkohegde-routing-planes-using-sr-00

Abstract

   Many network deployments arrange the network topologies in two or
   more planes.  The traffic generally uses one of the planes and fails
   over to the other plane when there are link or node failure.  Certain
   applications require the traffic to be strictly restricted to a
   particular plane and should not failover to the other plane.  This
   document proposes a solution for the strict planar routing using
   Segment Routing.

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 RFC 2119 [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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Hegde & Gulko          Expires September 14, 2017               [Page 1]
Internet-DrafSeparating Routing Planes using Segment Routing  March 2017

   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
   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.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Solutions . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Routing-plane SID . . . . . . . . . . . . . . . . . . . .   3
       3.1.1.  Elements of procedure . . . . . . . . . . . . . . . .   4
     3.2.  Multi-topology SID  . . . . . . . . . . . . . . . . . . .   4
   4.  Backward compatibility  . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

                       A3----------------------A4
                     / |                      /|
                    /  |                     / |
                   /   |                    /  |
                  A1---|-------------------A2  |
                  |    B3------------------|---B4
                  |   /                    |   /
                  |  /                     |  /
                  | /                      | /
                  B1-----------------------B2

                         Figure 1: Network Planes

   The above Figure 1 represents a network topology in two planes.Nodes
   A1, A2, A3, A4 are in plane A and B1, B2, B3, B4 are in plane B.
   A1->B1, A2->B2, A3->B3, A4->B4 represent the "shunt links" which
   connect the two planes.  Certain applications require that the

Hegde & Gulko          Expires September 14, 2017               [Page 2]
Show full document text