--- 1/draft-ietf-nfsv4-layout-types-02.txt 2015-01-30 12:14:50.769030745 -0800 +++ 2/draft-ietf-nfsv4-layout-types-03.txt 2015-01-30 12:14:50.793031334 -0800 @@ -1,19 +1,19 @@ NFSv4 T. Haynes Internet-Draft Primary Data -Updates: 5661 (if approved) October 27, 2014 -Intended status: Informational -Expires: April 30, 2015 +Updates: 5661 (if approved) January 30, 2015 +Intended status: Standards Track +Expires: August 3, 2015 Requirements for pNFS Layout Types - draft-ietf-nfsv4-layout-types-02.txt + draft-ietf-nfsv4-layout-types-03.txt Abstract 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 RFC5661. @@ -26,25 +26,25 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 30, 2015. + This Internet-Draft will expire on August 3, 2015. Copyright Notice - Copyright (c) 2014 IETF Trust and the persons identified as the + Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as