Re: [nfsv4] Agenda items for virtual interim

David Noveck <davenoveck@gmail.com> Sun, 17 October 2021 02:26 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 2DB6F3A0866 for <nfsv4@ietfa.amsl.com>; Sat, 16 Oct 2021 19:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjS5uWVzZudB for <nfsv4@ietfa.amsl.com>; Sat, 16 Oct 2021 19:26:23 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D43813A0863 for <nfsv4@ietf.org>; Sat, 16 Oct 2021 19:26:22 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id t16so55046725eds.9 for <nfsv4@ietf.org>; Sat, 16 Oct 2021 19:26:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7Ylht8RiPO0HPUKk0hMMBLpRrQQvQpOigFXR5okhMw8=; b=abRfg6A63tLwEUOe0yHcFK6aIdX2CX5nJNrkdTBftcU6BFjN3g7ga9zFkwDIwLkSm4 +7kJ8XjigDPZS0pDIxemQHA9ZUC4qeKwcA8K5dQYpzThBq2HnJp8m+MLFKqF1wDsY+Cz FHbvKJ86xEOnT7dpyoEenGegMFyjW/5UAMcnX2QYn0uZcnbjg/eTnnYJUFImUYsPUx51 uSz8uLcBrfdzeFZ3AXI3GLOBBOn8fbmTRoPWhWfZy4oWNigVJaM5TqsSo14MqtNH0gs9 wNFedPw3dWoYk/La7aOkMYN+pVKe5EexB4yQHp1bYObEb2P0t32rX5y0TRzM5ytAfxiI Ifnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7Ylht8RiPO0HPUKk0hMMBLpRrQQvQpOigFXR5okhMw8=; b=eOuG3AsdBx+PxfFnEGKslNN2KRC1fd8txXTASzlkb0NS13aPj+TGurgLCywRkGcAqF 7QsLNKOSZuahytgKb0MYFu8/vw235QPCpC9kkfafV5t6RDcMCL5sIJHk5K41lu12aVQQ jo0veKxAOvQh4AAWFIpcGPhCzNczxUN0EgPJ/BL/Lwhs2O43/FK0rI9rOoh67l2pmRgk 14OnfbOxi2ZIUHHo9bw/kvHVNDdOTOJkona5KO8C8pIn/A+YqTKigLwVhgq5rqmdE+O4 tRRY/mpvNC9dIpY7dkjk/CxAzcn7VAuJhuHJ1FovuVYxQ0jD46ZjMHBn6D89BXIi30jE Z9Xw==
X-Gm-Message-State: AOAM532EcB2MyJyDHNw27vHWIxxJcT9dyoVszxHRY4DpxnqNIPeTayiL HATTCt41BgIPdDp/3itrXfWeI5M2giM95aHmliQ=
X-Google-Smtp-Source: ABdhPJzZyTFhEGqykqc0HM3DmjJMHkj3XlcdEs7tZ7BPl/R7NRDYFo9/A6UEHBqmdwjWdTJ9VPN5yrlCzF8uOtKOolQ=
X-Received: by 2002:a50:99c6:: with SMTP id n6mr31038508edb.171.1634437579551; Sat, 16 Oct 2021 19:26:19 -0700 (PDT)
MIME-Version: 1.0
References: <CADaq8jd_pcwJrqnFCqnHo7DXxnzc+ZpL28wRUMqkK-3zesc6mg@mail.gmail.com> <7560301C-4C5C-422C-9F55-B4F362AE5BF7@oracle.com>
In-Reply-To: <7560301C-4C5C-422C-9F55-B4F362AE5BF7@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Sat, 16 Oct 2021 22:26:10 -0400
Message-ID: <CADaq8je9MWT5CzLaTYnRgMh5x9+AHL8F78QxJs_YyGSR67F6nQ@mail.gmail.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Tom Talpey <tom@talpey.com>, Tom Haynes <loghyr@gmail.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000056371c05ce83272e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ml6XCxlT-Ijip0ZIvXTEvK2bnIg>
Subject: Re: [nfsv4] Agenda items for virtual interim
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 17 Oct 2021 02:26:30 -0000

On Sat, Oct 16, 2021, 5:25 PM Chuck Lever III <chuck.lever@oracle.com>
wrote:

>
>
> > On Oct 16, 2021, at 9:28 AM, David Noveck <davenoveck@gmail.com> wrote:
> >
> > I'd be interested in hearing from Chuck about his thoughts about
> addressing use of RPC-with-TLS for NFSv3 and how that might or might not
> interact with the v4 security work now going on.
>
> I haven't had a chance to read nfsv4-security yet. That is at
> the top of my to-do list.
>

It's 118 pages so it would be best to start soon.


> After that, I think I'd like to huddle with Rick to discuss
> how NFSv3 should work. Once we have something, we can present
> options or discuss it on the mailing list.
>
> In short, I agree this is something that needs to be discussed
> at some point, but I'm not confident I'll be ready by Oct 27.
> I'd prefer to see some discussion on list about this before
> we bring it to a WG meeting.
>

I think I should publish an agenda by 10/20 so let me know by then if you
have an item to present.  I can specify a period of general discussion for
miscellaneous items


> (Given the limited degree of interactivity available during a
> virtual meeting,


I don't think we will face the interactivity issues that we saw with
meetecho, given that we will use WebEx.

I'd say we should consider restricting the
> agenda to slides plus a couple of executive WG decisions for
> each chosen topic, at least until the virtual meeting
> technology improves).
>

I don't see all that many decisions being made anyway..  in any case, any
decisions made have to be confirmed on the list.

This is not really a technology issue.  I don't remember large numbers of
decisions being made when we were meeting with everybody in the same room.

>
>
> > I also want to hear from Tom T about a number of RDMA-related topics:
> >       • His 'push-mode" work.
> >       • Possible approaches to a secure RDMA protocol taking advantage
> of either TLS or Quic.
>
> This might not be a popular opinion, but DDP/MPA over QUIC in
> my opinion would be a more straightforward option than plumbing
> a bespoke authentication protocol into RPC/RDMA.


It's not unpopular with me.  If you want to avoid the work of putting
authentication into RPC/RDMA v2 by talking this approach, I'm OK with it
but you might want to send a message to the wg list to inform the group
about this decision.

A transport
> level approach could also help resolve the authentication issues
> that came up last time we considered a pNFS/RDMA layout type.
>

As I recall things, the issues we were dealing with were related to ofed's
approach to authorization rather than being due to authentication issues
per se.

>
>
> --
> Chuck Lever
>
>
>
>