IETF Logo Mail Archive

Re: [netconf] Secdir last call review of draft-ietf-netconf-http-client-server-16

Shivan Kaul Sahib <shivankaulsahib@gmail.com> Fri, 16 February 2024 01:05 UTC

Return-Path: <shivankaul.1993@gmail.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 956E3C1CAF2B; Thu, 15 Feb 2024 17:05:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=gmail.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 bYiwZZipwDE8; Thu, 15 Feb 2024 17:05:49 -0800 (PST)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9312FC1CAF29; Thu, 15 Feb 2024 17:05:49 -0800 (PST)
Received: by mail-wr1-x42e.google.com with SMTP id ffacd0b85a97d-33ce2d1ab86so110681f8f.2; Thu, 15 Feb 2024 17:05:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708045548; x=1708650348; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=orTDpmGeJ87Kmuc6jHr3hnh69Lu4LnZgWzqnpNrswUA=; b=Jv3xcnmLfTEml98BMVv3YfeS1iYKK0Hy0VaHItcRVt87IGm+eDqjmnoo8V7/MtO0Up Z+RTv5B7RL1kjc2oBZUJlPZGeM/NgH1Jg0CVCIJ0X/RdqKMNnlMo5ZvtswJsgtBCKQ0u G+23S1srNn6q1MKxQw+ygETIKOS2Q06gk6oll0qvUON9g89bAy+p6bAzkE1gHNbE6+8t VviSroI3BBk1rxE7w0feBhoR+5+hHq2V2Hyb6QNbh8Q4dY/SoiY5ne5qjpbcUCKfhOX7 VGaW6jeRy0oqD+0rBEvT2IBmEKu4W1+YFFFBDjxCfhLr+4vkZpe3gQgXC4xThhMLR+65 VTyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708045548; x=1708650348; h=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=orTDpmGeJ87Kmuc6jHr3hnh69Lu4LnZgWzqnpNrswUA=; b=WOPqxZ6z86Bqtn1UVsjuH2arhOnSjiswzK3mzCK7OOvkXMfO7st4FSBoa5rGgOf+3P lnsLroA9wTZvYeu3DQixyi2x9oWDlbuzh5ihFCiF17g7G1kJ5TjbgD0v49+WChoIlobB BHVXy5SzLN3/TET4tJRcAOIERpGl080KBVTf5S067dpDhYCUXYHIuhAzZfgrIYap8LxD KyEvSA4Qld9o9h2X3/SzRXvMfd7ZS4Bnvakjal8CWai/y1N83ev1powtu3w41p8yRLQw xYyHLdghVHrNVypBPpU/xLdIXuxTHnr0CIys3tvk5dWZ0vk1IYsKsZTbGDWiwwdgCMV4 Hhlg==
X-Forwarded-Encrypted: i=1; AJvYcCVj3pnc99e7jAJ1Hj3h4OZJWX1pGYGSY7RJA3vj8b0+fyXb+bdbC2s92d+jUz+7oV1CuVtrmy5ldoBqSxxHqs6BH/n7MrnlmC7+NeH2cppmF41nMexdYl+GjC+22lG7bO672uU/U4nTkttgIjZurxMyAFW6Uut+ZrpjeiebHMDwoo5GGb7Xbnke
X-Gm-Message-State: AOJu0Yz0r/zAxc41YRrOl+ePZTHB7xxHZwc7blpSzR5Yih66len+MR3u DIBE1StrMlwySxp4zEUYAwxTy5TF6KugJKthax/8HR9tRg4jju0W+DRQlZrKba/wS9wSy3ptYFm 2B+WMbndf/eKiB4YjQVU0a3crABko8myHOtM=
X-Google-Smtp-Source: AGHT+IE3TfbBwSruw28OCDk4aMl7kIbUpKK+LVu1mLuHpZiHpuLXYwzOGQ5/Ec+GjyEW5y7uoVlOlAdx4OZoFGsOlPs=
X-Received: by 2002:adf:e542:0:b0:33b:7b43:4ea4 with SMTP id z2-20020adfe542000000b0033b7b434ea4mr2245297wrm.28.1708045547369; Thu, 15 Feb 2024 17:05:47 -0800 (PST)
MIME-Version: 1.0
References: <170753393187.36817.12725850532997691597@ietfa.amsl.com> <0100018d9ebe5603-4201597f-dbb2-4c63-ba32-f94da0979463-000000@email.amazonses.com>
In-Reply-To: <0100018d9ebe5603-4201597f-dbb2-4c63-ba32-f94da0979463-000000@email.amazonses.com>
From: Shivan Kaul Sahib <shivankaulsahib@gmail.com>
Date: Thu, 15 Feb 2024 17:05:11 -0800
Message-ID: <CAG3f7Mg-HkQPkV4w=kwSfpk8u8cbQbJU+61tpoZSTxC_JMWgzw@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: secdir@ietf.org, draft-ietf-netconf-http-client-server.all@ietf.org, last-call@ietf.org, "netconf@ietf.org" <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001c7a1d0611755892"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/_ReTZyqlg_4uDFhM2TU74FyMujI>
Subject: Re: [netconf] Secdir last call review of draft-ietf-netconf-http-client-server-16
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 16 Feb 2024 01:05:53 -0000

On Mon, 12 Feb 2024 at 11:14, Kent Watsen <kent+ietf@watsen.net> wrote:

> Hi Shivan,
>
> Thank you for your review!
> Responses below.
>
> Kent
>
>
> On Feb 9, 2024, at 9:58 PM, Shivan Sahib via Datatracker <noreply@ietf.org>
> wrote:
>
> Reviewer: Shivan Sahib
> Review result: Has Nits
>
> It looks like the document previously got review from HTTP WG, and
> generally
> looks well thought out.
>
>
> Thanks.
>
>
> However, I'm not sure why only TCP and TLS are discussed in
>
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-http-client-server-16#section-2.1.2.2
> .
> Is the intention that network protocols like QUIC can be "augmented" in?
>
>
> This document doesn’t support QUIC (yet).
> The document’s title is “YANG Groupings for HTTP 1.1/2.0 Clients and HTTP
> Servers”.
>
>
> Everybody wants this document to support QUIC.
> Doing this would entail a new document called “quic-client-server”.
>

> Do you know if there are any quic-specific configurations, beyond
> the basic UDP local/remote/ address/port config?
> - for either the client or the server?
>

I guess a broader question I had (non-blocking security wise) is who is
looking to deploy this document? Are those parties not interested in QUIC?


>
>
>
> I suspected that, but in that case, it should be mentioned the same way
> Basic
> auth is explicitly mentioned to be only one of the ways auth can happen
> with a
> MAY for other schemes:
>
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-http-client-server-16#section-2.1.2.1-4.4
>
>
> I just added the following sentence to that section:
>
>      The "proxy-connect" node defines support for HTTP 1.1 and HTTP 2.0.
> Support
>      for other protocols versions, e.g., HTTP/3, MAY be augmented in via
> future work.
>

s/protocols/protocol, but lgtm otherwise.

>
>
> Thanks again!
> Kent
>
>

v2.23.0 | Report a Bug | By Email