Re: [nfsv4] 3530bis Issue 39: Clarification on renewing sequence IDs
"Haynes, Tom" <Thomas.Haynes@netapp.com> Sat, 20 November 2010 01:49 UTC
Return-Path: <Thomas.Haynes@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 8EBAD28C0FF for <nfsv4@core3.amsl.com>; Fri, 19 Nov 2010 17:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.203
X-Spam-Level:
X-Spam-Status: No, score=-9.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 f40Anj9wqzub for <nfsv4@core3.amsl.com>; Fri, 19 Nov 2010 17:49:18 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 83F143A6942 for <nfsv4@ietf.org>; Fri, 19 Nov 2010 17:49:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.59,226,1288594800"; d="scan'208";a="484756433"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 19 Nov 2010 17:49:54 -0800
Received: from sacrsexc2-prd.hq.netapp.com (sacrsexc2-prd.hq.netapp.com [10.99.115.28]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id oAK1nrBB016814; Fri, 19 Nov 2010 17:49:54 -0800 (PST)
Received: from rtprsexc1-prd.hq.netapp.com ([10.100.161.114]) by sacrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Nov 2010 17:49:54 -0800
Received: from RTPMVEXC1-PRD.hq.netapp.com ([10.100.161.112]) by rtprsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Nov 2010 20:49:52 -0500
Received: from 10.99.95.204 ([10.99.95.204]) by RTPMVEXC1-PRD.hq.netapp.com ([10.100.161.119]) with Microsoft Exchange Server HTTP-DAV ; Sat, 20 Nov 2010 01:49:52 +0000
References: <4CACD9BF.2010809@oracle.com> <4CD32C31.3040909@oracle.com> <1288965554.3975.27.camel@heimdal.trondhjem.org> <BF3BB6D12298F54B89C8DCC1E4073D8002945154@CORPUSMX50A.corp.emc.com> <1290100143.7245.9.camel@heimdal.trondhjem.org> <BF3BB6D12298F54B89C8DCC1E4073D8002A5EE45@CORPUSMX50A.corp.emc.com> <1290207533.3135.80.camel@heimdal.trondhjem.org>
Thread-Topic: [nfsv4] 3530bis Issue 39: Clarification on renewing sequence IDs
Thread-Index: AcuIVTjfZg6p4F6rSOSo1crxKbHdyg==
Content-Transfer-Encoding: quoted-printable
From: "Haynes, Tom" <Thomas.Haynes@netapp.com>
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <1290207533.3135.80.camel@heimdal.trondhjem.org>
Message-ID: <B038A121-D2A2-4FAE-B499-309125BBE4C9@netapp.com>
Date: Fri, 19 Nov 2010 17:49:19 -0800
To: Trond Myklebust <Trond.Myklebust@netapp.com>
MIME-Version: 1.0 (iPhone Mail 8B117)
X-OriginalArrivalTime: 20 Nov 2010 01:49:52.0451 (UTC) FILETIME=[39437130:01CB8855]
Cc: Robert.Thurlow@oracle.com, nfsv4@ietf.org
Subject: Re: [nfsv4] 3530bis Issue 39: Clarification on renewing sequence IDs
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: Sat, 20 Nov 2010 01:49:19 -0000
Yeah, I was planning on starting it anyway. I'll get it done by Monday. And github works great for me. On Nov 19, 2010, at 2:58 PM, "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote: > On Fri, 2010-11-19 at 17:39 -0500, david.noveck@emc.com wrote: >> I think we will need to have a v4.2 document minor version document in >> place soon. This kind of small thing (bug or not) is just not big >> enough to merit an internet-draft. If you require it, these things will >> just not get done. I think that once we have a framework for this sort >> of small addition, we can publish the text for the new op or callback in >> messages on the working group list and then incorporate them in the next >> v4.2 draft, once there is rough consensus. My suggestion is that we >> make it the practice to publish proposed v4.2 text in the form of >> xml2rfc xml within the working group email to make it simpler for the >> v4.2 document editor to incorporate. > > Tom, now is your chance to shine even brighter! Another git repository > to complement git://github.com/loghyr/3530bis.git and a 4.2 review > process incorporating Dave's suggestions? > > Cheers > Trond > > -- > Trond Myklebust > Linux NFS client maintainer > > NetApp > Trond.Myklebust@netapp.com > www.netapp.com >
- [nfsv4] 3530bis Issue 39: Clarification on renewi… Robert Thurlow
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Robert Thurlow
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Trond Myklebust
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… david.noveck
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Trond Myklebust
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… david.noveck
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Trond Myklebust
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Haynes, Tom
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Spencer Shepler
- Re: [nfsv4] 3530bis Issue 39: Clarification on re… Thomas Haynes