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

Christopher Morrow <christopher.morrow@gmail.com> Mon, 11 June 2012 20:21 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791FF21F85C3 for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 13:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.372
X-Spam-Level:
X-Spam-Status: No, score=-103.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L5Wm4ybpjDuG for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 13:21:53 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 95CD621F85AF for <grow@ietf.org>; Mon, 11 Jun 2012 13:21:51 -0700 (PDT)
Received: by yhq56 with SMTP id 56so3418830yhq.31 for <grow@ietf.org>; Mon, 11 Jun 2012 13:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=nN86dXuxca/34s7mr2oTM+VxO7mXUotU8/E9dIOCK6Q=; b=saJs+aTc7nCfz+x4I4QX/b8WZ4QZe9Nz5F6LBwkq2qwMZbk7dm5bcuZzLvfY/M6fVw NvqM8j31rZAJwrdfHOTLSiCIzDUFs7cwJ7eI/jcsZeojW7+Fq56Icojidi2u4CTMl53L 8NEtNuUpoKLl4DTO/j5awM47ERb8Vr7uamfzHRUCrnybE89M/fq79v5gA4MKcGpEDYQt BQZUpSQl1FZoJDkRTkVlnK+gZtYcEIooI62AkAUIibeGpzstLLTXkNUuu7Kk6FEkylLD W1BUPL+pBRN+psEOCIYoWVX7PPq5lKjRUtCBswe2v6GMAtJVFUKw32YiPjxtuZvlnpGF rp4w==
MIME-Version: 1.0
Received: by 10.60.24.7 with SMTP id q7mr17734852oef.50.1339446109067; Mon, 11 Jun 2012 13:21:49 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Mon, 11 Jun 2012 13:21:49 -0700 (PDT)
Date: Mon, 11 Jun 2012 16:21:49 -0400
Message-ID: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:21:53 -0000

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