Operational Requirements for Enhanced Error Handling Behaviour in BGP-4
draft-ietf-grow-ops-reqs-for-bgp-error-handling-07

Internet Engineering Task Force                                R. Shakir
Internet-Draft                                                        BT
Intended status: Informational                          November 9, 2014
Expires: May 13, 2015

Operational Requirements for Enhanced Error Handling Behaviour in BGP-4
           draft-ietf-grow-ops-reqs-for-bgp-error-handling-07

Abstract

   BGP-4 is utilised as a key intra- and inter-Autonomous System routing
   protocol in modern IP networks.  The failure modes as defined by the
   original protocol standards are based on a number of assumptions
   around the impact of session failure.  Numerous incidents both in the
   global Internet routing table and within Service Provider networks
   have been caused by strict handling of a single invalid UPDATE
   message causing large-scale failures in one or more Autonomous
   Systems.

   This memo describes the current use of BGP-4 within Service Provider
   networks, and outlines a set of requirements for further work to
   enhance the mechanisms available to a BGP-4 implementation when
   erroneous data is detected.  Whilst this document does not provide
   specification of any standard, it is intended as an overview of a set
   of enhancements to BGP-4 to improve the protocol's robustness to suit
   its current deployment.

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 May 13, 2015.

Shakir                    Expires May 13, 2015                  [Page 1]
Internet-Draft     Requirements for BGP Error Handling     November 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.

Table of Contents

   1.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Role of BGP-4 in Service Provider Networks  . . . . . . .   3
     2.2.  Service Requirements for Amended BGP Error Handling . . .   4
   3.  Classes of Errors within UPDATE Messages  . . . . . . . . . .   6
     3.1.  Characteristics of Session Scope Errors . . . . . . . . .   6
     3.2.  Characteristics of Message Scope Errors . . . . . . . . .   7
     3.3.  Characteristics of Attribute Scope Errors . . . . . . . .   7
     3.4.  Avoiding Session Scope Errors . . . . . . . . . . . . . .   7
     3.5.  Future Attributes introduced to BGP . . . . . . . . . . .   8
   4.  Error Handling for Non-Critical Errors  . . . . . . . . . . .   8
     4.1.  NLRI-level Error Handling Requirements  . . . . . . . . .   8
       4.1.1.  Notifying the Remote Peer of Non-Critical Errors  . .   9
     4.2.  Recovering RIB Consistency following NLRI-level Error
           Handling  . . . . . . . . . . . . . . . . . . . . . . . .  10
   5.  Error Handling for Critical Errors  . . . . . . . . . . . . .  10
     5.1.  Long-Lived Critical Errors  . . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     9.2.  Informational References  . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",