Skip to main content

Anycast Segments in MPLS based Segment Routing
draft-ietf-spring-mpls-anycast-segments-02

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Pushpasis Sarkar , Hannes Gredler , Clarence Filsfils , Stefano Previdi , Bruno Decraene , Martin Horneffer
Last updated 2018-08-01 (Latest revision 2018-01-28)
Replaces draft-psarkar-spring-mpls-anycast-segments
RFC stream Internet Engineering Task Force (IETF)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd Rob Shakir
IESG IESG state Expired
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to Rob Shakir <robjs@google.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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.

Authors

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.)