[nfsv4] RFC 8154 on Parallel NFS (pNFS) Small Computer System Interface (SCSI) Layout

rfc-editor@rfc-editor.org Wed, 03 May 2017 01:37 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 61133131660; Tue, 2 May 2017 18:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 LrdFXEG9QO1T; Tue, 2 May 2017 18:37:51 -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 B3A5E12EB2D; Tue, 2 May 2017 18:34:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A87ADB80A4A; Tue, 2 May 2017 18:33:57 -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
Message-Id: <20170503013357.A87ADB80A4A@rfc-editor.org>
Date: Tue, 02 May 2017 18:33:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ezL6X_lFUhq5XePRr5pqtNBng-o>
Subject: [nfsv4] RFC 8154 on Parallel NFS (pNFS) Small Computer System Interface (SCSI) Layout
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: Wed, 03 May 2017 01:37:56 -0000

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

        
        RFC 8154

        Title:      Parallel NFS (pNFS) Small Computer 
                    System Interface (SCSI) Layout 
        Author:     C. Hellwig
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2017
        Mailbox:    hch@lst.de
        Pages:      30
        Characters: 72094
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nfsv4-scsi-layout-10.txt

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

        DOI:        10.17487/RFC8154

The Parallel Network File System (pNFS) allows a separation between
the metadata (onto a metadata server) and data (onto a storage
device) for a file.  The Small Computer System Interface (SCSI)
layout type is defined in this document as an extension to pNFS to
allow the use of SCSI-based block storage devices.

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