Re: [nfsv4] WG adoption of draft-dnoveck-nfsv4-security

David Noveck <davenoveck@gmail.com> Mon, 08 January 2024 14:53 UTC

Return-Path: <davenoveck@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B303C15107E; Mon, 8 Jan 2024 06:53:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 dTfEK0rdV0wA; Mon, 8 Jan 2024 06:53:20 -0800 (PST)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 5F76CC14F706; Mon, 8 Jan 2024 06:53:20 -0800 (PST)
Received: by mail-qk1-x733.google.com with SMTP id af79cd13be357-783253c2182so60205785a.3; Mon, 08 Jan 2024 06:53:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704725599; x=1705330399; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=YP3EUAqQs4LZmuNsAcdcU/WFaWgV+c6bVBvz6dXZjN8=; b=Dqn8hF4Ox8xyqT5R481irbJZNcTlXNllguYShVQa6WJaYTBT+8bsg9HGiuKAYXrsaH GHvcWHev4JLwBx1N0KLR90XZIm524jWyhHmW41tO90RqGFJHiAy73mBw/SAbqWg4KtDN RtsVc14yMwhjc40o/tz8rodjSK52URvqxc50dhJsqL3vY8Ui1xlrpYZ7LskWm0e+xDVp kvWlvxv/FJ48AEJ9pOEFkJMlXJqtc3+XQZpHc7fN7NaKh8hgk4BsZGfoodkNNC7Z8Ona j5qKKLqF9MwF6sh+kqeBlYgQzqbw6BB094kDPFMOenop9csNxHPzX7RsNdVZngJ9KZYZ mPPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704725599; x=1705330399; h=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=YP3EUAqQs4LZmuNsAcdcU/WFaWgV+c6bVBvz6dXZjN8=; b=SFmDmKn3nZ2iSYkzq2XwcND5gFe1MOMUG1Zbca/Iz0i/b3T93kOoYdvgcQqzhMx8BI EKLvr+hwLpY3XGITYjOAyPM89OfXIjmbVHz6J0aa0ILaXCPbtGyBz+GiozOu5hBRFaDu hjplHxkJxMj57B9SKtO5pQ2fVKiojzgKBGoC4SQk0QpaCRETHdDOiazOoJJLNWM5LxQn 54ZBP+PYim1JJxnjmaLVGocDIkn1Nk6CLKMGJ6fq+L3rbwaF/ZT+if40RTW2JXNbmrVU CGj/TRJBl2zonvtkgHFsbzCfhwIlDEwoPnPSkp9IzUtQ/lbBFQ5mIJhE4iH2v72qF03+ liUQ==
X-Gm-Message-State: AOJu0YyVV0T68gNvSKSpOg98e22pdtaxTf2dcfoxAU+Puu7wwMLt3uty AoVAkRdINBiIaDRgLXOr8+gdkPeIsfhO2/8GA9NxZ+HH
X-Google-Smtp-Source: AGHT+IHazygGeJCELq4s6FrlyRYfWv5qg8OC4DLXOl5qkVKUIJhBIG5/Wx/gUtnRKfDllc5NVkFmA1KqreLJNjgTp3k=
X-Received: by 2002:ad4:4f28:0:b0:67f:9341:76c1 with SMTP id fc8-20020ad44f28000000b0067f934176c1mr3902255qvb.118.1704725598990; Mon, 08 Jan 2024 06:53:18 -0800 (PST)
MIME-Version: 1.0
References: <CADaq8jeJR5+qgN+QkD3E8ZSryz0UypLB7uwCfFTR-b7gZjOcBA@mail.gmail.com>
In-Reply-To: <CADaq8jeJR5+qgN+QkD3E8ZSryz0UypLB7uwCfFTR-b7gZjOcBA@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 08 Jan 2024 09:53:07 -0500
Message-ID: <CADaq8je0jGV=NQGxui6kSA9z4KUgLYb0MQWXP_ahL5Lw8=symA@mail.gmail.com>
To: nfsv4-chairs <nfsv4-chairs@ietf.org>, Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c476ec060e705b10"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/cxO1D1ddB_SeLfR7K_X7ICwAnig>
Subject: Re: [nfsv4] WG adoption of draft-dnoveck-nfsv4-security
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2024 14:53:22 -0000

Although Gmail thinks that this a reply, it is actually a follow-up for my
request sent on 12/20/2023. So there is no issue of me replying to myself
and no issue of multiple personality syndrome to worry about :-)

I had originally hoped that the three weeks to the next wg interim meeting
would give us time to complete a two-week comment period and allow us to
resolve this long-deferred matter at the 1/16 interim meeting.  Given the
time that has already elapsed, that no longer seems possible. Sigh!

I have received no updates regarding this request.  If there are
impediments that would delay prompt work on this request, I need whoever is
dealing with this request to let me know about the issue so that it can get
addressed.

If that is not possible, we will have to address the matter at the 1/16
interim meeting.  Given what happened with the original request to adopt
-06, I don't think that we can again simply wait passively and hope that
one of the chairs is taking care of this matter.  It makes more sense for
me and whichever chair takes responsibility for this to discuss the next
steps at this and subsequent interim meetings, allowing us  to make sure we
have process  that leads to a prompt resolution of this matter.

On Wed, Dec 20, 2023, 5:23 AM David Noveck <davenoveck@gmail.com> wrote:

> I would like to formally request that the working group adopt this
> document, currently at its -07 draft, as a working group document.
>
> I suggest that the working group be asked for its comments as soon as
> possible. Given that the next interim meeting is scheduled for 1/16, this
> should allow a two-week period for comments  plus time to summarise the
> results and present a decision at the interim meeting.  This will give us
> an opportunity to formulate a plan of action, whatever the decision is.  I
> don't think we can afford a repeat of the situation with the previous
> adoption call in which there was uncertainty about the precise contours of
> the working group's response and a consequent delay as the draft whose
> adoption was request ceased to be relevant.
>
> One important point regarding the adoption call is that we need to clearly
> distinguish issues with the precise contents of the draft, which could be
> addressed after adoption from feelings, if they exist,, that the
> current draft is not a suitable vehicle in its current form , for the
> working group to address  NFSv4 security issues.  If the latter, we need to
> understand what changes might be required, so those changes cab made,
> allowing the working group to continue to make progress.
>