Anycast Segments in MPLS based Segment Routing

Document Type Replaced Internet-Draft (spring WG)
Authors Pushpasis Sarkar  , Hannes Gredler  , Clarence Filsfils  , Stefano Previdi  , Bruno Decraene  , Martin Horneffer 
Last updated 2016-10-11 (latest revision 2016-04-12)
Replaced by draft-ietf-spring-mpls-anycast-segments
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized pdfized bibtex
Stream WG state Adopted by a WG
Document shepherd Martin Vigoureux
IESG IESG state Replaced by draft-ietf-spring-mpls-anycast-segments
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Martin Vigoureux" <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Pushpasis Sarkar (
Hannes Gredler (
Clarence Filsfils (
Stefano Previdi (
Bruno Decraene (
Martin Horneffer (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)