BGP OPERATIONAL Message
draft-frs-bgp-operational-message-00

Document Type Expired Internet-Draft (individual)
Last updated 2011-07-01
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-frs-bgp-operational-message-00.txt

Abstract

The BGP Version 4 routing protocol (RFC4271) is now used in many ways, crossing boundaries of administrative and technical responsibility. The protocol lacks an operational messaging plane which could be utilised to diagnose, troubleshoot and inform upon various conditions across these boundaries, securely, during protocol operation, without disruption. This document proposes a new BGP message type, the OPERATIONAL message, which can be used to effect such a messaging plane for use both between and within Autonomous Systems.

Authors

Rob Shakir (rob.shakir@cw.com)
Robert Raszuk (raszuk@cisco.com)
Rob Shakir (rob.shakir@cw.com)
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.)