
From christopher.morrow@gmail.com  Fri Apr  1 00:53:31 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 345733A6BD7 for <grow@core3.amsl.com>; Fri,  1 Apr 2011 00:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.581
X-Spam-Level: 
X-Spam-Status: No, score=-103.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lGquIEyviR5L for <grow@core3.amsl.com>; Fri,  1 Apr 2011 00:53:29 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 491503A6BF7 for <grow@ietf.org>; Fri,  1 Apr 2011 00:53:29 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3049719wyb.31 for <grow@ietf.org>; Fri, 01 Apr 2011 00:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=gGNJj131iVesn3rRJPTneQUoWcYNAR9FaGIdf1EkFzg=; b=hyjoZL08yw3ozo9Q7rG8YpTBIxYQmNoZLsUoguqoOHRHVeRDxitZMgi6NRwn2LoR4W Ts953dATGWAB0CIQhUhQPrHFtabMD1XbGEUR6lxgctTM71BzVaGQF2DBOVKQyZM/N3Il RN7zToBCcNrQEi2O72wtx+UO8CWxPNXrpwVDY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TyZHpMUEwvdJcawB6IJTxp8W1IdMKMVq4dIyUjVVVMO/br0fJYamwErp6tKBf9bQyA dWpnP4RvA+5b/jaEH4Dako9rMcJAiIQ9LCDX7WoUDfv1La0atx97FctYqu4OLqx0n+ln Pb/V1NhpCIau5987jN4tgzFU94avn5w2A+MKg=
MIME-Version: 1.0
Received: by 10.216.144.166 with SMTP id n38mr522305wej.75.1301644508842; Fri, 01 Apr 2011 00:55:08 -0700 (PDT)
Received: by 10.216.185.16 with HTTP; Fri, 1 Apr 2011 00:55:08 -0700 (PDT)
Date: Fri, 1 Apr 2011 09:55:08 +0200
Message-ID: <AANLkTinV89qabJ-KnFYEnzAkqC7-rXdp5=8SZA=AsMb9@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>,  draft-shishio-grow-isp-rfd-implement-survey@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] Call for WG Adoption - draft-shishio-grow-isp-rfd-implement-survey-01
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 07:53:31 -0000

Given the discussion in IDR yesterday and in GROW today, it seems that
the room temperature pushed to adoption the survey work and potential
default's change discussion to GROW. Could we get some discussion
on-list about this, draft:
draft-shishio-grow-isp-rfd-implement-survey-01

<http://tools.ietf.org/html/draft-shishio-grow-isp-rfd-implement-survey-01>

"BGP Route Flap Damping [RFC2439] is a mechanism that targets route
   stability.  It penalyzes routes that flap with the aim of reducing
   CPU load on the routers.

   But it has side-effects.  Thus, in 2006, RIPE recommended not to use
   Route Flap Damping (see RIPE-378).

   Now, some researchers propose to turn RFD, with less aggressive
   parameters, back on [draft-ymbk-rfd-usable].

   This document describes results of a survey conducted amoung service
   provider on their use of BGP Route Flap Damping."

Again, with the goal to pick up the draft as a WG Item, and end up
feeding Route Flap Dampening defaults back into vendor
implementations.

Thanks!
-Chris
grow-co-chair

From christopher.morrow@gmail.com  Fri Apr  1 01:17:22 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40A7B3A6B0B for <grow@core3.amsl.com>; Fri,  1 Apr 2011 01:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.468
X-Spam-Level: 
X-Spam-Status: No, score=-103.468 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YqsNdASMCM7a for <grow@core3.amsl.com>; Fri,  1 Apr 2011 01:17:21 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 3790A3A6AF8 for <grow@ietf.org>; Fri,  1 Apr 2011 01:17:21 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3067616wyb.31 for <grow@ietf.org>; Fri, 01 Apr 2011 01:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=Wzg0QLAcDVmKnZVS3zzEb7sgWKPTfjRKQOgGDelDvqM=; b=rmcBCLtf4EydFlg8UT+VxpeBoXMp77hu+5i7DX5lqBfSkhIjhl8RS/DRZm1ah3SAEf sF/aZxkEoeR/4haoI0Wpps3egMcWHc4cJ5krUDNo1TLheIjI4w85J2bMwIdzzdvYFTP4 TfBK2GhQ+j2S0IHqVDczCCrYbRpC9mPBAzsKI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=qsddfg93Pf86EGLLhhwOxVUJMDkEDyY230WfwXjhebHuAzy2I8RBIP072VaEJFAbKs afqhK1umHnlp/NnyDZ8BKH5ReMq0d/lrJHFxrGvngO1UFy4b7IQWwUMqsuvLDhUgep6p M6udbXH9iv+JfhWwulyBUx/7rj6IVDxbyYjBE=
MIME-Version: 1.0
Received: by 10.216.244.6 with SMTP id l6mr548874wer.60.1301645940713; Fri, 01 Apr 2011 01:19:00 -0700 (PDT)
Received: by 10.216.185.16 with HTTP; Fri, 1 Apr 2011 01:19:00 -0700 (PDT)
In-Reply-To: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com>
Date: Fri, 1 Apr 2011 10:19:00 +0200
Message-ID: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org,  draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org,  "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 08:17:22 -0000

(+wg this time, for realz)

On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
> Given the discussion in the room today, and the overlap of
> readers-of-draft + folk-asking-for-adoption a call to the list is
> appropriate.
>
> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
> =A0<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-hand=
ling-01.txt>
>
> "BGP-4 is utilised as a key intra- and inter-Autonomous System routing
> =A0 protocol in modern IP networks. =A0The failure modes as defined by th=
e
> =A0 original protocol standards are based on a number of assumptions
> =A0 around the impact of session failure. =A0Numerous incidents both in t=
he
> =A0 global Internet routing table and within Service Provider networks
> =A0 have been caused by strict handling of a single invalid UPDATE
> =A0 message causing large-scale failures in one or more Autonomous
> =A0 Systems.
>
> =A0 This memo describes the current use of BGP-4 within Service Provider
> =A0 networks, and outlines a set of requirements for further work to
> =A0 enhance the mechanisms available to a BGP-4 implementation when
> =A0 erroneous data is detected. =A0Whilst this document does not provide
> =A0 specification of any standard, it is intended as an overview of a set
> =A0 of enhancements to BGP-4 to improve the protocol's robustness to suit
> =A0 its current deployment."
>
> can we have some discussion about adoption in GROW for this at this
> time, please?
>
> Call ends 4/14/2011
>
> Thanks!
> -Chris
> grow-wg-co-chair
>

