A Framework for BGP Feedback Message In Segment Routing
draft-deevimajumdar-spring-bgp-feedback-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Kausik Majumdar , Krishna | ||
Last updated | 2017-10-23 (Latest revision 2017-04-21) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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), routing protocols advertise a variety of identifiers used to define the segments that direct packet forwarding. 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 notifying the originator about the inconsistency is required. This document defines a generic mechanism to notify the BGP originator about the inconsistency in the network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)