Segment Routing in MPLS-TP Inter-domain Use Cases
draft-hu-mpls-sr-inter-domain-use-cases-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-12-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
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)
MPLS Workgroup                                                Fangwei Hu
Internet-Draft                                                Quan Xiong
Intended status: Standards Track                             Greg Mirsky
Expires: June 12, 2019                                   ZTE Corporation
                                                          Weiqiang Cheng
                                                            China Mobile
                                                             Dec 9, 2018

           Segment Routing in MPLS-TP Inter-domain Use Cases
               draft-hu-mpls-sr-inter-domain-use-cases-00

Abstract

   This document discusses SR-MPLS-TP inter-domain scenarios and use
   cases, and also SR-MPLS-TP inter-working with MPLS-TP network
   requirement and use cases.

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 June 12, 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
   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

Fangwei Hu, et al.        Expires June 12, 2019                 [Page 1]
Internet-Draft          SR Inter-domain use cases               Dec 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   3.  SR-MPLS-TP Inter-domain . . . . . . . . . . . . . . . . . . .   3
     3.1.  SR-MPLS-TP Stitching Inter-domain . . . . . . . . . . . .   4
       3.1.1.  Border Node Inter-domain Scenario . . . . . . . . . .   4
       3.1.2.  Border Link Inter-domain Scenario . . . . . . . . . .   5
     3.2.  SR-MPLS-TP Nesting Inter-domain . . . . . . . . . . . . .   6
   4.  SR-MPLS-TP Inter-working with MPLS-TP . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Segment Routing (SR) leverages the source routing paradigm.  A node
   steers a packet through an SR Policy instantiated as an ordered list
   of instructions called "segments".  A segment can represent any
   instruction, topological or service based.  A segment can have a
   semantic local to an SR node or global within an SR domain.  SR
   supports per-flow explicit routing while maintaining per-flow state
   only at the ingress nodes to the SR domain.  Segment Routing can be
   instantiated on MPLS data plane or IPv6 data plane.  The former is
   called SR-MPLS [I-D.ietf-spring-segment-routing-mpls] , the latter is
   called SRv6 [I-D.ietf-6man-segment-routing-header].  SR-MPLS
   leverages the MPLS label stack to construct SR path, and SRv6 uses
   the Segment Routing Header to construct SR path.

   [I-D.cheng-spring-mpls-path-segment] provides a path segment to
   support bidirectional path correlation in an AS domain.  A Path
   Segment is defined to unique identify an SR path in a specific
   context.  This document proposes to discuss SR-MPLS-TP inter-domain
   scenarios and use cases, and SR-MPLS-TP inter-working with MPLS-TP
   network requirement and use case.

2.  Conventions used in this document

Fangwei Hu, et al.        Expires June 12, 2019                 [Page 2]
Internet-Draft          SR Inter-domain use cases               Dec 2018

2.1.  Terminology

   A->B SID list: The SID List from SR node A to SR node B.

   AS: Autonomous Systems.
Show full document text