Re: [nfsv4] Interim meeting for nfsv4 working group

Benjamin Kaduk <kaduk@mit.edu> Sat, 05 December 2020 04:31 UTC

Return-Path: <kaduk@mit.edu>
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 BBE993A09E7; Fri, 4 Dec 2020 20:31:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lDfjIg4M3BTd; Fri, 4 Dec 2020 20:31:05 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CC153A09E1; Fri, 4 Dec 2020 20:31:04 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0B54Ut8a028703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 4 Dec 2020 23:31:00 -0500
Date: Fri, 04 Dec 2020 20:30:54 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: David Noveck <davenoveck@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>, nfsv4-chairs <nfsv4-chairs@ietf.org>, "nfsv4-ads@ietf.org" <nfsv4-ads@ietf.org>
Message-ID: <20201205043054.GW64351@kduck.mit.edu>
References: <CADaq8jf9BqwbUpy2atq-jzBVfW8xYDBAsFX65DbjL_Xn8kHRdw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADaq8jf9BqwbUpy2atq-jzBVfW8xYDBAsFX65DbjL_Xn8kHRdw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/WXnUI9A9arollX6z8NM3fIbZOkk>
Subject: Re: [nfsv4] Interim meeting for nfsv4 working group
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: Sat, 05 Dec 2020 04:31:07 -0000

On Fri, Dec 04, 2020 at 03:43:46PM -0500, David Noveck wrote:
> 
> I have the following areas in mind for discussion of the meeting:
[...]
>    - Discussion of the next steps for security,given where rpc-tls is
>    (approved but not an RPC for a while).   I'm hoping that Chuck will present.

It looks like rpc-tls is in MISSINGREF due to three drafts, all of which
I'm responsible AD for:

- draft-ietf-kitten-tls-channel-bindings-for-tls13 is still in the WG but
  as of the -01 should be pretty much done; we're just looking for a couple
  more reviews (and I have some arms I can twist)
- draft-ietf-tls-dtls-connection-id will go to IETF LC once
  https://github.com/tlswg/dtls-conn-id/pull/77 is merged, and it's
  currently in the "give WG members a chance to object" stage
- draft-ietf-tls-dtls13 is waiting for a revised I-D in response to my AD
  evaluation comments.  It's been a couple weeks since we heard from the
  author about it, so I will ask for an update.

-Ben