Usage of Non Shortest Path Forwarding (NSPF) Ids in IS-IS
draft-ct-isis-nspfid-for-sr-paths-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-03-05
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
LSR Working Group                                       U. Chunduri, Ed.
Internet-Draft                                                Huawei USA
Intended status: Standards Track                             J. Tantsura
Expires: September 6, 2018                                Nuage Networks
                                                                   Y. Qu
                                                     Huawei Technologies
                                                           March 5, 2018

       Usage of Non Shortest Path Forwarding (NSPF) Ids in IS-IS
                  draft-ct-isis-nspfid-for-sr-paths-00

Abstract

   This document specifies the advertisement of Non Shortest Path
   Forwarding IDentifier (NSPF ID) TLV and the computation procedures
   for the same in IS-IS protocol.  NSPF ID allows to simplify the data
   plane path description of data traffic in SR deployments.  This helps
   mitigate the MTU issues that are caused by additional SR overhead of
   the packet and allows traffic statistics.

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 [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 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 6, 2018.

Chunduri, et al.        Expires September 6, 2018               [Page 1]
Internet-DraUsage of Non Shortest Path Forwarding (NSPF) Ids  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
     1.1.  Mitigation with MSD and RLD . . . . . . . . . . . . . . .   3
     1.2.  Issues with Increased SID Depth . . . . . . . . . . . . .   3
     1.3.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Non Shortest Path Forwarding IDentifier TLV . . . . . . . . .   5
     2.1.  Flags . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  NSPF-ID Fields  . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  NSP sub-TLVs  . . . . . . . . . . . . . . . . . . . . . .   8
     2.4.  Non-NSP sub-TLVs  . . . . . . . . . . . . . . . . . . . .   9
   3.  Elements of Procedure . . . . . . . . . . . . . . . . . . . .   9
   4.  NSPF ID Data plane aspects  . . . . . . . . . . . . . . . . .  11
   5.  NSP Traffic Accounting  . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   In a network implementing source routing, packets may be transported
   through the use of segment identifiers (SIDs), where a SID uniquely
   identifies a segment as defined in [I-D.ietf-spring-segment-routing].
   In SR-MPLS, a segment is encoded as a label and an ordered list of
   segments is encoded as a stack of labels.  In SRv6, a segment is
   encoded as an IPv6 address, with a new type of IPv6 routing header
   called SRH.  An ordered list of segments is encoded as an ordered
   list of IPv6 addresses in SRH [I-D.ietf-6man-segment-routing-header].

Chunduri, et al.        Expires September 6, 2018               [Page 2]
Show full document text