Segment Routing MPLS Conflict Resolution
draft-ietf-spring-conflict-resolution-05
| Document | Type |
Expired Internet-Draft
(spring WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Les Ginsberg , Peter Psenak , Stefano Previdi , Martin Pilka | ||
| Last updated | 2018-04-16 (Latest revision 2017-07-02) | ||
| Replaces | draft-ginsberg-spring-conflict-resolution | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | Martin Vigoureux | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In support of Segment Routing (SR) for an MPLS data plane routing protocols advertise a variety of identifiers used to define the segments which direct forwarding of packets. In cases where the information advertised by a given protocol instance is either internally inconsistent or conflicts with advertisements from another protocol instance a means of achieving consistent forwarding behavior in the network is required. This document defines the policies used to resolve these occurrences.
Authors
Les Ginsberg
Peter Psenak
Stefano Previdi
Martin Pilka
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)