Re: [Idr] Adoption call for draft-heitz-idr-wklc-02 (3/9 to 3/23)

Aijun Wang <wangaijun@tsinghua.org.cn> Wed, 10 March 2021 13:38 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
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 7163B3A0597 for <idr@ietfa.amsl.com>; Wed, 10 Mar 2021 05:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SrEZcZht1TDT for <idr@ietfa.amsl.com>; Wed, 10 Mar 2021 05:37:59 -0800 (PST)
Received: from mail-m17638.qiye.163.com (mail-m17638.qiye.163.com [59.111.176.38]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64913A0651 for <idr@ietf.org>; Wed, 10 Mar 2021 05:37:57 -0800 (PST)
Received: from [240.0.0.1] (unknown [106.121.64.78]) by mail-m17638.qiye.163.com (Hmail) with ESMTPA id 958231C0216; Wed, 10 Mar 2021 21:37:51 +0800 (CST)
Content-Type: multipart/alternative; boundary=Apple-Mail-E86D7ADF-8DA4-471E-9A38-E451C701E43A
Content-Transfer-Encoding: 7bit
From: Aijun Wang <wangaijun@tsinghua.org.cn>
Mime-Version: 1.0 (1.0)
Date: Wed, 10 Mar 2021 21:37:49 +0800
Message-Id: <CBFDE565-E501-4344-BF6C-53A541D50391@tsinghua.org.cn>
References: <BYAPR11MB3207CF86CF2FBD56CA3EAD66C0919@BYAPR11MB3207.namprd11.prod.outlook.com>
Cc: idr@ietf.org
In-Reply-To: <BYAPR11MB3207CF86CF2FBD56CA3EAD66C0919@BYAPR11MB3207.namprd11.prod.outlook.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
X-Mailer: iPhone Mail (18D52)
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZS1VLWVdZKFlBSkxLS0o3V1ktWUFJV1 kPCRoVCBIfWUFZSxhLTx1CQ0hCTE5IVkpNSk5IQ0hPTEpDT0NVEwETFhoSFyQUDg9ZV1kWGg8SFR 0UWUFZT0tIVUpKS0JITVVLWQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6M006AQw5TD8UEwxWNxZIEhwu PzZPCixVSlVKTUpOSENIT0xJSkNNVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlKS01VSklKVU1PVUxDWVdZCAFZQUJDSUI3Bg++
X-HM-Tid: 0a781c5ba5fdd993kuws958231c0216
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/2nk0z4hEjmagl1C1RdTkTX78MHA>
Subject: Re: [Idr] Adoption call for draft-heitz-idr-wklc-02 (3/9 to 3/23)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Mar 2021 13:38:02 -0000

Yes, if we reserve some 4-bytes AS range, then your concerns will not happen.
The well-known large community need just be allocated from this reserved range. That’s all.
Do we need other definitions in your draft then?

Aijun Wang
China Telecom

> On Mar 10, 2021, at 21:18, Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:
> 
> 
> Consider if there is a real AS that uses 4,093,640,704 as its ASN.
> And if this AS were to send a large community of its own.
> It would put its ASN into the Global Administrator field of the LC.
> This ASN is 11110100000000000000000000000000 in binary.
> Then another AS sends a WKLC with WKLC ID 0, Transitivity 0 and Data 1 = 0.
> This has the same bit pattern.
> To avoid the clash, we need to reserve the ASNs that would clash.
>  
> Regards,
> Jakob.
>  
> From: Aijun Wang <wangaijun@tsinghua.org.cn> 
> Sent: Wednesday, March 10, 2021 12:11 AM
> To: Jakob Heitz (jheitz) <jheitz@cisco.com>om>; 'Susan Hares' <shares@ndzh.com>om>; idr@ietf.org
> Subject: RE: [Idr] Adoption call for draft-heitz-idr-wklc-02 (3/9 to 3/23)
>  
> And, what the reason to assign the “111101”value in the first 6bit your encoding? It is not conformed to general definition of large community, in which the first 4-bytes is to identify the Global Administrator.
>