Re: [nfsv4] Current implementation status of NFSv4.1

Spencer Shepler <sshepler@microsoft.com> Tue, 19 October 2010 17:05 UTC

Return-Path: <sshepler@microsoft.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 3F7803A6909 for <nfsv4@core3.amsl.com>; Tue, 19 Oct 2010 10:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.399
X-Spam-Level:
X-Spam-Status: No, score=-10.399 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 k75kvK5a360q for <nfsv4@core3.amsl.com>; Tue, 19 Oct 2010 10:05:38 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 9AA033A68C2 for <nfsv4@ietf.org>; Tue, 19 Oct 2010 10:05:38 -0700 (PDT)
Received: from TK5EX14CASC132.redmond.corp.microsoft.com (157.54.52.17) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 19 Oct 2010 10:07:02 -0700
Received: from TK5EX14MBXC131.redmond.corp.microsoft.com ([169.254.10.108]) by TK5EX14CASC132.redmond.corp.microsoft.com ([157.54.52.17]) with mapi id 14.01.0255.003; Tue, 19 Oct 2010 10:07:02 -0700
From: Spencer Shepler <sshepler@microsoft.com>
To: Thomas Haynes <thomas@netapp.com>
Thread-Topic: [nfsv4] Current implementation status of NFSv4.1
Thread-Index: Actu/83Ct4Pao8iEToO3K+G6bhr2MAAQo4eAAA3NNAAAADsrgAANRB6A
Date: Tue, 19 Oct 2010 17:07:00 +0000
Message-ID: <E043D9D8EE3B5743B8B174A814FD584F0C9AA8F9@TK5EX14MBXC131.redmond.corp.microsoft.com>
References: <E043D9D8EE3B5743B8B174A814FD584F0C98E09C@TK5EX14MBXC131.redmond.corp.microsoft.com> <AANLkTi=x3DHMNkQP7dOZEoKHPyHB-oriqH513f5HmiGP@mail.gmail.com> <E043D9D8EE3B5743B8B174A814FD584F0C98E1BE@TK5EX14MBXC131.redmond.corp.microsoft.com> <30F2A30E-5EB0-4D28-8560-8308CB3024B1@netapp.com>
In-Reply-To: <30F2A30E-5EB0-4D28-8560-8308CB3024B1@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.74]
Content-Type: multipart/alternative; boundary="_000_E043D9D8EE3B5743B8B174A814FD584F0C9AA8F9TK5EX14MBXC131r_"
MIME-Version: 1.0
Cc: "William A. (Andy) Adamson" <androsadamson@gmail.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] Current implementation status of NFSv4.1
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, 19 Oct 2010 17:05:43 -0000

Tom,

It appears that a good portion of agenda (half?) will be
dedicated to proposals targeted towards NFSv4.x.

I appreciate the desire to discuss NFSv4.2 and we should
but what exactly is to be covered in that slot if not proposals
for functionality?   As I have suggested about other topics,
we should do our best to start a discussion here on the WG alias
and then close or move those discussions forward dramatically
at the WG meeting.

Said another way, I want content behind agenda items and
this includes the NFSv4.2 discussion.  If there isn't predetermined
content then the item will be pushed to the end of agenda
with little time.

btw: I will be posting an updated agenda later today.

Spencer

From: Thomas Haynes [mailto:thomas@netapp.com]
Sent: Monday, October 18, 2010 8:44 PM
To: Spencer Shepler
Cc: William A. (Andy) Adamson; nfsv4@ietf.org
Subject: Re: [nfsv4] Current implementation status of NFSv4.1


On Oct 18, 2010, at 4:27 PM, Spencer Shepler wrote:






I'd be willing to give a Linux implementation status.  How long a time
slot were you thinking of?

Interestingly, I didn't have a duration in mind -- if there is material
to cover that would be helpful in moving our work forward, we will
make time for it.

Spencer


Could we put it at the end of the agenda, after the 4.2 discussion?

I.e., I was unhappy that the 4.2 discussion fell off of the end in Maastricht.