Re: [nfsv4] FW: New Version Notification for draft-faibish-nfsv4-pnfs-block-disk-protection-01.txt

Benny Halevy <bhalevy@tonian.com> Thu, 07 July 2011 14:25 UTC

Return-Path: <bhalevy@tonian.com>
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 09F049E8009 for <nfsv4@ietfa.amsl.com>; Thu, 7 Jul 2011 07:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.479
X-Spam-Level:
X-Spam-Status: No, score=-3.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33Sdfv8H8sFY for <nfsv4@ietfa.amsl.com>; Thu, 7 Jul 2011 07:24:58 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5524D9E8005 for <nfsv4@ietf.org>; Thu, 7 Jul 2011 07:24:58 -0700 (PDT)
Received: by wyj26 with SMTP id 26so788612wyj.31 for <nfsv4@ietf.org>; Thu, 07 Jul 2011 07:24:57 -0700 (PDT)
Received: by 10.227.174.11 with SMTP id r11mr785845wbz.11.1310048697140; Thu, 07 Jul 2011 07:24:57 -0700 (PDT)
Received: from lt.bhalevy.com ([82.166.165.132]) by mx.google.com with ESMTPS id fn12sm3362952wbb.21.2011.07.07.07.24.55 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Jul 2011 07:24:56 -0700 (PDT)
Message-ID: <4E15C1B5.5070600@tonian.com>
Date: Thu, 07 Jul 2011 17:24:53 +0300
From: Benny Halevy <bhalevy@tonian.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Thunderbird/3.1.10
MIME-Version: 1.0
To: david.black@emc.com
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589392870@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E0589392870@MX14A.corp.emc.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] FW: New Version Notification for draft-faibish-nfsv4-pnfs-block-disk-protection-01.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 07 Jul 2011 14:25:06 -0000

Isn't it a problem to have this draft on the proposed standard track
while it builds and references the non-standard GPT structure.

I can see this going in the "best practices" informational RFC
direction.

Benny

On 2011-07-06 20:58, david.black@emc.com wrote:
> A new version of the draft explaining how to use the GPT (GUID partition table) to protect
> pNFS block devices from access when the pNFS server can't be contacted (e.g., during early
> stages of boot) has been posted.  This has been shortened and focused from the -00 version.
> 
> Would the keeper of the Quebec City agenda please include a short slot for this draft?
> 
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: Wednesday, July 06, 2011 1:55 PM
> To: Black, David
> Cc: Black, David; faibish, sorin; jglasgow@google.com
> Subject: New Version Notification for draft-faibish-nfsv4-pnfs-block-disk-protection-01.txt
> 
> A new version of I-D, draft-faibish-nfsv4-pnfs-block-disk-protection-01.txt has been successfully submitted by David Black and posted to the IETF repository.
> 
> Filename:	 draft-faibish-nfsv4-pnfs-block-disk-protection
> Revision:	 01
> Title:		 pNFS block disk protection
> Creation date:	 2011-07-08
> WG ID:		 Individual Submission
> Number of pages: 6
> 
> Abstract:
>    Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to
>    enable direct client access to file data on storage, bypassing the
>    NFSv4 server.  This can increase both performance and parallelism,
>    but requires additional client functionality, some of which depends
>    upon the type of storage used.  The pNFS specification for block
>    storage (RFC 5663) describes how clients can identify the volumes
>    used for pNFS, but this mechanism requires communication with the
>    NFSv4 server.  This document adds a mechanism to RFC 5663 that
>    enables clients to identify block storage devices used by pNFS file
>    systems without communicating with the server.  This enables clients
>    to control access to pNFS block devices when the client initially
>    boots, as opposed to waiting until the client can communicate with
>    the NFSv4 server.
> 
>                                                                                   
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4