Hi Liyan, > On Aug 31, 2026, at 2:38 AM, Liyan Gong <[email protected]> wrote: > > Hi Acee, > > We are not using FRR. Our deployments are based on commercial, closed‑source > routing systems (proprietary vendor stacks) .
Would you be able to disclose these? There is a question on the Shepherd's report. Thanks, Acee > > Best regards， > Liyan > > ----邮件原文---- > 发件人：Acee Lindem <[email protected]> > 收件人：Liyan Gong <[email protected]> > 抄 送: lsr <[email protected]>,draft-ietf-lsr-l2-bu > <[email protected]> > 发送时间：2026-08-28 19:38:35 > 主题：Re: [Lsr] I-D Action:draft-ietf-lsr-l2-bundle-member-remote-id-06.txt > > Hi Liyan, > > What is the implementation platform? For example, are you using FRR? > > Thanks, > Acee > > > On Aug 27, 2026, at 11:45PM, Liyan Gong wrote: > > > > Hi Acee, > > > > Thanks for your checking. > > > > Yes, we have some early implementation experience in our network. > > > > This solution has been deployed on a small scale, covering the IS-IS and > > BGP-LS extensions. OSPF/OSPFv3 are not yet included at this stage. > > > > We hope that once the document is finalized, this mechanism can be more > > widely adopted. > > > > Best regard, > > Liyan > > > > > > -----邮件原件----- > > 发件人: Acee Lindem > > 发送时间: 2026年8月27日 3:08 > > 收件人: [email protected] > > 抄送: lsr > > 主题: Re: [Lsr] I-D Action: draft-ietf-lsr-l2-bundle-member-remote-id-06.txt > > > > Co-authors, > > > > One more question, are you aware of any implementations? > > > > Thanks, > > Acee > > > > > On Aug 22, 2026, at 3:27AM, [email protected] wrote: > > > > > > Internet-Draft draft-ietf-lsr-l2-bundle-member-remote-id-06.txt is now > > > available. It is a work item of the Link State Routing (LSR) WG of the > > > IETF. > > > > > > Title: Advertisement of Remote Interface Identifiers for Layer 2 > > > Bundle Members > > > Authors: Liyan Gong > > > Changwang Lin > > > Xiaolong Hu > > > Les Ginsberg > > > Peter Psenak > > > Name: draft-ietf-lsr-l2-bundle-member-remote-id-06.txt > > > Pages: 14 > > > Dates: 2026-08-22 > > > > > > Abstract: > > > > > > In networks where Layer 2 (L2) interface bundles (such as a Link > > > Aggregation Group (LAG) as defined in IEEE 802.1AX) are deployed, a > > > controller may need to collect the connectivity relationships between > > > bundle members for traffic engineering (TE) purposes. For example, > > > when performing topology management and bidirectional path > > > computation for TE, it is essential to know the connectivity > > > relationships among bundle members. > > > > > > This document describes how OSPF and IS-IS would advertise the remote > > > interface identifiers for Layer 2 bundle members. The corresponding > > > extension of BGP Link State (BGP-LS) is also specified. > > > > > > The IETF datatracker status page for this Internet-Draft is: > > > https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remot > > > e-id/ > > > > > > There is also an HTML version available at: > > > https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote > > > -id-06.html > > > > > > A diff from the previous version is available at: > > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-l2-bundle-mem > > > ber-remote-id-06 > > > > > > Internet-Drafts are also available by rsync at: > > > rsync.ietf.org::internet-drafts > > > > > > > > > _______________________________________________ > > > Lsr mailing list -- [email protected] > > > To unsubscribe send an email to [email protected] > > _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
