Mitigating Negative Impact of Maintenance through BGP Session Culling
draft-iops-grow-bgp-session-culling-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Will Hargrave , Matt Griswold , Job Snijders , Nick Hilliard | ||
Last updated | 2017-09-28 (Latest revision 2017-03-27) | ||
Replaced by | draft-ietf-grow-bgp-session-culling | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-grow-bgp-session-culling | |
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
This document outlines an approach to mitigate negative impact on networks resulting from maintenance activities. It includes guidance for both IP networks and Internet Exchange Points (IXPs). The approach is to ensure BGP-4 sessions affected by the maintenance are forcefully torn down before the actual maintenance activities commence.
Authors
Will Hargrave
Matt Griswold
Job Snijders
Nick Hilliard
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)