[nfsv4] 3530bis Issue 39: Clarification on renewing sequence IDs

Robert Thurlow <Robert.Thurlow@oracle.com> Wed, 06 October 2010 20:19 UTC

Return-Path: <Robert.Thurlow@oracle.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 AFA293A6FF3 for <nfsv4@core3.amsl.com>; Wed, 6 Oct 2010 13:19:35 -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 hXNgH5ZWH1Rg for <nfsv4@core3.amsl.com>; Wed, 6 Oct 2010 13:19:34 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 3F71D3A71C8 for <nfsv4@ietf.org>; Wed, 6 Oct 2010 13:19:34 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o96KKWWS009865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <nfsv4@ietf.org>; Wed, 6 Oct 2010 20:20:34 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o96FjUPm023751 for <nfsv4@ietf.org>; Wed, 6 Oct 2010 20:20:32 GMT
Received: from abhmt009.oracle.com by acsmt354.oracle.com with ESMTP id 668627681286396413; Wed, 06 Oct 2010 13:20:13 -0700
Received: from [10.7.250.62] (/10.7.250.62) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 06 Oct 2010 13:20:12 -0700
Message-ID: <4CACD9BF.2010809@oracle.com>
Date: Wed, 06 Oct 2010 14:19:11 -0600
From: Robert Thurlow <Robert.Thurlow@oracle.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080811)
MIME-Version: 1.0
To: NFSv4 <nfsv4@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [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: Wed, 06 Oct 2010 20:19:35 -0000

Hi folks,

This is issue 39 from http://github.com/loghyr/3530bis/blob/master/tasklist.txt.

In implementing NFSv4 migration support, we believe that
MOVED and LEASE_MOVED need to be added to the list of errors
in 8.1.5 which do NOT result in incrementing the open owner
or lock owner sequence ID.  The goal is to make the sequence
ID readily calculable for both the client and the destination
server after the migration has occurred.

On the 3530bis call, this appeared exactly backwards to some
others - that since a completely gross error had not occurred,
we should increment the sequence ID and the client and the
destination server should know to expect that when they interact
after a migration.  I do not know this issue well enough to
properly defend a position, so please reply with your reasoned
opinion :-)

Thanks,
Rob T