[nfsv4] RFC 8435 on Parallel NFS (pNFS) Flexible File Layout

rfc-editor@rfc-editor.org Fri, 24 August 2018 21:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 86390130EA0; Fri, 24 Aug 2018 14:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Teyb_8EQuWcs; Fri, 24 Aug 2018 14:30:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD02130E20; Fri, 24 Aug 2018 14:30:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 252DBB8122B; Fri, 24 Aug 2018 14:30:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nfsv4@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180824213013.252DBB8122B@rfc-editor.org>
Date: Fri, 24 Aug 2018 14:30:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Fo9R4cr8cCEB9nizEwBGlAdfC8Q>
Subject: [nfsv4] RFC 8435 on Parallel NFS (pNFS) Flexible File Layout
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 24 Aug 2018 21:30:35 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8435

        Title:      Parallel NFS (pNFS) Flexible File Layout
        Author:     B. Halevy, 
                    T. Haynes
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2018
        Mailbox:    bhalevy@gmail.com, 
                    loghyr@gmail.com
        Pages:      42
        Characters: 98505
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nfsv4-flex-files-19.txt

        URL:        https://www.rfc-editor.org/info/rfc8435

        DOI:        10.17487/RFC8435

Parallel NFS (pNFS) allows a separation between the metadata (onto a
metadata server) and data (onto a storage device) for a file.  The
flexible file layout type is defined in this document as an extension
to pNFS that allows the use of storage devices that require only a
limited degree of interaction with the metadata server and use
already-existing protocols.  Client-side mirroring is also added to
provide replication of files.


This document is a product of the Network File System Version 4 Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC