%% You should probably cite draft-wang-lsr-igp-extensions-ifit-01 instead of this revision.
@techreport{wang-lsr-igp-extensions-ifit-00,
    number =    {draft-wang-lsr-igp-extensions-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-wang-lsr-igp-extensions-ifit/00/},
    author =    {Yali Wang and Tianran Zhou and Liu Min and Huanan Chen and Ran Pang},
    title =     {{IGP Extensions for In-situ Flow Information Telemetry (IFIT) Capability Advertisement}},
    pagetotal = 12,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document extends Node and Link Attribute TLVs to Interior Gateway Protocols (IGP) to advertise supported In-situ Flow Information Telemetry (IFIT) capabilities at node and/or link granularity. An ingress router cannot insert IFIT-Data-Fields for packets going into a path unless an egress router has indicated via signaling that it has the capability to process IFIT-Data-Fields. In addition, such advertisements would be useful for ingress routers to gather each router's IFIT capability for achieving the computation of Traffic Engineering (TE) paths or loose TE paths that be able to fulfill the visibility of on-path OAM data.},
}