IETF Logo Mail Archive

[nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-rfc5667bis-07.txt

Chuck Lever <chuck.lever@oracle.com> Thu, 09 March 2017 17:21 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 2EF461296C3 for <nfsv4@ietfa.amsl.com>; Thu, 9 Mar 2017 09:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level:
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, 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 sFEJb955f8tN for <nfsv4@ietfa.amsl.com>; Thu, 9 Mar 2017 09:21:04 -0800 (PST)
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 AD9C712966B for <nfsv4@ietf.org>; Thu, 9 Mar 2017 09:21:02 -0800 (PST)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v29HL1FP031468 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <nfsv4@ietf.org>; Thu, 9 Mar 2017 17:21:02 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.13.8/8.14.4) with ESMTP id v29HL1Mh002324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <nfsv4@ietf.org>; Thu, 9 Mar 2017 17:21:01 GMT
Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id v29HKxTt007629 for <nfsv4@ietf.org>; Thu, 9 Mar 2017 17:21:00 GMT
Received: from anon-dhcp-171.1015granger.net (/68.46.169.226) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 09 Mar 2017 09:20:59 -0800
From: Chuck Lever <chuck.lever@oracle.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 09 Mar 2017 12:20:52 -0500
References: <148907920323.5831.17181933745255318033@ietfa.amsl.com>
To: NFSv4 <nfsv4@ietf.org>
Message-Id: <88EC74BD-8BBC-4BF8-B54B-1B88EEC72AAF@oracle.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/wetKDOYe8WMHHAqnj8Vnso95bQE>
Subject: [nfsv4] Fwd: I-D Action: draft-ietf-nfsv4-rfc5667bis-07.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Mar 2017 17:21:06 -0000

> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: [nfsv4] I-D Action: draft-ietf-nfsv4-rfc5667bis-07.txt
> Date: March 9, 2017 at 12:06:43 PM EST
> To: <i-d-announce@ietf.org>
> Cc: nfsv4@ietf.org
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network File System Version 4 of the IETF.
> 
>        Title           : Network File System (NFS) Upper Layer Binding To RPC-Over-RDMA Version One
>        Author          : Charles Lever
> 	Filename        : draft-ietf-nfsv4-rfc5667bis-07.txt
> 	Pages           : 19
> 	Date            : 2017-03-09
> 
> Abstract:
>   This document specifies Upper Layer Bindings of Network File System
>   (NFS) protocol versions to RPC-over-RDMA Version One, enabling the
>   use of Direct Data Placement.  This document obsoletes RFC 5667.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rfc5667bis/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-nfsv4-rfc5667bis-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-rfc5667bis-07
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4

This revision:

- picks up the latest revision of rpcrdma-bidirection

- merges Dave Noveck's review of -06

- clarifies reply size estimation for NLM


Note that MOUNT/NLM/NSM operation on RPC-over-RDMA has also
never been implemented, and is thus speculative. A disclaimer
that TCP is typically used for these protocols has been left
at the top of that section, but perhaps more is needed there.


This revision does not attempt to address whether multiple
chunks are allowed in a single RPC transaction.

Allowing multiple NFS READ and WRITE operations per COMPOUND
is an issue for NFS implementations on all transports. Does
an NFS/TCP client have a way to probe a server to see if it
can handle such a request?


--
Chuck Lever

v2.23.0 | Report a Bug | By Email