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

linchangwang <linchangwang.04414@h3c.com> Mon, 19 February 2024 03:07 UTC

Return-Path: <linchangwang.04414@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 11129C14F5EF; Sun, 18 Feb 2024 19:07:39 -0800 (PST)
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 SO8b1sTiWtYE; Sun, 18 Feb 2024 19:07:34 -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 6EBC0C14F5EB; Sun, 18 Feb 2024 19:07:25 -0800 (PST)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 41J36xhR073745; Mon, 19 Feb 2024 11:06:59 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX09-BJD.srv.huawei-3com.com (unknown [10.153.34.11]) by mail.maildlp.com (Postfix) with ESMTP id 23F2E2004BA9; Mon, 19 Feb 2024 11:07:54 +0800 (CST)
Received: from DAG6EX01-IMDC.srv.huawei-3com.com (10.62.14.10) by DAG6EX09-BJD.srv.huawei-3com.com (10.153.34.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Mon, 19 Feb 2024 11:06:59 +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; Mon, 19 Feb 2024 11:06:59 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, "spring@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>
Thread-Topic: WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)
Thread-Index: AQHaW45+LLWqKiNz+0agnaKZc+gV4rERA8xg
Date: Mon, 19 Feb 2024 03:06:59 +0000
Message-ID: <3adb1aee97d84d3997cd62682a707782@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.114.76.67]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_3adb1aee97d84d3997cd62682a707782h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 41J36xhR073745
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Ncjx1K8B56tiNAslBMQRPvDbw0g>
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: Mon, 19 Feb 2024 03:07:39 -0000

Hi:

       I support the adoption of this draft as a co-author .
I am not aware of any  IPR relevant to this draft.

The replies to several questions are as follows:

••  Do we need these different solutions?

----Yes, [draft-cheng-rtgwg-srv6-multihome-egress-protection-05] is suitable for scenarios where the ingress node can arrange primary and backup SIDs based on the idea of source routing.

••  Technical merits and drawbacks of each solution

【draft-ietf-rtgwg-srv6-egress-protection-16】: Requires control plane extension and Mirror sid extension, does not require ingress node awareness.

 【draft-cheng-rtgwg-srv6-multihome-egress-protection-05】: Does not require control plane extension, requires  ingress node to include the backup service SID in the encoding.

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

   ----H3C has implemented the egress protection method as mentioned in the draft document "draft-cheng-rtgwg-srv6-multihome-egress-protection-05".

Organization: New H3C Technologies.

Maturity Level: Beta

Version: draft-cheng-rtgwg-srv6-multihome-egress-protection-05



Thanks,

Changwang


From: Yingzhen Qu [mailto:yingzhen.ietf@gmail.com]
Sent: Saturday, February 10, 2024 3:30 AM
To: RTGWG; spring@ietf.org; rtgwg-chairs; draft-cheng-rtgwg-srv6-multihome-egress-protection
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!