Skip to main content

Liaison statement
Liaison to IETF LSVR work group on l3dl (Layer-3 Discovery and Liveness)

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2025-03-16
From Group IEEE-802-1
From Contact Glenn Parsons
To Group lsvr
To Contacts Ketan Talaulikar <ketant.ietf@gmail.com>
Jie Dong <jie.dong@huawei.com>
Acee Lindem <acee.ietf@gmail.com>
Cc János Farkas <janos.farkas@ericsson.com>
Link State Vector Routing Discussion List <lsvr@ietf.org>
Acee Lindem <acee.ietf@gmail.com>
Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Jim Guichard <james.n.guichard@futurewei.com>
Jie Dong <jie.dong@huawei.com>
Ketan Talaulikar <ketant.ietf@gmail.com>
John Scudder <jgs@juniper.net>
Response Contact Paul Nikolich <p.nikolich@ieee.org>
Glenn Parsons <glenn.parsons@ericsson.com>
John Messenger <JMessenger@advaoptical.com>
Purpose For action
Deadline 2025-07-27 Action Needed
Attachments liaison-ietf-lsvr-0325-v01
Body
As a result of the re-chartering of the IETF LSVR working group to include the
l3dl protocol draft-ietf-lsvr-l3dl-14 - Layer-3 Discovery and Liveness, IEEE
802.1 would like to follow up to our liaison statement in
https://datatracker.ietf.org/liaison/1637/.

IEEE Std 802.1AB-2016 specifies a simple and widely deployed layer-2 discovery
protocol known as the Link Layer Discovery Protocol (LLDP). Further, to provide
for applications such as LSVR, IEEE Std 802.1ABdh-2021 specifies an extension
that greatly expands the amount of information LLDP can exchange while
maintaining backward compatibility with all prior LLDP versions. Based on our
review of the current l3dl draft, IEEE 802.1 believes that extended LLDP per
IEEE Std 802.1ABdh-2021 has sufficient facilities to support the required
information exchange.

Additionally, IEEE Std 802.1ABcu-2021 specifies the YANG modules related to the
management of extended LLDP. Clause 12 of IEEE Std 802.1ABcu-2021 describes the
configuration and monitoring objects for LLDP at large, and the YANG is written
to be extensible to support new TLVs in a consistent manner.

IEEE 802.1 still believes that it is undesirable for the industry to have
multiple discovery protocols and that new protocols should be backward
compatible with widely deployed LLDP. In addition, existing solutions for layer
2 liveness include Connectivity Fault Management (CFM) specified in clauses
18-22 of IEEE Std 802.1Q-2022 and for layer 2 security include both encryption
and authentication specified in IEEE Std 802.1AE-2018, IEEE Std 802.1X-2020,
and IEEE Std 802.1AR-2018.

All previously mentioned IEEE 802.1 standards are available at no cost at
https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68. The
IEEE 802 process is open and contribution driven. Participation is on an
individual basis and technical discussion can be conducted based on individual
contributions.

IEEE 802.1 looks forward to continued discussion on the IEEE 802.1 email
reflector and to collaboration with representatives from the IETF LSVR WG: ●
Through the IEEE 802 – IETF Coordination Group, and ● At upcoming IEEE 802.1
Maintenance Task Group meetings, both electronically
https://1.ieee802.org/maintenance/#Upcoming_Meeting_Calendar or in-person
https://1.ieee802.org/meetings/.

Considering IETF 123 and IEEE 802.1 meet back-to-back in July 2025 at the same
venue in Madrid, IEEE 802.1 would also like to invite representatives from the
IETF LSVR WG to join us for discussion during our July 27-31, 2025 IEEE 802.1
plenary session.

Respectfully submitted,

Glenn Parsons
Chair IEEE 802.1 WG