Last Call Review of draft-ietf-nfsv4-minorversion2-39
review-ietf-nfsv4-minorversion2-39-secdir-lc-kelly-2015-12-03-00
| Request | Review of | draft-ietf-nfsv4-minorversion2 |
|---|---|---|
| Requested rev. | no specific revision (document currently at 41) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2015-12-09 | |
| Requested | 2015-11-26 | |
| Authors | Thomas Haynes | |
| Draft last updated | 2015-12-03 | |
| Completed reviews |
Genart Last Call review of -39 by Elwyn Davies
(diff)
Genart Telechat review of -40 by Elwyn Davies (diff) Secdir Last Call review of -39 by Scott Kelly (diff) Opsdir Last Call review of -39 by Sheng Jiang (diff) |
|
| Assignment | Reviewer | Scott Kelly |
| State | Completed | |
| Review | review-ietf-nfsv4-minorversion2-39-secdir-lc-kelly-2015-12-03 | |
| Reviewed rev. | 39 (document currently at 41) | |
| Review result | Ready | |
| Review completed: | 2015-12-03 |
Review
review-ietf-nfsv4-minorversion2-39-secdir-lc-kelly-2015-12-03
I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This doc describes minor version 2 updates to NFSv4. There are 6 new operations/features supported: Server Side Copy, Application I/O Advise, Space Reservations, Sparse Files, Application Data Blocks, and Labeled NFS. Consistent with other NFS docs, security considerations specific to an operation are described in the section for that operation. Server Side Copy and Labeled NFS each contain their own sub-sections. The main security considerations section states that this revision has all the security considerations of NFS version 4.1 (referencing RFC5661), and also refers to the feature-specific discussions in previous sections. I didn't find any issues not already addressed by the security considerations in this and referenced docs. --Scott