Re: [Idr] Review of draft-ietf-large-community-06.txt

Job Snijders <job@instituut.net> Sat, 05 November 2016 10:35 UTC

Return-Path: <job@instituut.net>
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 54444129704 for <idr@ietfa.amsl.com>; Sat, 5 Nov 2016 03:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 s11DI3b1K027 for <idr@ietfa.amsl.com>; Sat, 5 Nov 2016 03:35:30 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EC89129766 for <idr@ietf.org>; Sat, 5 Nov 2016 03:35:30 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id t79so92957920wmt.0 for <idr@ietf.org>; Sat, 05 Nov 2016 03:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JIgKyq8ojN1ZnFsLHDMJuIquKt94QZs85mGr5JGi+IA=; b=Ugo7nFik63A9wYxuYIZ60qGPbAssJUzv91oFzcLc+uz9uf6F5Q8Pgt/UaW9Q7Ci2Sm PKE0fRW7fe690flzlnjE5i2KBos3wXZDIy7fH394SThsTP2K45mAlS3dDzblZKSlOxqi 3EUHmyEDEIFAP7IQn1I+uttOVkUEWk22gqF7G6U1o15ZIJQLFfzOXgVk+vH337l+3n3E m2kmmfycxn2PJqXqLSLn8NNDPh5H2rdcKsHo1bCIbTXUZAnuqcirx+3DQq0JSDgGw9R2 GAmVEgwqfyafVNukXYNo7QvabNYmpgjgcSGuZn32Oy72HRB+CvUhczCFE0q867gNLjPl lwyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JIgKyq8ojN1ZnFsLHDMJuIquKt94QZs85mGr5JGi+IA=; b=i9nthnEz9/Y8SP796RGDVMLac27WgJMPGLGyVADYCOX56Zg00Em78b6OVer4vrT9MC CUauaZ+Iy/yPr4NQfRLevw/M18ayjL/hfebG/Io84xkO8OD5e3NIrzRnNSX1j2/63OC+ lSA34y0LbFLmGXywB4RzBmQ58khl947NofYdPkxBpI6akMYWXGfVTVFKZyqAoE077v/L UFKu60YVAMdg+ghzxjPwEOPV85mYyTbDoTUkmz/zDfqTvLyGePtyw3zSHfuCla17w983 TEUA3O35QKo9+xpCNXg3vjfT4FoelghQF7J3OmSuTYn6w7EDK0d57E0FSIp5XPkJzepp JOaQ==
X-Gm-Message-State: ABUngvfUpvET8DLzeNg6uFA7s/EqGEn3eis7bULZP9qFv5YzDSAACaGSPb36F3sv1tGo4g==
X-Received: by 10.194.235.7 with SMTP id ui7mr15116231wjc.66.1478342128893; Sat, 05 Nov 2016 03:35:28 -0700 (PDT)
Received: from localhost ([188.206.66.42]) by smtp.gmail.com with ESMTPSA id ym3sm19011445wjc.6.2016.11.05.03.35.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Nov 2016 03:35:28 -0700 (PDT)
Date: Sat, 5 Nov 2016 11:35:26 +0100
From: Job Snijders <job@instituut.net>
To: Zhuangshunwan <zhuangshunwan@huawei.com>
Message-ID: <20161105103526.GM952@Vurt.local>
References: <6c5d83aa1d6a4a04b651b8f14f4b445b@XCH-ALN-014.cisco.com> <40D942F5-0710-46D1-BF09-76C827377479@cisco.com> <95F42982-7DCF-46A9-A26C-71EF70DB3C59@apnic.net> <20161104195346.GK961@Vurt.local> <20161104201631.GA35942@Vurt.lan> <8a293ce4fc134657aa98134b5017d92e@XCH-ALN-014.cisco.com> <20161104221030.GD37681@Vurt.lan> <0919e676e12d49d1a2ba30f4acc3b273@XCH-ALN-014.cisco.com> <20161104230536.GJ37681@Vurt.lan> <19AB2A007F56DB4E8257F949A2FB9858C87AFC6E@NKGEML515-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19AB2A007F56DB4E8257F949A2FB9858C87AFC6E@NKGEML515-MBX.china.huawei.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ZNLCygHZxj88W4KA37AGSg6-fyE>
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] Review of draft-ietf-large-community-06.txt
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: Sat, 05 Nov 2016 10:35:32 -0000

On Sat, Nov 05, 2016 at 10:28:58AM +0000, Zhuangshunwan wrote:
> I have read this document and it looks good to me!

Thank you for the kind words!

> One comment:
> 
> In most of the network operating systems, we must enable neighbor/peer
> send-community command knob in order BGP speaker include community in
> routes announcement. 
> By default, the BGP speaker does not send/transmit community
> attributes. Even if the COMMUNITIES path attribute is an optional
> transitive attribute. This is the current reality application.

Then change your default!

> So the following case describing in draft-ietf-idr-large-community-06
> maybe cannot reflect the reality:
>
>    "Because BGP communities are optional transitive BGP attributes,
>    BGP communities may be acted upon or otherwise used by routing
>    policies in other Autonomous Systems (ASes) on the Internet."
> 
> Some customers from IDC/OTT complain that ISPs can not transmit their
> community attributes, because ISPs do not transmit community
> attributes in most cases.

I find it hard to make or accept quantative statements in this context,
I know some ISP that scrub all communities, and I know some ISPs that
pass on as much communities as possible. The market will decide.

> Should we clearly define whether LargeCommunity should act different
> from (or the same with) the RFC1997's Community?

I consider it a feature that the behaviour is exactly aligned with
RFC1997 communities. Some OTT operators might desire slightly different
behaviour, but that is really a commercial dicussion outside of IETF
scope. 

Thanks for the feedback.

Kind regards,

Job