IETF Logo Mail Archive

Re: [Lsvr] Initiating LSVR re-chartering discussion - draft#1 proposal

Randy Bush <randy@psg.com> Wed, 06 December 2023 20:39 UTC

Return-Path: <randy@psg.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5361C151096 for <lsvr@ietfa.amsl.com>; Wed, 6 Dec 2023 12:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3etmWmEC4iXF for <lsvr@ietfa.amsl.com>; Wed, 6 Dec 2023 12:39:35 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 352C6C14EB19 for <lsvr@ietf.org>; Wed, 6 Dec 2023 12:39:35 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.93) (envelope-from <randy@psg.com>) id 1rAyg8-000pHd-7W; Wed, 06 Dec 2023 20:39:32 +0000
Date: Wed, 06 Dec 2023 12:39:31 -0800
Message-ID: <m2msunqd4s.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Paul Congdon <paul.congdon@outlook.com>
Cc: lsvr@ietf.org
In-Reply-To: <BY3PR06MB80525FC7A1751CCD26126C619A84A@BY3PR06MB8052.namprd06.prod.outlook.com>
References: <AS1PR07MB85897E82BA2DFFEDFB7C08FBE085A@AS1PR07MB8589.eurprd07.prod.outlook.com> <CA+RyBmVAgM7d2eN3S2+mnw1vzkMKm4VoVEuyMmLXExVY4kiYGQ@mail.gmail.com> <AS1PR07MB85891B2E18F6A9F826247C10E084A@AS1PR07MB8589.eurprd07.prod.outlook.com> <BY3PR06MB80525FC7A1751CCD26126C619A84A@BY3PR06MB8052.namprd06.prod.outlook.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0
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/lsvr/sxMomBQtw3G01XzfZpK04J305vY>
Subject: Re: [Lsvr] Initiating LSVR re-chartering discussion - draft#1 proposal
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Dec 2023 20:39:35 -0000

> Back in 2021, IEEE 802.1 enhanced LLDP to support the discovery
> requirements of LSVR.

uh, did lldpv2 get through the ieee sausage machine yet?  i think we had
a race to see which machine could take the longest :)

as i remember, there were two problems with using lldpv2 in this space
which l3dl addresses, security and serious scale.  has lldpv2 managed to
move forward on these?  truth is, it has all been so long, i did not
keep my eyes on the ball.

btw, there was other work, at layer 3, which played into this space,
though the drafts just expired, draft-ymbk-idr-l3nd*.  we can renew them
if the wg needs additional confusion :)

randy

v2.23.0 | Report a Bug | By Email