[Idr] Re: [spring] request for review and comments

linchangwang <linchangwang.04414@h3c.com> Wed, 15 May 2024 11:37 UTC

Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86AE6C1D876A; Wed, 15 May 2024 04:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LlIV1ugL7PXe; Wed, 15 May 2024 04:37:04 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92D81C14F689; Wed, 15 May 2024 04:37:02 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 44FBa3Mj020400; Wed, 15 May 2024 19:36:12 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX03-IMDC.srv.huawei-3com.com (unknown [10.62.14.12]) by mail.maildlp.com (Postfix) with ESMTP id 3BBB62004BB5; Wed, 15 May 2024 19:39:12 +0800 (CST)
Received: from DAG6EX01-IMDC.srv.huawei-3com.com (10.62.14.10) by DAG6EX03-IMDC.srv.huawei-3com.com (10.62.14.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Wed, 15 May 2024 19:36:15 +0800
Received: from DAG6EX01-IMDC.srv.huawei-3com.com ([fe80::1d4d:847c:a7e3:1f10]) by DAG6EX01-IMDC.srv.huawei-3com.com ([fe80::1d4d:847c:a7e3:1f10%20]) with mapi id 15.02.1258.027; Wed, 15 May 2024 19:36:15 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Thread-Topic: [spring] request for review and comments
Thread-Index: Adqmuqya8DjAS+7JQBWeWmqxR9KK1g==
Date: Wed, 15 May 2024 11:36:15 +0000
Message-ID: <87fb7f019c3740c4a39929d6b75ea635@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.156]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_87fb7f019c3740c4a39929d6b75ea635h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 44FBa3Mj020400
Message-ID-Hash: UDIWGXA6NUJTG74LV6QHGXQVXUSVYSMV
X-Message-ID-Hash: UDIWGXA6NUJTG74LV6QHGXQVXUSVYSMV
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: idr-chairs <idr-chairs@ietf.org>, draft-lin-idr-sr-epe-over-l2bundle <draft-lin-idr-sr-epe-over-l2bundle@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "spring@ietf.org" <spring@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: [spring] request for review and comments
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/quAS4WpTp3hLawxsSESJGKCL8dE>
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 Alvaro,

       Thank you for your comments and suggestions, version-06 has been updated to include an explanation for the updated RFC:
https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/06/


1.     Before the update to RFC9085: [RFC9085] does not specify the support of BGP EPE over L2 Bundle


After the update:
This document updates [RFC9085] to allow the L2 Bundle Member Attributes TLV to be added to the BGP-LS Attribute associated with the Link NLRI of BGP peering link.



2.     Before the update to RFC9086: RFC9086 only specifies how BGP-LS advertises IGP L2 Bundle Member Attributes information through the L2 Bundle Member Attributes TLV, with no mention of how BGP EPE over   L2 Bundle can be advertised through BGP-LS.

After the update:
This document updates [RFC9085] and [RFC9086] to allow the PeerAdj SID TLV to be included as a sub-TLV of the L2 Bundle Member Attributes TLV.


Thanks,
Changwang

发件人: Alvaro Retana <aretana.ietf@gmail.com>
发送时间: 2024年5月15日 16:26
收件人: linchangwang (RD) <linchangwang.04414@h3c.com>
抄送: li_zhenqiang@hotmail.com; idr-chairs <idr-chairs@ietf.org>; draft-lin-idr-sr-epe-over-l2bundle <draft-lin-idr-sr-epe-over-l2bundle@ietf.org>; idr@ietf.org; spring@ietf.org
主题: Re: [spring] request for review and comments

Hi!

If you want to formally update other RFCs, you need to do several other things: include a tag in the header, indicate the update in the Abstract and Introduction, and indicate what are the text changes (if any) to the original RFCs.

While I still think the (formal) update is not needed, it may be a discussion to be had if the document is adopted.

Thanks!

Alvaro.


On May 15, 2024 at 7:51:46 AM, linchangwang (linchangwang.04414@h3c.com<mailto:linchangwang.04414@h3c.com>) wrote:
Therefore, the update proposed in section 3.1 is needed.
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
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!