Re: [nfsv4] IETF 105 - Montreal - NFSv4 WG meeting ?

David Noveck <davenoveck@gmail.com> Thu, 25 April 2019 22:35 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 358821200C5 for <nfsv4@ietfa.amsl.com>; Thu, 25 Apr 2019 15:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_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 fb9aNdCQmjs1 for <nfsv4@ietfa.amsl.com>; Thu, 25 Apr 2019 15:35:28 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 6E7CE12008A for <nfsv4@ietf.org>; Thu, 25 Apr 2019 15:35:28 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id k6so1418911oic.4 for <nfsv4@ietf.org>; Thu, 25 Apr 2019 15:35:28 -0700 (PDT)
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=o2rTt7gEfaRlbgk/cj9vpYWmJCGKsehvqjn2J90HYIQ=; b=BRY/1UsX21+8ugmtROlQAen2601dJ9lYSJn8sOcLubZ6TkziWkE6kPZD/9BDzJgLYh P4C4CQnL+Bz8uQdwpoqTFNgbwMDkbPIyXJQEfhgVsR/+ZaKlXKSVjy1FqX+dsTPrCw6g fuShvIA53i6EBpPMwUeScJh9WkywzXQIBHcpo3sM1ij/tEtx0wqoeeOME52PsnQB1ryu n/LE/dg4aEPGUTvdquZbIilxzs4RlAjO5bOS3FXgFjIRv3HokHEUcu53CyTcs9D6KvDu VHrD1CHBPyVj1tfok2cSeiXWyflCiXGaiA+5GEhp46o4onYFng5xWf7HcNCEtqbTAS/P UkPA==
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=o2rTt7gEfaRlbgk/cj9vpYWmJCGKsehvqjn2J90HYIQ=; b=dh4PpzxrTqd7uwlV0bhA5XXef/sbE2Ss65j8mAzvLNePqEmYBvPBM7/0uLGRFF8FEb jS+NxxVhGXa3YDjajqoUrOLZUvGfmi6MpLSL1nEQTa6rTlrlp3DSGYauCS66x3kLtgRN pa0BAcn0fMlEULBcIfRwDRhK/Eik6Tm/1pDo6HjoxplauGReaquJL85fJfs5xzsFcItF Bs4UajglqjUOHDVRNe6+dz7dP8qzjYvhYnPVzTUT2/wissWnacTQMqA7q2IasZBDb9xP +3JKJOzVQzrOKyH64bnl/bZQk5fbvdu2gsRXXVyaohaFYIyKenmeeT9kbZGFsV6iYrSB RM5A==
X-Gm-Message-State: APjAAAUDAN7fze0Rr79B/xb4ldMxSg8DIMcJJjAdbmFUDZCgCp2FVXKn GF0L0L+b1Wj76iTnncwt97o1uNXtd0K7+F6XlBY=
X-Google-Smtp-Source: APXvYqyTnLohzOivsu/rRG1zkWOn5PFpPP8GJmdkeb3E5YsCyh1ZtZUv+cL/CIDI29uwCShJf2T5G9EcoIQhHhv5NhU=
X-Received: by 2002:aca:5b85:: with SMTP id p127mr4855512oib.90.1556231727408; Thu, 25 Apr 2019 15:35:27 -0700 (PDT)
MIME-Version: 1.0
References: <CAFt6BakCHvOnMR5RaX59uXSga03VVskRwKVpg97CbFr+Pxiz9A@mail.gmail.com> <CADaq8jdaquKW0=jWB+H3BNbGTLVZTK=_TheN-gn52xrurn=yNw@mail.gmail.com> <056AA26B-0DBC-4E4C-AE09-C6C6CAC26D58@oracle.com>
In-Reply-To: <056AA26B-0DBC-4E4C-AE09-C6C6CAC26D58@oracle.com>
From: David Noveck <davenoveck@gmail.com>
Date: Thu, 25 Apr 2019 18:35:15 -0400
Message-ID: <CADaq8jcTwyJ+A-mpYjTxWVt5H8T41_UXiy8L4aN2ZotC8D6cDg@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: spencer shepler <spencer.shepler@gmail.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ced580587626f18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/BaHksV28WBFi3yeEgLcbDC-OwfE>
Subject: Re: [nfsv4] IETF 105 - Montreal - NFSv4 WG meeting ?
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: Thu, 25 Apr 2019 22:35:31 -0000

I agree that we should discuss integrity measurement face to face.  It
seems that some of the issues with this could go round  and round
indefinitely on the mailing list, without making much progress.

On Thu, Apr 25, 2019, 17:04 Chuck Lever <chuck.lever@oracle.com> wrote:

> From my list:
>
> - Milestone updates (fs_locations and related, RPC/RDMA)
> - Towards a set of Working Group github repositories
> - Improving the performance of NFS directory operations
> - An emerging Computational Storage architecture for NFS
> - Long-term strategies for RPC over encrypted transports
> - Replacing RFC 5661
> - Open issues with integrity measurement
>
> The directory performance and computational storage topics are
> not mature and can be considered low priority for this meeting.
>
> The others intersect with your suggestions except for the
> integrity measurement topic, which I would like to keep on the
> agenda for now.
>
>
> > On Apr 25, 2019, at 4:56 PM, David Noveck <davenoveck@gmail.com> wrote:
> >
> > I can't see us not meeting given that the last time we met was at
> IETF102 and that we are in the midst of major effort to move NFSv4 security
> from its current unsatisfactory state to something better.
> >
> > With regard to filling up a timeslot, I'll let Check and Trond (who, as
> I undertand it wil be working on a v4-specific document to go with Chuck's
> RPC-generic one) define their agenda items.
> >
> > With regard to my own needs, we will need to discuss work on a possible
> rfc5661bis.   It is now pretty clear that the IESG will want to see this.
> The only question is whether they will be OK with publishing
> rfc5661-msns-update soon.   Even if they are, there will be a need for an
> rfc5661bis that includes a new Security Considerations section (with a real
> threat analysis) and that will have to be co-ordinated with Trond and Chuck.
> >
> > I know Tom thinks I'm crazy to even consider this, but, so far as I
> know, there is no working group consensus on this point :-)
> >
> > Also, there are there are a number of documets with target dates in the
> second half of 2019., that we need to briefly discuss.  Given the securitty
> work  underway, I don't see any need to add any non-security milestones for
> 2020 right now.
> >
> >> On Thu, Apr 25, 2019 at 4:07 PM spencer shepler <
> spencer.shepler@gmail.com> wrote:
> >>
> >> The WG/BOF scheduling is open.
> >>
> >> Does the working group have the topics/agenda items necessary to meet
> face to face?
> >>
> >> Spencer
> >>
> >> _______________________________________________
> >> nfsv4 mailing list
> >> nfsv4@ietf.org
> >> https://www.ietf.org/mailman/listinfo/nfsv4
> > _______________________________________________
> > nfsv4 mailing list
> > nfsv4@ietf.org
> > https://www.ietf.org/mailman/listinfo/nfsv4
>
> --
> Chuck Lever
>
>
>
>