Re: [Idr] WG Adoption call for draft-wang-idr-rd-orf-05.txt (2/4/2021 to 2/18/2021) - no consensus + Next steps
Aijun Wang <wangaijun@tsinghua.org.cn> Mon, 22 February 2021 09:25 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 81E453A11C4 for <idr@ietfa.amsl.com>; Mon, 22 Feb 2021 01:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 GOKZtH7cLYr1 for <idr@ietfa.amsl.com>; Mon, 22 Feb 2021 01:25:05 -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 891E83A1163 for <idr@ietf.org>; Mon, 22 Feb 2021 01:25:04 -0800 (PST)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m17638.qiye.163.com (Hmail) with ESMTPA id C8EBB1C018B; Mon, 22 Feb 2021 17:24:59 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Susan Hares' <shares@ndzh.com>, idr@ietf.org
References: <00cf01d707a7$bc976410$35c62c30$@ndzh.com>
In-Reply-To: <00cf01d707a7$bc976410$35c62c30$@ndzh.com>
Date: Mon, 22 Feb 2021 17:24:59 +0800
Message-ID: <00b601d708fc$9798bff0$c6ca3fd0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B7_01D7093F.A5BEBF10"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQE9JIkUwHtB4YXYAlm0fFMCp0T8d6uXroAA
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZS1VLWVdZKFlBSkxLS0o3V1ktWUFJV1 kPCRoVCBIfWUFZGRhJGBlLTB1DSU4ZVkpNSkhCQ05CS0tLSk1VEwETFhoSFyQUDg9ZV1kWGg8SFR 0UWUFZT0tIVUpKS0JITVVLWQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Ogw6PDo*HD8NFxgjISktHwk8 LA1PCUxVSlVKTUpIQkNOQktLSExDVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQUpJQ0pMNwY+
X-HM-Tid: 0a77c90e6570d993kuwsc8ebb1c018b
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ht6Itp9zaboZG79G-EQnA4udUKs>
Subject: Re: [Idr] WG Adoption call for draft-wang-idr-rd-orf-05.txt (2/4/2021 to 2/18/2021) - no consensus + Next steps
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: Mon, 22 Feb 2021 09:25:14 -0000
Hi, Susan: Thanks for your efforts to forward this draft. Based on your request, we have finished and uploaded the problem definitions in the newly updated draft https://datatracker.ietf.org/doc/html/draft-wang-idr-vpn-routes-control-anal ysis and will try to discuss it at Jeffery's thread "[Idr] rd-orf problem clarification at the local level thread." We have also gotten useful suggestions and considerations for the design of the updated solution, will update the solution draft accordingly later. Best Regards Aijun Wang China Telecom From: idr-bounces@ietf.org <idr-bounces@ietf.org> On Behalf Of Susan Hares Sent: Sunday, February 21, 2021 12:45 AM To: idr@ietf.org Subject: Re: [Idr] WG Adoption call for draft-wang-idr-rd-orf-05.txt (2/4/2021 to 2/18/2021) - no consensus + Next steps Aijun and co-authors and IDR participants: Thank you for the lively discussion on IDR regarding this draft. It is obvious there is interest in this topic, but no consensus on accepting this draft in its current form. The 3 co-chairs of IDR have been discussing this work for the past 2 weeks in our meeting. As Jeff mentioned earlier this week, we'd like to see the problem broken down into the local AS level and push-back through-out the web of remote BGP Peers. We encourage the authors and other IDR participants to discuss the local AS level solution on [Idr] rd-orf problem clarification at the local level thread. Please use this thread to clarify this problem. Based on this clarification, perhaps the authors can split their work into two parts. There issues with consensus this solution's push-back process past the local AS. These include: definition of the problem, determining if there are gaps in current solutions (Prefix-ORF), IPR issues on proposed solution, and additional refinement of the solution. Prior to any consideration of the solution beyond the local AS, the IDR chairs would like to see a clear definition of the problem in a draft. This draft may not be published, but it will help the IDR chairs and the WG have a clear description of the problem. Cheers, Sue