[nfsv4] Mirja Kühlewind's No Objection on draft-ietf-nfsv4-layout-types-10: (with COMMENT)

Mirja Kühlewind <ietf@kuehlewind.net> Fri, 13 April 2018 13:12 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-nfsv4-layout-types@ietf.org, nfsv4-chairs@ietf.org, spencer.shepler@gmail.com, nfsv4@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152362516302.26230.3528157123925353021.idtracker@ietfa.amsl.com>
Date: Fri, 13 Apr 2018 06:12:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/nKtGAuwXKjkFyNzsnCcfOGxnmoY>
Subject: [nfsv4] Mirja Kühlewind's No Objection on draft-ietf-nfsv4-layout-types-10: (with COMMENT)

Mirja Kühlewind has entered the following ballot position for
draft-ietf-nfsv4-layout-types-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-layout-types/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Please use RFC8174 boilerplate and maybe double-check the use of lower case
MUSTs and MAYs, e.g. should this sentence in the security considerations maybe
use an upper case MUST:

"The layout type specification must ensure that only data accesses
   consistent with the NFSV4.1 security model are allowed."

[nfsv4] Mirja Kühlewind's No Objection on draft-i… Mirja Kühlewind