Preferred Path Routing (PPR) in IS-IS
draft-chunduri-isis-preferred-path-routing-00

Document Type Active Internet-Draft (individual)
Last updated 2018-06-18
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)
LSR Working Group                                            U. Chunduri
Internet-Draft                                                     R. Li
Intended status: Standards Track                              Huawei USA
Expires: December 18, 2018                                      R. White
                                                                LinkedIn
                                                             J. Tantsura
                                                          Nuage Networks
                                                            L. Contreras
                                                              Telefonica
                                                                   Y. Qu
                                                              Huawei USA
                                                           June 16, 2018

                 Preferred Path Routing (PPR) in IS-IS
             draft-chunduri-isis-preferred-path-routing-00

Abstract

   This document specifies a Preferred Path Routing (PPR) mechanism to
   simplify the path description of data plane traffic in Segment
   Routing (SR) deployments.  PPR aims to mitigate the MTU and data
   plane processing issues that may result from SR packet overheads; and
   also supports traffic measurement, accounting statistics and further
   attribute extensions along the paths.  Preferred Path Routing is
   achieved through the addition of descriptions to IS-IS advertised
   prefixes, and mapping those to a PPR data-plane identifier.

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],
   RFC8174 [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

Chunduri, et al.        Expires December 18, 2018               [Page 1]
Internet-Draft    Preferred Path Routing (PPR) in IS-IS        June 2018

   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 December 18, 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Challenges with Increased SID Depth . . . . . . . . . . .   4
     1.3.  Mitigation with MSD . . . . . . . . . . . . . . . . . . .   5
   2.  Preferred Path Routing (PPR)  . . . . . . . . . . . . . . . .   6
     2.1.  PPR-ID and PPR Path Description . . . . . . . . . . . . .   6
   3.  PPR Related TLVs  . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  PPR-Prefix Sub-TLV  . . . . . . . . . . . . . . . . . . .   9
     3.2.  PPR-ID Sub-TLV  . . . . . . . . . . . . . . . . . . . . .   9
     3.3.  PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . . . . .  11
     3.4.  PPR-Attributes Sub-TLV  . . . . . . . . . . . . . . . . .  13
   4.  PPR Processing Procedure Example  . . . . . . . . . . . . . .  14
     4.1.  PPR TLV Processing  . . . . . . . . . . . . . . . . . . .  16
   5.  PPR Data Plane aspects  . . . . . . . . . . . . . . . . . . .  17
     5.1.  SR-MPLS with PPR  . . . . . . . . . . . . . . . . . . . .  17
     5.2.  SRv6 with PPR . . . . . . . . . . . . . . . . . . . . . .  17
     5.3.  PPR Native IP Data Planes . . . . . . . . . . . . . . . .  18
   6.  PPR Traffic Accounting  . . . . . . . . . . . . . . . . . . .  18
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
Show full document text