IETF Logo Mail Archive

[netconf] Re: I-D Action: draft-ietf-netconf-over-quic-02.txt

Per Andersson <per.ietf@ionio.se> Wed, 02 April 2025 13:57 UTC

Return-Path: <perkietf@gmail.com>
X-Original-To: netconf@mail2.ietf.org
Delivered-To: netconf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 7B8021673040 for <netconf@mail2.ietf.org>; Wed, 2 Apr 2025 06:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHuff9YBXpvw for <netconf@mail2.ietf.org>; Wed, 2 Apr 2025 06:57:51 -0700 (PDT)
Received: from mail-pf1-f174.google.com (mail-pf1-f174.google.com [209.85.210.174]) (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 mail2.ietf.org (Postfix) with ESMTPS id 243A11673031 for <netconf@ietf.org>; Wed, 2 Apr 2025 06:57:51 -0700 (PDT)
Received: by mail-pf1-f174.google.com with SMTP id d2e1a72fcca58-7373aa99e2cso21212b3a.0 for <netconf@ietf.org>; Wed, 02 Apr 2025 06:57:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743602270; x=1744207070; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9xhIW1zKJOg3CoR7KdD8lmPPV0kP9bJgotzg5yjf1A8=; b=sFYZBGM8ixPVphKKOn7z3pMh7x9Q99+TFDW1zvfsbDUOcHKrbpz7E7AAm8knzHW1B7 oBnvf4AWWDFYlu7s48XZbSZ3KMFgdO4LJEOF4+GY+KVRtWg0ZwPfBPwuzmkteYKFQXfe haS7Z+WLz663SAeuzktBcZelmjWDbvJvin6v81qn5U1RlbmJ39nsmnPuJi4AvCespRLu /wql2p+R/5BzeX8VMOX5Mxmge0sgKG4G1ddf+4pVkRUSHPd9Wwl+XfzIM4dvjiX0xQwv Y945x8fav0XoGGq7W3t9mMMQAXPWKg2CbFVbmf3lPpXL+5Dx2bOO5Od38JqusaWazAf/ 9CnA==
X-Forwarded-Encrypted: i=1; AJvYcCUAtjcyY4Qs36A6r8p5RQh29abPtZMcBZ7GbFouyoikkOLCWoXp995qffDYGCr0z3nX+s1qoapQ@ietf.org
X-Gm-Message-State: AOJu0YxfjPbGlfoy8xjvSOcyIoIyIj7cLpQkLRuaYqZbbGMOV0RQrwF8 RYX7yXaJDfQIhFCccoJ0jWlfRSUPEvFSY5186a3kJWz9XCP6/gzkPgeCUScM
X-Gm-Gg: ASbGncusXqTDIG8JYW20Xpqm+Y8RwbJZOLMcgSM8WzR/TU1gk4agVFGRW0sCS7ABdSE wXwIt8aBZAM0U+v55Dg3gHc902eVL4v0aGMF/6gWV5xgO9j81xol0n9Clr+3hZu07s27r6BJGjr FqLJ/gLPXOlZk2/mFxAZVvJccrMA/YI+PX7cQ4B/xX2iRaRi0bXDHK3dycs7EVmDKOI42GfwdNw O1Bsi6Sc2wGsL6pIG4I6X97QV1GZq4yLN9/X/NpPkpGruupiVsBZCzP8B9MpXksA7Xkbu2Hhx6Q mAwih/ncH+XqEO2TLM5PQ8Nt/JWZOPXRRxVeg6aU0hWpwuu3imDcOIKMVJ9gIfLWs3t+YGDWq1n lwhEHlKUDmXfLAGjncQ==
X-Google-Smtp-Source: AGHT+IFKgR41FDr6Fn4vMfedxicmT+WOack70uNIvBYzDoPR2MUvCseEoZl2Dz9dn6CGtNpfVgvfOQ==
X-Received: by 2002:a05:6a00:1947:b0:730:8526:5db2 with SMTP id d2e1a72fcca58-739b8a6d3ddmr3274925b3a.5.1743602269084; Wed, 02 Apr 2025 06:57:49 -0700 (PDT)
Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com. [209.85.214.179]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-73970e4cfadsm10956690b3a.78.2025.04.02.06.57.48 for <netconf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Apr 2025 06:57:48 -0700 (PDT)
Received: by mail-pl1-f179.google.com with SMTP id d9443c01a7336-224172f32b3so14245625ad.2 for <netconf@ietf.org>; Wed, 02 Apr 2025 06:57:48 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCVZ2LM7WP02DQoSDkxqFgNQSTLlhd1Seow0iTeCqid0yX2YTXIDKKtyHgwsIWArqvg0+2lu6hhc@ietf.org
X-Received: by 2002:a17:903:985:b0:223:5525:622f with SMTP id d9443c01a7336-2295eb545c1mr34233695ad.1.1743602268549; Wed, 02 Apr 2025 06:57:48 -0700 (PDT)
MIME-Version: 1.0
References: <174049253099.534708.14293621468858996462@dt-datatracker-865df477df-9x8cj> <2A323C4F-20BA-4B70-8486-2EDB27809816@sn3rd.com>
In-Reply-To: <2A323C4F-20BA-4B70-8486-2EDB27809816@sn3rd.com>
From: Per Andersson <per.ietf@ionio.se>
Date: Wed, 02 Apr 2025 13:57:37 +0000
X-Gmail-Original-Message-ID: <CACvbXWGeHipS-kLm6yEoAQbYZUxHa3xy9tU=jTLtS0PCP3cF2Q@mail.gmail.com>
X-Gm-Features: AQ5f1JovyRbqN0G00QHI0bqfqKoa54awMvUiVNjdJDMwoOnpWvimMBQ_hAULZiA
Message-ID: <CACvbXWGeHipS-kLm6yEoAQbYZUxHa3xy9tU=jTLtS0PCP3cF2Q@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: PMLXKXOEZCRD7LPDNYO56FIJSVHRO4QC
X-Message-ID-Hash: PMLXKXOEZCRD7LPDNYO56FIJSVHRO4QC
X-MailFrom: perkietf@gmail.com
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: NETCONF WG <netconf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: I-D Action: draft-ietf-netconf-over-quic-02.txt
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/6zJcYjuKf1TGbJR2JzKU5QVflxU>
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>

(Cc netconf.)

On Wed, Apr 2, 2025 at 1:40 PM Sean Turner <sean@sn3rd.com> wrote:
>
> Should this I-D include say something about 0-RTT?  With the requirement in s1:
>
>    2.  NETCONF connections MUST provide authentication, data integrity,
>        confidentiality, and replay protection.  NETCONF depends on the
>        transport protocol for this capability.
>
> If you look at the warning in s2.3 of RFC 8446:
> https://datatracker.ietf.org/doc/html/rfc8446#section-2.3
> You will note that 0-RTT does not provide replay protection.

Good point! This was included in a very early review of the draft
I did but it doesn't seem to have made it into the document.

Thanks for the reminder!


--
Per

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