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

Jeffrey Haas <jhaas@pfrc.org> Thu, 12 July 2018 20:03 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 04C0D130EDB; Thu, 12 Jul 2018 13:03:15 -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, 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 wy4jDTa3ds4u; Thu, 12 Jul 2018 13:03:13 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 92FF8130EA0; Thu, 12 Jul 2018 13:03:13 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CABF71E28F; Thu, 12 Jul 2018 16:03:03 -0400 (EDT)
Date: Thu, 12 Jul 2018 16:03:03 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Eric C Rosen <erosen@juniper.net>
Cc: Susan Hares <shares@ndzh.com>, idr@ietf.org, draft-xu-idr-neighbor-autodiscovery@ietf.org
Message-ID: <20180712200303.GU12853@pfrc.org>
References: <013701d41227$579d2d10$06d78730$@ndzh.com> <d0ae2da8-e932-84f2-f634-3e0f280a6fb5@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <d0ae2da8-e932-84f2-f634-3e0f280a6fb5@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4inHNyCSoa0TbWZ16VUmTBa37IQ>
Subject: Re: [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: Thu, 12 Jul 2018 20:03:15 -0000

On Thu, Jul 12, 2018 at 10:35:12AM -0400, Eric C Rosen wrote:
> There is so much overlap with the idr-lldp-peer-discovery draft that
> I don't see how the WG could adopt both of them.  The
> idr-neighbor-autodiscovery draft thus should not be adopted unless
> the intention is to reject the idr-lldp-peer discovery draft. Is
> that the intention?  I don't recall seeing much discussion comparing
> and contrasting the two.

And not contradicting any of Eric's other good points, we have other work
happening outside of IDR that overlaps this auto discovery problem space:

https://datatracker.ietf.org/doc/draft-acee-ospf-bgp-rr/

Easy to say that it's a popular topic. :-)

-- Jeff