Re: [nfsv4] List of possible work items for NFSv4.2

R N ALEX <nalex@netapp.com> Tue, 18 August 2009 16:49 UTC

Return-Path: <rnalex@netapp.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 7668128C297 for <nfsv4@core3.amsl.com>; Tue, 18 Aug 2009 09:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 kpeIT86JBoEg for <nfsv4@core3.amsl.com>; Tue, 18 Aug 2009 09:49:58 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 3439228C292 for <nfsv4@ietf.org>; Tue, 18 Aug 2009 09:49:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,403,1246863600"; d="scan'208";a="226958177"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 18 Aug 2009 09:50:03 -0700
Received: from sacrsexc1-prd.hq.netapp.com (sacrsexc1-prd.hq.netapp.com [10.99.115.27]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id n7IGo2nL022487; Tue, 18 Aug 2009 09:50:03 -0700 (PDT)
Received: from btcrsexc1-prd.hq.netapp.com ([10.73.251.109]) by sacrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 18 Aug 2009 09:50:02 -0700
Received: from BTCMVEXC1-PRD.hq.netapp.com ([10.73.251.107]) by btcrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 18 Aug 2009 22:19:59 +0530
Received: from [10.30.48.183] ([10.30.48.183]) by BTCMVEXC1-PRD.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 18 Aug 2009 22:19:58 +0530
From: R N ALEX <nalex@netapp.com>
To: sfaibish <sfaibish@emc.com>
In-Reply-To: <op.uyu0tvkaunckof@usensfaibisl2e.eng.emc.com>
References: <fe7adea4b3fba5af3e063472b7048e41.squirrel@webmail.eisler.com> <e71b6973da27bdf1d978112177f9b9c2.squirrel@webmail.eisler.com> <op.uyu0tvkaunckof@usensfaibisl2e.eng.emc.com>
Content-Type: text/plain
Date: Tue, 18 Aug 2009 22:19:56 +0530
Message-Id: <1250614197.27798.7.camel@nalex-debian.hq.netapp.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Aug 2009 16:49:58.0431 (UTC) FILETIME=[EBBAC2F0:01CA2023]
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] List of possible work items for NFSv4.2
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: Tue, 18 Aug 2009 16:49:59 -0000

