[GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)

Christopher Morrow <christopher.morrow@gmail.com> Mon, 10 August 2015 17:29 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C881ACD21; Mon, 10 Aug 2015 10:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qs3rVbgSuJnY; Mon, 10 Aug 2015 10:29:42 -0700 (PDT)
Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB4B61A7007; Mon, 10 Aug 2015 10:29:41 -0700 (PDT)
Received: by ykeo23 with SMTP id o23so145059202yke.3; Mon, 10 Aug 2015 10:29:41 -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=V4rjHKsm02Jw2aLfRDxT5Z4FuN64W7IVOixu0VLcxW4=; b=r2nB5TwctCqdv856uTh270A621q0KWMX0jvY6TcXE6C/K5SqZCSR27fPX+qEbJ/gcS u1X0Tod/o4VL7HqQa6pJmAn4xvUJrMyQyhkpBbijJAcL7y/jb4w/dM3b0a176wMnhn6P mK9NqRZQ/e6aCSFI3h589xRGOTAJL2GLfcdgAooQlKoyzhFugOrCXE7DydBqciQOXy3X hRCz1GTEx2kNwmb9Q5625kaEJcXH6zRUErK/ZqVoKcRqDjEnu8vvvBBMKHIKip1qEvse QYgtn+Fh29+KPishA6OqOJzCPWIfFK09/oIRYXckpHwbzZ+N7cggO6OlbLzIgQ3HPO/D wajA==
MIME-Version: 1.0
X-Received: by 10.129.85.66 with SMTP id j63mr21048029ywb.28.1439227781198; Mon, 10 Aug 2015 10:29:41 -0700 (PDT)
Received: by 10.13.228.196 with HTTP; Mon, 10 Aug 2015 10:29:41 -0700 (PDT)
Date: Mon, 10 Aug 2015 13:29:41 -0400
Message-ID: <CAL9jLaaOPvY2WZtunCOkuuCDV5-Do+cpHBfa8eEhquGdzSLVuA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow-ads@tools.ietf.org" <grow-ads@tools.ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/tMkBxITOebdIoWG1LWxmmULaM_4>
Subject: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Aug 2015 17:29:43 -0000

Howdy grow folk,
please consider this a WGLC for:
  draft-ietf-grow-route-leak-problem-definition

Abstract:
  "A systemic vulnerability of the Border Gateway Protocol routing
   system, known as 'route leaks', has received significant attention in
   recent years.  Frequent incidents that result in significant
   disruptions to Internet routing are labeled "route leaks", but to
   date we have lacked a common definition of the term.  In this
   document, we provide a working definition of route leaks, keeping in
   mind the real occurrences that have received significant attention.
   Further, we attempt to enumerate (though not exhaustively) different
   types of route leaks based on observed events on the Internet.  We
   aim to provide a taxonomy that covers several forms of route leaks
   that have been observed and are of concern to Internet user community
   as well as the network operator community."

there have been 3 revisions of this document in the WG, along with 2
prior to adoption. A new read-through of the document and comments
prior to sending this along to the IESG would be great!

Let's get that done in the next 14 days and pass this up the chain for
further review/comment/process.

thanks!
-chris
(grow-co-chair)