[Idr] Re: Éric Vyncke's Discuss on draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06: (with DISCUSS and COMMENT)

linchangwang <linchangwang.04414@h3c.com> Fri, 31 July 2026 13:12 UTC

Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: idr@mail2.ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E09F91219E742; Fri, 31 Jul 2026 06:12:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785503526; bh=xbG2oV9ONV9npKOiXSZPc29uVokXoZ0j0Ic/dQHYCAs=; h=From:To:CC:Subject:Date; b=Vc+xZSKW0PEgKhOcntZhSsBj9AeO/mxX1ynN7LJRTrXwbfnp3ChexIYO2UFeFhoBe nbfHySCYo/lQFFh5ffDIqcvska18t1o3krhzNDlPnBM83/LRKTIB7Dj5yuTP/G61Gt crGEFNRmZJ13NlGj0ZVTl2B6mvCmX14qFqz0dcBg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 eaIl_c8SBI9S; Fri, 31 Jul 2026 06:12:05 -0700 (PDT)
Received: from h3cspam01-ex.h3c.com (smtp.h3c.com [60.191.123.56]) (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 A26D21219E72A; Fri, 31 Jul 2026 06:11:39 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.155]) by h3cspam01-ex.h3c.com with ESMTP id 66VDBCfw089718; Fri, 31 Jul 2026 21:11:12 +0800 (+08) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (unknown [10.153.34.10]) by mail.maildlp.com (Postfix) with ESMTP id BE28920091FC; Fri, 31 Jul 2026 21:11:16 +0800 (CST)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) by DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Fri, 31 Jul 2026 21:11:02 +0800
Received: from DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738]) by DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738%17]) with mapi id 15.02.1258.027; Fri, 31 Jul 2026 21:11:02 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Éric Vyncke <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Thread-Topic: Éric Vyncke's Discuss on draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06: (with DISCUSS and COMMENT)
Thread-Index: Ad0g7f1HippGz4x9gE6ztQgwtlqyeg==
Date: Fri, 31 Jul 2026 13:11:02 +0000
Message-ID: <e5a6095b3b954268b01eaf393d5c39c1@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.192.32]
x-sender-location: DAG2
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam01-ex.h3c.com 66VDBCfw089718
Message-ID-Hash: OS2DMP6USZTI22PH5YDXEN24PWNKDGQY
X-Message-ID-Hash: OS2DMP6USZTI22PH5YDXEN24PWNKDGQY
X-MailFrom: linchangwang.04414@h3c.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle@ietf.org" <draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: Éric Vyncke's Discuss on draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06: (with DISCUSS and COMMENT)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ellMlL6lcooERdFtO5luU4dyLJ8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>


Hi Éric ,

  Thank you for your review.
  We appreciate your thoughtful comments and suggestions.

  We submitted version-07 to address your comments.
  The IETF datatracker status page for this Internet-Draft is:
  https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle/07/
  A diff from the previous version is available at:
  https://author-tools.ietf.org/iddiff?url1=draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06&url2=draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-07&difftype=--html

  Pls check and let us know if there are any further comments.
  Pls see inline with “Changwang>” tag.

Thanks,
Changwang



发件人: Éric Vyncke via Datatracker <noreply@ietf.org>
发送时间: 2026年7月30日 21:04
收件人: The IESG <iesg@ietf.org>
抄送: draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle@ietf.org; idr-chairs@ietf.org; idr@ietf.org; shares@ndzh.com
主题: Éric Vyncke's Discuss on draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06: (with DISCUSS and COMMENT)



Éric Vyncke has entered the following ballot position for
draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06: Discuss

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------


# Éric Vyncke INT AD comments for draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-06
CC @evyncke

Thank you for the work put into this document.

Please find below some blocking DISCUSS points (easy to address), some non-blocking COMMENT points/nits (replies would be appreciated even if only for my own education).

Special thanks to Sue Hares for the shepherd's write-up.

I hope that this review helps to improve the document,

Regards,

-éric

Note: this ballot comments follow the Markdown syntax of https://github.com/mnot/ietf-comments/tree/main, i.e., they can be processed by a tool to create github issues.

## DISCUSS (blocking)

As noted in
https://datatracker.ietf.org/doc/statement-iesg-handling-ballot-positions-20220121/,
a DISCUSS ballot is a request to have a discussion on the points below; I really think that the document would be improved with a change here, but can be convinced otherwise.

### Section 3

Why not a MUST in `If so, it SHOULD advertise the Peer Adjacency Segments of bundle members in BGP-LS` ? There is condition to the MUST. Else, provide guidance of the effect of bypassing the SHOULD.

Changwang> ACK, modified in the new version.

See also:
https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/

### Unbalancing the L2 bundle ?

I failed to find an operational consideration about the potential load unbalance when select specific bundle members, I am afraid that this could lead to overloaded bundle members. Please add some considerations on this issue (or explain why it is not an issue).

Moreover, if some packets of the flow happen to have different policies, then the packer ordering within a flow can be broken. As I am not a SR expert, this kind of policies may be impossible though.

Changwang> ACK, modified in the new version. See the newly added operation consideration section.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

## COMMENTS (non-blocking)

### Section 1

s/This document describes/This document *specifies*/ as it is PS.

Changwang> ACK, modified in the new version.

## NITS (non-blocking / cosmetic)

### Layer-2 vs. Layer 2

As English is not my primary language, I learned it at school and my grammar says to use "layer-2 interface" rather than the "Layer 2 interface" (i.e., hyphen and lowercase)...

Changwang> RFC8668 uses layer 2. Please check if it needs to be modified.

### Use of SVG graphics

To make a much nicer HTML rendering, suggest using the aasvg tool to generate SVG graphics. It is worth a try especially if the I-D uses the Kramdown file format ;-)

Changwang> Not modified yet. I'll familiarize myself with the tool locally and will make the changes in the next version. Thanks for the suggestion.



-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出的个人或群组。
禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。
如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited.
If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!