[nfsv4] question on bulk recall text

Fred Isaman <iisaman@citi.umich.edu> Tue, 12 October 2010 16:18 UTC

Return-Path: <faisaman4@gmail.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 52AC53A684F for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 09:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 hhpA+fccKzXT for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 09:18:06 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 105663A68D5 for <nfsv4@ietf.org>; Tue, 12 Oct 2010 09:18:05 -0700 (PDT)
Received: by bwz14 with SMTP id 14so2325169bwz.31 for <nfsv4@ietf.org>; Tue, 12 Oct 2010 09:19:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=BetiQXpxDOM/f+gwZiI2HpN5vMOoIPS98OU1z69fRD0=; b=hxDxTVHV6tDH8UWbLatwVQa6l9BLIdA5hOxbn3XndA3covmOE7L401T2FzpCrkG1x5 wipKiGsevu8IvJ0lLBOW+rG5b87NCyv5s4pjQtMvVka5+p6o0WFbdhh9IEHK247guape 2OuqjbPKjGS1bk5hEgDpJVf+5jz0qwNKsnwPY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=EPz8Bl3tkPpkc2lJjL7rRT8X6IbRLVfkRvYJKIfqO7FtEujAWKXVS2PO6Mt0Xt1f4T 0sdRJserMJvpXbJSbeTYhI1nyG2vvuUNB1zBgifiEDeausdGZE3WJL7uSi6LPaiZI47a 0lFhD232Ci7Y34NaZOJniKGL6909GbjBH70x4=
MIME-Version: 1.0
Received: by 10.204.121.84 with SMTP id g20mr6228551bkr.37.1286900358329; Tue, 12 Oct 2010 09:19:18 -0700 (PDT)
Sender: faisaman4@gmail.com
Received: by 10.204.77.1 with HTTP; Tue, 12 Oct 2010 09:19:18 -0700 (PDT)
Date: Tue, 12 Oct 2010 12:19:18 -0400
X-Google-Sender-Auth: JMv9utlbzuoKY6VPBZWpji2dshM
Message-ID: <AANLkTinx1ZQWko8D9XgmikaGAv4nHxoWJ2bDuM5O=y_u@mail.gmail.com>
From: Fred Isaman <iisaman@citi.umich.edu>
To: nfsv4@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [nfsv4] question on bulk recall text
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, 12 Oct 2010 16:18:07 -0000

The text for bulk recalls in 12.5.5.2.1.5 seems flawed:

   Once a CB_LAYOUTRECALL of LAYOUTRECALL4_ALL is sent, the server MUST
   NOT allow the client to use any layout stateid except for
   LAYOUTCOMMIT operations.  Once the client receives a CB_LAYOUTRECALL
   of LAYOUTRECALL4_ALL, it MUST NOT use any layout stateid except for
   LAYOUTCOMMIT operations.

(similarly for LAYOUTRECALL4_FSID)

My question: what stateid does the client use to send the required LAYOUTRETURN?

Fred