datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Revised Error Handling for BGP UPDATE Messages
draft-ietf-idr-error-handling-06

Document type: Active Internet-Draft (idr WG)
Document stream: IETF
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: Susan Hares

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Internet Engineering Task Force                             E. Chen, Ed.
Internet-Draft                                       Cisco Systems, Inc.
Updates: 1997, 4271, 4360, 4456, 4760, 5701 (if approved)J. Scudder, Ed.
Intended status: Standards Track                        Juniper Networks
Expires: August 18, 2014                                    P. Mohapatra
                                                  Cumulus Networks, Inc.
                                                                K. Patel
                                                     Cisco Systems, Inc.
                                                       February 14, 2014

             Revised Error Handling for BGP UPDATE Messages
                    draft-ietf-idr-error-handling-06

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 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, and 5701.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on August 18, 2014.

Chen, et al.             Expires August 18, 2014                [Page 1]
Internet-Draft       Revised Error Handling for BGP        February 2014

Copyright Notice

   Copyright (c) 2014 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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Revision to Base Specification  . . . . . . . . . . . . . . .   4
   3.  Parsing of NLRI Fields  . . . . . . . . . . . . . . . . . . .   6
     3.1.  Inconsistency of Attribute Length Fields  . . . . . . . .   6
     3.2.  Syntactic Correctness of NLRI Fields  . . . . . . . . . .   7
   4.  Operational Considerations  . . . . . . . . . . . . . . . . .   7
   5.  Error Handling Procedures for Existing Attributes . . . . . .   8
     5.1.  ORIGIN  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  AS_PATH . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  NEXT_HOP  . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.4.  MULTI_EXIT_DESC . . . . . . . . . . . . . . . . . . . . .   9
     5.5.  LOCAL_PREF  . . . . . . . . . . . . . . . . . . . . . . .   9
     5.6.  ATOMIC_AGGREGATE  . . . . . . . . . . . . . . . . . . . .   9
     5.7.  AGGREGATOR  . . . . . . . . . . . . . . . . . . . . . . .   9

[include full document text]