IETF Logo Mail Archive

Re: [nfsv4] Can we make draft-haynes-nfsv4-layout-types-02 a WG item?

Spencer Shepler <sshepler@microsoft.com> Mon, 05 May 2014 06:47 UTC

Return-Path: <sshepler@microsoft.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC631A026F for <nfsv4@ietfa.amsl.com>; Sun, 4 May 2014 23:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 fCo5Y1qSTsgf for <nfsv4@ietfa.amsl.com>; Sun, 4 May 2014 23:47:28 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0183.outbound.protection.outlook.com [207.46.163.183]) by ietfa.amsl.com (Postfix) with ESMTP id 312DC1A026D for <nfsv4@ietf.org>; Sun, 4 May 2014 23:47:27 -0700 (PDT)
Received: from BL2PR03MB369.namprd03.prod.outlook.com (10.141.89.12) by BL2PR03MB372.namprd03.prod.outlook.com (10.141.89.15) with Microsoft SMTP Server (TLS) id 15.0.929.12; Mon, 5 May 2014 06:47:23 +0000
Received: from BL2PR03MB369.namprd03.prod.outlook.com ([10.141.89.12]) by BL2PR03MB369.namprd03.prod.outlook.com ([10.141.89.12]) with mapi id 15.00.0934.000; Mon, 5 May 2014 06:47:22 +0000
From: Spencer Shepler <sshepler@microsoft.com>
To: Tom Haynes <thomas.haynes@primarydata.com>, nfsv4 <nfsv4@ietf.org>
Thread-Topic: [nfsv4] Can we make draft-haynes-nfsv4-layout-types-02 a WG item?
Thread-Index: AQHPZs466sZ83LjH7Uq6+6NTJmvPYpsxjgSw
Date: Mon, 05 May 2014 06:47:21 +0000
Message-ID: <c8e87c080ff9450e816b794d8c0eed84@BL2PR03MB369.namprd03.prod.outlook.com>
References: <5643C90C-D579-4344-9C7D-16FA563FB5BD@primarydata.com>
In-Reply-To: <5643C90C-D579-4344-9C7D-16FA563FB5BD@primarydata.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [98.203.245.144]
x-forefront-prvs: 0202D21D2F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(164054003)(51704005)(377454003)(13464003)(92566001)(86362001)(80022001)(4396001)(76576001)(83322001)(76482001)(83072002)(74502001)(74662001)(31966008)(50986999)(87936001)(99396002)(99286001)(19580405001)(66066001)(74316001)(33646001)(19580395003)(77982001)(81542001)(77096999)(76176999)(54356999)(15975445006)(101416001)(2656002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BL2PR03MB372; H:BL2PR03MB369.namprd03.prod.outlook.com; FPR:F40E4D7F.1C20E361.99D27B57.50E2D3D9.20196; MLV:sfv; PTR:InfoNoRecords; LANG:en;
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/nfsv4/fHWD317MgUQDgzOdw3Y5DNzmAGg
Subject: Re: [nfsv4] Can we make draft-haynes-nfsv4-layout-types-02 a WG item?
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 05 May 2014 06:47:30 -0000

Any comment from others in the WG about Tom's request?

Spencer

> -----Original Message-----
> From: nfsv4 [mailto:nfsv4-bounces@ietf.org] On Behalf Of Tom Haynes
> Sent: Saturday, May 3, 2014 5:50 AM
> To: nfsv4
> Subject: [nfsv4] Can we make draft-haynes-nfsv4-layout-types-02 a WG
> item?
> 
> Hi Spencer,
> 
> Can we make this a WG item?
> 
> Thanks,
> Tom
> 
> Considerations for a New pNFS Layout Type
>                  draft-haynes-nfsv4-layout-types-02.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
>    may be troublesome for those trying to specify new Layout Types.
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4

v2.23.0 | Report a Bug | By Email