Resources for Preferred Path Routes in IGPs
draft-cls-ppr-te-attributes-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-16
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, Ed.
Internet-Draft                                                     R. Li
Intended status: Standards Track                              Huawei USA
Expires: January 17, 2019                                       K. Smith
                                                                Vodafone
                                                           July 16, 2018

              Resources for Preferred Path Routes in IGPs
                     draft-cls-ppr-te-attributes-00

Abstract

   Preferred Path Routing (PPR) is concerned with setting up the route
   for a given prefix as specified in the path description along with a
   corresponding data plane/forwarding identifier PPR-ID.  This document
   specifies an extension to PPR, a mechanism to perform resource
   reservations nodes on Preferred Path Routes (PPR) for IGPs (IS-IS,
   OSPFv2, OSPFv3).  This is done by specifying the resources that need
   to be reserved along the path using PPR path attributes.

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
   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 January 17, 2019.

Chunduri, et al.        Expires January 17, 2019                [Page 1]
Internet-Draft Resources for Preferred Path Routes in IGPs     July 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
   2.  Solution Overview . . . . . . . . . . . . . . . . . . . . . .   4
   3.  PPR Resource Reservation Related Parameters . . . . . . . . .   4
     3.1.  IS-IS Parameters  . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Bandwidth Sub-TLV . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Burst Size Sub-TLV  . . . . . . . . . . . . . . . . .   5
       3.1.3.  Per-hop Queuing Latency Sub-TLV . . . . . . . . . . .   5
       3.1.4.  Lifetime Sub-TLV  . . . . . . . . . . . . . . . . . .   6
       3.1.5.  Node Resource Capability Sub-TLV  . . . . . . . . . .   7
       3.1.6.  Node Status TLV . . . . . . . . . . . . . . . . . . .   8
       3.1.7.  IS-IS TE Metric Extensions  . . . . . . . . . . . . .   9
         3.1.7.1.  Per PPR queuing delay on the node . . . . . . . .  10
         3.1.7.2.  Unidirectional Utilized PPR Bandwidth . . . . . .  10
     3.2.  OSPFv2/OSPFv3 Parameters  . . . . . . . . . . . . . . . .  11
   4.  Elements of Procedure . . . . . . . . . . . . . . . . . . . .  11
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     6.1.  IGP Common Parameters . . . . . . . . . . . . . . . . . .  12
     6.2.  IS-IS Registries  . . . . . . . . . . . . . . . . . . . .  12
     6.3.  OSPFv2 Registries . . . . . . . . . . . . . . . . . . . .  13
     6.4.  OSPFv3 Registries . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16
Show full document text