Path Computation Element Communication Protocol (PCEP) Extensions to Enable IFIT
draft-chen-pce-pcep-ifit-01

Document Type Active Internet-Draft (individual)
Authors Huanan Chen  , Hang Yuan  , Tianran Zhou  , Weidong Li  , Giuseppe Fioccola  , Yali Wang 
Last updated 2020-09-22
Replaces draft-chen-pce-sr-policy-ifit
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) 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)
PCE                                                              H. Chen
Internet-Draft                                             China Telecom
Intended status: Standards Track                                 H. Yuan
Expires: March 26, 2021                                         UnionPay
                                                                 T. Zhou
                                                                   W. Li
                                                             G. Fioccola
                                                                 Y. Wang
                                                                  Huawei
                                                      September 22, 2020

  Path Computation Element Communication Protocol (PCEP) Extensions to
                              Enable IFIT
                      draft-chen-pce-pcep-ifit-01

Abstract

   This document defines PCEP extensions to distribute In-situ Flow
   Information Telemetry (IFIT) information.  So that IFIT behavior can
   be enabled automatically when the path is instantiated.  In-situ Flow
   Information Telemetry (IFIT) refers to network OAM data plane on-path
   telemetry techniques, in particular the most popular are In-situ OAM
   (IOAM) and Alternate Marking.  The IFIT attributes here described can
   be generalized for all path types but the application to Segment
   Routing (SR) is considered in this document.  This document extends
   PCEP to carry the IFIT attributes under the stateful PCE model.

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

Chen, et al.             Expires March 26, 2021                 [Page 1]
Internet-Draft                  pcep-ifit                 September 2020

   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 March 26, 2021.

Copyright Notice

   Copyright (c) 2020 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
   2.  PCEP Extensions for IFIT Attributes . . . . . . . . . . . . .   4
     2.1.  IFIT for SR Policies  . . . . . . . . . . . . . . . . . .   4
   3.  IFIT capability advertisement TLV . . . . . . . . . . . . . .   4
   4.  IFIT Attributes TLV . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  IOAM Sub-TLVs . . . . . . . . . . . . . . . . . . . . . .   8
       4.1.1.  IOAM Pre-allocated Trace Option Sub-TLV . . . . . . .   8
       4.1.2.  IOAM Incremental Trace Option Sub-TLV . . . . . . . .   9
       4.1.3.  IOAM Directly Export Option Sub-TLV . . . . . . . . .  10
       4.1.4.  IOAM Edge-to-Edge Option Sub-TLV  . . . . . . . . . .  11
     4.2.  Enhanced Alternate Marking Sub-TLV  . . . . . . . . . . .  12
   5.  PCEP Messages . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  The PCInitiate Message  . . . . . . . . . . . . . . . . .  13
     5.2.  The PCUpd Message . . . . . . . . . . . . . . . . . . . .  13
     5.3.  The PCRpt Message . . . . . . . . . . . . . . . . . . . .  13
   6.  Example of application to SR Policy . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  17
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  17
Show full document text