IETF Logo Mail Archive

[netconf] Re: Adoption call for quic-netconf-over-quic-06

Marc Blanchet <marc.blanchet@viagenie.ca> Mon, 19 August 2024 02:21 UTC

Return-Path: <marc.blanchet@viagenie.ca>
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 AB6ACC14F6E2 for <netconf@ietfa.amsl.com>; Sun, 18 Aug 2024 19:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=viagenie-ca.20230601.gappssmtp.com
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 JSx0AJMDnQMg for <netconf@ietfa.amsl.com>; Sun, 18 Aug 2024 19:21:38 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF4D1C14F5EE for <netconf@ietf.org>; Sun, 18 Aug 2024 19:21:38 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-7a1d81dc0beso269965185a.2 for <netconf@ietf.org>; Sun, 18 Aug 2024 19:21:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=viagenie-ca.20230601.gappssmtp.com; s=20230601; t=1724034097; x=1724638897; darn=ietf.org; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KBNPSGIhRlB56GjVmysc5Cx1zfFdRYZWYvllJ8aMh6o=; b=qvTrLUGkKmRzgAoMeQU+/V9QSyvuR5N6YkBLJSwx2m6zl+5/RK+kqIOpodHbfxpVn6 /7e+A4W1JSQ1XUh4UGxLvZE+sfSsiTjTb4IdjjT/R2khG6aMbV9VIqTluGUJ7Mt7rzNu XbQm4sRC561oD9jvvsOYE6a1z8vVyB/Vn9LO0GGnc0axaOcitJyFjNLIdOidV9450+Hn 37vEklqXkpErMQaZ7QPyQR9l6yjXwjPw17nB+qdUj8+hAS1k49UGaAXn22rnYSevs4q/ C4fpBP0klep09ad/GsYL1hqAhRr1DYJfb9/ISEO5I/kSVGk9vkj4GH0QL3mtzN2aw50t pU0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724034097; x=1724638897; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KBNPSGIhRlB56GjVmysc5Cx1zfFdRYZWYvllJ8aMh6o=; b=Syo4QkS5hOz95kGuwjY48yadKqvwW2N+TD9sjRIZnqAHH5W8SRKfgq/cW/jv/7T+/S njK3pZ6vUrf8oLeoxmGum5wJme2zNpdfSwr3ynF/09Z4mPQ+60bXEFq6SfSAMyHVni32 C0q2g1clcVImJLsj+HQJaLEQ6jUieWAOPTsvBEEgVrGGczR0SJrg+QnakAHbhoofEsTp 5iY2sNjmF2h9kr/+1eFN8k/0aKkkaLUT8KC1uTJYOx+XIL3PXbNCfAFOq4fLUIqypbvd apyK/gcs+nud4PriUQCtaKJ+EOYWU/hX/GH2kLsSBhAdGA7bAZZkG7zJ8r+VP0F/UxYq 6ing==
X-Forwarded-Encrypted: i=1; AJvYcCV4AAGFVr3Ellzj+yi8/MFg3qxZMfwgE64Ua/3fH10aYitzc0zDYIKBhBGOvcDJt7OcR4DWM9zhpPOXMJ5ItOIh
X-Gm-Message-State: AOJu0YyeVUDUaZO/nrJ2XDPV/9ITklLmw4QlE8eciy2L14T0r1RRfpbh evdEVvQR2Kh6ZhfbjRlNS+yQdwCEogaxggCHtrESkAk+IrN958i+xOWE0JUl41g=
X-Google-Smtp-Source: AGHT+IFrRt2aALC4L5LdvAI9Ju2q83hLHqnbXyYm7Nflvy3nGaDQW0wdl0UFetBltUANeFZ/44yLzA==
X-Received: by 2002:a05:620a:469f:b0:79d:7cfb:884e with SMTP id af79cd13be357-7a5069000f4mr1265321285a.4.1724034097353; Sun, 18 Aug 2024 19:21:37 -0700 (PDT)
Received: from smtpclient.apple (modemcable108.66-162-184.mc.videotron.ca. [184.162.66.108]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7a4ff11cfbcsm393110885a.129.2024.08.18.19.21.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Aug 2024 19:21:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2B1F332E-EF6B-421F-95FC-8E75B680D454"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
X-Priority: 3
In-Reply-To: <tencent_4E1D0A65F24BAE6D0069391ACCB8639F2A09@qq.com>
Date: Sun, 18 Aug 2024 22:21:25 -0400
Message-Id: <C5839E45-2C48-4C80-BA82-F711367A6FCF@viagenie.ca>
References: <0100019151cda6b9-99bdca9e-ec7f-443d-b792-2f0d606aff55-000000@email.amazonses.com> <tencent_4E1D0A65F24BAE6D0069391ACCB8639F2A09@qq.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Message-ID-Hash: THO6RJTAP23DUTHZ53PLBXYLIII3ZUN6
X-Message-ID-Hash: THO6RJTAP23DUTHZ53PLBXYLIII3ZUN6
X-MailFrom: marc.blanchet@viagenie.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: kent+ietf <kent+ietf@watsen.net>, "netconf@ietf.org" <netconf@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: Adoption call for quic-netconf-over-quic-06
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/bUvIK7GoWhmzlW5HrLYaCAj3Oew>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>


> Le 18 août 2024 à 21:46, Chongfeng Xie <chongfeng.xie@foxmail.com> a écrit :
> 
> Hi Authors,
> 
> I have the following question about "NETCONFoQUIC" raised in the draft,
> 
> The abstract mentions that "This document describes  how to use NETCONF over the QUIC transport protocol, named NETCONFoQUIC."  But in section 7,  NETCONFoQUIC is shown as one type of protocol.  So my question is that whether NETCONFoQUIC is a kind of new protocol? If yes, what't the relationship of NETCONFoQUIC with NETCONF?

From TLS point of view, it is another protocol, therefore it is registered as an ALPN. All protocols over QUIC do the same.

Marc.

> 
> Best regards
> 
> Chongfeng
> 
> From: 【外部账号】Kent Watsen <mailto:kent+ietf@watsen.net>
> Date: 2024-08-15 00:51
> To: netconf@ietf.org <mailto:netconf@ietf.org>
> Subject: [netconf] Adoption call for quic-netconf-over-quic-06
> NETCONF WG,
> 
> This message starts a two week poll on adopting the following document:
> 
> 	Using NETCONF over QUIC connection
> 	https://datatracker.ietf.org/doc/html/draft-dai-netconf-quic-netconf-over-quic-06
> 
> The poll ends August 28.
> 
> Please send email to the list indicating "yes/support” or "no/do not support".  If indicating no, please state your reservations with the document.  If yes, please also feel free to provide comments you'd like to see addressed once the document is a WG document.
> 
> FWIW, no IPR is known for this document:
> 
> 	https://mailarchive.ietf.org/arch/msg/netconf/L9a1nQFdNuGH0rXZyEbd_RaN-UQ/
> 
> Kent  // as NETCONF WG chair
> 
> _______________________________________________
> netconf mailing list -- netconf@ietf.org <mailto:netconf@ietf.org>
> To unsubscribe send an email to netconf-leave@ietf.org <mailto:netconf-leave@ietf.org>

v2.28.0 | Report a Bug | By Email | System Status