Re: [spring] WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)

"Mengxiao.Chen" <chen.mengxiao@h3c.com> Sun, 18 February 2024 03:45 UTC

Return-Path: <chen.mengxiao@h3c.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D27C6C14F5E6; Sat, 17 Feb 2024 19:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 qbZ6b7v6bNhq; Sat, 17 Feb 2024 19:45:04 -0800 (PST)
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 B3BC6C14F5E3; Sat, 17 Feb 2024 19:44:52 -0800 (PST)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 41I3iNAP028680; Sun, 18 Feb 2024 11:44:23 +0800 (GMT-8) (envelope-from chen.mengxiao@h3c.com)
Received: from DAG6EX11-BJD.srv.huawei-3com.com (unknown [10.153.34.13]) by mail.maildlp.com (Postfix) with ESMTP id 31D472005129; Sun, 18 Feb 2024 11:45:17 +0800 (CST)
Received: from DAG6EX03-IMDC.srv.huawei-3com.com (10.62.14.12) by DAG6EX11-BJD.srv.huawei-3com.com (10.153.34.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Sun, 18 Feb 2024 11:44:24 +0800
Received: from DAG6EX03-IMDC.srv.huawei-3com.com ([fe80::ecd2:1dde:6a91:c9ef]) by DAG6EX03-IMDC.srv.huawei-3com.com ([fe80::ecd2:1dde:6a91:c9ef%19]) with mapi id 15.02.1258.027; Sun, 18 Feb 2024 11:44:24 +0800
From: "Mengxiao.Chen" <chen.mengxiao@h3c.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>
CC: "spring@ietf.org" <spring@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>
Thread-Topic: WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)
Thread-Index: AQHaW46AFC5iZIXxZkCSaGB17TsiALEIXhIw
Date: Sun, 18 Feb 2024 03:44:23 +0000
Message-ID: <29ccd828987d4c98936c493c55904328@h3c.com>
References: <CABY-gOMQ=LaECWJsJHsdKX7i+BUsiX=LF5b5ZPMVp=3qQjZ8Mg@mail.gmail.com>
In-Reply-To: <CABY-gOMQ=LaECWJsJHsdKX7i+BUsiX=LF5b5ZPMVp=3qQjZ8Mg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.99.152.251]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_29ccd828987d4c98936c493c55904328h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 41I3iNAP028680
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/HhwJS5_Xux4P2DvAatkZu-uPgO4>
Subject: Re: [spring] WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Feb 2024 03:45:08 -0000

Hi,

I support the adoption of this draft.
It proposes a source-routing-based mechanism of egress protection. It is not dependent on control plane protocols, and it is easy to deploy.

Thanks,
Mengxiao

From: rtgwg <rtgwg-bounces@ietf.org> On Behalf Of Yingzhen Qu
Sent: Saturday, February 10, 2024 3:30 AM
To: RTGWG <rtgwg@ietf.org>; spring@ietf.org; rtgwg-chairs <rtgwg-chairs@ietf.org>; draft-cheng-rtgwg-srv6-multihome-egress-protection <draft-cheng-rtgwg-srv6-multihome-egress-protection@ietf.org>
Subject: WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)


Hi,



This email begins a 2 week WG adoption poll for the following draft:

draft-cheng-rtgwg-srv6-multihome-egress-protection-05 - SRv6 Egress Protection in Multi-homed scenario (ietf.org)<https://datatracker.ietf.org/doc/draft-cheng-rtgwg-srv6-multihome-egress-protection/>



Please review the document and indicate your support or objections by Feb 24th, 2024.

Please note that there is an existing WG document:draft-ietf-rtgwg-srv6-egress-protection-16 - SRv6 Path Egress Protection<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-srv6-egress-protection/> Which proposes fast protections for the egress node and link of an SRv6 path through extending IGP and using Mirror SID. As you discuss adopting draft-cheng-rtgwg-srv6-multihome-egress-protection, please also consider:

·  Do we need these different solutions?

·  Technical merits and drawbacks of each solution

·  If there is any implementation of the proposals, please voice it.

Authors, please respond to the list indicating whether you are aware of any IPR that applies to the draft.

Also copying SPRING WG.

Thanks,

Yingzhen (RTGWG Co-chair)

-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
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!