RFC 7606: Revised Error Handling for BGP UPDATE Messages
In plain English — editorial summary, not part of the RFC
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 because 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 attributes. Finally, it revises the error handling procedures for a number of existing attributes. This document updates error handling for RFCs 1997, 4271, 4360, 4456, 4760, 5543, 5701, and 6368.
Document record
- Document ID
- RFC7606
- Published
- August 2015
- Authors
- E. Chen; J. Scudder; P. Mohapatra; K. Patel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7607Codification of AS 0 ProcessingCurrent
August 2015
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 7674Clarification of the Flowspec Redirect Extended CommunityObsoleted
October 2015
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7938Use of BGP for Routing in Large-Scale Data CentersCurrent
August 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?