[Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery

Lizhenbin <lizhenbin@huawei.com> Sun, 15 July 2018 14:42 UTC

Return-Path: <lizhenbin@huawei.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 8B3A7130E09; Sun, 15 Jul 2018 07:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 AY8ROSQJAyCz; Sun, 15 Jul 2018 07:42:15 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52140130DE4; Sun, 15 Jul 2018 07:42:15 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id BA3E5B0D5B7EF; Sun, 15 Jul 2018 15:41:50 +0100 (IST)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.399.0; Sun, 15 Jul 2018 15:41:51 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.64]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0382.000; Sun, 15 Jul 2018 22:41:45 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-xu-idr-neighbor-autodiscovery@ietf.org" <draft-xu-idr-neighbor-autodiscovery@ietf.org>
Thread-Topic: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery
Thread-Index: AdQY3ZgTPylai0FFTx6TtuTV7fzVrQDa80J2
Date: Sun, 15 Jul 2018 14:41:44 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F45D82A@DGGEMM532-MBX.china.huawei.com>
References: <19AB2A007F56DB4E8257F949A2FB9858DC3B8B4C@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <19AB2A007F56DB4E8257F949A2FB9858DC3B8B4C@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.194.53]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D8F45D82ADGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/CF8xEcnwHKydce9WsinSQ9uaXmY>
Subject: [Idr] 答复: WG adoption call for draft-xu-idr-neighbor-autodiscovery
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.27
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, 15 Jul 2018 14:42:18 -0000

Support for the WG adoption. BGP is widely used and simplifying the provisioning is important and useful. The solution proposed in the draft can solve the issue better. Moreover the solution should be better to be provided by BGP's self. Dependency on other protocols may add unnecessary limitation.



Best Regards,

Zhenbin(Robin)






·¢¼þÈË: Idr [mailto:idr-bounces@ietf.org] ´ú±í Susan Hares
·¢ËÍʱ¼ä: 2018Äê7ÔÂ3ÈÕ 1:09
ÊÕ¼þÈË: idr@ietf.org
³­ËÍ: draft-xu-idr-neighbor-autodiscovery@ietf.org
Ö÷Ìâ: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery

Greetings:

This begins a 2 week WG adoption call for draft-xu-idr-neighbor-autodiscovery (July 2 ¨C July 16).

https://datatracker.ietf.org/doc/draft-xu-idr-neighbor-autodiscovery/

The authors of this draft should send their IPR statements in response to this email.  I hope the authors will ihelp their vacationing co-authors to respond by July 7th.

The WG should consider the following:

1)      Does BGP need to have an autodiscovery mechanism for peers within Data Centers?

2)      Does this mechanism work for other deployments?



3)      If so, should be passed in BGP Hello message?

Or should it be a part of another protocol (e..g. LLDP, BFD, etc).


4)      Does this interact with any of the LSVR work?

I want to thank the authors for their patience while we sorted through some of the WG LC for other drafts.  We decided to wait until some of those discussion were cleared up prior to starting a new WG Adoption call.


Susan Hares