IETF Logo Mail Archive

Re: [nfsv4] Review of draft-ietf-nfsv4-rfc5667bis-09

Chuck Lever <chuck.lever@oracle.com> Thu, 27 April 2017 15:53 UTC

Return-Path: <chuck.lever@oracle.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF43129A9A for <nfsv4@ietfa.amsl.com>; Thu, 27 Apr 2017 08:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OH6SMuj6_J6k for <nfsv4@ietfa.amsl.com>; Thu, 27 Apr 2017 08:53:58 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAB93129AE0 for <nfsv4@ietf.org>; Thu, 27 Apr 2017 08:51:56 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v3RFptXL025169 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <nfsv4@ietf.org>; Thu, 27 Apr 2017 15:51:56 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id v3RFpshR010767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <nfsv4@ietf.org>; Thu, 27 Apr 2017 15:51:54 GMT
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id v3RFpp3W003476 for <nfsv4@ietf.org>; Thu, 27 Apr 2017 15:51:52 GMT
Received: from dhcp-whq-5op-3rd-and-4th-floor-gen-off-10-211-46-5.usdhcp.oraclecorp.com (/10.211.46.5) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 27 Apr 2017 08:51:51 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <700f84d2-a514-bfa8-7f0b-5ffd4173c16d@talpey.com>
Date: Thu, 27 Apr 2017 08:53:29 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <EBC491EB-860B-401C-B192-9A8E9F8176B0@oracle.com>
References: <CADaq8jdkGgL+H-yoO-+bTNbSYiE_1us9cN5SXY8QV0gfYfK0Ng@mail.gmail.com> <ce42960d-d1e9-8fa6-e98e-3e9b1a2af7d6@oracle.com> <f66e8e66-ba54-ff57-945a-7951eab2f8b1@talpey.com> <BB65A737-BDBD-4A23-9CEE-2EA153293842@oracle.com> <33468014-6695-a2da-1af8-f1f355fbe986@talpey.com> <CADaq8jcJJQ3TiVX6fFURg22YgNg=Cd7ezNQewjt6fgNK4LrPVg@mail.gmail.com> <F417EA11-D49F-420D-A64F-AE6A382B920C@oracle.com> <7213a956-6157-d0a6-432d-1da8d555d8e9@talpey.com> <A7BB8A22-53E3-4910-A6DE-C6103343D309@oracle.com> <6974E7E7-051B-4F28-A61A-DF6F841B248B@oracle.com> <af6ed8c5-6a7d-08ed-590b-1774f34e05f2@talpey.com> <6f23e91a-2d66-cbd8-aea9-2753ddfb9b79@oracle.com> <9726D6E8-0A9E-46C9-9DCF-FB2FB492622D@oracle.com> <700f84d2-a514-bfa8-7f0b-5ffd4173c16d@talpey.com>
To: NFSv4 <nfsv4@ietf.org>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/XP9Yx-S9c8Y7UKJbj4nAkUhxV30>
Subject: Re: [nfsv4] Review of draft-ietf-nfsv4-rfc5667bis-09
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 15:54:00 -0000

> On Apr 27, 2017, at 8:46 AM, Tom Talpey <tom@talpey.com> wrote:
> 
> On 4/27/2017 11:35 AM, Chuck Lever wrote:
>> We could do something clever like add these limits to the
>> RDMA CM private data.
> 
> Please, no. Placing a message in that data is in itself a protocol,
> and the size and support for that data is implementation defined,
> in the RDMA layer.

So you would object strenuously to

https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpcrdma-cm-pvt-msg/


> If such a parameter exchange is required (and remember it needs to
> go both ways), just define it as a full-blown negotiation, at the
> RPC-RDMA, or better, the NFS layer. There are already some RDMA
> values exchanged in the NFSv4.1 Session establishment, which could
> be extended.


--
Chuck Lever

v2.23.0 | Report a Bug | By Email