Re: [nfsv4] I-D Action: draft-ietf-nfsv4-integrity-measurement-01.txt

[Chuck Lever <[e-mail]>]

> On Sep 24, 2018, at 8:45 AM, Spencer Dawkins at IETF <[e-mail]> wrote:
> 
> Hi, Chuck, 
>> On Mon, Sep 24, 2018 at 10:06 AM Chuck Lever <[e-mail]> wrote:
>> 
>> 
>> > On Sep 24, 2018, at 7:55 AM, [e-mail] 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           : File Content Provenance for Network File System version 4
>> >        Author          : Charles Lever
>> >       Filename        : draft-ietf-nfsv4-integrity-measurement-01.txt
>> >       Pages           : 9
>> >       Date            : 2018-09-24
>> > 
>> > Abstract:
>> >   This document specifies an OPTIONAL extension to NFS version 4 minor
>> >   version 2 that enables file provenance information to be conveyed
>> >   between NFS version 4.2 servers and clients.  File provenance
>> >   information authenticates the creator of a file's content and helps
>> >   guarantee the content's integrity from creation to use.
>> > 
>> > 
>> > The IETF datatracker status page for this draft is:
>> > https://datatracker.ietf.org/doc/draft-ietf-nfsv4-integrity-measurement/
>> > 
>> > There are also htmlized versions available at:
>> > https://tools.ietf.org/html/draft-ietf-nfsv4-integrity-measurement-01
>> > https://datatracker.ietf.org/doc/html/draft-ietf-nfsv4-integrity-measurement-01
>> > 
>> > A diff from the previous version is available at:
>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-integrity-measurement-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/
>> 
>> As a result of the discussion at IETF 102 and recent follow-ups
>> on this mailing list, I've made substantial changes to this
>> document.
>> 
>> - References to and discussion of Linux IMA have been replaced
>> throughout the document, with the exception of a single citation
>> as an informative example in the Introduction. IMA metadata is
>> now referred to generically using the term "file provenance
>> information".
>> 
>> - Integrity checking of file attributes is no longer an included
>> feature. There were some issues that made attribute integrity
>> not straightforward for NFS, especially without an existing
>> IMA/EVM standard even for local file systems. Attribute
>> integrity can still be addressed at a later time.
>> 
>> - The Introduction now makes a problem statement and discusses
>> use cases instead of explaining the mechanism of file integrity
>> checking. The new Introduction addresses the most common
>> questions I've received during previous review.
>> 
>> Spencer D. and other reviewers:
>> - Have previously stated interoperability concerns been addressed?
>> - Have normative citation requirements been sufficiently met?
> 
> Recognizing that I haven't done an AD Evaluation of this draft, but looking at the responses to my previous questions, I think dropping down to one explicit mention of IMA pointing to the best available reference is about right. 
> 
> Thanks for making that change. It will be helpful during Last Call and IESG Evaluation.

Thanks for the quick response!


> Spencer (D)
>  
> 
>> I know time is precious, but even a cursory review of this new
>> revision would be helpful. It's wafer-thin!
>> 
>> --
>> Chuck Lever

--
Chuck Lever