BGP Advisory Message
draft-scholl-idr-advisory-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Tom Scholl , John Scudder | ||
| Last updated | 2010-04-08 (Latest revision 2009-03-04) | ||
| Replaced by | draft-ietf-idr-advisory | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-idr-advisory | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-scholl-idr-advisory-00.txt
Abstract
The BGP routing protocol is used with external as well as internal neighbors to propagate route advertisements. In the case of external BGP sessions, there is typically a demarcation of administrative responsibility between the two entities. Provisioning, maintenance and administrative actions are communicated via off-line methods such as email or telephone calls. While these methods have been used for many years, it can be troublesome for an operator to correlate a BGP- related event in the network with a notice that was transmitted in email. This document proposes a new BGP message type, the Advisory message, which can be used to convey advisory information to a BGP speaker's peer. A capability is used to ensure that the recipient of the Advisory message is capable of supporting it.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)