IETF Logo Mail Archive

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

Cheng Li <c.l@huawei.com> Fri, 19 April 2024 13:21 UTC

Return-Path: <c.l@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA0BC14F614; Fri, 19 Apr 2024 06:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level:
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 LWC1F0k6Adh6; Fri, 19 Apr 2024 06:21:55 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7809DC14F609; Fri, 19 Apr 2024 06:21:55 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VLZxb1k4bz6FCL5; Fri, 19 Apr 2024 21:19:47 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (unknown [7.191.160.241]) by mail.maildlp.com (Postfix) with ESMTPS id A183D140C98; Fri, 19 Apr 2024 21:21:53 +0800 (CST)
Received: from kwepemf200012.china.huawei.com (7.202.181.238) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Fri, 19 Apr 2024 14:21:52 +0100
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by kwepemf200012.china.huawei.com (7.202.181.238) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.4; Fri, 19 Apr 2024 21:21:51 +0800
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2507.035; Fri, 19 Apr 2024 21:21:50 +0800
From: Cheng Li <c.l@huawei.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>
Thread-Topic: WG Adoption Call - draft-dmk-rtgwg-multisegment-sdwan (04/10/24 - 04/26/24)
Thread-Index: AQHai3GCv8vD2RWR8U6gZEuZFCiIIrFvoA4g
Date: Fri, 19 Apr 2024 13:21:50 +0000
Message-ID: <c6784bf4161d4645af2240db369855be@huawei.com>
References: <CABY-gOPp3xJsQfbVvWvANsKZSQbPwKimZyx94w2wETSEQHGz7g@mail.gmail.com>
In-Reply-To: <CABY-gOPp3xJsQfbVvWvANsKZSQbPwKimZyx94w2wETSEQHGz7g@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.221.205.154]
Content-Type: multipart/alternative; boundary="_000_c6784bf4161d4645af2240db369855behuaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/rxyDG39eDp2L-WxBMfPTVTT_4Nc>
Subject: Re: [nvo3] WG Adoption Call - draft-dmk-rtgwg-multisegment-sdwan (04/10/24 - 04/26/24)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2024 13:21:59 -0000

I would say the use case is interesting, and worth to work on it, so I support to adopt it and let’s treat it more critical to work out a good RFC.
But I would recommend the authors to use Markdown or XML tools to rewrite the document, the format seems can be better to me 😊

I am interested in working on this work if it can be adopted.

Thanks,
Cheng




From: rtgwg <rtgwg-bounces@ietf.org> On Behalf Of Yingzhen Qu
Sent: Wednesday, April 10, 2024 8:02 PM
To: RTGWG <rtgwg@ietf.org>; rtgwg-chairs <rtgwg-chairs@ietf.org>; nvo3-chairs@ietf.org; nvo3@ietf.org
Subject: 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

v2.23.0 | Report a Bug | By Email