%% You should probably cite draft-ietf-spring-mpls-anycast-segments instead of this I-D.
@techreport{psarkar-spring-mpls-anycast-segments-00,
	number =	{draft-psarkar-spring-mpls-anycast-segments-00},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-psarkar-spring-mpls-anycast-segments-00},
        author =	{Hannes Gredler},
	title =		{{Anycast Segments in MPLS based SPRING}},
	pagetotal =	15,
	year =		,
	month =		,
	day =		,
	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. {[}I-D.ietf-spring-segment-routing{]} extended the use of anycast addresses to a SPRING network, wherein a group of SPRING-capable devices can represent a anycast address, by having the same SRGB label block 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 SPRING, 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.},
}