Last Call: <draft-ietf-nfsv4-layout-types-03.txt> (Requirements for pNFS Layout Types) to Informational RFC

The IESG <> Thu, 26 March 2015 23:01 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3F20B1A1B3E; Thu, 26 Mar 2015 16:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jOJswyLYR37S; Thu, 26 Mar 2015 16:01:50 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 0DCB41A005D; Thu, 26 Mar 2015 16:01:50 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-nfsv4-layout-types-03.txt> (Requirements for pNFS Layout Types) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 26 Mar 2015 16:01:50 -0700
Archived-At: <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Mar 2015 23:01:51 -0000

The IESG has received a request from the Network File System Version 4 WG
(nfsv4) to consider the following document:
- 'Requirements for pNFS Layout Types'
  <draft-ietf-nfsv4-layout-types-03.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2015-04-16. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   This document provides help in distinguishing between the
   requirements for Network File System (NFS) version 4.1's Parallel NFS
   (pNFS) and those those specifically directed to the pNFS File Layout.
   The lack of a clear separation between the two set of requirements
   has been troublesome for those specifying and evaluating new Layout
   Types.  As this document clarifies RFC5661, it effectively updates

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.