Re: [GROW] WG Adoption Call: draft-ymbk-grow-wkc-behavior-01 2018.06.11-2018.06.26

"Serpil Bayraktar (serpil)" <serpil@cisco.com> Wed, 13 June 2018 19:09 UTC

Return-Path: <serpil@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D73D130E88 for <grow@ietfa.amsl.com>; Wed, 13 Jun 2018 12:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 IOfAcb6wm7Fs for <grow@ietfa.amsl.com>; Wed, 13 Jun 2018 12:09:36 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7408C12426A for <grow@ietf.org>; Wed, 13 Jun 2018 12:09:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14466; q=dns/txt; s=iport; t=1528916976; x=1530126576; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=R/JAPuuglPdn2jXSmorO9kvWMAfEZ0Eb/6q5e+7BRr0=; b=K3ZuZ/gAWcZS+3lF2DzPZS/KGjU9Ctvj2La8pDekmhsQfj7Nf+hOdUCL l3Y6qmzWimYkKFfxjBnhYY/wH73tf90CFkeTEI+PDkgff8oPzswMsIKW2 bPt6Ow3aP8yty5j8DiNoQJbUPl0HUAQw9I3Xi99Js0eo4sDj5zfeVtdBs 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAgBcayFb/49dJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYJTRy5ifygKg2+UbYF/j2uEfoF4CxgBCoRJAheCICE2FgECAQEBAQEBAm0cDIUoAQEBAQMBARsGSxsCAQgRAwECKAMCAgIlCxQJCAIEARIUgw4CgRtkD6teghyEWoNugWMFiEuCE4EPJIJogUGBUAEBA4F0CRaCSzGCJAKIO4h+h1EJAoVycIgXDIEzg36CaIUPigqHDAIREwGBJCQGK4FScBU7KgGCGAmCJByISIU+b44NgRoBAQ
X-IronPort-AV: E=Sophos;i="5.51,220,1526342400"; d="scan'208,217";a="128619576"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jun 2018 19:09:35 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id w5DJ9Zxn002196 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Jun 2018 19:09:35 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 13 Jun 2018 14:09:34 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1320.000; Wed, 13 Jun 2018 14:09:34 -0500
From: "Serpil Bayraktar (serpil)" <serpil@cisco.com>
To: Job Snijders <job@ntt.net>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] WG Adoption Call: draft-ymbk-grow-wkc-behavior-01 2018.06.11-2018.06.26
Thread-Index: AQHUAcdUfqO9gLyKwUiFZLFH/h7kGqRb4kiAgAKMuoA=
Date: Wed, 13 Jun 2018 19:09:34 +0000
Message-ID: <EB6D0DED-26F1-406D-BB56-4719669DACC3@cisco.com>
References: <20180611205939.GH50997@vurt.meerval.net> <20180611211315.GI50997@vurt.meerval.net>
In-Reply-To: <20180611211315.GI50997@vurt.meerval.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.157.20.50]
Content-Type: multipart/alternative; boundary="_000_EB6D0DED26F1406DBB564719669DACC3ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/7gIYmcz4gxMfjap5flRU-2yptfc>
Subject: Re: [GROW] WG Adoption Call: draft-ymbk-grow-wkc-behavior-01 2018.06.11-2018.06.26
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2018 19:09:39 -0000

I support adoption (as author) and I like the idea of adding an “Action Items” section perhaps with some of the examples discussed.

Serpil

From: GROW <grow-bounces@ietf.org> on behalf of Job Snijders <job@ntt.net>
Date: Monday, June 11, 2018 at 2:13 PM
To: Grow Mailing List <grow@ietf.org>
Subject: Re: [GROW] WG Adoption Call: draft-ymbk-grow-wkc-behavior-01 2018.06.11-2018.06.26

Hi all,

On Mon, Jun 11, 2018 at 08:59:39PM +0000, Job Snijders wrote:
The authors of draft-ymbk-grow-wkc-behavior [1] requested the chairs to
consider issuing a call for working group adoption. Here is the
abstract:
     "Well-Known BGP Communities are manipulated inconsistently by
     current implementations. This results in difficulties for
     operators. It is recommended that removal policies be applied
     consistently to Well-Known Communities."
     [1]: https://tools.ietf.org/html/draft-ymbk-grow-wkc-behavior-01
Please take a moment to read and evaluate the document and let the
working group know whether you'd like to continue work on this document
as working group or not.
We'll close the call on 2018-06-26

Speaking with no hats: I support adoption of this document.

Commenting specifically on the draft content, I'd maybe like to see
Section 6 "Action items" be along the lines of "Operators are recommened
not to use "set community" or "community set" and just explicitly
remove/add what needs to be done. Getting the vendors to align may be
very challenging, but we can at least inform operators in such a way
they are aware of the risks and encouraged to write more portable,
readable routing policies.

Kind regards,

Job

_______________________________________________
GROW mailing list
GROW@ietf.org<mailto:GROW@ietf.org>
https://www.ietf.org/mailman/listinfo/grow