[nfsv4] AD review: draft-ietf-nfsv4-nfsdirect-05
Lars Eggert <lars.eggert@nokia.com> Mon, 28 May 2007 14:03 UTC
Return-path: <nfsv4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hsfow-00018J-88; Mon, 28 May 2007 10:03:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hsfou-00014T-3D for nfsv4@ietf.org; Mon, 28 May 2007 10:03:36 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hsfos-0006tT-DP for nfsv4@ietf.org; Mon, 28 May 2007 10:03:36 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l4SE37Ui032690 for <nfsv4@ietf.org>; Mon, 28 May 2007 17:03:32 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 May 2007 17:02:49 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 28 May 2007 17:02:46 +0300
Received: from [172.21.37.17] (esdhcp03717.research.nokia.com [172.21.37.17]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l4SE2joF008591 for <nfsv4@ietf.org>; Mon, 28 May 2007 17:02:45 +0300
Mime-Version: 1.0 (Apple Message framework v752.3)
To: nfsv4@ietf.org
Message-Id: <6F6D23E4-CBF4-4E5A-92A9-5BD895A99114@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Mon, 28 May 2007 17:02:36 +0300
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 28 May 2007 14:02:46.0175 (UTC) FILETIME=[DE333AF0:01C7A130]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Subject: [nfsv4] AD review: draft-ietf-nfsv4-nfsdirect-05
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1706383306=="
Errors-To: nfsv4-bounces@ietf.org
I'm trying to do the AD review phase early (i.e., in parallel WG last call rather than afterwards), and for this document it has actually worked. Summary: Generally good to go. Main issue is that port 2050 is already registered. Needs minor editorial wordsmithing. Detailed comments: Section 7., paragraph 5: > nfs-rdma 2050 According to http://www.iana.org/assignments/port-numbers, port 2050 is already registered to "Avaya EMB Config Port" - conflict? Section 9., paragraph 4: > [RFC1094] > "NFS: Network File System Protocol Specification", > (NFS version 2) Informational RFC, > http://www.ietf.org/rfc/rfc1094.txt Please call out this DOWNREF in the document shepherd writeup - we need to confirm that this is OK during the IETF last call. > [RFC1813] > B. Callaghan, B. Pawlowski, P. Staubach, "NFS Version 3 Protocol > Specification", > Informational RFC, > http://www.ietf.org/rfc/rfc1813.txt Please call out this DOWNREF in the document shepherd writeup - we need to confirm that this is OK during the IETF last call. The rest are all nits (typos, etc.) Section 1., paragraph 1: > posted buffers to RPC. This document details the mapping for each > version of the NFS protocol [RFC1831] [RFC4506] [RFC1094] [RFC1813] > [RFC3530] [NFSv4.1]. Nit: Shouldn't references to the NFS RFCs be sufficient here? Can the reference to XDR and RPC be omitted? Section 3., paragraph 7: > returned by other methods, e.g. by read chunk list or inline. If no Nit: s/e.g./e.g.,/ (also elsewhere) Section 4, paragraph 2: > If there is no Write list, i.e. the list is null, then any READ or Nit: s/i.e./i.e.,/ (also elsewhere) Section 4, paragraph 17: > operate with prearranged sie constraints, for example use of the Nit: s/sie/size/ Section 10., paragraph 2: > [NFSv4.1] > S. Shepler et. al., ed., "NFSv4 Minor Version 1" Nit: s/et./et/ Section 10., paragraph 4: > [DDP] > H. Shah et al, "Direct Data Placement over Reliable Transports", Nit: s/al/al./ Section 12., paragraph 5: > Intellectual Property Nit: idnits finds a boilerplate issue in the text below - please correct.
_______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www1.ietf.org/mailman/listinfo/nfsv4
- [nfsv4] AD review: draft-ietf-nfsv4-nfsdirect-05 Lars Eggert