Re: [Idr] [Lsvr] Issue 2: Auto-configuration Requirements
Randy Bush <randy@psg.com> Mon, 10 June 2019 20:01 UTC
Return-Path: <randy@psg.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 CF5A51200F1; Mon, 10 Jun 2019 13:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=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 0h2gsuMA45-P; Mon, 10 Jun 2019 13:01:22 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 1E31812006B; Mon, 10 Jun 2019 13:01:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1haQTn-0003Ii-UT; Mon, 10 Jun 2019 20:01:20 +0000
Date: Mon, 10 Jun 2019 13:01:19 -0700
Message-ID: <m2sgshp5v4.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org, lsvr@ietf.org
In-Reply-To: <01bf01d51fc2$5a07ba30$0e172e90$@ndzh.com>
References: <01bf01d51fc2$5a07ba30$0e172e90$@ndzh.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/XgJM20JvxXsJRszt1-pYg1fY4dI>
Subject: Re: [Idr] [Lsvr] Issue 2: Auto-configuration Requirements
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, 10 Jun 2019 20:01:24 -0000
> Does IDR think that we should include a generalized auto-discovery > protocol in the IDR WG charter? > > If so, should it be for WAN or Data Center or IPRAN topologies > (grid/ring)? somewhere is the saying that what is designed for the LAN ends up on the WAN. and if not designed well, does not work well on the WAN. > LSVR is progressing with Layer 3 liveness in draft-ietf-lsvr-l3dl-00 > https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl/ l3dl is discovery and liveness. no fun discovering dead things :) you may also be amused by draft-ymbk-lsvr-l3dl-ulpc-00.txt there are updates to these drafts in emacs edit buffers. if you get serious, i can push them out earlier then planned. randy
- [Idr] Issue 2: Auto-configuration Requirements Susan Hares
- Re: [Idr] [Lsvr] Issue 2: Auto-configuration Requ… Randy Bush