datatracker.ietf.org
Sign In
Version 5.1.0, 2014-03-05
Report a bug

BGP OPERATIONAL Message
draft-ietf-idr-operational-message-00

Document type: Expired Internet-Draft (idr WG)
Document stream: IETF
Last updated: 2012-09-14 (latest revision 2012-03-13)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html
IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned
IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided
Email Authors | IPR Disclosures | Dependencies to this document | References | Referenced By | Check nits | History feed | Search Mailing Lists

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-idr-operational-message

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

David Freedman <david.freedman@uk.clara.net>
Robert Raszuk <robert@raszuk.net>
Rob Shakir <rob.shakir@bt.com>

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