%% You should probably cite draft-ietf-idr-bgp-ls-link-mtu-12 instead of this revision.
@techreport{ietf-idr-bgp-ls-link-mtu-10,
    number =    {draft-ietf-idr-bgp-ls-link-mtu-10},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-link-mtu/10/},
    author =    {Yongqing Zhu and Zhibo Hu and Shuping Peng and Robbins Mwehair},
    title =     {{Signaling Maximum Transmission Unit (MTU) using BGP-LS}},
    pagetotal = 9,
    year =      2025,
    month =     sep,
    day =       18,
    abstract =  {Segment Routing (SR) leverages the source routing paradigm, which can be directly applied to the MPLS architecture and IPv6 architecture, with a new type of routing header. Since multiple labels or SRv6 SIDs are pushed in the packets, it is more likely that the packet size exceeds the path MTU of SR tunnel. However, SR uses the IGP as the routing protocol and does not support the negotiation of the Path MTU. BGP Link State (BGP-LS) describes a mechanism by which link-state and TE information can be collected from networks and shared with external components using the BGP routing protocol. This document specifies the extensions to BGP-LS to carry MTU information of link. The centralized controller (PCE/SDN) calculates the Path MTU while completing the service path calculation based on the information transmitted by the BGP-LS.},
}