BGP Advisory Message
draft-ietf-idr-advisory-00
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tom Scholl , John Scudder , Richard Steenbergen , David Freedman | ||
| Last updated | 2009-10-16 | ||
| Replaces | draft-scholl-idr-advisory | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
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
Tom Scholl
John Scudder
Richard Steenbergen
David Freedman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)