IETF Logo Mail Archive

Re: [nfsv4] IETF 107 Agendas needed in early March

David Noveck <davenoveck@gmail.com> Fri, 14 February 2020 10:19 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 70894120289 for <nfsv4@ietfa.amsl.com>; Fri, 14 Feb 2020 02:19:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 v5WC6qw1fU7v for <nfsv4@ietfa.amsl.com>; Fri, 14 Feb 2020 02:19:37 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 4E6C71200A3 for <nfsv4@ietf.org>; Fri, 14 Feb 2020 02:19:37 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id c26so10574185eds.8 for <nfsv4@ietf.org>; Fri, 14 Feb 2020 02:19:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2UdPQTL7+rTXFrn1oUXGu5rKCpJOyX4yqsd7hVY+6dw=; b=I5k584Bkf0Bk8jqMuC5Ge2wMmJdDKSlw3zHcETReKVIt5nZ8NhGrfugJuPFdJkZo1G UA7SQ5+uXrkFTLETPC42oa1fhdUajYNiW51KrlMinWtMnaNhA5EyGbf+6sG7GQRqDLTE vi1dmOAEFenBbHwwdirAUE2GhfQzMq38P+cX5Kz20R2lloYBharhlpm+WF9ulvsvSdde zdZ2/UzoGhwybOXNIRRx3dl89BuHYtmC0lLlSF+qec/mIhSE9n7Pf9SzViA4Sts9k+wV dCvLcUKzWPi6hXdruAhj4A1Hq7y3aUV2Bz2MSb+jpb5BcBGpcS/6LHEFP8ljA/11o4pt ZSRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2UdPQTL7+rTXFrn1oUXGu5rKCpJOyX4yqsd7hVY+6dw=; b=UaitBKIuTQg8FEZKDBAe8AgYtEWR2b0i9aUXxscivdDfpvdlLOiGpyLTSGfFHvFCXQ 630l64qnRHx9edldowwbTkP/aSRrIth+JkjOSlfY4nF0vFimYunEVM9t99eU2OKvd7wj dR+NYWtQDQQIqGOIBDaWhxYwkBBwQ1L0sY6RnqHdxm50WSnEHTYqwFZtKHph+LauQSa+ CHmmu6Dmu/m+E2B89SbmtYrrNBtarL7Sgi5MDqs/M5QD3LhTDlFxcw02iip2FgHCQDwA sxK/RPvdb9IlvnCE1NsPDlV4fD0i+fGhu04mfi8J9Gfn0UOfbR7ksYEI9nYT9ukVcrPI 8MpQ==
X-Gm-Message-State: APjAAAWh/X26aE/5ZUYwGPGe0y4AlXico5xUrtE6PNMCEcNZ5U5TDvN3 vgw+2LvJCNCwrODcK+ISxWhHKoNxqHA4sLUV894=
X-Google-Smtp-Source: APXvYqyCqTcZlUcZpaKSx74Fzf0PWqT46lp6FEQrTEQVBxsgL57NF4S1qaYHd69Ta1U+5z3isjYgxBwHlP0ZorXoBUw=
X-Received: by 2002:a17:906:2799:: with SMTP id j25mr2341547ejc.216.1581675575605; Fri, 14 Feb 2020 02:19:35 -0800 (PST)
MIME-Version: 1.0
References: <CADaq8jc=QosG5T+DRT4m9XjbVm8qMvKdYk5GzZmvFhhdtaVCTg@mail.gmail.com> <47FFE1B7-6DAE-4B33-B4BF-A417A68A020F@oracle.com>
In-Reply-To: <47FFE1B7-6DAE-4B33-B4BF-A417A68A020F@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Fri, 14 Feb 2020 05:19:24 -0500
Message-ID: <CADaq8jdeQfOpmU=sC9T1bzwQ0bzARsHnC=KKw21LQcb8KXD-ow@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d57e80059e868a7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/286QMX3SF7-y2I7UNilKaTu9hcE>
Subject: Re: [nfsv4] IETF 107 Agendas needed in early March
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: Fri, 14 Feb 2020 10:19:39 -0000

On Thu, Feb 13, 2020, 4:28 PM Chuck Lever <chuck.lever@oracle.com> wrote:

> Hi Dave-
>
> > On Feb 10, 2020, at 12:17 PM, David Noveck <davenoveck@gmail.com> wrote:
>
> Mentioning this again: As rpcrdma-version-two is a current WG milestone, is
> there a need to discuss that document and/or draft-ietf-nfsv4-nfs-ulb-v2
> during the first session?
>

Yes there is.  Somehow I screwed up and dropped this. Is ten minutes ok?


> Missing from the second session, and perhaps more important than either
> computational storage or document review is a discussion of future RPC
> transports.
>

Agree with regard to computational storage but would like to keep the
document review discussion.  Do you have time to lead that discussion and
address future RPC transports issues as well?


>  - RPC-on-TLS: possible support for enabling user certs or EAP
>

Personally, I'd be OK putting this off but I sense that others feel
differently. It makes sense to have the discussion.

 - RPC-on-QUIC: after basic RPC-on-TLS is published, where to begin
>

I think we need to set expectations/priorities about this.

 - RPC-on-MPTCP: are there any standards actions required to support it?
>

It would help to get clarity on this, so that those interested in
prototyping know what their path forward is.


> Is there other work in this area?


I don't know.

Do we want to set this topic aside until
> there is an Internet-Draft.
>

No.  I think we need a discussion of what specification work and prototype
work it makes sense to do in the future

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

v2.23.0 | Report a Bug | By Email