Re: I-D Action: draft-ietf-nfsv4-rpc-tls-04.txt

Hi Spencer-

> On Nov 17, 2019, at 1:59 PM, [email protected] wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network File System Version 4 WG of the IETF.
> 
>        Title           : Towards Remote Procedure Call Encryption By Default
>        Authors         : Trond Myklebust
>                          Charles Lever
> 	Filename        : draft-ietf-nfsv4-rpc-tls-04.txt
> 	Pages           : 20
> 	Date            : 2019-11-17
> 
> Abstract:
>   This document describes a mechanism that, through the use of
>   opportunistic Transport Layer Security (TLS), enables encryption of
>   in-transit Remote Procedure Call (RPC) transactions while
>   interoperating with ONC RPC implementations that do not support this
>   mechanism.  This document updates RFC 5531.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rpc-tls/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-nfsv4-rpc-tls-04
> https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-rpc-tls-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-rpc-tls-04
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/

Revision 04 of draft-ietf-nfsv4-rpc-tls addresses changes requested
during the second early SecDir review. There might be a few more minor
security-related tweaks needed. The Security Directorate plans to
assign this document to Derrell Piper for the official SecDir review,
at which time we can take care of any remaining issues.

Therefore I'd like to request WGLC for this document. Please schedule
this for whenever is convenient for the Working Group. Thanks!

I also note that during IETF 105, the members present agreed that this
work should be documented as a Charter milestone. The nfsv4 Charter has
yet to reflect this change.


--
Chuck Lever



_______________________________________________
nfsv4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nfsv4