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

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    grow mailing list <grow@ietf.org>,
    grow chair <grow-chairs@tools.ietf.org>
Subject: Document Action: 'Operational Requirements for Enhanced Error Handling Behaviour in BGP-4' to Informational RFC (draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt)

The IESG has approved the following document:
- 'Operational Requirements for Enhanced Error Handling Behaviour in
   BGP-4'
  (draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt) as
Informational RFC

This document is the product of the Global Routing Operations Working
Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-handling/

Ballot Text

Technical Summary

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


Working Group Summary

       Significant discussion on-list about this draft, which
        included its earlier version being split into this document and a sister
        document in IDR. The discussions in GROW settled down into a
        successful conclusion for this document.

Document Quality
 
     No outstanding problems detected

Personnel

Chris Morrow is document shepherd. Ron Bonica is responsible AD.

RFC Editor Note

  (Insert RFC Editor Note here or remove section)

IRTF Note

  (Insert IRTF Note here or remove section)

IESG Note

  (Insert IESG Note here or remove section)

IANA Note

  (Insert IANA Note here or remove section)

RFC Editor Note