Revised Error Handling for BGP UPDATE Messages
draft-ietf-idr-optional-transitive-04
| Document | Type | Replaced Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2011-11-16 (latest revision 2011-10-25) | ||
| Replaces | draft-scudder-idr-optional-transitive | ||
| Replaced by | draft-ietf-idr-error-handling | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-idr-error-handling | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-idr-optional-transitive-04.txt
Abstract
According to the base BGP specification, a BGP speaker that receives an UPDATE message containing a malformed attribute is required to reset the session over which the offending attribute was received. This behavior is undesirable as a session reset would impact not only routes with the offending attribute, but also other valid routes exchanged over the session. This document partially revises the error handling for UPDATE messages, and provides guidelines for the authors of documents defining new optional attributes. Finally, it revises the error handling procedures for several existing attributes.
Authors
John Scudder
(jgs@juniper.net)
Enke Chen
(enkechen@cisco.com)
Prodosh Mohapatra
(pmohapat@cisco.com)
Keyur Patel
(keyupate@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)