IETF Logo Mail Archive

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

Liurubing <liurubing@h3c.com> Mon, 05 August 2024 06:19 UTC

Return-Path: <liurubing@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 92FCAC14CF12 for <idr@ietfa.amsl.com>; Sun, 4 Aug 2024 23:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 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, 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 JxXHmqz_daar for <idr@ietfa.amsl.com>; Sun, 4 Aug 2024 23:19:42 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B238C14CF1E for <idr@ietf.org>; Sun, 4 Aug 2024 23:19:41 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 4756JF04062550; Mon, 5 Aug 2024 14:19:15 +0800 (GMT-8) (envelope-from liurubing@h3c.com)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (unknown [10.153.34.10]) by mail.maildlp.com (Postfix) with ESMTP id 892452004733; Mon, 5 Aug 2024 14:24:05 +0800 (CST)
Received: from DAG6EX10-BJD.srv.huawei-3com.com (10.153.34.12) 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; Mon, 5 Aug 2024 14:19:16 +0800
Received: from DAG6EX10-BJD.srv.huawei-3com.com ([fe80::ade6:b219:16f8:9aa8]) by DAG6EX10-BJD.srv.huawei-3com.com ([fe80::ade6:b219:16f8:9aa8%6]) with mapi id 15.02.1258.027; Mon, 5 Aug 2024 14:19:16 +0800
From: Liurubing <liurubing@h3c.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
Thread-Index: Adrk5OcKbcHJAvS7RzC9jEn2PoHm4wCButZQ
Date: Mon, 05 Aug 2024 06:19:16 +0000
Message-ID: <780387e280f24c56b3760d52d23575a9@h3c.com>
References: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com>
In-Reply-To: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.101.1.57]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_780387e280f24c56b3760d52d23575a9h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 4756JF04062550
Message-ID-Hash: PGT3EX7ZLYGA2DZMT6ZMLGQFPH3Q6ON3
X-Message-ID-Hash: PGT3EX7ZLYGA2DZMT6ZMLGQFPH3Q6ON3
X-MailFrom: liurubing@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
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/_scUlbCs6II7IZHyxkv9axkrO0w>
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 All,

I support the WG adoption.

1) Does this BGP-LS addition help SR Egress Peering points in operational networks?
   Yes.
2) Does this draft handle the BUM traffic in a way that Prevents looping? (Broadcast, Unknown Unicast, and Multicast (BUM))
   Yes.
3) Are there any problems in the technology described?
   No.

Thanks,

Rubing Liu
H3C (New H3C Technologies Co., Ltd)
Mobile: 0086-159-6889-1896
E-mail: liurubing@h3c.com
Address: No.466 Changhe Road, Binjiang District, Hangzhou, Zhejiang, 310052 China


From: Susan Hares <shares@ndzh.com>
Sent: Friday, August 2, 2024 10:12 PM
To: 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
-------------------------------------------------------------------------------------------------------------------------------------
?????????????????????????????????
????????????????????????????????????????
????????????????????????????????????????
???
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!

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