[Lsvr] Re: Draft of Liaison to IEEE about draft-ietf-lsvr-l3dl
Russ Housley <housley@vigilsec.com> Fri, 14 March 2025 03:02 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: lsvr@mail2.ietf.org
Delivered-To: lsvr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E8221B14C70; Thu, 13 Mar 2025 20:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIET3bE3Xuxb; Thu, 13 Mar 2025 20:01:59 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id ECE42B14C5B; Thu, 13 Mar 2025 20:01:58 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id A9CB19D1EB; Thu, 13 Mar 2025 23:01:58 -0400 (EDT)
Received: from smtpclient.apple (rtr-guestwired.meeting.ietf.org [31.133.144.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id A3D1B9CE46; Thu, 13 Mar 2025 23:01:57 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <0ADE8D9B-E563-4ADE-9637-C7D20CA79511@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B67DEF27-DC3A-47C1-B686-B87F523C722A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Thu, 13 Mar 2025 09:05:19 -0400
In-Reply-To: <178dd2bdaca34d7da12f4e01fe4a4493@huawei.com>
To: "Dongjie (Jimmy)" <jie.dong=40huawei.com@dmarc.ietf.org>
References: <178dd2bdaca34d7da12f4e01fe4a4493@huawei.com>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:message-id:content-type:mime-version:subject:date:in-reply-to:cc:to:references; s=pair-202402141609; bh=TfP0lQZ2KL/gdvmAXo4wcevm7DYJ4GQTsIJ81RKFvdw=; b=d5ACczdKzIr17+hYHYEujvUYTAVAbpz3Gml5KgTfEnIsXSGSEGe3B3eq29O1W0KBsAM4kUpegFlfSEKCwdp0/8pYjWSMJ6NzvLm3hLlos+5VN3in+F/BU+mVHI4NC3GHMy0EtRtgCCss4BqRySjwVR9stvm9s68n8X+jaB4pUX8WNG2NmtGSQwzdHXoft7m6/my+XSF1a3KSMlW9rOXTGI2e6ps7I0JegXfIj6ek3IkDuLOqLtrSt3kbALesMZR6XEh++6ONloI2AyEkW53xPivU8WzUVoB44Zae62IyLxCY11in8hQ/Nnb8CU+5FV63WQ2Ess1sMpszYUoRp3ZgVQ==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Message-ID-Hash: S23HG7QL4DENOZP5BUHZP5UN4QH7OOHU
X-Message-ID-Hash: S23HG7QL4DENOZP5BUHZP5UN4QH7OOHU
X-MailFrom: housley@vigilsec.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-lsvr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "lsvr@ietf.org" <lsvr@ietf.org>, "lsvr-chairs@ietf.org" <lsvr-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Lsvr] Re: Draft of Liaison to IEEE about draft-ietf-lsvr-l3dl
List-Id: Link State Vector Routing <lsvr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/o3ZbUm6neLSuk7jKZghq7uxD2QU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Owner: <mailto:lsvr-owner@ietf.org>
List-Post: <mailto:lsvr@ietf.org>
List-Subscribe: <mailto:lsvr-join@ietf.org>
List-Unsubscribe: <mailto:lsvr-leave@ietf.org>
The liaison should go to IEEE 802.1. Russ > On Mar 13, 2025, at 3:38 AM, Dongjie (Jimmy) <jie.dong=40huawei.com@dmarc.ietf.org> wrote: > > Dear WG, > > As we are preparing for the WG last call on draft-ietf-lsvr-l3dl, the WG chairs and our AD think it would be useful to send a liaison to IEEE to inform them about the progress of this document, and ask for their review and feedbacks. > > Please find below the initial draft of the liaison statement. Please review and let us know if you have any comment or suggestion: > > Best regards, > Ketan, Acee and Jie > > > > ***** > > Dear IEEE Colleagues, > We would like to draw your attention to the WG last call on L3DL protocol (https://datatracker.ietf.org/doc/html/draft-ietf-lsvr-l3dl-14) in the IETF’s Link State Vector Routing Protocol (LSVR) working Group. > Used in Massive Data Centers (MDCs), BGP Link-State Shortest Path First (BGP-SPF) produced in LSVR and similar protocols need a mechanism for link neighbor discovery, link encapsulation data, and Layer 2 and Layer 3 liveness. The BGP-SPF base protocol (https://datatracker.ietf.org/doc/draft-ietf-lsvr-bgp-spf/) does not standardize a discovery and liveness technology, however in some scenarios it relies on such technology. The Layer-3 Discovery and Liveness (L3DL) protocol provides link discovery, exchanges endpoint and interface identifiers (IPv4, IPv6, ...), discovers supported encapsulation information (Layer 3, Layer 2.5) over Ethernet, provides layer 2 liveness checking, enable layer 3 liveness checking and exchange parameters needed for upper layer protocol configuration. The development of L3DL is initially focused around the BGP-SPF requirements for operation in MDCs. > The L3DL protocol used to be named as LSoE (Link State over Ethernet), on which a liaison was sent on January 10, 2019 (https://datatracker.ietf.org/liaison/1621 <https://datatracker.ietf.org/liaison/1621/>). Early this year, L3DL is added as the deliverable of the LSVR WG's charter https://datatracker.ietf.org/doc/charter-ietf-lsvr, and the WG plans to initiate the WG LC for this document soon. We anticipates that there will be ongoing discussion of this topic at the IETF's meeting in Bangkok during the week of March 16, 2025. > At this stage we welcome your views on the L3DL draft, and welcome your participation in the WG Last Call on the LSVR WG's mailing list (lsvr@ietf.org <mailto:lsvr@ietf.org>). More specifically, this document has one section on IEEE considerations, your feedback on that is much appreciated. > > We will continue the communication on any update through the IEEE IETF Coordination Group. > > Best regards, > Ketan Talaulikar & Acee Lindem & Jie Dong > IETF LSVR WG Chairs > > ***** > > _______________________________________________ > Lsvr mailing list -- lsvr@ietf.org <mailto:lsvr@ietf.org> > To unsubscribe send an email to lsvr-leave@ietf.org <mailto:lsvr-leave@ietf.org>
- [Lsvr] Draft of Liaison to IEEE about draft-ietf-… Dongjie (Jimmy)
- [Lsvr] Re: Draft of Liaison to IEEE about draft-i… Russ Housley
- [Lsvr] Re: Draft of Liaison to IEEE about draft-i… Dongjie (Jimmy)