[netconf] Comment on draft-dai-netconf-quic-netconf-over-quic
Qin Wu <bill.wu@huawei.com> Tue, 22 March 2022 08:24 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E9A3A0C51; Tue, 22 Mar 2022 01:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHPJUS2xWtoo; Tue, 22 Mar 2022 01:24:32 -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 716783A0C7A; Tue, 22 Mar 2022 01:24:32 -0700 (PDT)
Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KN4Gg2vs1z6884q; Tue, 22 Mar 2022 16:22:19 +0800 (CST)
Received: from canpemm100007.china.huawei.com (7.192.105.181) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Tue, 22 Mar 2022 09:24:29 +0100
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm100007.china.huawei.com (7.192.105.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Tue, 22 Mar 2022 16:24:27 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2308.021; Tue, 22 Mar 2022 16:24:27 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "djy@fiberhome.com" <djy@fiberhome.com>
CC: Netconf <netconf@ietf.org>, "draft-dai-netconf-quic-netconf-over-quic@ietf.org" <draft-dai-netconf-quic-netconf-over-quic@ietf.org>
Thread-Topic: Comment on draft-dai-netconf-quic-netconf-over-quic
Thread-Index: Adg9xWCUu0DnfI3VQ7WwxdVi1IFlxQ==
Date: Tue, 22 Mar 2022 08:24:27 +0000
Message-ID: <93bfb8a49e2e495386e409342b239b1c@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: multipart/alternative; boundary="_000_93bfb8a49e2e495386e409342b239b1chuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/u4hBO3_gkblJrmzvf6yPOyAXAMg>
Subject: [netconf] Comment on draft-dai-netconf-quic-netconf-over-quic
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 08:24:38 -0000
Hi, Dai: Thank for proposing NETCONF over quic to NETCONF WG. Since all current implementations of NETCONF are based on TCP based protocol, I am wondering whether there are some implementation or PoC on NETCONF over QUIC. Have you discussed your proposal in QUIC WG and any feedback you collect? My impression is it have a lot of challenges to switch transport protocol of NETCONF from TCP to QUIC. One possibility is to come up with QUIC Notif proposal, which might be related to UDP notif which has been proceeded in NETCONF. Happy to discuss with you if you have any input an thought on this direction. -Qin