Error Handling For Optional Transitive Bgp Attributes
Cisco Systems March 1, 2009 Error Handling for Optional Transitive BGP Attributes draft-scudder-idr-optional-transitive-00.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on September 2, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract According to the base BGP specification, a BGP speaker that receives an UPDATE message containing a malformed attribute is required to Scudder & Chen Expires September 2, 2009 [Page 1] Internet-Draft Optional Transitive Error Handling March 2009 reset the session over which the offending attribute was received. This behavior is undesirable in the case of optional transitive attributes. This document revises BGP's error-handling rules for optional transitive attributes, and provides guidelines for the authors of documents defining new optional transitive attributes. It also revises the error handling procedures for several existing optional transitive attributes. 1. Introduction According to the base BGP specification [RFC4271], 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 in the case of optional transitive attributes whose Partial bit is set; the reason is that such attributes have been propagated without being checked by intermediate routers that do not recognize the attribute -- in effect the attributes have been tunneled, and when they do reach a router that recognizes and checks them, the session that
Update: 1997, 4271, 4360 (if approved) E. Chen Intended Status: Standards Track P. Mohapatra Expires: April 26, 2012 K. Patel Cisco Systems October 25, 2011 Revised Error Handling for BGP UPDATE Messages 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, https://tools.ietf.org/html/draft-scudder-idr-optional-transitive-00 and provides guidelines for the authors of documents defining new optional attributes. Finally, it revises the error handling procedures for several existing attributes. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that https://tools.ietf.org/html/draft-ietf-idr-optional-transitive other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on April 26, 2012. draft-ietf-idr-optional-transitive-04.txt [Page 1] Internet Draft draft-ietf-idr-optional-transitive-04.txt Oct., 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 1. Introduction Accor
of Life Solutions Services Tech Library Design & Architecture Center Support Support Case Management Cases/RMAs Your Open Cases Your Open RMAs Create a Case/RMA Managing Contact Support https://www.juniper.net/documentation/en_US/junos14.1/topics/topic-map/bgp-error-tolerance.html Product Warranty Downloads & Docs Platforms Junos ScreenOS Junos Space All Downloads Documentation TechLibrary Pathfinder Troubleshooting Knowledge Base Service Now Service Insight Problem Report Search Contracts & Licenses Contracts/Products Register New Product Serial Number Entitlement Search Contracts/Products Order Status Licenses Generate Product Licenses Find License Keys Security Security Intelligence Report a Vulnerability Training Training Training Courses Learning error handling Paths Getting Started Learning Bytes Certification Getting Started Already Certified Exam Registration Fast Track Program Academic Alliance How to Buy How to Buy Contact Sales Request a Quote Buy from a Local Partner Find a Sales Office All Buying Options About Juniper Partners Community TechLibrary Navigation CLI Explorer Compliance Advisor Content Explorer Documentation Help Enterprise MIBs EOL Documentation error handling for Feature Explorer Glossary Hardware Compatibility Tool Pathfinder Portable Libraries SNMP MIB Explorer System Log Explorer XML API Explorer New Table of Contents Guide That Contains This Content [+] Expand All [-] Collapse All Home > Support > Technical Documentation > Junos OS > Example: Configuring Error Handling for BGP Update Messages Rate and give feedback: Feedback Received. Thank You! DynamicBook 0 Select All Rate and give feedback: X This document helped resolve my issue Yes No Additional Comments 800 characters remaining May we contact you if necessary? Name: E-mail: Enter a valid Email ID Need product assistance? Contact Juniper Support Submit DynamicBooks i Add Multiple Topics to DynamicBooks Add Current Topic to DynamicBooks Related DocumentationACX SeriesExample: Preventing BGP Session ResetsJ SeriesExamples: Configuring BGP Flap DampingM SeriesExample: Preventing BGP Session ResetsExamples: Configuring BGP Flap DampingMX SeriesExample: Preventing BGP Session ResetsExamples: Configuring BGP Flap DampingSRX SeriesExamples: Configuring BGP Flap DampingT SeriesExample: Preventing BGP Session ResetsExamples: Configuring BGP Flap Damping Example: Configuring Error Handling for BGP Update MessagesUnderstanding Error Handling for BGP Update M