[secdir] secdir review of draft-ietf-nfsv4-minorversion2-39

"Scott G. Kelly" <scott@hyperthought.com> Sun, 29 November 2015 15:10 UTC

Return-Path: <scott@hyperthought.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id D1D491B2A0C for <secdir@ietfa.amsl.com>; Sun, 29 Nov 2015 07:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1ipL4k_GKzDO for <secdir@ietfa.amsl.com>; Sun, 29 Nov 2015 07:10:50 -0800 (PST)
Received: from smtp66.iad3a.emailsrvr.com (smtp66.iad3a.emailsrvr.com []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E65791B2A0B for <secdir@ietf.org>; Sun, 29 Nov 2015 07:10:49 -0800 (PST)
Received: from smtp25.relay.iad3a.emailsrvr.com (localhost.localdomain []) by smtp25.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 00A89180383; Sun, 29 Nov 2015 10:10:48 -0500 (EST)
Received: from app22.wa-webapps.iad3a (relay-webapps.rsapps.net []) by smtp25.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id E4F0E18023D; Sun, 29 Nov 2015 10:10:48 -0500 (EST)
X-Sender-Id: scott@hyperthought.com
Received: from app22.wa-webapps.iad3a (relay-webapps.rsapps.net []) by (trex/5.5.4); Sun, 29 Nov 2015 10:10:48 -0500
Received: from hyperthought.com (localhost.localdomain []) by app22.wa-webapps.iad3a (Postfix) with ESMTP id D64F218006B; Sun, 29 Nov 2015 10:10:48 -0500 (EST)
Received: by apps.rackspace.com (Authenticated sender: scott@hyperthought.com, from: scott@hyperthought.com) with HTTP; Sun, 29 Nov 2015 07:10:48 -0800 (PST)
Date: Sun, 29 Nov 2015 07:10:48 -0800 (PST)
From: "Scott G. Kelly" <scott@hyperthought.com>
To: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, draft-ietf-nfsv4-minorversion2.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
X-Priority: 3 (Normal)
X-Type: plain
X-Auth-ID: scott@hyperthought.com
Message-ID: <1448809848.875230642@apps.rackspace.com>
X-Mailer: webmail/11.6.7-RC
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/GkMCsGvn9_-WSOD7QBrNuB_wKl4>
Subject: [secdir] secdir review of draft-ietf-nfsv4-minorversion2-39
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2015 15:10:51 -0000

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.