Chuck Lever | 20 May 23:05 2015
Picon

new revisions of fedfs individual drafts

Hi-

I’ve posted revised versions of the following individual I-Ds:

https://datatracker.ietf.org/doc/draft-cel-nfsv4-federated-fs-security-addendum/

and

https://datatracker.ietf.org/doc/draft-cel-nfsv4-federated-fs-nce/

The main change is to replace references to the pending draft
FedFS documents with equivalent newly minted RFCs.

I’d like to get more review of these two I-Ds so that they can be moved
to Working Group drafts. Any comments or review is welcome.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4

Chuck Lever | 20 May 21:19 2015
Picon

Fwd: New Version Notification for draft-cel-nfsv4-rpcrdma-bidirection-01.txt

Hi-

This draft has been revised. The revisions include:

 - A discussion on avoiding XID collision in the forward
   and backward direction has been added

 - The “Payload Size” subsection has been rewritten for clarity

 - Review comments since -00 have been addressed (thanks!)

Begin forwarded message:

> From: internet-drafts <at> ietf.org
> Subject: New Version Notification for draft-cel-nfsv4-rpcrdma-bidirection-01.txt
> Date: May 20, 2015 at 3:09:57 PM EDT
> To: "Charles Lever" <chuck.lever <at> oracle.com>, "Chuck Lever" <chuck.lever <at> oracle.com>
> 
> 
> A new version of I-D, draft-cel-nfsv4-rpcrdma-bidirection-01.txt
> has been successfully submitted by Charles Lever and posted to the
> IETF repository.
> 
> Name:		draft-cel-nfsv4-rpcrdma-bidirection
> Revision:	01
> Title:		Size-Limited Bi-directional Remote Procedure Call On Remote Direct Memory Access Transports
> Document date:	2015-05-20
> Group:		Individual Submission
> Pages:		14
> URL:            https://www.ietf.org/internet-drafts/draft-cel-nfsv4-rpcrdma-bidirection-01.txt
(Continue reading)

internet-drafts | 28 Apr 19:19 2015
Picon

I-D Action: draft-ietf-nfsv4-minorversion2-dot-x-38.txt


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 Working Group of the IETF.

        Title           : NFSv4 Minor Version 2 Protocol External Data Representation Standard (XDR) Description
        Author          : Thomas Haynes
	Filename        : draft-ietf-nfsv4-minorversion2-dot-x-38.txt
	Pages           : 81
	Date            : 2015-04-28

Abstract:
   This Internet-Draft provides the XDR description for NFSv4 minor
   version two.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-minorversion2-dot-x/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-dot-x-38

A diff from the previous version is available at:
https:https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-minorversion2-dot-x-38

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/

_______________________________________________
(Continue reading)

Christoph Hellwig | 28 Apr 15:58 2015
Picon

Re: [PATCH] document stateid and filehandle rules for ALLOCATE and DEALLOCATE

Sorry, forgot to Cc the nfsv4 list..

On Tue, Apr 28, 2015 at 03:54:46PM +0200, Christoph Hellwig wrote:
> diff --git a/nfsv42_middle_op_allocate.xml b/nfsv42_middle_op_allocate.xml
> index 293b4dc..cfd62d0 100644
> --- a/nfsv42_middle_op_allocate.xml
> +++ b/nfsv42_middle_op_allocate.xml
>  <at>  <at>  -35,6 +35,17  <at>  <at> 
>      </t>
>  
>      <t>
> +      CURRENT_FH must be a regular file. If CURRENT_FH is not a regular file,
> +      the operation MUST fail and return NFS4ERR_WRONG_TYPE.
> +    </t>
> +
> +    <t>
> +      The aa_stateid MUST refer to a stateid that is valid for a WRITE
> +      operation and follows the rules for stateids in Sections 8.2.5 and
> +      18.32.3 of <xref target='RFC5661' />.
> +    </t>
> +
> +    <t>
>        The server will ensure that backing blocks are reserved to the region
>        specified by aa_offset and aa_length, and that no future writes into
>        this region will return NFS4ERR_NOSPC. If the region lies partially or
> diff --git a/nfsv42_middle_op_deallocate.xml b/nfsv42_middle_op_deallocate.xml
> index fac011b..5bc7fa3 100644
> --- a/nfsv42_middle_op_deallocate.xml
> +++ b/nfsv42_middle_op_deallocate.xml
>  <at>  <at>  -36,7 +36,18  <at>  <at> 
(Continue reading)

internet-drafts | 28 Apr 07:15 2015
Picon

I-D Action: draft-ietf-nfsv4-minorversion2-37.txt


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 Working Group of the IETF.

        Title           : NFS Version 4 Minor Version 2
        Author          : Thomas Haynes
	Filename        : draft-ietf-nfsv4-minorversion2-37.txt
	Pages           : 97
	Date            : 2015-04-27

Abstract:
   This Internet-Draft describes NFS version 4 minor version two,
   describing the protocol extensions made from NFS version 4 minor
   version 1.  Major extensions introduced in NFS version 4 minor
   version two include: Server Side Copy, Application I/O Advise, Space
   Reservations, Sparse Files, Application Data Blocks, and Labeled NFS.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-minorversion2/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-37

