Re: [nfsv4] draft-haynes-nfsv4-versioning-01
Christoph Hellwig <hch@lst.de> Thu, 23 October 2014 07:21 UTC
Return-Path: <hch@lst.de>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 699E91A8925 for <nfsv4@ietfa.amsl.com>; Thu, 23 Oct 2014 00:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level:
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBAJvhiE1qLt for <nfsv4@ietfa.amsl.com>; Thu, 23 Oct 2014 00:21:03 -0700 (PDT)
Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF21B1A8924 for <nfsv4@ietf.org>; Thu, 23 Oct 2014 00:21:02 -0700 (PDT)
Received: by newverein.lst.de (Postfix, from userid 2407) id C5F4013F1F; Thu, 23 Oct 2014 09:20:59 +0200 (CEST)
Date: Thu, 23 Oct 2014 09:20:59 +0200
From: Christoph Hellwig <hch@lst.de>
To: Benny Halevy <bhalevy@primarydata.com>
Message-ID: <20141023072059.GA28814@lst.de>
References: <896EE07C-552B-412C-B30E-85A223AAA6B2@primarydata.com> <CAEMWVhsYYTxbw44C+oOmyWTCiMbCf_yOebTBWv0z2W6YHrChSg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAEMWVhsYYTxbw44C+oOmyWTCiMbCf_yOebTBWv0z2W6YHrChSg@mail.gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Archived-At: http://mailarchive.ietf.org/arch/msg/nfsv4/kSK9ijqM0kJZfhlx7Pnw57_yd-s
Cc: NFSv4 <nfsv4@ietf.org>
Subject: Re: [nfsv4] draft-haynes-nfsv4-versioning-01
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 23 Oct 2014 07:21:04 -0000
On Thu, Oct 23, 2014 at 09:18:26AM +0300, Benny Halevy wrote: > Why wouldn't they be able to respond with "not supported"? > Even today some callbacks are (feature) optional, e.g. CB_NOTIFY_DEVICEID But clients needs to ask for it using a bitmasp in the GETDEVICEINFO arguments. I suspect if we really get a callback that doesn't have an operation to request it we just need a attribute that the client sets to allow it.
- [nfsv4] draft-haynes-nfsv4-versioning-01 Tom Haynes
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 Benny Halevy
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 Christoph Hellwig
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 J. Bruce Fields
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 David Noveck
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 Tom Haynes
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 J. Bruce Fields
- Re: [nfsv4] draft-haynes-nfsv4-versioning-01 Nico Williams