[Lsr] Re: WG Last Call Request for draft-ietf-lsr-l2-bundle-member-remote-id

Acee Lindem <acee.ietf@gmail.com> Fri, 31 July 2026 19:05 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
From: Acee Lindem <acee.ietf@gmail.com>
In-Reply-To: <2afd69f1c3c0b4b-00019.Richmail.00007022652980107067@chinamobile.com>
Date: Fri, 31 Jul 2026 15:04:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E86A7A2C-5EE9-4E69-87C5-AB4D034DA631@gmail.com>
References: <177353902203.601.17314240307942744045@dt-datatracker-5477d56788-5pkt5> <2afd69f1c3c0b4b-00019.Richmail.00007022652980107067@chinamobile.com>
To: Liyan Gong <gongliyan@chinamobile.com>
Message-ID-Hash: RGNHT6FRSPA2DGOP6BZP6KMZCWRLRT32
CC: lsr-chairs <lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Precedence: list
Subject: [Lsr] Re: WG Last Call Request for draft-ietf-lsr-l2-bundle-member-remote-id
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/-__YQyzocYqSjIMhf_xr6XH4VVE>

I think the draft is close but it could be better. 

   1. Can you add an "Operational Considerations" section? 
   2. Do you have a reference for TE bidirectional path computation? In other words, a reference
       for the controller needed to know the pairing of interface IDs for TE computation. 

Thanks,
Acee

> On Apr 29, 2026, at 4:56 AM, Liyan Gong <gongliyan@chinamobile.com> wrote:
> 
> Dear Chairs and WG,
> 
> We sincerely appreciate all the comments, feedback, and guidance from the WG. 
> 
> After the discussion at IETF 125, We think the draft is stable and there are no remaining open issues. 
> 
> The authors would like to kindly request WG Last Call.
> 
> Further comments and suggestions are always very welcome. Thank you very much.
> 
> Best regards,
> Liyan(on behalf of the authors)
> 
> 
> ----邮件原文----
> 发件人：internet-drafts <internet-drafts@ietf.org>
> 收件人：Changwang Lin <linchangwang.04414@h3c.com>,Les Ginsberg <ginsberg@cisco.com>,Liyan Gong <gongliyan@chinamobile.com>,Mengxiao Chen <chen.mengxiao@h3c.com>,Peter Psenak <ppsenak@cisco.com>
> 抄　送: (无)
> 发送时间：2026-03-15 09:43:42
> 主题：New Version Notification for draft-ietf-lsr-l2-bundle-member-remote-id-02.txt
> 
> A new version of Internet-Draft
> draft-ietf-lsr-l2-bundle-member-remote-id-02.txt has been successfully
> submitted by Changwang Lin and posted to the
> IETF repository.
> 
> Name:     draft-ietf-lsr-l2-bundle-member-remote-id
> Revision: 02
> Title:    Advertisement of Remote Interface Identifiers for Layer 2 Bundle Members
> Date:     2026-03-15
> Group:    lsr
> Pages:    11
> URL:      https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote-id-02.txt
> Status:   https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remote-id/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-lsr-l2-bundle-member-remote-id
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-l2-bundle-member-remote-id-02
> 
> Abstract:
> 
>    In networks where Layer 2 (L2) interface bundles (such as a Link
>    Aggregation Group (LAG) [IEEE802.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-LS is also specified.
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> Subject：New Version Notification for draft-ietf-lsr-l2-bundle-member-remote-id-02.txt
> 
> A new version of Internet-Draft
> draft-ietf-lsr-l2-bundle-member-remote-id-02.txt has been successfully
> submitted by Changwang Lin and posted to the
> IETF repository.
> 
> Name:     draft-ietf-lsr-l2-bundle-member-remote-id
> Revision: 02
> Title:    Advertisement of Remote Interface Identifiers for Layer 2 Bundle Members
> Date:     2026-03-15
> Group:    lsr
> Pages:    11
> URL:      https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote-id-02.txt
> Status:   https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remote-id/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-lsr-l2-bundle-member-remote-id
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-l2-bundle-member-remote-id-02
> 
> Abstract:
> 
>    In networks where Layer 2 (L2) interface bundles (such as a Link
>    Aggregation Group (LAG) [IEEE802.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-LS is also specified.
> 
> 
> 
> The IETF Secretariat
> 
> 
>

[Lsr] WG Last Call Request for draft-ietf-lsr-l2-… Liyan Gong
[Lsr] Re: WG Last Call Request for draft-ietf-lsr… Acee Lindem
[Lsr] Re: WG Last Call Request fordraft-ietf-lsr-… Liyan Gong