BGP Advisory Message
draft-ietf-idr-advisory-00

Document Type Expired Internet-Draft (idr WG)
Last updated 2009-10-16
Replaces draft-scholl-idr-advisory
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-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

Tom Scholl (tom.scholl@att.com)
John Scudder (jgs@juniper.net)
Richard Steenbergen (ras@e-gerbil.net)
David Freedman (david.freedman@uk.clara.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)