Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20)

Linda Dunbar <linda.dunbar@huawei.com> Mon, 06 June 2016 21:56 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0637E12B051 for <idr@ietfa.amsl.com>; Mon, 6 Jun 2016 14:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4E9Y4nveqd2 for <idr@ietfa.amsl.com>; Mon, 6 Jun 2016 14:56:44 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E75012B015 for <idr@ietf.org>; Mon, 6 Jun 2016 14:56:44 -0700 (PDT)
Received: from 172.18.9.243 (EHLO lhreml705-cah.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQY56528; Mon, 06 Jun 2016 16:56:43 -0500 (CDT)
Received: from DFWEML701-CAH.china.huawei.com (10.193.5.175) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 6 Jun 2016 22:56:38 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml701-cah.china.huawei.com ([10.193.5.175]) with mapi id 14.03.0235.001; Mon, 6 Jun 2016 14:56:32 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20)
Thread-Index: AdHAElYAB9sVfa6xQkej61auMDdHAwAK+4yA
Date: Mon, 06 Jun 2016 21:56:31 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657EAFE4F@dfweml501-mbb>
References: <017501d1c01a$41156960$c3403c20$@ndzh.com>
In-Reply-To: <017501d1c01a$41156960$c3403c20$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.226]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657EAFE4Fdfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mnu6iTJmEalGLqTkmilhKxgJDqk>
Subject: Re: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2016 21:56:47 -0000

Support.

Linda Dunbar

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, June 06, 2016 12:39 PM
To: idr@ietf.org
Subject: [Idr] WG Adoption of draft-keyupate-idr-bgp-attribute-announcement - 2 week WG Adoption call (6/6 to 6/20)

This begins a 2 week WG Adoption call for draft-keyupate-idr-bgp-attribute-announcement.  You can find the draft at:
https://datatracker.ietf.org/doc/draft-keyupate-idr-bgp-attribute-announcement/

This draft defines attribute extensions that help confine the scope of Optional attributes within a given AS or a given BGP member-AS in Confederation.   In your comments please include:


1)      "Support" or "No support" for this draft as an IDR WG draft,

2)      Experiences with debugging optional attributes errors that this draft would aid,

3)      Deployments that use AS confederations where this draft's ability to confined scope of the optional attributes would help restrict errors,


Sue Hares and John Scudder