Re: [nvo3] WG Adoption Call - draft-dmk-rtgwg-multisegment-sdwan (04/10/24 - 04/26/24)

linchangwang <linchangwang.04414@h3c.com> Thu, 25 April 2024 14:00 UTC

Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2422AC14F694; Thu, 25 Apr 2024 07:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, 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 1yoAneSv_wKJ; Thu, 25 Apr 2024 07:00:22 -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 8D0E7C14F5FA; Thu, 25 Apr 2024 07:00:18 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 43PDxtlC049319; Thu, 25 Apr 2024 21:59:55 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX10-BJD.srv.huawei-3com.com (unknown [10.153.34.12]) by mail.maildlp.com (Postfix) with ESMTP id 8DC20200C1F4; Thu, 25 Apr 2024 22:02:28 +0800 (CST)
Received: from DAG6EX01-IMDC.srv.huawei-3com.com (10.62.14.10) by DAG6EX10-BJD.srv.huawei-3com.com (10.153.34.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Thu, 25 Apr 2024 21:59: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; Thu, 25 Apr 2024 21:59:59 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>, "nvo3-chairs@ietf.org" <nvo3-chairs@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [nvo3] WG Adoption Call - draft-dmk-rtgwg-multisegment-sdwan (04/10/24 - 04/26/24)
Thread-Topic: [nvo3] WG Adoption Call - draft-dmk-rtgwg-multisegment-sdwan (04/10/24 - 04/26/24)
Thread-Index: AdqXFSG3cKB8l2DFRsm4d7Omc/j0LA==
Date: Thu, 25 Apr 2024 13:59:59 +0000
Message-ID: <a59a6c38e56340278658fa987ce644ca@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_a59a6c38e56340278658fa987ce644cah3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 43PDxtlC049319
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/_t6xbZYq5VqU-ctccKFsHQtmzlA>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2024 14:00:27 -0000

Hi WG,

This draft allows the Cloud Backbone to connect multiple segments of SD-WAN without the need for decryption and re-encryption by the Cloud GWs.
This improves efficiency and enhances security.

The solution seems to be reasonable, so I support this adoption.

I have two questions and I recommend making modifications after adoption:

1.       In Figure 4, there are two instances of "Type = Multi-seg-SDWAN_subType3".

Should one of these be "Type = Multi-seg-SDWAN_subType2"?

Additionally, if these two Multi-Hop Transit SD-WAN types are used, I suggest providing further detailed descriptions in subsequent sections.


2.       Figures 8 and 9 are intended to illustrate single-hop and multi-hop encapsulation, but the actual figures do not show the difference between single-hop and multi-hop.

I suggest modifying the descriptions in the figures. Additionally, Figure 8 has a UDP port number, while Figure 9 does not.

Best Regards,
Changwang


发件人: nvo3 <nvo3-bounces@ietf.org> 代表 Yingzhen Qu
发送时间: 2024年4月11日 2:02
收件人: RTGWG <rtgwg@ietf.org>; rtgwg-chairs <rtgwg-chairs@ietf.org>; nvo3-chairs@ietf.org; nvo3@ietf.org
主题: [nvo3] WG Adoption Call - draft-dmk-rtgwg-multisegment-sdwan (04/10/24 - 04/26/24)

Hi,

This email begins a 2 week WG adoption poll for the following draft: draft-dmk-rtgwg-multisegment-sdwan-07 - Multi-segment SD-WAN via Cloud DCs (ietf.org)<https://datatracker.ietf.org/doc/draft-dmk-rtgwg-multisegment-sdwan/>

After the draft was presented at IETF 119, the chairs did a poll of the draft, and here are the questions and results:

  *   "Do you think the multi-segment SD-WAN as described in the draft is a use case that the IETF should work on?"
yes: 20 no: 9 no_opinion: 33 total: 84

  *   "Do you support adoption of this work in RTGWG?"
yes: 9 no: 9 no_opinion: 25 total: 92

There is currently one IPR disclosure of this draft: IPR disclosures (ietf.org)<https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-dmk-rtgwg-multisegment-sdwan>
Authors, please respond to the list indicating whether you are aware of any IPR that applies to the draft.

The draft proposes a solution which extends GENEVE, so also copying NVO3 WG. If you don't think the draft should be adopted in RTGWG, please voice your opinion.

Please review the document and indicate your support or objections by Apr 26th, 2024.

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