Subject: [Idr] Fwd: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04

From: Rob Shakir <[email-masked]>
Date: Tue, 12 Jun 2012 12:04:20 +0100

Hi IDR,

As there has been discussion of this draft previously in IDR, as well as GROW. Please accept this as a heads-up for the WGLC in GROW being initiated.

As per usual, comments and/or feedback are very welcome.

Many thanks,
r.

Begin forwarded message:

> From: Christopher Morrow <[email-masked]>
> Subject: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
> Date: 11 June 2012 21:21:49 GMT+01:00
> To: [email-masked], "[email-masked] [email-masked]" <[email-masked]>
> 
> Hello GROW-WG folk,
> Please take this message as the start of a 2 week, ending 6/25/2012
> (June 25, 2012) WGLC for the subject draft, link to current version:
>  <http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-handling-04.txt>
> 
> 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."
> 
> -Chris
> co-chair
> _______________________________________________
> GROW mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/grow