Re: [nfsv4] I-D Action: draft-ietf-nfsv4-rpc-tls-01.txt

OK, but use of the adverb "opportunistically" without TLS being mentioned
does add confusion.  How about:

This document describes a mechanism that, through the use of
opportunistic TLS, enables
encryption of in-transit Remote Procedure Call (RPC) transactions.
This is done with
minimal administrative overhead and full interoperation with ONC RPC
implementations that do not support this mechanism.  This document
updates RFC 5531.

On Tue, Apr 16, 2019 at 1:11 PM Chuck Lever <chuck.lever@oracle.com> wrote:

>
> > On Apr 16, 2019, at 1:09 PM, David Noveck <davenoveck@gmail.com> wrote:
> >
> > I'm confused by the addition of the word "opportunistically" in the
> abstract.   This document defines an important way of providing security to
> RPC-based protocols such as NFSv4, so as to deal with the very real
> security problemms that these protocols have.    While these facilities can
> only be used when both client and the server provides support, I don't
> think that fact alone make the use of these facilties "opportunistic".
> What exactlty is this word intended to imply?
>
> "Opportunistic" is a term of art. See:
>
> https://en.wikipedia.org/wiki/Opportunistic_TLS
>
>
> > On Mon, Apr 15, 2019 at 1:48 PM <internet-drafts@ietf.org> 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           : Remote Procedure Call Encryption By Default
> >         Authors         : Trond Myklebust
> >                           Charles Lever
> >         Filename        : draft-ietf-nfsv4-rpc-tls-01.txt
> >         Pages           : 17
> >         Date            : 2019-04-15
> >
> > Abstract:
> >    This document describes a mechanism that opportunistically enables
> >    encryption of in-transit Remote Procedure Call (RPC) transactions
> >    with minimal administrative overhead and full interoperation 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-01
> > https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-rpc-tls-01
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-rpc-tls-01
> >
> >
> > 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/
> >
> > _______________________________________________
> > nfsv4 mailing list
> > nfsv4@ietf.org
> > https://www.ietf.org/mailman/listinfo/nfsv4
>
> --
> Chuck Lever
>
>
>
>