Re: [nfsv4] NFSv4.2
"David P. Quigley" <dpquigl@tycho.nsa.gov> Thu, 29 July 2010 21:28 UTC
Return-Path: <dpquigl@tycho.nsa.gov>
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 4268F28C193 for <nfsv4@core3.amsl.com>; Thu, 29 Jul 2010 14:28:12 -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 UMzYYL990u6F for <nfsv4@core3.amsl.com>; Thu, 29 Jul 2010 14:28:11 -0700 (PDT)
Received: from msux-gh1-uea01.nsa.gov (msux-gh1-uea01.nsa.gov [63.239.65.39]) by core3.amsl.com (Postfix) with ESMTP id 483CF28C190 for <nfsv4@ietf.org>; Thu, 29 Jul 2010 14:28:11 -0700 (PDT)
Received: from tarius.tycho.ncsc.mil (localhost [127.0.0.1]) by msux-gh1-uea01.nsa.gov (8.12.10/8.12.10) with ESMTP id o6TLSUL6002326; Thu, 29 Jul 2010 21:28:30 GMT
Received: from [144.51.25.2] (moss-terrapins [144.51.25.2]) by tarius.tycho.ncsc.mil (8.13.1/8.13.1) with ESMTP id o6TLSYSL028404; Thu, 29 Jul 2010 17:28:34 -0400
From: "David P. Quigley" <dpquigl@tycho.nsa.gov>
To: Tom Haynes <tom.haynes@oracle.com>
In-Reply-To: <4C50D308.7050501@oracle.com>
References: <4C50D308.7050501@oracle.com>
Content-Type: text/plain
Organization: National Security Agency
Date: Thu, 29 Jul 2010 17:17:30 -0400
Message-Id: <1280438250.2673.61.camel@moss-terrapins.epoch.ncsc.mil>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11)
Content-Transfer-Encoding: 7bit
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] 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: Thu, 29 Jul 2010 21:28:12 -0000
On Thu, 2010-07-29 at 03:02 +0200, Tom Haynes wrote: > It was clear in the meeting that we all have an interest in > getting NFSv4.2 into the charter. > > I think we also don't know what it will look like. We have > a great starting off point with Mike's document, but we have > seen some more proposals as drafts since then. > > My view of NFSv4.2 is that it will be neither a large > document nor a large set of changes to the protocol. It will > be a collection of small changes with many of them > being optional. > > I personally do not think there will be much space > devoted to fixing things in NFSv4.1, because I don't > envision implementations being far enough along to > find such interoperability issues. > > Does anyone have another take on what 4.2 should > be? > > Is the next step getting the requirements document > updated and resubmitted? > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4 If any wordsmithing is needed for the Labeled NFSv4 portion (known as compliance in the current document) just let me know. Last I looked it captured one of the use cases for Labeled NFSv4 very well and if calling it compliance is a compelling way of referring to it I can deal with that. Dave
- [nfsv4] NFSv4.2 Tom Haynes
- Re: [nfsv4] NFSv4.2 David P. Quigley
- Re: [nfsv4] NFSv4.2 Noveck_David