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

"Susan Hares" <shares@ndzh.com> Mon, 02 July 2018 17:09 UTC

Return-Path: <shares@ndzh.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 46C15130E54; Mon, 2 Jul 2018 10:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level:
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=no 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 WWG9_rjKukyc; Mon, 2 Jul 2018 10:09:02 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 6779E130FA6; Mon, 2 Jul 2018 10:09:02 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.223.101;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Cc: draft-xu-idr-neighbor-autodiscovery@ietf.org, "'徐小虎(义先)'" <xiaohu.xxh@alibaba-inc.com>, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>, aretana.ietf@gmail.com, 'John Scudder' <jgs@juniper.net>
Date: Mon, 02 Jul 2018 13:08:47 -0400
Message-ID: <013701d41227$579d2d10$06d78730$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0138_01D41205.D08CC590"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AdQSJcQmPylai0FFTx6TtuTV7fzVrQ==
X-Antivirus: AVG (VPS 180702-2, 07/02/2018), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7lxaNCosHpnq77SdssuX-pGL9QA>
Subject: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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, 02 Jul 2018 17:09:05 -0000

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