Late Last Call + Gen-ART review of draft-ietf-nfsv4-rfc1831bis-10
Christian Vogt <christian.vogt@ericsson.com> Thu, 11 December 2008 13:17 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 525D93A67F4; Thu, 11 Dec 2008 05:17:06 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C50F13A6A4D; Thu, 11 Dec 2008 05:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level:
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iwa3jmX5gXVd; Thu, 11 Dec 2008 05:17:03 -0800 (PST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 7A4953A67F4; Thu, 11 Dec 2008 05:17:03 -0800 (PST)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 8218F21F28; Thu, 11 Dec 2008 14:16:56 +0100 (CET)
X-AuditID: c1b4fb3c-aa757bb00000304c-aa-494112c84e74
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 710C621F9C; Thu, 11 Dec 2008 14:16:56 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Dec 2008 14:15:51 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 11 Dec 2008 14:15:31 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id EA1AC227A; Thu, 11 Dec 2008 15:15:30 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A4C2E4DAAA; Thu, 11 Dec 2008 15:15:30 +0200 (EET)
Message-Id: <F76BA305-C2EB-438D-BF0C-040689F1B732@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Late Last Call + Gen-ART review of draft-ietf-nfsv4-rfc1831bis-10
Date: Thu, 11 Dec 2008 15:15:30 +0200
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 11 Dec 2008 13:15:31.0181 (UTC) FILETIME=[8AFAB9D0:01C95B92]
X-Brightmail-Tracker: AAAAAA==
Cc: Gen-ART Mailing List <gen-art@ietf.org>, robert.thurlow@sun.com, nfsv4-ads@tools.ietf.org, nfsv4-chairs@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document..........: draft-ietf-nfsv4-rfc1831bis-10 Reviewer..........: Christian Vogt Review date.......: December 11, 2008 IESG Telechat date: December 11, 2008 Summary: This draft is basically ready for publication, but has nits that should be fixed before publication. Document draft-ietf-nfsv4-rfc1831bis-10 is an update of the "Remote Procedure Call Protocol Specification Version 2", RFC 1831. It seeks to promote the RPC protocol to draft standard. The document is overall in good quality. However, one aspect where I found the document to be insufficient is in the specification of security methods. The documents does list possible security methods, but it neither specifies them, nor does it state a mandatory-to-support method other than null-authentication. I am aware that the predecessor document, RFC 1831 also did not attend to security methods any more carefully. But the security-related requirements for IETF documents have become stricter since the publication of the predecessor document in 1995, which implies that this document would need to pay more attention to security-related aspects. Suggestion: Could the list of possible security methods (alias "security flavors") be limited to those for which there are clear protocol specifications? E.g., one of the possible methods, AUTH_DH, currently refers to an academic publication rather than a protocol specification. That's insufficient. And could one of the non-null security methods be made mandatory? - Christian _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Late Last Call + Gen-ART review of draft-ietf-nfs… Christian Vogt
- Re: Late Last Call + Gen-ART review of draft-ietf… Robert Thurlow