Packet-Optical Integration in Segment Routing
draft-anand-spring-poi-sr-04

Document Type Active Internet-Draft (individual)
Last updated 2017-11-14
Stream (None)
Intended RFC status (None)
Formats plain text 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 Working Group                                      Madhukar Anand
Internet-Draft                                            Sanjoy Bardhan
Intended Status: Informational                      Infinera Corporation

                                                     Ramesh Subrahmaniam
                                                              Individual

                                                           Jeff Tantsura
                                                              Individual

                                                     Utpal Mukhopadhyaya
                                                             Equinix Inc

                                                       Clarence Filsfils
                                                     Cisco Systems, Inc.

Expires: May 18, 2018                                  November 14, 2017

             Packet-Optical Integration in Segment Routing 
                      draft-anand-spring-poi-sr-04

Abstract

   This document illustrates a way to integrate a new class of nodes and
   links in segment routing to represent transport networks in an opaque
   way into the segment routing domain.  An instance of this class would
   be optical networks that are typically transport centric.  In the IP
   centric network, this will help in defining a common control protocol
   for packet optical integration that will include optical paths as
   'transport segments' or sub-paths as an augmentation to packet paths.
   The transport segment option also defines a general mechanism to
   allow for future extensibility of segment routing into non-packet
   domains.

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 to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

 

Anand et al.,             Expires May 18, 2018                  [Page 1]

Internet-Draft        draft-anand-spring-poi-sr-04     November 14, 2017

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Reference Taxonomy . . . . . . . . . . . . . . . . . . . . . .  4
   3. Use case - Packet Optical Integration . . . . . . . . . . . . .  5
   4.  Mechanism overview . . . . . . . . . . . . . . . . . . . . . .  8
   5.  Transport Segments as SR Policy  . . . . . . . . . . . . . . .  9
   6.  PCEP extensions for supporting the transport segment . . . . . 10
   7.  BGP-LS extensions for supporting the transport segment . . . . 11
   8. Note about Transport Segments and Scalability . . . . . . . . . 13
   9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
   10.  Security Considerations . . . . . . . . . . . . . . . . . . . 14
   11  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
     11.1 PCEP  . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     11.2 BGP-LS  . . . . . . . . . . . . . . . . . . . . . . . . . . 15
   12  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
 

Anand et al.,             Expires May 18, 2018                  [Page 2]

Internet-Draft        draft-anand-spring-poi-sr-04     November 14, 2017

   13  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     13.1  Normative References . . . . . . . . . . . . . . . . . . . 15
Show full document text