IETF Logo Mail Archive

Re: [nfsv4] nfsv4.x

Dean Hildebrand <seattleplus@gmail.com> Fri, 10 September 2010 17:23 UTC

Return-Path: <seattleplus@gmail.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02EF53A6820 for <nfsv4@core3.amsl.com>; Fri, 10 Sep 2010 10:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mD9vXQ9OnCCK for <nfsv4@core3.amsl.com>; Fri, 10 Sep 2010 10:23:23 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id A706E3A685C for <nfsv4@ietf.org>; Fri, 10 Sep 2010 10:23:22 -0700 (PDT)
Received: by fxm18 with SMTP id 18so2205269fxm.31 for <nfsv4@ietf.org>; Fri, 10 Sep 2010 10:23:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=tEG1zoiMd95SFob51548YduKVevPEmXbST27GU9ebFo=; b=VCcmJjKhOptXqKH+Cf7yMaj90jclq4/USKNaVO023+y/e3vlRLZXQbCWiJHbwW4Nue V7MMRxKMWgXAWev+60drSIHDNYeTrDYD50bi7qvMePFgd7nXdRiUIWqspAV+E1OaL1Ni 8jtu9SSzBVvdSje7B8fxLLsgK5BXCsHUAa6t0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=vHAAda7v+PONGdLBx9ZLDoKKrgVuaIVs7N3XyvyiUhR9H5LfJX6SjYXwTLMPqhMXIY OIkYZVf9VpweFZGtczPrlTtILZ0Iwh72LFy33xUbYoxM8lOG/2Jd/KL1huREcVM2dCRl RU36Hk5qZ8E+2DcmD5ydDefUPEwLMN5n9qch8=
Received: by 10.223.119.138 with SMTP id z10mr578068faq.93.1284139428938; Fri, 10 Sep 2010 10:23:48 -0700 (PDT)
Received: from [9.1.74.30] (p1.almaden.ibm.com [198.4.83.52]) by mx.google.com with ESMTPS id m17sm2944095fag.0.2010.09.10.10.23.46 (version=SSLv3 cipher=RC4-MD5); Fri, 10 Sep 2010 10:23:47 -0700 (PDT)
Message-ID: <4C8A69C7.50707@gmail.com>
Date: Fri, 10 Sep 2010 10:24:23 -0700
From: Dean Hildebrand <seattleplus@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: nfsv4@ietf.org, Spencer Shepler <Spencer.Shepler@Sun.COM>
References: <E043D9D8EE3B5743B8B174A814FD584F09C3E912@TK5EX14MBXC126.redmond.corp.microsoft.com>
In-Reply-To: <E043D9D8EE3B5743B8B174A814FD584F09C3E912@TK5EX14MBXC126.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [nfsv4] nfsv4.x
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 10 Sep 2010 17:23:24 -0000

  On 9/9/2010 12:23 PM, Spencer Shepler wrote:
> I would like to clarify potential NFSv4.2 (or more appropriately NFSv4.x) efforts.
> If there is interest, energy and rough WG consensus, new work can be
> undertaken; rough consensus and running code is the rule.  Having said that,
> we do have responsibilities to curate past efforts (e.g. rfc35030bis).
>
> As Dave Noveck has suggested in the past, the size of the protocol and
> its resultant documents likely require varying methods of capturing
> new protocol features.  Smaller, targeted, reviewable protocol updates
> are my personal preference.
>
> Spencer

We are still very committed to our sparse file support draft 
(http://tools.ietf.org/id/draft-hildebrand-nfsv4-read-sparse-00.txt) and 
strongly believe it should be included in NFSv4.2.  My impression from 
the 3 IETF meetings we presented it at is that there is strong support.  
Also, it fits both desires/requirements perfectly, 1. virtualization 
improvement, 2. small, targeted, and reviewable.

Dean


> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4

v2.23.0 | Report a Bug | By Email