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

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Sun, 06 November 2016 06:26 UTC

Return-Path: <jheitz@cisco.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 4A99C129608 for <idr@ietfa.amsl.com>; Sat, 5 Nov 2016 23:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.017
X-Spam-Level:
X-Spam-Status: No, score=-16.017 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, 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 pJqR3Y20bhhj for <idr@ietfa.amsl.com>; Sat, 5 Nov 2016 23:26:53 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9812012960A for <idr@ietf.org>; Sat, 5 Nov 2016 23:26:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4604; q=dns/txt; s=iport; t=1478413613; x=1479623213; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=A0UajCog+s0awWVWmBuateyNnQElGMbofTiHyfcyyYQ=; b=JSFDgDlL64ld1DBGRuFP0tUHw0oYNkwpUN8yoJzNLFo6/tjUW0IY1QcH qKLQyPmW4dZ0xIm+KN1DWcFpgxiEC/mWetFleB9Pk0C42pL9bZIA3uY/t RONnBeJqNSGgOH75tESFLLr8xH2hQvyPks+cXMMXYBbT9biO72VTQvIWo 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CNAQAbzB5Y/5RdJa1cGgEBAQECAQEBAQgBAQEBgy4BAQEBAR9YfI04ln6POIUaggglhX8CGoFvPxQBAgEBAQEBAQFiKIRiAQEEI1YQAgEGAgQ7AwICAjAUEQIEDgUUiESSSp0/gkCLMwEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhj6BfYJYh0stgi8FjlSFc4VgAYY0ig+BboRwiTKNKoQFAR43eoUqcodMAQEB
X-IronPort-AV: E=Sophos;i="5.31,600,1473120000"; d="scan'208,217";a="342888567"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Nov 2016 06:26:52 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id uA66QqX2032305 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 6 Nov 2016 06:26:52 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 6 Nov 2016 01:26:53 -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.1210.000; Sun, 6 Nov 2016 01:26:53 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Zhuangshunwan <zhuangshunwan@huawei.com>
Thread-Topic: [Idr] Review of draft-ietf-large-community-06.txt
Thread-Index: AQHSNjBz6sRcMeSZxEiIR579im5tsaDIY72wgAB9DlKAAK2JAIAAA2sAgAAGW4D//8SNUIAAW0wA//+1BgCAAFpfAIAAvu4AgAABzgCAAV2lgA==
Date: Sun, 06 Nov 2016 06:26:53 +0000
Message-ID: <804168D3-12A6-478A-A390-19A02791A0D0@cisco.com>
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> <20161105103526.GM952@Vurt.local>
In-Reply-To: <20161105103526.GM952@Vurt.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_804168D312A6478AA39019A02791A0D0ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/v1WmNdaEqsljPpX8p723TDNxNfk>
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: Sun, 06 Nov 2016 06:26:55 -0000

Shunwan,

On Nov 5, 2016, at 3:35 AM, Job Snijders <job@instituut.net<mailto:job@instituut.net>> wrote:

On Sat, Nov 05, 2016 at 10:28:58AM +0000, Zhuangshunwan wrote:

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.

Another reason is that some ISPs use private ASNs rather than their own ASN in the first 16 bits of the community, because there is not enough leftover bits to express the action. That makes it impossible for an ISP to transmit them to another ISP, because of name space clashes. That should no longer be a problem with large communities.
See https://onestep.net/communities<https://onestep.net/communities/>/ for examples of communities. BTW, I don't recognize any Chinese ISPs on that site. Can you share some community specifications for any Chinese ISPs, please?

谢谢,
Jakob.