%% You should probably cite draft-mirsky-6man-unified-id-sr-10 instead of this revision.
@techreport{mirsky-6man-unified-id-sr-03,
    number =    {draft-mirsky-6man-unified-id-sr-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mirsky-6man-unified-id-sr/03/},
    author =    {Weiqiang Cheng and Greg Mirsky and Shaofu Peng and Aihua Liu and XiaoLan Wan and Cheng Wei},
    title =     {{Unified Identifier in IPv6 Segment Routing Networks}},
    pagetotal = 11,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Segment Routing architecture leverages the paradigm of source routing. It can be realized in a network data plane by prepending the packet with a list of instructions, a.k.a. segments. A segment can be encoded as a Multi-Protocol Label Switching (MPLS) label, IPv4 address, or IPv6 address. Segment Routing can be applied in MPLS data plane by encoding segments in MPLS label stack. It also can be applied to IPv6 data plane by encoding a list of segment identifiers in IPv6 Segment Routing Extension Header (SRH). This document extends the use of the SRH to unified identifiers encoded as MPLS label and IPv4 address, to support interworking between SR-MPLS and SRv6.},
}