From jie.dong@huawei.com  Fri Apr  1 01:32:22 2011
Return-Path: <jie.dong@huawei.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1022A3A63D2 for <grow@core3.amsl.com>; Fri,  1 Apr 2011 01:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.465
X-Spam-Level: 
X-Spam-Status: No, score=-3.465 tagged_above=-999 required=5 tests=[AWL=0.803,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i0HZdAVUuTmp for <grow@core3.amsl.com>; Fri,  1 Apr 2011 01:32:21 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C91FB3A63EB for <grow@ietf.org>; Fri,  1 Apr 2011 01:32:20 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIY004TZT3Q3H@szxga03-in.huawei.com> for grow@ietf.org; Fri, 01 Apr 2011 16:33:26 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LIY0012NT3P6H@szxga03-in.huawei.com> for grow@ietf.org; Fri, 01 Apr 2011 16:33:26 +0800 (CST)
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 01 Apr 2011 16:33:18 +0800
Received: from SZXEML508-MBX.china.huawei.com ([169.254.6.115]) by szxeml403-hub.china.huawei.com ([169.254.173.75]) with mapi id 14.01.0270.001; Fri, 01 Apr 2011 16:33:25 +0800
Date: Fri, 01 Apr 2011 08:33:25 +0000
From: Jie Dong <jie.dong@huawei.com>
In-reply-to: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
X-Originating-IP: [172.24.2.40]
To: Christopher Morrow <christopher.morrow@gmail.com>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>, "draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org" <draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Message-id: <76CD132C3ADEF848BD84D028D243C927AD42B4@szxeml508-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
Thread-index: AQHL8EXvaSq4T/8X4EultOO51vtu65RIrki2
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 08:32:22 -0000

Support.

-Jie
________________________________________
From: grow-bounces@ietf.org [grow-bounces@ietf.org] on behalf of Christopher Morrow [christopher.morrow@gmail.com]
Sent: Friday, April 01, 2011 16:19
To: grow-chairs@tools.ietf.org; draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org; grow@ietf.org grow@ietf.org
Subject: Re: [GROW] Call for WG Adoption -      draft-shakir-idr-ops-reqs-for-bgp-error-handling

(+wg this time, for realz)

On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
> Given the discussion in the room today, and the overlap of
> readers-of-draft + folk-asking-for-adoption a call to the list is
> appropriate.
>
> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>  <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling-01.txt>
>
> "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."
>
> can we have some discussion about adoption in GROW for this at this
> time, please?
>
> Call ends 4/14/2011
>
> Thanks!
> -Chris
> grow-wg-co-chair
>
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

From russell@heilling.net  Fri Apr  1 02:31:11 2011
Return-Path: <russell@heilling.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67EFA3A67B3 for <grow@core3.amsl.com>; Fri,  1 Apr 2011 02:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.157
X-Spam-Level: 
X-Spam-Status: No, score=-3.157 tagged_above=-999 required=5 tests=[AWL=-0.407, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v+LHLEOslUnO for <grow@core3.amsl.com>; Fri,  1 Apr 2011 02:31:10 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id E3C9B3A67A4 for <grow@ietf.org>; Fri,  1 Apr 2011 02:31:09 -0700 (PDT)
Received: by qyk7 with SMTP id 7so2189286qyk.10 for <grow@ietf.org>; Fri, 01 Apr 2011 02:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heilling.net; s=google; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Ki3iJAERZiclfOUjGwOLNAn28flFnrELAF4+ifNeeN8=; b=gkVQx38QU8yT4oi4TGyD2sCEON3duwvvEPCfTvtrnVwLxf9eF6nusnHnXOOKGQwLw5 zBNTkCIW1y5eH43Vejx0UcI0XIFxoD1gWzW5zThya8VF7lEnjq5dnvyvtkCeVH70P3nh AbhSoDx2NWmtsHXXDu3Eyj8VA/YncCrLikL2Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=heilling.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AiI5NEcZyRSEP3pLs6w9NknUZvXy8Yd1Tt7pyaVbYUbBlaxC/AYSWMuKMHye3PAedQ OLCzGWCu6WJ245WMrm87AgnJbdMn8pC7glAAJHYbW6xshdtxfQxQ56GxVvyYfJNgiVU0 TXDxK7gUgQiBuXQd5tCooTTLlW37/z8V3ABug=
MIME-Version: 1.0
Received: by 10.229.102.165 with SMTP id g37mr3173019qco.120.1301650369777; Fri, 01 Apr 2011 02:32:49 -0700 (PDT)
Received: by 10.229.89.197 with HTTP; Fri, 1 Apr 2011 02:32:49 -0700 (PDT)
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Date: Fri, 1 Apr 2011 10:32:49 +0100
Message-ID: <AANLkTinnR=_WRkF2N7JNoW-Rz2dXfCn+ccWC3JzxR_UT@mail.gmail.com>
From: Russell Heilling <russell@heilling.net>
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 09:31:11 -0000

+1 support

On 1 April 2011 09:19, Christopher Morrow <christopher.morrow@gmail.com> wr=
ote:
> (+wg this time, for realz)
>
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>> =A0<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-han=
dling-01.txt>
>>
>> "BGP-4 is utilised as a key intra- and inter-Autonomous System routing
>> =A0 protocol in modern IP networks. =A0The failure modes as defined by t=
he
>> =A0 original protocol standards are based on a number of assumptions
>> =A0 around the impact of session failure. =A0Numerous incidents both in =
the
>> =A0 global Internet routing table and within Service Provider networks
>> =A0 have been caused by strict handling of a single invalid UPDATE
>> =A0 message causing large-scale failures in one or more Autonomous
>> =A0 Systems.
>>
>> =A0 This memo describes the current use of BGP-4 within Service Provider
>> =A0 networks, and outlines a set of requirements for further work to
>> =A0 enhance the mechanisms available to a BGP-4 implementation when
>> =A0 erroneous data is detected. =A0Whilst this document does not provide
>> =A0 specification of any standard, it is intended as an overview of a se=
t
>> =A0 of enhancements to BGP-4 to improve the protocol's robustness to sui=
t
>> =A0 its current deployment."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



--=20
Russell Heilling=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://perl=
monkey.blogspot.com
"The amazing ability of the bee to adapt herself often helps the
=A0beekeeper to overcome the results of his ignorance." - Brother Adam

From Donald.Smith@qwest.com  Fri Apr  1 08:03:05 2011
Return-Path: <Donald.Smith@qwest.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 895A83A6881 for <grow@core3.amsl.com>; Fri,  1 Apr 2011 08:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=0.024,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stPW8ft+eFbC for <grow@core3.amsl.com>; Fri,  1 Apr 2011 08:03:04 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by core3.amsl.com (Postfix) with ESMTP id 93E293A6875 for <grow@ietf.org>; Fri,  1 Apr 2011 08:03:04 -0700 (PDT)
Received: from lxomavmpc030.qintra.com (lxomavmpc030.qintra.com [151.117.207.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id p31F4akO003758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Apr 2011 10:04:37 -0500 (CDT)
Received: from lxomavmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id C89EC1E004F; Fri,  1 Apr 2011 10:04:31 -0500 (CDT)
Received: from suomp61i.qintra.com (unknown [10.6.10.61]) by lxomavmpc030.qintra.com (Postfix) with ESMTP id ADF621E003F; Fri,  1 Apr 2011 10:04:31 -0500 (CDT)
Received: from qtdenexhtm21.AD.QINTRA.COM (localhost [127.0.0.1]) by suomp61i.qintra.com (8.14.4/8.14.4) with ESMTP id p31F4Uq0014301; Fri, 1 Apr 2011 10:04:30 -0500 (CDT)
Received: from qtdenexmbm24.AD.QINTRA.COM ([151.119.91.226]) by qtdenexhtm21.AD.QINTRA.COM ([151.119.91.230]) with mapi; Fri, 1 Apr 2011 09:04:29 -0600
From: "Smith, Donald" <Donald.Smith@qwest.com>
To: Russell Heilling <russell@heilling.net>, Christopher Morrow <christopher.morrow@gmail.com>
Date: Fri, 1 Apr 2011 09:04:04 -0600
Thread-Topic: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
Thread-Index: AcvwT8mSWG/h0iLWSVelcv3do8ydWQALkDHW
Message-ID: <B01905DA0C7CDC478F42870679DF0F10101B05583E@qtdenexmbm24.AD.QINTRA.COM>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>, <AANLkTinnR=_WRkF2N7JNoW-Rz2dXfCn+ccWC3JzxR_UT@mail.gmail.com>
In-Reply-To: <AANLkTinnR=_WRkF2N7JNoW-Rz2dXfCn+ccWC3JzxR_UT@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org" <draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 15:03:05 -0000

+1 support
(coffee !=3D sleep) & (!coffee =3D=3D sleep)
 Donald.Smith@qwest.com
________________________________________
From: grow-bounces@ietf.org [grow-bounces@ietf.org] On Behalf Of Russell He=
illing [russell@heilling.net]
Sent: Friday, April 01, 2011 3:32 AM
To: Christopher Morrow
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org; grow@i=
etf.org grow@ietf.org; grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption -      draft-shakir-idr-ops-reqs-f=
or-bgp-error-handling

+1 support

On 1 April 2011 09:19, Christopher Morrow <christopher.morrow@gmail.com> wr=
ote:
> (+wg this time, for realz)
>
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handl=
ing-01.txt>
>>
>> "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."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



--
Russell Heilling                        http://perlmonkey.blogspot.com
"The amazing ability of the bee to adapt herself often helps the
 beekeeper to overcome the results of his ignorance." - Brother Adam
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

From jgs@juniper.net  Fri Apr  1 08:07:59 2011
Return-Path: <jgs@juniper.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 171EF3A688C for <grow@core3.amsl.com>; Fri,  1 Apr 2011 08:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.437
X-Spam-Level: 
X-Spam-Status: No, score=-6.437 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkfCnrE+EeCQ for <grow@core3.amsl.com>; Fri,  1 Apr 2011 08:07:58 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by core3.amsl.com (Postfix) with ESMTP id 13EB43A689A for <grow@ietf.org>; Fri,  1 Apr 2011 08:07:58 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKTZXqrQkaT60g/LuKJ3jmyBYeIpP3BA+C@postini.com; Fri, 01 Apr 2011 08:09:38 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Fri, 1 Apr 2011 08:07:40 -0700
From: John Scudder <jgs@juniper.net>
To: Christopher Morrow <christopher.morrow@gmail.com>
Date: Fri, 1 Apr 2011 08:09:13 -0700
Thread-Topic: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
Thread-Index: AcvwfotawhEg0a8MQ0iL6nD/3zlCYg==
Message-ID: <839E1F07-5E7C-4C11-80D3-708F72A39A8B@juniper.net>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org" <draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Apr 2011 15:07:59 -0000

Yes please.

--John

On Apr 1, 2011, at 10:19 AM, Christopher Morrow wrote:

> (+wg this time, for realz)
>=20
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>=20
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handl=
ing-01.txt>
>>=20
>> "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.
>>=20
>>   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."
>>=20
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>=20
>> Call ends 4/14/2011
>>=20
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From jakob.heitz@ericsson.com  Fri Apr  1 22:57:57 2011
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12CEC3A6A43 for <grow@core3.amsl.com>; Fri,  1 Apr 2011 22:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.686
X-Spam-Level: 
X-Spam-Status: No, score=-5.686 tagged_above=-999 required=5 tests=[AWL=-0.606, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4YE7HlCHZe2j for <grow@core3.amsl.com>; Fri,  1 Apr 2011 22:57:55 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 5E4B53A6A3B for <grow@ietf.org>; Fri,  1 Apr 2011 22:57:55 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p325xLpk008006; Sat, 2 Apr 2011 00:59:36 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.2.141]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Sat, 2 Apr 2011 01:59:14 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
Date: Sat, 2 Apr 2011 01:59:15 -0400
Thread-Topic: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
Thread-Index: Acvw+xfWx/wauCIKSLW/xam0HzWo9g==
Message-ID: <46303164-FB28-40DC-BE1C-85FFAD2E3CC9@ericsson.com>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org" <draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 02 Apr 2011 05:57:57 -0000

Support

--
Jakob Heitz.


On Apr 1, 2011, at 1:19 AM, "Christopher Morrow" <christopher.morrow@gmail.=
com> wrote:

> (+wg this time, for realz)
>=20
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>=20
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handl=
ing-01.txt>
>>=20
>> "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.
>>=20
>>   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."
>>=20
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>=20
>> Call ends 4/14/2011
>>=20
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From danny@tcb.net  Sat Apr  2 05:54:54 2011
Return-Path: <danny@tcb.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C1713A67E9 for <grow@core3.amsl.com>; Sat,  2 Apr 2011 05:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.188
X-Spam-Level: 
X-Spam-Status: No, score=-110.188 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CP3SQXu6kUrJ for <grow@core3.amsl.com>; Sat,  2 Apr 2011 05:54:53 -0700 (PDT)
Received: from farnsworth.verisignlabs.com (farnsworth.verisignlabs.com [72.13.58.64]) by core3.amsl.com (Postfix) with ESMTP id 8DCEF3A67E6 for <grow@ietf.org>; Sat,  2 Apr 2011 05:54:53 -0700 (PDT)
Received: from monsoon.verisignlabs.com (h87.s239.verisign.com [216.168.239.87]) by farnsworth.verisignlabs.com (Postfix) with ESMTP id 6D6C0A539; Sat,  2 Apr 2011 12:56:34 +0000 (UTC)
Received: from dul1dmcphers-m2.vcorp.ad.vrsn.com (dul1dmcphers-m2.vcorp.ad.vrsn.com [10.100.0.40]) by monsoon.verisignlabs.com (Postfix) with ESMTP id 1047B24251E; Sat,  2 Apr 2011 08:56:33 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Date: Sat, 2 Apr 2011 08:56:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8146D209-0DCD-4DD4-A322-ABD10165B1BD@tcb.net>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 02 Apr 2011 12:54:54 -0000

Support.

-danny


On Apr 1, 2011, at 4:19 AM, Christopher Morrow wrote:

> (+wg this time, for realz)
>=20
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>=20
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  =
<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling=
-01.txt>
>>=20
>> "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.
>>=20
>>   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."
>>=20
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>=20
>> Call ends 4/14/2011
>>=20
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From raszuk@cisco.com  Sat Apr  2 06:27:00 2011
Return-Path: <raszuk@cisco.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0AC83A67F5 for <grow@core3.amsl.com>; Sat,  2 Apr 2011 06:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.405
X-Spam-Level: 
X-Spam-Status: No, score=-10.405 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FZKvjCG0o1c for <grow@core3.amsl.com>; Sat,  2 Apr 2011 06:26:59 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 2B49D3A67F1 for <grow@ietf.org>; Sat,  2 Apr 2011 06:26:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=raszuk@cisco.com; l=1787; q=dns/txt; s=iport; t=1301750920; x=1302960520; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=dDsZPAAEZ72fvOPyPWl6nJErcBscktnqL5IcbLm9gFU=; b=R20ybdwK+22oAqHWnYXQ1vnxXBXS8ptEEZiA+hPN4kkGLHyzSex5gikG knxzv35/oI3/UElMuGlsKXTtnL8IwGq6uwFrgncfKmOjRjojS3FydOKPy lWt/Io86acnAUt79UN9bfFBnvT7qMXFNP8Och+PC8+/KUg/f52UwJ/P0P c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFMjl02rRDoH/2dsb2JhbAClY3ekKoJwDgGYcIVrBI0jg1uDMQ
X-IronPort-AV: E=Sophos;i="4.63,287,1299456000"; d="scan'208";a="674852869"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-6.cisco.com with ESMTP; 02 Apr 2011 13:28:40 +0000
Received: from [192.168.1.66] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p32DScuj009511; Sat, 2 Apr 2011 13:28:39 GMT
Message-ID: <4D972498.9070301@cisco.com>
Date: Sat, 02 Apr 2011 15:28:56 +0200
From: Robert Raszuk <raszuk@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 02 Apr 2011 13:27:00 -0000

Support.

R.

> (+wg this time, for realz)
>
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com>  wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>   <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling-01.txt>
>>
>> "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."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>


From shtsuchi@cisco.com  Sat Apr  2 07:15:30 2011
Return-Path: <shtsuchi@cisco.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5BD83A6824 for <grow@core3.amsl.com>; Sat,  2 Apr 2011 07:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.372
X-Spam-Level: 
X-Spam-Status: No, score=-10.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMqzlHxGWOj4 for <grow@core3.amsl.com>; Sat,  2 Apr 2011 07:15:29 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id C56273A681E for <grow@ietf.org>; Sat,  2 Apr 2011 07:15:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=1832; q=dns/txt; s=iport; t=1301753831; x=1302963431; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=C6xQ4umrVTiolGOxoMk/casWKAM3WM0dutBUWmDCUL4=; b=a14kdqmTe4AIhxOo4Tb699yHQFjipeCgMyh6ZY5Qq2AW9LP4K51RIq4D orvGB+TvMTL07Np7lI+DitXWEet905EtUHEXgly7MWQ52IwN7zyYK417z g1gHJb6Ehsg31XNUeLLxEi4uUW+qbw1u4lwwu4N4hqlVimVFDhmBhKe7X Y=;
X-IronPort-AV: E=Sophos;i="4.63,287,1299456000"; d="scan'208";a="353160139"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by sj-iport-5.cisco.com with ESMTP; 02 Apr 2011 14:17:10 +0000
Received: from [10.71.33.218] (tky-shtsuchi-8719.cisco.com [10.71.33.218]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id p32EH2Kv012327;  Sat, 2 Apr 2011 14:17:04 GMT
Message-ID: <4D972FDC.9060704@cisco.com>
Date: Sat, 02 Apr 2011 23:17:00 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: christopher.morrow@gmail.com, grow-chairs@tools.ietf.org, draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, grow@ietf.org
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 02 Apr 2011 14:15:31 -0000

+1 Support

(2011/04/01 17:19), Christopher Morrow wrote:
> (+wg this time, for realz)
> 
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com>  wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>   <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling-01.txt>
>>
>> "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."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 



From ilya@nobulus.com  Sun Apr  3 13:39:35 2011
Return-Path: <ilya@nobulus.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 015663A687D for <grow@core3.amsl.com>; Sun,  3 Apr 2011 13:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level: 
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[AWL=0.197,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKpZxI161gv6 for <grow@core3.amsl.com>; Sun,  3 Apr 2011 13:39:34 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by core3.amsl.com (Postfix) with ESMTP id C992C3A685B for <grow@ietf.org>; Sun,  3 Apr 2011 13:39:33 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id 8CF1F17121; Sun,  3 Apr 2011 22:41:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id E66m-Z5SCzGr; Sun,  3 Apr 2011 22:41:11 +0200 (CEST)
Received: from [IPv6:2001:6f8:893:ffff:225:4bff:fea6:3684] (unknown [IPv6:2001:6f8:893:ffff:225:4bff:fea6:3684]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nobulus.com (Postfix) with ESMTPSA id 3EC8E1711F; Sun,  3 Apr 2011 22:41:11 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ilya Varlashkin <ilya@nobulus.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Date: Sun, 3 Apr 2011 22:41:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <500DAE59-AFB7-4FFE-A93C-55BCBD4DB432@nobulus.com>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 03 Apr 2011 20:39:35 -0000

support

/iLya

On Apr 1, 2011, at 10:19 , Christopher Morrow wrote:

> (+wg this time, for realz)
>=20
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>=20
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  =
<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling=
-01.txt>
>>=20
>> "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.
>>=20
>>   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."
>>=20
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>=20
>> Call ends 4/14/2011
>>=20
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20

/iLya




From bruno.decraene@orange-ftgroup.com  Mon Apr  4 00:41:34 2011
Return-Path: <bruno.decraene@orange-ftgroup.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 829A63A6932 for <grow@core3.amsl.com>; Mon,  4 Apr 2011 00:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.834
X-Spam-Level: 
X-Spam-Status: No, score=-2.834 tagged_above=-999 required=5 tests=[AWL=0.188,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OpG304z3uYO for <grow@core3.amsl.com>; Mon,  4 Apr 2011 00:41:27 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 6813A3A6936 for <grow@ietf.org>; Mon,  4 Apr 2011 00:41:27 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 0F3CF7D8002; Mon,  4 Apr 2011 09:49:16 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id F2B24778003; Mon,  4 Apr 2011 09:49:15 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 4 Apr 2011 09:43:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 4 Apr 2011 09:43:07 +0200
Message-ID: <FE8F6A65A433A744964C65B6EDFDC24002126EDB@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [GROW] Call for WG Adoption -draft-shakir-idr-ops-reqs-for-bgp-error-handling
Thread-Index: AcvwRYoAD4OjCJhSRoex8OVRh0T68ACVk48A
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
From: <bruno.decraene@orange-ftgroup.com>
To: <christopher.morrow@gmail.com>, <grow-chairs@tools.ietf.org>, <grow@ietf.org>
X-OriginalArrivalTime: 04 Apr 2011 07:43:08.0737 (UTC) FILETIME=[F1004310:01CBF29B]
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption -draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 07:41:34 -0000

Support.

> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf =
Of Christopher Morrow
> Sent: Friday, April 01, 2011 10:19 AM
> To: grow-chairs@tools.ietf.org; =
draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org;
> grow@ietf.org grow@ietf.org
> Subject: Re: [GROW] Call for WG Adoption =
-draft-shakir-idr-ops-reqs-for-bgp-error-handling
>=20
> (+wg this time, for realz)
>=20
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
> > Given the discussion in the room today, and the overlap of
> > readers-of-draft + folk-asking-for-adoption a call to the list is
> > appropriate.
> >
> > For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
> > =
=A0<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-hand=
ling-01.txt>
> >
> > "BGP-4 is utilised as a key intra- and inter-Autonomous System =
routing
> > =A0 protocol in modern IP networks. =A0The failure modes as defined =
by the
> > =A0 original protocol standards are based on a number of assumptions
> > =A0 around the impact of session failure. =A0Numerous incidents both =
in the
> > =A0 global Internet routing table and within Service Provider =
networks
> > =A0 have been caused by strict handling of a single invalid UPDATE
> > =A0 message causing large-scale failures in one or more Autonomous
> > =A0 Systems.
> >
> > =A0 This memo describes the current use of BGP-4 within Service =
Provider
> > =A0 networks, and outlines a set of requirements for further work to
> > =A0 enhance the mechanisms available to a BGP-4 implementation when
> > =A0 erroneous data is detected. =A0Whilst this document does not =
provide
> > =A0 specification of any standard, it is intended as an overview of =
a set
> > =A0 of enhancements to BGP-4 to improve the protocol's robustness to =
suit
> > =A0 its current deployment."
> >
> > can we have some discussion about adoption in GROW for this at this
> > time, please?
> >
> > Call ends 4/14/2011
> >
> > Thanks!
> > -Chris
> > grow-wg-co-chair
> >
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From warren@kumari.net  Mon Apr  4 06:20:11 2011
Return-Path: <warren@kumari.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B5C73A69F2 for <grow@core3.amsl.com>; Mon,  4 Apr 2011 06:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gQt7VMylz2J for <grow@core3.amsl.com>; Mon,  4 Apr 2011 06:20:04 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id 47AF23A693B for <grow@ietf.org>; Mon,  4 Apr 2011 06:20:02 -0700 (PDT)
Received: from [172.19.118.183] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 1F89B1B40958; Mon,  4 Apr 2011 09:21:44 -0400 (EDT)
Message-Id: <68450291-C8D5-4E89-BF51-41BCA8EC6E70@kumari.net>
From: Warren Kumari <warren@kumari.net>
To: Christopher Morrow <christopher.morrow@gmail.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 4 Apr 2011 09:21:22 -0400
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 13:20:11 -0000

And another "support"...
On Apr 1, 2011, at 4:19 AM, Christopher Morrow wrote:

> (+wg this time, for realz)
>
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling-01.txt 
>> >
>>
>> "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."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>


From carlosm3011.ietf@gmail.com  Mon Apr  4 11:53:29 2011
Return-Path: <carlosm3011.ietf@gmail.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E2603A679C for <grow@core3.amsl.com>; Mon,  4 Apr 2011 11:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.93
X-Spam-Level: 
X-Spam-Status: No, score=-2.93 tagged_above=-999 required=5 tests=[AWL=0.441,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUYFSrIoVD97 for <grow@core3.amsl.com>; Mon,  4 Apr 2011 11:53:28 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 3DC343A6784 for <grow@ietf.org>; Mon,  4 Apr 2011 11:53:28 -0700 (PDT)
Received: by wyb29 with SMTP id 29so5551352wyb.31 for <grow@ietf.org>; Mon, 04 Apr 2011 11:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:x-google-sender-delegation :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=AjVG1PjbxZ2e7O6V5wASDVsYxPUb7b2y41tB9FxPyWs=; b=OlGCt6NU6G2CI1bioDjE0iaR247dUEcapI2mi0+ShrLU97XssiFQpbDB0FfcNmAvJT VY2uZyMOej/v3MtTiQ3ivOpOS+tNjEykm0Wa9qq0pBaFZFaAUX/m+MlxEud09ZPs0o66 eSg5xRhkrXXWSPziJUHKv67rrTqMRx3IL2kNg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:x-google-sender-delegation:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; b=MToA5r8eKZvmTROn1iPCSPYLV8rw92dv4GzMMF41d2EXFx4THExv857Ohj6y1FFLy6 HKFzTv6JVS1hzENtq6oZGQBvgMw14oMK7s8N6CEHgfApFK88TImIIvoTamxAt6xIo+Is BKwKO6KzqEtGFJ0dBJsR5uVK+D3A1TZDUnGbQ=
MIME-Version: 1.0
Received: by 10.216.171.133 with SMTP id r5mr4179540wel.91.1301943310115; Mon, 04 Apr 2011 11:55:10 -0700 (PDT)
Sender: carlosm3011@gmail.com
X-Google-Sender-Delegation: carlosm3011@gmail.com
Received: by 10.217.0.131 with HTTP; Mon, 4 Apr 2011 11:55:10 -0700 (PDT)
In-Reply-To: <68450291-C8D5-4E89-BF51-41BCA8EC6E70@kumari.net>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com> <68450291-C8D5-4E89-BF51-41BCA8EC6E70@kumari.net>
Date: Mon, 4 Apr 2011 18:55:10 +0000
X-Google-Sender-Auth: WKbgkGdfMMqXib59OzI0Z6a4u64
Message-ID: <BANLkTimMHV_iht2_ooCgQiGgdJXE-wkb5Q@mail.gmail.com>
From: Carlos Martinez <carlosm3011.ietf@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=0016e65a0c7c84658d04a01c4c4e
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 18:53:29 -0000

--0016e65a0c7c84658d04a01c4c4e
Content-Type: text/plain; charset=ISO-8859-1

+1 support

On Mon, Apr 4, 2011 at 1:21 PM, Warren Kumari <warren@kumari.net> wrote:

> And another "support"...
>
> On Apr 1, 2011, at 4:19 AM, Christopher Morrow wrote:
>
>  (+wg this time, for realz)
>>
>> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
>> <christopher.morrow@gmail.com> wrote:
>>
>>> Given the discussion in the room today, and the overlap of
>>> readers-of-draft + folk-asking-for-adoption a call to the list is
>>> appropriate.
>>>
>>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>>  <
>>> http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling-01.txt
>>> >
>>>
>>> "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."
>>>
>>> can we have some discussion about adoption in GROW for this at this
>>> time, please?
>>>
>>> Call ends 4/14/2011
>>>
>>> Thanks!
>>> -Chris
>>> grow-wg-co-chair
>>>
>>>  _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

--0016e65a0c7c84658d04a01c4c4e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1 support<br><br><div class=3D"gmail_quote">On Mon, Apr 4, 2011 at 1:21 PM=
, Warren Kumari <span dir=3D"ltr">&lt;<a href=3D"mailto:warren@kumari.net">=
warren@kumari.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
And another &quot;support&quot;...<div class=3D"im"><br>
On Apr 1, 2011, at 4:19 AM, Christopher Morrow wrote:<br>
<br>
</div><div><div></div><div class=3D"h5"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(+wg this time, for realz)<br>
<br>
On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow<br>
&lt;<a href=3D"mailto:christopher.morrow@gmail.com" target=3D"_blank">chris=
topher.morrow@gmail.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Given the discussion in the room today, and the overlap of<br>
readers-of-draft + folk-asking-for-adoption a call to the list is<br>
appropriate.<br>
<br>
For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling<br>
=A0&lt;<a href=3D"http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bg=
p-error-handling-01.txt" target=3D"_blank">http://tools.ietf.org/id/draft-s=
hakir-idr-ops-reqs-for-bgp-error-handling-01.txt</a>&gt;<br>
<br>
&quot;BGP-4 is utilised as a key intra- and inter-Autonomous System routing=
<br>
 =A0protocol in modern IP networks. =A0The failure modes as defined by the<=
br>
 =A0original protocol standards are based on a number of assumptions<br>
 =A0around the impact of session failure. =A0Numerous incidents both in the=
<br>
 =A0global Internet routing table and within Service Provider networks<br>
 =A0have been caused by strict handling of a single invalid UPDATE<br>
 =A0message causing large-scale failures in one or more Autonomous<br>
 =A0Systems.<br>
<br>
 =A0This memo describes the current use of BGP-4 within Service Provider<br=
>
 =A0networks, and outlines a set of requirements for further work to<br>
 =A0enhance the mechanisms available to a BGP-4 implementation when<br>
 =A0erroneous data is detected. =A0Whilst this document does not provide<br=
>
 =A0specification of any standard, it is intended as an overview of a set<b=
r>
 =A0of enhancements to BGP-4 to improve the protocol&#39;s robustness to su=
it<br>
 =A0its current deployment.&quot;<br>
<br>
can we have some discussion about adoption in GROW for this at this<br>
time, please?<br>
<br>
Call ends 4/14/2011<br>
<br>
Thanks!<br>
-Chris<br>
grow-wg-co-chair<br>
<br>
</blockquote>
_______________________________________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/grow</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/grow</a><br>
</div></div></blockquote></div><br>

--0016e65a0c7c84658d04a01c4c4e--

From tom@someaddress.net  Mon Apr  4 13:22:12 2011
Return-Path: <tom@someaddress.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D15453A67C0 for <grow@core3.amsl.com>; Mon,  4 Apr 2011 13:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jI8-o+X7kg0o for <grow@core3.amsl.com>; Mon,  4 Apr 2011 13:22:12 -0700 (PDT)
Received: from zinc.someaddress.net (zinc.someaddress.net [82.152.104.99]) by core3.amsl.com (Postfix) with ESMTP id 368423A67B1 for <grow@ietf.org>; Mon,  4 Apr 2011 13:22:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zinc.someaddress.net (Postfix) with ESMTPS id DC4F73C001025 for <grow@ietf.org>; Mon,  4 Apr 2011 21:23:22 +0100 (BST)
Date: Mon, 4 Apr 2011 21:23:22 +0100 (BST)
From: Tom Hodgson <tom@someaddress.net>
X-X-Sender: tom@zinc
To: grow@ietf.org
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1104042121160.12191@zinc>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 20:22:12 -0000

On Fri, 1 Apr 2011, Christopher Morrow wrote:
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.

Draft expounds our current concerns in this regard well and agree that it 
should be adopted.

-- 
Tom Hodgson
tom@someaddress.net

From paaguti@gmail.com  Mon Apr  4 23:07:41 2011
Return-Path: <paaguti@gmail.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74DA33A68B3 for <grow@core3.amsl.com>; Mon,  4 Apr 2011 23:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A99kcDL6PK-T for <grow@core3.amsl.com>; Mon,  4 Apr 2011 23:07:40 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 2A8A83A6806 for <grow@ietf.org>; Mon,  4 Apr 2011 23:07:40 -0700 (PDT)
Received: by vxg33 with SMTP id 33so36846vxg.31 for <grow@ietf.org>; Mon, 04 Apr 2011 23:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yc1tpOCuVPQ3AsRComHNmK/csmn8r2EWOiqqS/9Msdc=; b=KCdBCoHYx1WeBGIwdMycoNIcaZ7tJwk2TJCSyPsmm5a6JkvUcMNSVzaL+fPM4F8sVE mLFkcOssEQhoFcELGZTw/0iDrxAWpp6XhuAu0QZNhUAll8D1MBWxtbD7TD+EdZzghjMW oqkzV0LPjBSKKXJxNKvbZzoQyLrV+2PHWLGG0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MDZ6b2JVxvXily/l/20Pl0qGO5I+yOERYjOrRlqb+5qEHAbh7b4nC8Mg7F9HJtDPib lp1WJdoIRXsJk8GoDvpsqaGDkgW0/Mz0BULYQGtHVO1kjAMf+ArWL83zmQQMUv3XYVPi rVfBEHSR8OmhpU+uVKBL9j0v9cJ4pC5TDZqK4=
MIME-Version: 1.0
Received: by 10.220.183.134 with SMTP id cg6mr397087vcb.222.1301983762529; Mon, 04 Apr 2011 23:09:22 -0700 (PDT)
Received: by 10.220.200.77 with HTTP; Mon, 4 Apr 2011 23:09:22 -0700 (PDT)
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Date: Tue, 5 Apr 2011 08:09:22 +0200
Message-ID: <BANLkTikxAt3ijU1=4NN2QxSzi2x9ev-Swg@mail.gmail.com>
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 05 Apr 2011 06:07:41 -0000

Support

On Fri, Apr 1, 2011 at 10:19 AM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
> (+wg this time, for realz)
>
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>> =A0<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-han=
dling-01.txt>
>>
>> "BGP-4 is utilised as a key intra- and inter-Autonomous System routing
>> =A0 protocol in modern IP networks. =A0The failure modes as defined by t=
he
>> =A0 original protocol standards are based on a number of assumptions
>> =A0 around the impact of session failure. =A0Numerous incidents both in =
the
>> =A0 global Internet routing table and within Service Provider networks
>> =A0 have been caused by strict handling of a single invalid UPDATE
>> =A0 message causing large-scale failures in one or more Autonomous
>> =A0 Systems.
>>
>> =A0 This memo describes the current use of BGP-4 within Service Provider
>> =A0 networks, and outlines a set of requirements for further work to
>> =A0 enhance the mechanisms available to a BGP-4 implementation when
>> =A0 erroneous data is detected. =A0Whilst this document does not provide
>> =A0 specification of any standard, it is intended as an overview of a se=
t
>> =A0 of enhancements to BGP-4 to improve the protocol's robustness to sui=
t
>> =A0 its current deployment."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

From chwhite@drevil.org  Tue Apr  5 05:33:39 2011
Return-Path: <chwhite@drevil.org>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C88643A67A1 for <grow@core3.amsl.com>; Tue,  5 Apr 2011 05:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.429
X-Spam-Level: 
X-Spam-Status: No, score=-3.429 tagged_above=-999 required=5 tests=[AWL=-1.057, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISpvKbDN11oH for <grow@core3.amsl.com>; Tue,  5 Apr 2011 05:33:34 -0700 (PDT)
Received: from fatbastard.drevil.org (fatbastard.drevil.org [206.213.88.6]) by core3.amsl.com (Postfix) with ESMTP id 470813A67B2 for <grow@ietf.org>; Tue,  5 Apr 2011 05:33:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by fatbastard.drevil.org (Postfix) with ESMTP id 187B34CB5738; Tue,  5 Apr 2011 05:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at drevil.org
Received: from fatbastard.drevil.org ([127.0.0.1]) by localhost (fatbastard.drevil.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fi574e10G2yD; Tue,  5 Apr 2011 05:35:12 -0700 (PDT)
Received: from shagwell.drevil.org (shagwell.drevil.org [206.213.88.227]) by fatbastard.drevil.org (Postfix) with ESMTPSA id 334314CB5729; Tue,  5 Apr 2011 05:35:12 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Chris White <chwhite@drevil.org>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
Date: Tue, 5 Apr 2011 05:35:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FC2F926-F726-444E-8693-14C5FA73DF7E@drevil.org>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 05 Apr 2011 12:33:39 -0000

+1

On Apr 1, 2011, at 1:19 AM, Christopher Morrow wrote:

> (+wg this time, for realz)
>=20
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>=20
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  =
<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling=
-01.txt>
>>=20
>> "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.
>>=20
>>   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."
>>=20
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>=20
>> Call ends 4/14/2011
>>=20
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From colin@spakka.net  Tue Apr  5 06:38:51 2011
Return-Path: <colin@spakka.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 845D528C0F4 for <grow@core3.amsl.com>; Tue,  5 Apr 2011 06:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.581
X-Spam-Level: 
X-Spam-Status: No, score=-1.581 tagged_above=-999 required=5 tests=[AWL=0.791,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qu4vApeLWo6 for <grow@core3.amsl.com>; Tue,  5 Apr 2011 06:38:44 -0700 (PDT)
Received: from mailhosting.spakka.net (mailhosting.spakka.net [213.229.81.134]) by core3.amsl.com (Postfix) with ESMTP id 9E9103A67DF for <grow@ietf.org>; Tue,  5 Apr 2011 06:38:44 -0700 (PDT)
Received: from loki.as29550.net ([213.229.80.68]) by mailhosting.spakka.net with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from <colin@spakka.net>) id 1Q76Ud-00056S-CR for grow@ietf.org; Tue, 05 Apr 2011 14:40:27 +0100
Message-ID: <4D9B1BCA.4000104@spakka.net>
Date: Tue, 05 Apr 2011 14:40:26 +0100
From: Colin Petrie <colin@spakka.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110307 Iceowl/1.0b1 Icedove/3.0.11
MIME-Version: 1.0
To: grow@ietf.org
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
In-Reply-To: <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SMTP-Authenticated-User: colin@spakka.net
Subject: Re: [GROW] Call for WG Adoption -	draft-shakir-idr-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 05 Apr 2011 13:38:51 -0000

Support.

On 01/04/11 09:19, Christopher Morrow wrote:
> (+wg this time, for realz)
> 
> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> Given the discussion in the room today, and the overlap of
>> readers-of-draft + folk-asking-for-adoption a call to the list is
>> appropriate.
>>
>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>  <http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-handling-01.txt>
>>
>> "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."
>>
>> can we have some discussion about adoption in GROW for this at this
>> time, please?
>>
>> Call ends 4/14/2011
>>
>> Thanks!
>> -Chris
>> grow-wg-co-chair
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From wwwrun@rfc-editor.org  Thu Apr 14 11:25:51 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3F46FE073F; Thu, 14 Apr 2011 11:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.352
X-Spam-Level: 
X-Spam-Status: No, score=-102.352 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P5pY9njxtrwo; Thu, 14 Apr 2011 11:25:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfc.amsl.com (Postfix) with ESMTP id 3E816E079F; Thu, 14 Apr 2011 11:25:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B4694E0776; Thu, 14 Apr 2011 11:25:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110414182537.B4694E0776@rfc-editor.org>
Date: Thu, 14 Apr 2011 11:25:37 -0700 (PDT)
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
Subject: [GROW] RFC 6198 on Requirements for the Graceful Shutdown of BGP Sessions
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: Thu, 14 Apr 2011 18:25:51 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6198

        Title:      Requirements for the Graceful Shutdown 
                    of BGP Sessions 
        Author:     B. Decraene, P. Francois,
                    C. Pelsser, Z. Ahmad,
                    A.J. Elizondo Armengol, T. Takeda
        Status:     Informational
        Stream:     IETF
        Date:       April 2011
        Mailbox:    bruno.decraene@orange-ftgroup.com, 
                    francois@info.ucl.ac.be, 
                    cristel@iij.ad.jp,  zubair.ahmad@orange-ftgroup.com, 
                    ajea@tid.es,  takeda.tomonori@lab.ntt.co.jp
        Pages:      20
        Characters: 37906
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-bgp-graceful-shutdown-requirements-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6198.txt

The Border Gateway Protocol (BGP) is heavily used in Service Provider
networks for both Internet and BGP/MPLS VPN services.  For resiliency
purposes, redundant routers and BGP sessions can be deployed to reduce
the consequences of an Autonomous System Border Router (ASBR) or BGP
session breakdown on customers' or peers' traffic.  However, simply
taking down or even bringing up a BGP session for maintenance purposes
may still induce connectivity losses during the BGP convergence.  This
is no longer satisfactory for new applications (e.g., voice over IP,
online gaming, VPN).  Therefore, a solution is required for the
graceful shutdown of a (set of) BGP session(s) in order to limit the
amount of traffic loss during a planned shutdown.  This document
expresses requirements for such a solution.  This document is not 
an Internet Standards Track specification; it is
published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From tkirkham@cisco.com  Thu Apr 14 17:10:55 2011
Return-Path: <tkirkham@cisco.com>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A7DCCE06C5 for <grow@ietfc.amsl.com>; Thu, 14 Apr 2011 17:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.178
X-Spam-Level: 
X-Spam-Status: No, score=-9.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_GIF_ATTACH=1.42]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzpPoEN4Clja for <grow@ietfc.amsl.com>; Thu, 14 Apr 2011 17:10:55 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfc.amsl.com (Postfix) with ESMTP id 960BBE0723 for <grow@ietf.org>; Thu, 14 Apr 2011 17:10:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tkirkham@cisco.com; l=16037; q=dns/txt; s=iport; t=1302826254; x=1304035854; h=message-id:date:from:mime-version:to:subject; bh=TkT11ockHQYpUkpe6O8mnxlWCn7quH0SkRGoGXMzMpo=; b=ibbUpZckEG46PlMMpgC17F4s6gyMCPt+6YB2tclRIu9eWYxZoyUbtxgu ouJm0qH5t4KHUJoES9MCvp1bPDoaskzQoR90sSYCF1r47mHKuk2qJHvWk Vt9Z/asbclgp27P8OBjh/sBUt1i2ICqayEOsRYJfhaygg0g+4zCjL8KIu 8=;
X-Files: logo.gif, smime.p7s : 837, 5878
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoHAAqMp02tJXG+/2dsb2JhbACCYpVcjT93p0mdBQKFbASNbw
X-IronPort-AV: E=Sophos;i="4.64,214,1301875200";  d="gif'147?p7s'147?scan'147,208,217,147";a="681751766"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-6.cisco.com with ESMTP; 15 Apr 2011 00:10:53 +0000
Received: from syd-tkirkham-8716.cisco.com (syd-tkirkham-8716.cisco.com [10.67.228.215]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3F0ApVa017070 for <grow@ietf.org>; Fri, 15 Apr 2011 00:10:52 GMT
Message-ID: <4DA78D0B.1070808@cisco.com>
Date: Fri, 15 Apr 2011 10:10:51 +1000
From: Anthony Kirkham <tkirkham@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: grow@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090802030708050602060308"
Subject: [GROW] Posted new draft of private IP in SP core
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: Fri, 15 Apr 2011 00:10:55 -0000

This is a cryptographically signed message in MIME format.

--------------ms090802030708050602060308
Content-Type: multipart/alternative;
 boundary="------------080005080201030105070004"

This is a multi-part message in MIME format.
--------------080005080201030105070004
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

All,

I have been working on this for a while now as time permits. I have=20
posted a new version of:

Filename:	 draft-kirkham-private-ip-sp-cores
Revision:	 03
Title:		 Issues with Private IP Addressing in the Internet
Creation_date:	 2011-04-15
WG ID:		 Independent Submission
Number_of_pages: 12

I'd appreciate any thoughts and feedback.

Regards and thanks in advance,
Tony K

--=20

*Anthony Kirkham*
*Solution Architect

***World Wide Security
Service Practice
**
tkirkham@cisco.com <mailto:tkirkham@cisco.com>
Phone: *+61 (0)7 3238 8203*
Mobile: *+61 (0)401 890 494*

CISSP, CCIE# - 1378

=09

**


Level 12, 300 Adelaide Street
Brisbane, Qld, 4000
Australia
Cisco home page <http://www.cisco.com/global/AU/>

=09




--------------080005080201030105070004
Content-Type: multipart/related;
 boundary="------------010701000305020107000008"


--------------010701000305020107000008
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DISO=
-8859-1">
  </head>
  <body bgcolor=3D"#ffffff" text=3D"#000000">
    All,<br>
    <br>
    I have been working on this for a while now as time permits. I have
    posted a new version of:<br>
    <pre wrap=3D"">Filename:	 draft-kirkham-private-ip-sp-cores
Revision:	 03
Title:		 Issues with Private IP Addressing in the Internet
Creation_date:	 2011-04-15
WG ID:		 Independent Submission
Number_of_pages: 12
</pre>
    I'd appreciate any thoughts and feedback. <br>
    <br>
    Regards and thanks in advance,<br>
    Tony K<br>
    <br>
    <div class=3D"moz-signature">-- <br>
      <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0" width=3D"54=
3">
        <tbody>
          <tr>
            <td>
              <table style=3D"background-color: transparent;
                background-image:
                url(&quot;http://www.cisco.com/global/EMEA/brand/signatur=
e/corporate/none.jpg&quot;);
                background-repeat: no-repeat; background-attachment:
                scroll; background-position: center top;
                -moz-background-size: auto auto; -moz-background-clip:
                -moz-initial; -moz-background-origin: -moz-initial;
                -moz-background-inline-policy: -moz-initial;" border=3D"0=
"
                cellpadding=3D"0" cellspacing=3D"0" width=3D"543">
                <tbody>
                  <tr>
                    <td colspan=3D"3"><img
                        src=3D"cid:part1.06090304.07000707@cisco.com"
                        height=3D"73" width=3D"110"> </td>
                  </tr>
                  <tr>
                    <td style=3D"padding-left: 24px; padding-bottom:
                      15px;" align=3D"left" nowrap=3D"nowrap" valign=3D"t=
op">
                      <p style=3D"font-family: Arial,Helvetica,sans-serif=
;
                        font-size: 11px; font-weight: normal; color:
                        rgb(102, 102, 102);"><strong>Anthony
                          Kirkham</strong><br>
                        <strong>Solution Architect<br>
                          <br>
                        </strong><strong><strong>World Wide Security<br>
                            Service Practice<br>
                          </strong></strong><br>
                        <a style=3D"color: rgb(102, 102, 102);"
                          href=3D"mailto:tkirkham@cisco.com">tkirkham@cis=
co.com</a>
                        <br>
                        Phone: <strong>+61 (0)7 3238 8203</strong><br>
                        Mobile: <strong>+61 (0)401 890 494</strong><br>
                        <br>
                        CISSP, CCIE# - 1378</p>
                    </td>
                    <td style=3D"padding-left: 20px; padding-bottom:
                      10px;" nowrap=3D"nowrap" valign=3D"top">
                      <p style=3D"font-family: Arial,Helvetica,sans-serif=
;
                        font-size: 11px; font-weight: normal; color:
                        rgb(102, 102, 102);"><strong></strong><br>
                      </p>
                      <p style=3D"font-family: Arial,Helvetica,sans-serif=
;
                        font-size: 11px; font-weight: normal; color:
                        rgb(102, 102, 102);"><br>
                      </p>
                      <p style=3D"font-family: Arial,Helvetica,sans-serif=
;
                        font-size: 11px; font-weight: normal; color:
                        rgb(102, 102, 102);">Level
                        12, 300 Adelaide Street<br>
                        Brisbane, Qld, 4000<br>
                        Australia<br>
                        <a style=3D"color: rgb(102, 102, 102);"
                          href=3D"http://www.cisco.com/global/AU/">Cisco
                          home page</a><br>
                        <br>
                      </p>
                    </td>
                    <td width=3D"200">&nbsp;</td>
                  </tr>
                </tbody>
              </table>
              <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0"
                width=3D"100%">
                <tbody>
                  <tr>
                    <td style=3D"padding: 0px 24px; font-family:
                      Arial,Helvetica,sans-serif; font-size: 10px;
                      color: rgb(0, 153, 0);"> <br>
                    </td>
                  </tr>
                </tbody>
              </table>
            </td>
          </tr>
        </tbody>
      </table>
      <br clear=3D"all">
    </div>
  </body>
</html>

--------------010701000305020107000008
Content-Type: image/gif;
 name="logo.gif"
Content-Transfer-Encoding: base64
Content-ID: <part1.06090304.07000707@cisco.com>
Content-Disposition: inline;
 filename="logo.gif"

R0lGODlhbgBJAMQAAP///3OXqtapqq1MTcmRki9mgZkAALpqbMl/f6g5O/Xq6+vX2OTIyaMq
K/nz9OW/v5sVFsbV3Nfh5p0PD5kFBf78/P38/Pz6+v/+/rZdXpcKDKAhIvv396QvMO/g4Ny4
uSH5BAAAAAAALAAAAABuAEkAQAX/ICCOZGmeaKqubOu+cCzPdG3feK6nkln8pp5LSPoVgruc
sbQsAp1HKPM5alapImtyy+16SwKDmJBCiBEWgMUsPgg8JMHEQCGTMACP2HDgiBQZYglfOQ+G
Dy2HhiqKKI2EkJGSk5SVlpeYmZpfWkpYmypEV1GjU6QjolmfnZ0AqZWvrj6fski2UiWxsZkc
HxkNYg0IABUibAjFIgsHwAYNBwokvb8QEMIOJAwICQYQCQgLoCgLHWIdHwoKCwzExmdpGBwc
xRgDYhkXAOTm6OoMfg4CiRGgwAOBOXzEKVzIsKHDhxAjSpxIsaKNCAEibMGo0WKLVjdAVgxQ
IICpEiRN/7JIeZIEy4WsVsk8BSAmTZstLb0csVMVzZ4AgALtJLQkRY4bM3pcupDAHgMduA1Q
484AGmJO7x04kCCaCAIaxFCISmGAVwZPu+1pEK5hVgPYUBxLQ4yBvacfvlIwMCFuCbRi2I34
sHfDQ0BpDUyFNxfABTZPGwgGACjsU7MiLLx9ukEA08+gQ4seTbq06dOoU6tezbq169evd92Q
HRooDtujRdbQDZr3DN8RkeIaIXxFcZ8ljkPEOVwF81ILlT9HTkL6zJwilE+aXvN68+43vUO3
xL28eOrj0VdSbp0me6XV4acH8L6jRNw28IumXYM/7P8kPJLIISkIWIKBD3GwmcIYiwGAQWP6
cJMWHCIoCEFamInwQTNPdYCIQwqUM8YCC3zgWTKNOXAAg14pkA9lIkJAAIkmYsPBim0YcsBe
Vjn0llcnQAjYHh14phdfQGazx2QAEGaAYQ2FMVAZ75BggTZ7HFCMHHQYWcICeyAjgormPASZ
YgN00CAAjV0gwAEEEACZlsbwCMEAaWb4wFMJJMDjBkwypAABErbRzoNnFFPBghnkRcKgCVim
wQF+VSDAXXw1CuCmnHbq6aeghirqqDiEAAA7
--------------010701000305020107000008--

--------------080005080201030105070004--

--------------ms090802030708050602060308
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIRzDCC
BWkwggRRoAMCAQICEBiEutwqPE/Lj8adoZFhyswwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz
aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG
A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe
Fw0xMTAzMDMwMDAwMDBaFw0xMjAzMDEyMzU5NTlaMIIBFjEXMBUGA1UEChMOVmVyaVNpZ24s
IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52
ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp
OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ
RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRowGAYDVQQDFBFBbnRob255IFcg
S2lya2hhbTEhMB8GCSqGSIb3DQEJARYSdGtpcmtoYW1AY2lzY28uY29tMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyEPcspvGF/lNCbx2OBimhOzRqfMerwXym1v1EmAd8VsW
C/PSaJJsc3zWL2X+bpcBUVEVwR4w3wgHQ21+AiS9SjYTJAy+S0u4BRA4EeW8P0lvcvZpmFrJ
QC7AKnQtCJbFIZnWs2+9w8Hkxn7IOqr2BTj2w8X5RldwZKbPfRlcxYPrfk2xHg6vMGV99tX9
LJrhjTI3mG9sisgpItRtl76XN/0dXlQojHs7uxsp5g20Y26Cq3micS4FD/8k6USD+WM8Hy/N
2M6GkYr3Atdu/+Ki7hVNmU4DNei7VYL+DKJfIC+/SOnoVRefG0UGrZ8ClqLqQBtwqfhOq/hw
WqSmHZquWQIDAQABo4HoMIHlMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQE
AwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwFAYKYIZIAYb4RQEGBwQGFgRO
b25lMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9pbmRjMWRpZ2l0YWxpZC1nMy1jcmwudmVy
aXNpZ24uY29tL0luZEMxRGlnaXRhbElELUczLmNybDANBgkqhkiG9w0BAQUFAAOCAQEAU855
LsCaVvrpl1BRXyKpcPvj7JDFuEcIxAWeuwyYbtShW5K7gJwGlm9/dIfaBCHKfVr3UlsAtW+u
1jq+d0oNWVI/IeU7gzKU7hcATlM0/Mxzw9kNYLYSmnHetWkKEJvgZejSKDljd6x/FNxDtiaK
bK/mBPwwO+Np7kNBZwLHPanB8X5hhtRgqUCeMkcR7ZSJ0+HnoebOQ8xj7oNR7bZ58hjraniA
67jOPl3sP3h/3h74bTnE1mp7+Z2/aEFMAqwMZm6PjLiqTlf4Ls6bdXHS0qGX1h0M4f+R1c6V
VFLGW1Y6wcdMmFoDEEfQh4tHBU5onqjPu7Xrca3rI/zqbpQ+BzCCBWkwggRRoAMCAQICEBiE
utwqPE/Lj8adoZFhyswwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkG
A1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMp
MDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTAzMDMwMDAwMDBa
Fw0xMjAzMDEyMzU5NTlaMIIBFjEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsT
FlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVw
b3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBl
cnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0
c2NhcGUgRnVsbCBTZXJ2aWNlMRowGAYDVQQDFBFBbnRob255IFcgS2lya2hhbTEhMB8GCSqG
SIb3DQEJARYSdGtpcmtoYW1AY2lzY28uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAyEPcspvGF/lNCbx2OBimhOzRqfMerwXym1v1EmAd8VsWC/PSaJJsc3zWL2X+bpcB
UVEVwR4w3wgHQ21+AiS9SjYTJAy+S0u4BRA4EeW8P0lvcvZpmFrJQC7AKnQtCJbFIZnWs2+9
w8Hkxn7IOqr2BTj2w8X5RldwZKbPfRlcxYPrfk2xHg6vMGV99tX9LJrhjTI3mG9sisgpItRt
l76XN/0dXlQojHs7uxsp5g20Y26Cq3micS4FD/8k6USD+WM8Hy/N2M6GkYr3Atdu/+Ki7hVN
mU4DNei7VYL+DKJfIC+/SOnoVRefG0UGrZ8ClqLqQBtwqfhOq/hwWqSmHZquWQIDAQABo4Ho
MIHlMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNVHSUEFjAU
BggrBgEFBQcDBAYIKwYBBQUHAwIwFAYKYIZIAYb4RQEGBwQGFgROb25lMFAGA1UdHwRJMEcw
RaBDoEGGP2h0dHA6Ly9pbmRjMWRpZ2l0YWxpZC1nMy1jcmwudmVyaXNpZ24uY29tL0luZEMx
RGlnaXRhbElELUczLmNybDANBgkqhkiG9w0BAQUFAAOCAQEAU855LsCaVvrpl1BRXyKpcPvj
7JDFuEcIxAWeuwyYbtShW5K7gJwGlm9/dIfaBCHKfVr3UlsAtW+u1jq+d0oNWVI/IeU7gzKU
7hcATlM0/Mxzw9kNYLYSmnHetWkKEJvgZejSKDljd6x/FNxDtiaKbK/mBPwwO+Np7kNBZwLH
PanB8X5hhtRgqUCeMkcR7ZSJ0+HnoebOQ8xj7oNR7bZ58hjraniA67jOPl3sP3h/3h74bTnE
1mp7+Z2/aEFMAqwMZm6PjLiqTlf4Ls6bdXHS0qGX1h0M4f+R1c6VVFLGW1Y6wcdMmFoDEEfQ
h4tHBU5onqjPu7Xrca3rI/zqbpQ+BzCCBu4wggXWoAMCAQICEHEVZgVK5JEhTem8RPms09ww
DQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j
LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkg
VmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVy
aVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAt
IEczMB4XDTA5MDUwMTAwMDAwMFoXDTE5MDQzMDIzNTk1OVowgd0xCzAJBgNVBAYTAlVTMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9y
cGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVy
aVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAO3ER98qKB18Bmu71yEyyWwTj+mxjUFONPfaC+Nq+mWI
IAsRE+mb4ElOi2/VAdBfDUeRilpMdD4/xpEJu0w0no1uoYJRYvdpdliWB6+eFBgHT1q9n9Ix
slQZc0ZqGUIR7BJzIY313DDN5dlWCjHFNm0pFJe9LdqJRxmI2EsEPeu2PGcedAATDdCG2pNn
+DMDrho8a2l49sAsjuGDP3f5mf/+n1JawrSHCthsqUfBVCllQz5KwJYfwa33d69ssQRevsG2
lC2XkC0n0rse6YNqhPbEsq4jBmUmpSdYKwcitG+mYkgad/LVUCeaKdOW+yj1uiR2YuOMWev7
btVCxL5Bx/UCAwEAAaOCArkwggK1MDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0
cDovL29jc3AudmVyaXNpZ24uY29tMBIGA1UdEwEB/wQIMAYBAf8CAQAwcAYDVR0gBGkwZzBl
BgtghkgBhvhFAQcXATBWMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
Y3BzMCoGCCsGAQUFBwICMB4aHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwNAYDVR0f
BC0wKzApoCegJYYjaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0P
AQH/BAQDAgEGMG4GCCsGAQUFBwEMBGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAhMB8wBwYF
Kw4DAhoEFEtruSiWBgy70FI4mymsSweLIQUYMCYWJGh0dHA6Ly9sb2dvLnZlcmlzaWduLmNv
bS92c2xvZ28xLmdpZjAuBgNVHREEJzAlpCMwITEfMB0GA1UEAxMWUHJpdmF0ZUxhYmVsNC0y
MDQ4LTExODAdBgNVHQ4EFgQUeUdhCEH9OASiS+e1zPVD9kkrEfgwgfEGA1UdIwSB6TCB5qGB
0KSBzTCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwg
SW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFz
cyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzOCEQCLW3VW
hFSFCwDPrzhIzrGkMA0GCSqGSIb3DQEBBQUAA4IBAQA5Tc9BmYG1qQW1UjjpOYSJbOQ0qFrn
2GwJTCQaulmkhztzIfGTgc+/aGNaZ/41hSuhw12jSsI6Gd0w1sxN7/HSgZfKVFpDvzeLeo4Z
jQ9DqIzyr2CzFYqzlZw84J6zJ5ikNXIX5fwqXYfTig3C0UUq+MD0rCqTOtWuEnAI6/s74nfs
6CtkNXbNutrg0csU1nFYm77VPn222egkxSRmTF2RH3azFz5/DcYhiS+zN7ih/1yybUneZVJC
+w6I0u1KHb9L4/jMcvpIDmWOScjW+JmYO7eUPjFxBof6bFlTLtffK+1fYwCsFe0DuFUWjMZo
A+ciqHMLsbyg2lJY3QoOf8GCMYIE7DCCBOgCAQEwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7
MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNp
Z24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMwIQGIS63Co8T8uPxp2h
kWHKzDAJBgUrDgMCGgUAoIICzjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0xMTA0MTUwMDEwNTFaMCMGCSqGSIb3DQEJBDEWBBRPcWwxA0GcIOBbhrh9QYvT
GljsGDBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG
9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwggEDBgkr
BgEEAYI3EAQxgfUwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j
LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2Yg
dXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBl
cnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlk
dWFsIFN1YnNjcmliZXIgQ0EgLSBHMwIQGIS63Co8T8uPxp2hkWHKzDCCAQUGCyqGSIb3DQEJ
EAILMYH1oIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAd
BgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBh
dCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25h
IE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBT
dWJzY3JpYmVyIENBIC0gRzMCEBiEutwqPE/Lj8adoZFhyswwDQYJKoZIhvcNAQEBBQAEggEA
fZZhP0EcEXk/WSvxaZwUs0TIFdAiMblIqoWZapYQhZXBWxDgaJx1K8Jl8/elPpQnPkCJoF8U
lNSGQjEIRT9GpeTkJwuGoWaJiP8oDPZma7cGyd+/J9fPQdebiQe/JN/z5odKSbCpyN4Ttq/u
Bg5MnBrl+Vv+Vn21F55OJtHQ8kulbIJ3oqRm1iJz+/CE946x8bQ7UDDzkMSVm1J2DXfVtXEu
UxzgSH1Xs0y8dTGgXUtlW1m45Zxj9VPRb3bk8fmS0+EAYKC7EfEkkqYqgAg3ASbYSPBDWOyf
JKKMXA6+bnTptwv/sB1Pg/pQC1tke9pnBvWbbFalXdW+FYKHyvxLeQAAAAAAAA==
--------------ms090802030708050602060308--

From iesg-secretary@ietf.org  Fri Apr 15 06:38:58 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 44C65E072F; Fri, 15 Apr 2011 06:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pcZ5Gks9MQ92; Fri, 15 Apr 2011 06:38:57 -0700 (PDT)
Received: from ietfc.amsl.com (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 73A0EE0685; Fri, 15 Apr 2011 06:38:57 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.51
Message-ID: <20110415133857.24087.35296.idtracker@ietfc.amsl.com>
Date: Fri, 15 Apr 2011 06:38:57 -0700
Cc: grow@ietf.org
Subject: [GROW] Last Call: <draft-ietf-grow-geomrt-01.txt> (MRT BGP routing	information export format with geo-location extensions) to	Informational RFC
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 15 Apr 2011 13:38:58 -0000

The IESG has received a request from the Global Routing Operations WG
(grow) to consider the following document:
- 'MRT BGP routing information export format with geo-location
extensions'
  <draft-ietf-grow-geomrt-01.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-04-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/



No IPR declarations have been submitted directly on this I-D.

From christopher.morrow@gmail.com  Fri Apr 15 06:56:59 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id B16F2E069A for <grow@ietfc.amsl.com>; Fri, 15 Apr 2011 06:56:59 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEUnAzKB-LcI for <grow@ietfc.amsl.com>; Fri, 15 Apr 2011 06:56:55 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfc.amsl.com (Postfix) with ESMTP id 5E3B2E06A2 for <grow@ietf.org>; Fri, 15 Apr 2011 06:56:55 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2548822wyb.31 for <grow@ietf.org>; Fri, 15 Apr 2011 06:56:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=yhgLt3gN+E8f3CE/UIjkcUnUmkcKZbQJhLkKAJeZcD4=; b=GBudJOm88XXdKWs8DxqT8wS3z8Ze5PUrc563dtg7+xBkY2tQEGPYU31USlIbZmhDBs lyMe1QY4gYR9ykZv4ZR25bZ8vCDjGS/A2u/XzsvEi0j+UjIHo9B04i7sMMYKKb49ujxH ZDWict0XAtRYu/5yewYJok6dkd0MK0kzsUbcQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=dT1duxWKIOIUvF2qsfDxBKiflSFsCiruKLqM2bZVkyrq1v9+83LfTGhliGN3CcAdNw QblgnpYVFOqCQ+dSFMrGG4nYQpwRyWiiLyaRvTaSoetynNn9S5ZlGg0LLsoDHTyiSi6v XarE/HBtXhxdEFE8YA097ssf/OFFoM5OJFnNo=
MIME-Version: 1.0
Received: by 10.216.48.197 with SMTP id v47mr7544082web.82.1302875813079; Fri, 15 Apr 2011 06:56:53 -0700 (PDT)
Received: by 10.216.50.211 with HTTP; Fri, 15 Apr 2011 06:56:53 -0700 (PDT)
In-Reply-To: <4D9B1BCA.4000104@spakka.net>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com> <4D9B1BCA.4000104@spakka.net>
Date: Fri, 15 Apr 2011 09:56:53 -0400
Message-ID: <BANLkTikL_8Ohy30dO_WkHYbspQeNX8ji7A@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow@ietf.org, grow-chairs@tools.ietf.org,  draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
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: Fri, 15 Apr 2011 13:56:59 -0000

This call ended today, it's successful (working group would like to adopt).

Rob, could you spin a new draft with the right name and submit to the
datatracker pls?

Thanks to everyone for participating!
:)
-Chris

On Tue, Apr 5, 2011 at 9:40 AM, Colin Petrie <colin@spakka.net> wrote:
> Support.
>
> On 01/04/11 09:19, Christopher Morrow wrote:
>> (+wg this time, for realz)
>>
>> On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow
>> <christopher.morrow@gmail.com> wrote:
>>> Given the discussion in the room today, and the overlap of
>>> readers-of-draft + folk-asking-for-adoption a call to the list is
>>> appropriate.
>>>
>>> For the draft: draft-shakir-idr-ops-reqs-for-bgp-error-handling
>>> =A0<http://tools.ietf.org/id/draft-shakir-idr-ops-reqs-for-bgp-error-ha=
ndling-01.txt>
>>>
>>> "BGP-4 is utilised as a key intra- and inter-Autonomous System routing
>>> =A0 protocol in modern IP networks. =A0The failure modes as defined by =
the
>>> =A0 original protocol standards are based on a number of assumptions
>>> =A0 around the impact of session failure. =A0Numerous incidents both in=
 the
>>> =A0 global Internet routing table and within Service Provider networks
>>> =A0 have been caused by strict handling of a single invalid UPDATE
>>> =A0 message causing large-scale failures in one or more Autonomous
>>> =A0 Systems.
>>>
>>> =A0 This memo describes the current use of BGP-4 within Service Provide=
r
>>> =A0 networks, and outlines a set of requirements for further work to
>>> =A0 enhance the mechanisms available to a BGP-4 implementation when
>>> =A0 erroneous data is detected. =A0Whilst this document does not provid=
e
>>> =A0 specification of any standard, it is intended as an overview of a s=
et
>>> =A0 of enhancements to BGP-4 to improve the protocol's robustness to su=
it
>>> =A0 its current deployment."
>>>
>>> can we have some discussion about adoption in GROW for this at this
>>> time, please?
>>>
>>> Call ends 4/14/2011
>>>
>>> Thanks!
>>> -Chris
>>> grow-wg-co-chair
>>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

From iesg-secretary@ietf.org  Fri Apr 15 11:29:47 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 23005E092E; Fri, 15 Apr 2011 11:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nj+7RoOlbDAk; Fri, 15 Apr 2011 11:29:46 -0700 (PDT)
Received: from ietfc.amsl.com (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5E437E0690; Fri, 15 Apr 2011 11:29:46 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.51
Message-ID: <20110415182946.9911.9480.idtracker@ietfc.amsl.com>
Date: Fri, 15 Apr 2011 11:29:46 -0700
Cc: grow@ietf.org
Subject: [GROW] Last Call: <draft-ietf-grow-unique-origin-as-00.txt> (Unique Per-Node	Origin ASNs for Globally Anycasted Services) to BCP
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 15 Apr 2011 18:29:47 -0000

The IESG has received a request from the Global Routing Operations WG
(grow) to consider the following document:
- 'Unique Per-Node Origin ASNs for Globally Anycasted Services'
  <draft-ietf-grow-unique-origin-as-00.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-04-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-grow-unique-origin-as/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-grow-unique-origin-as/



No IPR declarations have been submitted directly on this I-D.

From Internet-Drafts@ietf.org  Fri Apr 15 12:15:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8DC93E08A9; Fri, 15 Apr 2011 12:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5juv4I+nNzY7; Fri, 15 Apr 2011 12:15:02 -0700 (PDT)
Received: from ietfc.amsl.com (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 601E2E0774; Fri, 15 Apr 2011 12:15:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.51
Message-ID: <20110415191502.22826.94362.idtracker@ietfc.amsl.com>
Date: Fri, 15 Apr 2011 12:15:02 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action:draft-ietf-grow-ops-reqs-for-bgp-error-handling-00.txt
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: Fri, 15 Apr 2011 19:15:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations Working Group of the IETF.


	Title           : Operational Requirements for Enhanced Error Handling Behaviour in BGP-4
	Author(s)       : R. Shakir
	Filename        : draft-ietf-grow-ops-reqs-for-bgp-error-handling-00.txt
	Pages           : 22
	Date            : 2011-04-15

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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-handling-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-grow-ops-reqs-for-bgp-error-handling-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-04-15121254.I-D@ietf.org>


--NextPart--

From rjs@rob.sh  Sat Apr 16 09:14:46 2011
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfc.amsl.com
Delivered-To: grow@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7014FE0685 for <grow@ietfc.amsl.com>; Sat, 16 Apr 2011 09:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6l5PUBy6y54q for <grow@ietfc.amsl.com>; Sat, 16 Apr 2011 09:14:46 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfc.amsl.com (Postfix) with ESMTP id EA616E066B for <grow@ietf.org>; Sat, 16 Apr 2011 09:14:45 -0700 (PDT)
Received: from [86.2.91.228] (helo=[10.0.0.105]) by cappuccino.rob.sh with esmtpa (Exim 4.69) (envelope-from <rjs@rob.sh>) id 1QB88p-0001qu-7f; Sat, 16 Apr 2011 17:14:36 +0100
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <BANLkTikL_8Ohy30dO_WkHYbspQeNX8ji7A@mail.gmail.com>
Date: Sat, 16 Apr 2011 17:14:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <71B4DB6C-8BA9-4D2D-981C-BC5183B2F9FD@rob.sh>
References: <AANLkTinz8=_gGQ=L3bsp+fqqPrcAz_kZ_iFx1YQesvxE@mail.gmail.com> <AANLkTimeNXpbPBcwF_dD1EKnFBSoWFD=r9i0FZ1a5Hpc@mail.gmail.com> <4D9B1BCA.4000104@spakka.net> <BANLkTikL_8Ohy30dO_WkHYbspQeNX8ji7A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, grow@ietf.org
X-Mailer: Apple Mail (2.1082)
Cc: draft-shakir-idr-ops-reqs-for-bgp-error-handling@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling
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: Sat, 16 Apr 2011 16:14:46 -0000

On 15 Apr 2011, at 14:56, Christopher Morrow wrote:

> This call ended today, it's successful (working group would like to =
adopt).
>=20
> Rob, could you spin a new draft with the right name and submit to the
> datatracker pls?

Hi Chris, GROW,

Thanks very much for supporting this adoption. As I've said before, I =
think this is a key problem affecting the robustness of networks =
utilising BGP, and am keen to resolve it!  =09

There are a number of comments that have been made to me both in Prague =
and off-line to IDR/GROW - especially regarding some clarifications of =
requirements around where the NLRI cannot be recovered from a message. I =
am hoping to update the draft to address these comments in very near =
future.

In the meantime, if there are further comments as to clarifications to =
existing requirements, or requirements that are omitted from the current =
version - please let me know, so that we can try and make this draft =
complete.

Many thanks.

Kind regards,
r.


From dhc@dcrocker.net  Wed Apr 27 13:10:22 2011
Return-Path: <dhc@dcrocker.net>
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 BDA71E0793; Wed, 27 Apr 2011 13:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uv1rzzxyUjnr; Wed, 27 Apr 2011 13:10:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 35329E0758; Wed, 27 Apr 2011 13:10:19 -0700 (PDT)
Received: from [192.168.1.4] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3RKA9vH032033 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 27 Apr 2011 13:10:14 -0700
Message-ID: <4DB87813.2070900@dcrocker.net>
Date: Wed, 27 Apr 2011 13:09:55 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Terry Manderson <terry.manderson@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 27 Apr 2011 13:10:15 -0700 (PDT)
X-Mailman-Approved-At: Wed, 27 Apr 2011 21:36:16 -0700
Cc: grow@ietf.org, Apps Review <apps-review@ietf.org>
Subject: [GROW] Apps Area Review of:  draft-ietf-grow-geomrt-01
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 27 Apr 2011 20:10:22 -0000

Howdy.

I have been selected as the Applications Area Review Team reviewer for this 
draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

Please resolve these comments along with any other Last Call comments you may 
receive. Please wait for direction from your document shepherd or AD before 
posting a new version of the draft.


Document:      draft-ietf-grow-geomrt-01


Title:         MRT BGP routing information export format with
                geo-location extensions


Reviewer:      D. Crocker <dcrocker@bbiw.net>


Review Date:   27 April 2011


Summary:

    This document provides a focused enhancement to an existing data 
specification for exchanges reports about BGP activity externally.  It adds 
geo-location information to the tables.


Major Issues:

    0) The specification generally appears reasonable and concise. The 
enhancement seems intuitively useful, although I strongly suggest the document 
make the types of utility explicit.  Why is it good to add this information to 
the table?

    1) The document presumes extensive background by the reader.  Instead it 
needs a bit of tutorial and it needs to define every term -- acronym or core 
vocabulary -- it uses, either directly or by citation

    2) The GEO_PEER_TABLE needs a column with text defining the meaning of each 
value, rather than relying on the labels' being intuitive.



Detailed comment:


>  MRT BGP routing information export format with geo-location extensions
>                      draft-ietf-grow-geomrt-01.txt
>
> Abstract
>
>    This document extends the Border Gateway Protocol (BGP) MRT export
>    format for routing information to include terrestrial coordinates.

Expand MRT so that the Abstract requires less background to understand and gives 
a basic sense of the purpose/benefit of this work.


> 2.  Introduction
>
>    Research is underway that analyzes the network behavior of routing
>    protocol transactions from routing information base snapshots in
>    relation to geographical coordinates.  Specifically the BGP routing

The first sentence is confusing.  Although I could make guess, I don't really 
know what it means.  I suggest less redundant vocabulary and possibly two 
sentences and probably more active sentence form.

In contrast, I find draft-ietf-grow-mrt's related sentence:

      "Researchers and engineers often wish to analyze network behavior by
    studying routing protocol transactions and routing information base
    snapshots."

to be reasonably clear.


>    protocol is the subject of study and the analysis has been
>    significantly aided by the availability and extension of the "MRT
>    format" [I-D.ietf-grow-mrt] originally defined in the MRT
>    Programmer's Guide [MRT PROG GUIDE].
>
>    This memo documents an extension to the "MRT format"
>    [I-D.ietf-grow-mrt] and introduces an additional definition of a MRT
>    Subtype field.
>

Lots of acronym repetition, without any acronym definition.


> 3.  Geo-location aware MRT Routing Information Subtype
>
>    The additional Subtype is defined for the TABLE_DUMP_v format, which
>    extends the TABLE_DUMP_V2 type.
>
> 3.1.  GEO_PEER_TABLE
>
>    The GEO_PEER_TABLE Subtype updates the TABLE_DUMP_v2 Types to include
>    Geo-location information in the form of WGS84 [WGS 84] formatted
>    coordinates.  The MRT subtypes would be as follows.
>
>        1    PEER_INDEX_TABLE
>        2    RIB_IPV4_UNICAST
>        3    RIB_IPV4_MULTICAST
>        4    RIB_IPV6_UNICAST
>        5    RIB_IPV6_MULTICAST
>        6    RIB_GENERIC
>        7    GEO_PEER_TABLE

What does each of these value mean?

The labels might seem intuitive, but there should be explicit text defining 
their meaning.


>    The GEO_PEER_TABLE MRT record provides the BGP ID of the collector,
>    Its latitude and longitude in WGS84 [WGS 84] format, and a list of
>    indexed peers.

I'm guessing this is the single most important text in the document, since it 
specifies exactly what location info is being provided.  I suggest the Abstract 
and Introduction summarize this, along the lines of:

    ...to include terrestrial coordinates of the BGP collector.

On the other hand, I can't find a definition of what a BGP Collector is, in this 
or related documents.  (It's not in RFC 4271, for example.)  In looking over the 
vocabulary from RFC 4271, it does appear that there is no term for the system 
that receives BGP reports.  Clearly one is needed, but it needs to be defined 
explicitly, so please either provide definition text or cite it.0

In fact, it's probably a good idea to explain why this particular bit of 
information is useful.  A small segment of tutorial text would go a long way.

Depending on what the definition of a BGP Collector is, the usefulness might or 
might note be obvious, but it shouldn't be left to chance.


>    The format and function of the Collector BGP ID, Peer Count are as
>    defined by the TABLE_DUMP_V2 MRT PEER_INDEX_TABLE format.
>    [I-D.ietf-grow-mrt].
>
>    The Collector Latitude and Collector Longitude are the geographical
>    coordinates of the collector in WGS84 [WGS 84] datum decimal degrees
>    format stored as a single precision float in the 32 bits allocated to
>    the Collector Latitude and Collector Longitude.  The latitude and
>    longitude may be a Not A Number (NAN) for situations where the geo-

It's not required, but common practice is to capitalize normative terms, like MAY.


>    location of the collector is considered private.  The Collector
>    Latitude and Collector Longitude MUST NOT be a mix of WGS84 [WGS 84]
>    datum coordinate and NAN values.
>
>         0                   1                   2                   3
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                      Collector BGP ID                         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                      Collector Latitude                       |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                      Collector Longitude                      |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |          Peer Count           |  Peer entries (variable)
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>    The format of the peer entries is shown below.  The Peer Type and the
>    Peer BGP ID is as defined in the TABLE_DUMP_V2 MRT
>    [I-D.ietf-grow-mrt] PEER_INDEX_TABLE format.  The order of the Peer
>    entries in GEO_PEER_TABLE MUST match the order and number as existing
>    in the PEER_INDEX_TABLE.
>
>    0                   1                   2                   3
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Peer Type   |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         Peer BGP ID                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         Peer Latitude                         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         Peer Longitude                        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>    The Peer Latitude and Peer Longitude are the geographical coordinates
>    of the peer in WGS84 [WGS 84] datum decimal degrees format stored as
>    a single precision float in the 32 bits allocated to the Peer
>    Latitude and Peer Longitude.  The latitude and longitude may be a Not

MAY


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
