IETF Logo Mail Archive

[Idr] Re: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)

"易昕昕(联通集团本部)" <yixx3@chinaunicom.cn> Mon, 05 August 2024 02:57 UTC

Return-Path: <yixx3@chinaunicom.cn>
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 B8A48C14F6BC for <idr@ietfa.amsl.com>; Sun, 4 Aug 2024 19:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.326
X-Spam-Level:
X-Spam-Status: No, score=-6.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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 X7F1ujjTbrs1 for <idr@ietfa.amsl.com>; Sun, 4 Aug 2024 19:57:21 -0700 (PDT)
Received: from sendd.mailex.chinaunicom.cn (senda.mailex.chinaunicom.cn [123.138.59.136]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 7A0E9C14F6A5 for <idr@ietf.org>; Sun, 4 Aug 2024 19:57:19 -0700 (PDT)
Received: from M10-XA-MLCEN02.MailSrv.cnc.intra (unknown [10.236.3.198]) by sendd.mailex.chinaunicom.cn (SkyGuard) with ESMTPS id 4Wch1R4rJMzmGlty for <idr@ietf.org>; Mon, 5 Aug 2024 10:57:15 +0800 (CST)
Received: from smtpbg.qq.com (10.237.2.96) by M10-XA-MLCEN02.MailSrv.cnc.intra (10.236.3.198) with Microsoft SMTP Server id 15.0.1497.48; Mon, 5 Aug 2024 10:57:14 +0800
X-QQ-mid: Ymail-xx24b003-t1722826631t6c
Received: from yixx-PC (unknown [10.2.109.69]) by smtp.qq.com (ESMTP) with id ; Mon, 05 Aug 2024 10:57:11 +0800 (CST)
X-QQ-SSF: 00900000000000N0ZG20000A0000000
X-QQ-GoodBg: 0
From: "易昕昕(联通集团本部)" <yixx3@chinaunicom.cn>
To: shares <shares@ndzh.com>, idr <idr@ietf.org>
Date: Mon, 05 Aug 2024 10:57:11 +0800
References: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.300[cn]
MIME-Version: 1.0
Message-ID: <202408051057111410613@chinaunicom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart140846713173_=----"
X-QQ-SENDSIZE: 520
Feedback-ID: Ymail-xx:chinaunicom.cn:mail-xx:mail-xx24b003-zhyw44w
Message-ID-Hash: HN62CU4EDJCDD6W3EOKYYHX3YFXCMK7O
X-Message-ID-Hash: HN62CU4EDJCDD6W3EOKYYHX3YFXCMK7O
X-MailFrom: yixx3@chinaunicom.cn
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-q0TwG26JeeJPDHMEQtUnlXAnlg>
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  WG,

I support the adoption of this document.

The response to the issue is as follows:

  1.  Does this BGP-LS addition help SR Egress Peering points in operational networks?

            Yes.



  1.  Does this draft handle the BUM traffic in a way that Prevents looping?  (Broadcast, Unknown Unicast, and Multicast (BUM))

            Yes.



  1.  Are there any problems in the technology described?
            No.

Best Regards
Xinxin

From: Susan Hares<mailto:shares@ndzh.com>
Date: 2024-08-02 22:11
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [警惕！外部邮件][Idr] WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
IDR WG:

This begins a 2 week WG adoption call for
draft-lin-idr-sr-epe-over-l2bundle-07.txt
https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/


The authors should reply to this email with an
IPR statement indicating whether they know of an intellectual property.

This document describes how to support Segment Routing
BGP Egress Peer Engineering over Layer 2 bundle members.
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.


In your comments regarding adoption,  please consider


  1.  Does this BGP-LS addition help SR Egress Peering points

in operational networks?

  1.  Does this draft handle the BUM traffic in a way that

Prevents looping?

(Broadcast, Unknown Unicast, and Multicast (BUM))

  1.  Are there any problems in the technology described?

Cheerily, Sue Hares
如果您错误接收了该邮件，请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc@chinaunicom.cn，即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.

v2.26.15 | Report a Bug | By Email | System Status