IS-IS Extensions to Support Routing over IPv6 Dataplane
draft-bashandy-isis-srv6-extensions-02

Document Type Active Internet-Draft (individual)
Last updated 2018-03-19
Replaces draft-previdi-isis-ipv6-prefix-sid
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)
Networking Working Group                                     L. Ginsberg
Internet-Draft                                               A. Bashandy
Intended status: Standards Track                             C. Filsfils
Expires: September 20, 2018                                Cisco Systems
                                                             B. Decraene
                                                                  Orange
                                                                   Z. Hu
                                                     Huawei Technologies
                                                          March 19, 2018

        IS-IS Extensions to Support Routing over IPv6 Dataplane
               draft-bashandy-isis-srv6-extensions-02.txt

Abstract

   Segment Routing (SR) allows for a flexible definition of end-to-end
   paths by encoding paths as sequences of topological sub-paths, called
   "segments".  Segment routing architecture can be implemented over an
   MPLS data plane as well as an IPv6 data plane.  This draft describes
   the IS-IS extensions required to support Segment Routing over an IPv6
   data plane.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 September 20, 2018.

Ginsberg, et al.       Expires September 20, 2018               [Page 1]
Internet-Draft     draft-bashandy-isis-srv6-extensions        March 2018

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  SRv6-Capabilities sub-TLV . . . . . . . . . . . . . . . . . .   3
     2.1.  Maximum SL sub-sub-TLV  . . . . . . . . . . . . . . . . .   4
     2.2.  Maximum End Pop SRH sub-sub-TLV . . . . . . . . . . . . .   5
     2.3.  Maximum T.Insert SRH sub-sub-TLV  . . . . . . . . . . . .   5
     2.4.  Maximum T.Encap SRH sub-sub-TLV . . . . . . . . . . . . .   6
     2.5.  Maximum End D SRH sub-sub-TLV . . . . . . . . . . . . . .   6
   3.  SRv6 Endpoint function Descriptor . . . . . . . . . . . . . .   7
   4.  SRv6 Node SID TLV . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Endpoint function Code Points . . . . . . . . . . . . . . . .   9
   6.  Advertising SRv6 SIDs associated with a Neighbor  . . . . . .   9
     6.1.  SRv6 Adjacency-SID sub-TLV  . . . . . . . . . . . . . . .  10
     6.2.  SRv6 LAN Adjacency-SID sub-TLV  . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  SRv6 Node SID TLV . . . . . . . . . . . . . . . . . . . .  12
     7.2.  SRv6 Capabilities sub-TLV . . . . . . . . . . . . . . . .  12
     7.3.  SRv6 Adjacency-SID and SRv6 LAN Adjacecncy-SID sub-TLVs .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  13
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   With Segment Routing (SR) [I-D.ietf-spring-segment-routing], a node
   steers a packet through an ordered list of instructions, called
   segments.

   Segments are identified through Segment Identifiers (SIDs).
Show full document text