<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-pcep-ifit" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-ifit-06">
   <front>
      <title>Path Computation Element Communication Protocol (PCEP) Extensions to Enable IFIT</title>
      <author initials="H." surname="Yuan" fullname="Hang Yuan">
         <organization>UnionPay</organization>
      </author>
      <author initials="" surname="王雪荣" fullname="王雪荣">
         <organization>China Telecom</organization>
      </author>
      <author initials="P." surname="Yang" fullname="Pingan Yang">
         <organization>Huawei</organization>
      </author>
      <author initials="W." surname="Li" fullname="Weidong Li">
         <organization>Huawei</organization>
      </author>
      <author initials="G." surname="Fioccola" fullname="Giuseppe Fioccola">
         <organization>Huawei</organization>
      </author>
      <date month="January" day="3" year="2025" />
      <abstract>
	 <t>   In-situ Flow Information Telemetry (IFIT) refers to network OAM data
   plane on-path telemetry techniques, in particular In-situ OAM (IOAM)
   and Alternate Marking.  This document defines PCEP extensions to
   allow a Path Computation Client (PCC) to indicate which IFIT features
   it supports, and a Path Computation Element (PCE) to configure IFIT
   behavior at a PCC for a specific path in the stateful PCE model.  The
   application to Segment Routing (SR) is reported.  However, the PCEP
   extensions described in this document can be generalized for all path
   types, but that is out of scope of this document.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-pcep-ifit-06" />
   
</reference>
