IETF Logo Mail Archive

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

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 03 July 2018 20:18 UTC

Return-Path: <jefftant.ietf@gmail.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 D7326130E20; Tue, 3 Jul 2018 13:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1-i1Wn34BfBc; Tue, 3 Jul 2018 13:18:21 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 359D6130DF6; Tue, 3 Jul 2018 13:18:21 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id a12-v6so3176420wro.1; Tue, 03 Jul 2018 13:18:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=uoJQSa/+ZrNK63KSaGW0NkrTHPFpDKU5oq68J2McgUY=; b=T/a+DVI10pl7tk/POEZkK8z3mnouzEDbfuZAmS+HOa6G+Swpd+/tlyTKgHP38PhhBw ckcd2L3aV/JVH9nRcJqEqiEXAYxtlSgFfDq6n9qquy5v3eWEP8KJBDEakkgPsFIOiKdi MbvW8uKDnMZ1ZpswF7SWSYhc4V3ueKQtqpQg4wL9V7/B+3YvcsCMAjmd7mS4ftdSkMVo GBI///4d9vtmT55G2xJjhMZtuSemYPxbA+KKP8NsPy8/pHhS2Pa5qR4yAPvEMpyQwrzn xjeiHZRVPE4SSgNwA/zTJAosuitKUax0PwD0denxkmFv1XtFXfUCCSALdKARQmkNUpkV iWvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=uoJQSa/+ZrNK63KSaGW0NkrTHPFpDKU5oq68J2McgUY=; b=XbFeNrJL0UzFxQrxHQzsFIlr2+UK4fa+vV4Gfh2lYdK6W2X+FxjQoxWajezlH8QzD3 DsyWPIvdeOsrAj3pZ0UJNSNczkkgCM8lRs4wTx57wwX1kKpmw/9I0pd3NvlINJ0QA+DX TU1NJI4k7fS3tPjePQFAdNmF+aIH91tEZL/hd4MNnPvW5HGlHWOnd7lFad5WRLNxv2Hh v69m308+pOn2Ysvrj01rYvzl2bbMFb8LQreA3IMxPt5NBEOSyUaK3OubTMa6cw89JaU/ lwfJuRf7SCiZh+z5+YI1pu7JcE3bcHyihTTPwZ9aFqKkXLqT7GrVuHFxnvXUkioiSp/Y KlhA==
X-Gm-Message-State: APt69E25+oKuNhcr2wQtrcUhPh0yjnuQ/UrKoXhu64j8O1K7ySv6cogS iMyxjs4XmhLdnMqEi7C28cQ=
X-Google-Smtp-Source: AAOMgpdSjPfHMDXf7UpCIVcuuU4rOCG9EQtes8tHh94CkEDUWLDg6McW4zgLrIDpuAeqdyB0KfZOTg==
X-Received: by 2002:adf:92e7:: with SMTP id 94-v6mr23525641wrn.70.1530649099601; Tue, 03 Jul 2018 13:18:19 -0700 (PDT)
Received: from [135.227.239.108] ([66.201.62.254]) by smtp.gmail.com with ESMTPSA id f2-v6sm2303317wre.16.2018.07.03.13.18.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Jul 2018 13:18:18 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.e.1.180613
Date: Tue, 03 Jul 2018 13:18:12 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Susan Hares <shares@ndzh.com>, idr@ietf.org
CC: draft-xu-idr-neighbor-autodiscovery@ietf.org, "'徐小虎' (=?UTF-8?B?5LmJ5YWI?=)" <xiaohu.xxh@alibaba-inc.com>, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>, aretana.ietf@gmail.com, 'John Scudder' <jgs@juniper.net>
Message-ID: <BF85A860-9DCF-4809-ACAE-4F08D5947040@gmail.com>
Thread-Topic: WG adoption call for draft-xu-idr-neighbor-autodiscovery
References: <013701d41227$579d2d10$06d78730$@ndzh.com>
In-Reply-To: <013701d41227$579d2d10$06d78730$@ndzh.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3613468698_1443415877"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GP2oXOzjP3PoJW_FYk4YMWl87x8>
Subject: Re: [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: Tue, 03 Jul 2018 20:18:24 -0000

Hi Sue,

 

I’m not aware of any IPR.

 

1) Yes

2) if BGP is not used for reachability distribution, I’d question use of BGP as the neighbor autodiscovery technology, however for all practical reasons, there’s significant number of DC’s todays that run BGP (Use of BGP for Routing in Large-Scale Data Centers, RFC 7938) seems to be a rather popular way to deploy undelay routing.

3) Yes, it could and should if BGP is used, using Hello message to convey the information needed is a technically sound approach, while using other protocols to do the same is definitely possible, additional complexity should not be underestimated 

4) it could be leveraged by the LSVR

 

Cheers,

Jeff

 

From: Susan Hares <shares@ndzh.com>
Date: Monday, July 2, 2018 at 10:09
To: <idr@ietf.org>
Cc: <draft-xu-idr-neighbor-autodiscovery@ietf.org>, "'徐小虎' (义先)" <xiaohu.xxh@alibaba-inc.com>, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>, Alvaro Retana <aretana.ietf@gmail.com>, 'John Scudder' <jgs@juniper.net>
Subject: WG adoption call for draft-xu-idr-neighbor-autodiscovery
Resent-From: <alias-bounces@ietf.org>
Resent-To: <xiaohu.xxh@alibaba-inc.com>, <bikunyang@huawei.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, <nikos@linkedin.com>, <ketant@cisco.com>
Resent-Date: Mon, 2 Jul 2018 10:09:04 -0700 (PDT)

 

Greetings: 

 

This begins a 2 week WG adoption call for draft-xu-idr-neighbor-autodiscovery (July 2 – 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: 
Does BGP need to have an autodiscovery mechanism for peers within Data Centers? 
Does this mechanism work for other deployments? 
 
If so, should be passed in BGP Hello message?  
Or should it be a part of another protocol (e.g. LLDP, BFD, etc). 

 
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

v2.23.0 | Report a Bug | By Email