Re: [nfsv4] Fwd: New Version Notification for draft-cel-nfsv4-rpc-tls-01.txt

Hi Chuck et al.,

Thanks for pushing this forward!

One of the option that I would consider is an implicit TLS support on a
different port number without RPC NULL call handshake. Such
functionality will allow to simplify server implementation, where security
information have to be pushed down to server's internals to validate
desired security flavor, a-la sec=tls. In your proposal, after STARTTLS
client changes auth flavor to AUTH_SYS and sych validation will required
more internal changes to existing implementations. In addition, with the help
of stunnel, as was suggested in the this activity triggering article, old
clients will be able to talk `implicit TLS` servers (and wise versa).

Regards,
   Tigran.

----- Original Message -----
> From: "Chuck Lever" <chuck.lever@oracle.com>
> To: "NFSv4" <nfsv4@ietf.org>
> Sent: Monday, November 19, 2018 4:55:41 PM
> Subject: [nfsv4] Fwd: New Version Notification for draft-cel-nfsv4-rpc-tls-01.txt

> Hi-
> 
>> Begin forwarded message:
>> 
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for draft-cel-nfsv4-rpc-tls-01.txt
>> Date: November 19, 2018 at 10:52:07 AM EST
>> To: "Trond Myklebust" <trond.myklebust@hammerspace.com>, "Charles Lever"
>> <chuck.lever@oracle.com>, "Chuck Lever" <chuck.lever@oracle.com>
>> 
>> 
>> A new version of I-D, draft-cel-nfsv4-rpc-tls-01.txt
>> has been successfully submitted by Charles Lever and posted to the
>> IETF repository.
>> 
>> Name:		draft-cel-nfsv4-rpc-tls
>> Revision:	01
>> Title:		Remote Procedure Call Encryption By Default
>> Document date:	2018-11-19
>> Group:		Individual Submission
>> Pages:		9
>> URL:
>> https://www.ietf.org/internet-drafts/draft-cel-nfsv4-rpc-tls-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpc-tls/
>> Htmlized:       https://tools.ietf.org/html/draft-cel-nfsv4-rpc-tls-01
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-cel-nfsv4-rpc-tls
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-cel-nfsv4-rpc-tls-01
>> 
>> Abstract:
>>   This document describes a mechanism that enables encryption of in-
>>   transit Remote Procedure Call (RPC) transactions with little
>>   administrative overhead and full interoperation with RPC
>>   implementations that do not support this mechanism.  This document
>>   updates RFC 5531.
>> 
>> 
>> 
>> 
>> 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.
>> 
>> The IETF Secretariat
> 
> Minor changes in revision 01:
> - Correct a legal issue reported by idnits
> - Clarify terminology throughout document
> - Add editor's note in Section 4.3 "Authentication"
> - Wordsmithing throughout
> 
> 
> The immediate question I have is whether members of WG feel this
> topic and document are important enough to promote rpc-tls-01 to
> Working Group document status. If yes, I can submit the next
> revision as draft-ietf-nfsv4-rpc-tls-00.
> 
> 
> --
> Chuck Lever
> 
> 
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4