A diff from the previous version is available at:
https:https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-minorversion2-37

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:
(Continue reading)

internet-drafts | 28 Apr 07:14 2015
Picon

I-D Action: draft-ietf-nfsv4-minorversion2-dot-x-37.txt


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 Working Group of the IETF.

        Title           : NFSv4 Minor Version 2 Protocol External Data Representation Standard (XDR) Description
        Author          : Thomas Haynes
	Filename        : draft-ietf-nfsv4-minorversion2-dot-x-37.txt
	Pages           : 81
	Date            : 2015-04-27

Abstract:
   This Internet-Draft provides the XDR description for NFSv4 minor
   version two.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-minorversion2-dot-x/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-dot-x-37

A diff from the previous version is available at:
https:https://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-minorversion2-dot-x-37

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/

_______________________________________________
(Continue reading)

Chuck Lever | 27 Apr 16:49 2015
Picon

Fwd: New Version Notification for draft-cel-nfsv4-rpcrdma-bidirection-00.txt

Hi-

Here’s revision -00 of an experimental draft that describes how to do
bi-directional RPC on RDMA transports. This is published to enable
others to construct prototypes that can interoperate. It’s about 10
pages, easy to review and comment on.

Begin forwarded message:

> From: internet-drafts <at> ietf.org
> Subject: New Version Notification for draft-cel-nfsv4-rpcrdma-bidirection-00.txt
> Date: April 27, 2015 at 10:43:45 AM EDT
> To: "Charles Lever" <chuck.lever <at> oracle.com>, "Chuck Lever" <chuck.lever <at> oracle.com>
> 
> 
> A new version of I-D, draft-cel-nfsv4-rpcrdma-bidirection-00.txt
> has been successfully submitted by Charles Lever and posted to the
> IETF repository.
> 
> Name:		draft-cel-nfsv4-rpcrdma-bidirection
> Revision:	00
> Title:		Size-Limited Bi-directional Remote Procedure Call On Remote Direct Memory Access Transports
> Document date:	2015-04-24
> Group:		Individual Submission
> Pages:		13
> URL:            http://www.ietf.org/internet-drafts/draft-cel-nfsv4-rpcrdma-bidirection-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpcrdma-bidirection/
> Htmlized:       http://tools.ietf.org/html/draft-cel-nfsv4-rpcrdma-bidirection-00
> 
> 
(Continue reading)

Christoph Hellwig | 27 Apr 15:31 2015
Picon

stateids for SEEK, ALLOCATE and DEALLOCATE

Currently the 4.2 draft only speciefies the stateid requirements
for READ, COPY and CLONE by referring to the rules for READ and WRITE,
but it does not specify any rules for SEEK, ALLOCATE and DEALLOCATE.

It seems natural to refer to the WRITE or SEATTATR with size changes
for ALLOCATE and DEALLOCATE, but I'm not sure what we should do for
SEEK.  In fact I'm not even sure SEEK should have a stateid argument
at all when I think about it.

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4

Christoph Hellwig | 25 Apr 15:32 2015
Picon

updates based on the clone reviews


_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4

Trond Myklebust | 24 Apr 01:25 2015
Picon

A few questions about CLONE and COPY in draft-ietf-nfs4-minorversion2-36

1) If the cl_src_offset and/or cl_dst_offset are not aligned to the
clone block size, then what is the return value/protocol behaviour for
CLONE? Should it return NFS4ERR_BAD_RANGE?

2) Shouldn't CLONE be able to return NFS4ERR_LOCKED if the server
supports mandatory locking?

3) Shouldn't CLONE be able to return NFS4ERR_DQUOT?

4) Shouldn't CLONE and COPY be able to return NFS4ERR_XDEV for the
same reasons that LINK and RENAME do (i.e. crossing a filesystem
and/or security policy boundary)?

5) What happens to the current stateid? (this question goes for
COPY_OFFLOAD too, by the way) These 2 operations are the only ones
that take 2 stateids, so I don't think there is any precedent in
RFC5661 or RFC7530 to point to.

6) Do we need to describe what happens to the current filehandle?
There is a precedent here in the form of LINK, and RENAME AFAIK.

7) Shouldn't NFS4ERR_METADATA_NOTSUPP be removed from Section 11.2?

Cheers
  Trond

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4
(Continue reading)

internet-drafts | 22 Apr 19:56 2015
Picon

I-D Action: draft-ietf-nfsv4-minorversion2-dot-x-36.txt


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 Working Group of the IETF.

        Title           : NFSv4 Minor Version 2 Protocol External Data Representation Standard (XDR) Description
        Author          : Thomas Haynes
	Filename        : draft-ietf-nfsv4-minorversion2-dot-x-36.txt
	Pages           : 81
	Date            : 2015-04-22

Abstract:
   This Internet-Draft provides the XDR description for NFSv4 minor
   version two.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-nfsv4-minorversion2-dot-x/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-dot-x-36

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-nfsv4-minorversion2-dot-x-36

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/

_______________________________________________
(Continue reading)


Gmane