%% You should probably cite draft-ietf-pce-pcep-ifit instead of this I-D.
@techreport{chen-pce-pcep-ifit-00,
    number =    {draft-chen-pce-pcep-ifit-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-chen-pce-pcep-ifit/00/},
    author =    {Huanan Chen and Hang Yuan and Tianran Zhou and Weidong Li and Giuseppe Fioccola and Yali Wang},
    title =     {{Path Computation Element Communication Protocol (PCEP) Extensions to Enable IFIT}},
    pagetotal = 17,
    year =      ,
    month =     ,
    day =       ,
    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. The SR policy is a set of candidate SR paths consisting of one or more segment lists and necessary path attributes. It enables instantiation of an ordered list of segments with a specific intent for traffic steering.},
}