On Tue, 2009-08-18 at 09:23 -0400, sfaibish wrote:
> Mike,
> 
> I was in vacation the last 2 weeks and I couldn't reply to your email until
> now. I hope it is not too late.
> 
> On Sat, 15 Aug 2009 10:58:06 -0400, Mike Eisler <mre-ietf@eisler.com>  
> wrote:
> 
> > Reading through responses, both those published to the list and privately
> > sent to me, I see a strong consensus for NFSv4.2, strong indication
> > that there are people willing to contribute to the document process as
> > orginators, editors, and reviewers, and strong indication that this work
> > will be prototyped/implemented.
> >
> > I propose:
> > - that NFSv4.2, RPCSEC_GSSv3, MAC be authorized as a work items  
> > immediately.
> > -- I further propose that the primary editors of these three work items  
> > be,
> >    respectively, Mike Eisler, Nico Williams, and Dave Quigley.
> I will help with the review.
> 
> > - For the NFSv4.2 document, we start by combining the COPY operations  
> > I-D,
> >   and the part of the MAC I-D that describes the RECOMMENDED MAC  
> > attribute.
> > -- We should have a discussion and reach consensus on how to combine
> >    sub-file caching
> > (http://tools.ietf.org/html/draft-eisler-nfsv4-pnfs-dedupe
> >    or
> > http://tools.ietf.org/html/draft-myklebust-nfsv4-byte-range-delegations),
> >    peer-to-peer NFS (
> > http://tools.ietf.org/html/draft-myklebust-nfsv4-pnfs-backend ),
> >    and unstable file create (see Trond's emails on this thread),
> >    and then fold this consensus into NFSv4.2.
> I will be part of the discussion. I would also be interested to combine
> the sub-file caching for file, block and object layouts with some cross
> mapping. I can explain in more detail if it is of interest. I would also
> add to this perhaps an option to add later additional layout drivers. I  
> will
> be also interested to extend the P2P to take care of large numbers of small
> files to address the explosion of number of objects scalability. I believe
> that Benny Halevy will be also interested to contribute.
> 
> I want also to propose including a tighter error detection and reporting
> related to pNFS access permissions I proposed at the meeting. I will extend
> similar stats permission errors for the pNFS server.
> 
> One additional item should be the support of IPV6 in pNFS if there are any
> gaps in the protocol. I will try to work with Chuck Lever on this item.

I would like to contribute to the IPv6 related work for NFS4.2 as
continuation of the general IPv6 discussions had as part of the 75th
stockholm IETF meeting.

> 
> >
> > Going through the items one by one:
> >
> > On Wed, August 12, 2009 8:41 pm, Mike Eisler wrote:
> >
> >> Peer-to-Peer NFS
> >
> > Strong indication of support for this work in terms of reviewing,
> > contributing and implementing (it has already been prototyped).
> > Trond wants to re-do the prototype once the NFSv4.2 form of this
> > work is clarified.
> [Sorin] I will help with the review and test the prototype.
> 
> >
> >> Copy
> >
> > James indicated he'd like to continue to contribute here, including
> > with implementation. Tom Haynes also indicated a possibility to  
> > contribute
> > here.
> >
> >> Hole Punching
> >
> > I received a private response that proposals for hole punching and
> > thin provisioning will be coming soon.
> [Sorin] I will contribute to this item including possible prototyping.
> 
> >
> >> MAC Security Attribute
> >
> > Dave Quigley is committed to contributing to
> >
> >> Traffic Classification
> >
> > Thus far, no renewed interested has been expressed on this.
> >
> >> End-to-End Data Integrity
> >
> > Thus far, no renewed interested has been expressed on this.
> >
> >
> >> Umask Attribute
> >
> > Thus far, no renewed interested has been expressed on this.
> >
> >> Shutdown Callback
> >
> > Thus far, no renewed interested has been expressed on this.
> >
> >> Readahead Hint
> >
> > Thus far, no renewed interested has been expressed on this.
> >
> >> pNFS Connectivity/Access Indication
> >
> > A fresh item from Stockholm IETF meeting; absence of
> > re-stating support for this is not absence of proof of interest.
> > I for one am committed to seeing this solved in NFSv4.2.
> [Sorin] I will be involved in drafting the changes.
> 
> >
> >> Better Negotiation of Session Reply Cache Sizes
> >
> > A fresh item from after Stockholm IETF meeting; absence of
> > re-stating support for this is not absence of proof of interest.
> > But I remain luke warm on this ... not entirely convinced there is
> > a problem to solve.
> >
> >> Metadata Striping
> >
> > Andy Adamson has expressed interest in prototyping this.
> [Sorin] This relates close to the large number of small objects scalability
> and I will work with Andy on this.
> 
> >
> >> De-Dupe Awareness and Sub-File Caching
> >
> > In the context of peer-to-peer NFS, I see continued interested
> > in sub-file caching. Sub-file caching as proposed my me, gives
> > one de-dupe awareness for free (or the converse depending on
> > how one wants to look at it). As I've proposed at the beginning of
> > this message, the WG needs to discuss how it wants to approach all
> > these topics before adding them to an NFSv4.2 I-D.
> [Sorin] I want to contribute to this.
> 
> >
> > New items:
> >
> > - unstable file creates. This has a lot of interested within the WG
> > - capabilities: An item proposed by Nico Williams
> > - attributes: Dan Muntz expressed an interest in revisiting how  
> > attributes
> >   are handled.
> >
> >
> 
> /Sorin
> 
>