BGP Notification Cease: I'll Be Back
draft-ward-bgp4-ibb-00

Document Type Expired Internet-Draft (individual)
Last updated 1999-06-21
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-ward-bgp4-ibb-00.txt

Abstract

Many recent router architectures decouple the routing engine from the forwarding engine, so that packet forwarding can continue even if routing software is not active. The current definition of the BGP protocol does not support this. We propose a new variety of CEASE NOTIFICATION message (IBB) which indicates to a peer that the router sending the notification expects to be able to continue forwarding traffic for a certain period of time without an established BGP peering session. We also propose a new OPEN message (ICB) that if received during the HOLDTIME period, does not require conventional reestablishment of the BGP peering session. These capabilities are useful for orderly and non-intrusive routing software updates, operating system updates, AS number migration, redundancy and catastrophic event handling.

Authors

John Scudder (jgs@bgp.nu)
David Ward (dward@cisco.com)

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