%% You should probably cite draft-ietf-spring-mpls-anycast-segments instead of this I-D.
@techreport{psarkar-spring-mpls-anycast-segments-01,
    number =    {draft-psarkar-spring-mpls-anycast-segments-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-psarkar-spring-mpls-anycast-segments/01/},
    author =    {Hannes Gredler and Clarence Filsfils and Stefano Previdi and Bruno Decraene and Martin Horneffer},
    title =     {{Anycast Segments in MPLS based Segment Routing}},
    pagetotal = 19,
    year =      2015,
    month =     oct,
    day =       12,
    abstract =  {Instead of forwarding to a specific device or to all devices in a group, anycast addresses, let network devices forward a packet to (or steer it through) one or more topologically nearest devices in a specific group of network devices. The use of anycast addresses has been extended to the Segment Routing (SR) network, wherein a group of SR-capable devices can represent a anycast address, by having the same Segment Routing Global Block (SRGB) provisioned on all the devices and each one of them advertising the same anycast prefix segment (or Anycast SID). This document describes a proposal for implementing anycast prefix segments in a MPLS-based SR network, without the need to have the same SRGB block (label ranges) provisioned across all the member devices in the group. Each node can be provisioned with a separate SRGB from the label range supported by the specfic hardware platform.},
}