Re: [nfsv4] suggestion for section 5
James Lentini <jlentini@netapp.com> Wed, 15 September 2010 18:49 UTC
Return-Path: <jlentini@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 29D1F3A6A00 for <nfsv4@core3.amsl.com>; Wed, 15 Sep 2010 11:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.94
X-Spam-Level:
X-Spam-Status: No, score=-5.94 tagged_above=-999 required=5 tests=[AWL=0.659, 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 3EHl0NlFiava for <nfsv4@core3.amsl.com>; Wed, 15 Sep 2010 11:49:27 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 1B1193A6918 for <nfsv4@ietf.org>; Wed, 15 Sep 2010 11:49:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,372,1280732400"; d="scan'208";a="451030658"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 15 Sep 2010 11:49:52 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o8FInpjm019635; Wed, 15 Sep 2010 11:49:52 -0700 (PDT)
Date: Wed, 15 Sep 2010 14:49:51 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <66000740-0FCA-403D-A150-62741EE5F8E9@oracle.com>
Message-ID: <alpine.LFD.2.00.1009151411230.18626@jlentini-linux.nane.netapp.com>
References: <66000740-0FCA-403D-A150-62741EE5F8E9@oracle.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: NFSv4 Working Group <nfsv4@ietf.org>
Subject: Re: [nfsv4] suggestion for section 5
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, 15 Sep 2010 18:49:28 -0000
On Wed, 15 Sep 2010, Chuck Lever wrote: > James- > > The NCE seems like it is now a full blown NSDB object. Would it > make sense to add "create NCE" and "delete NCE" operations to > Chapter 5 section 1 of the NSDB protocol draft? The NCE is described in Chapter 4.1, the section describing NSDB configuration. Since it is part of the NSDB configuration, the specification doesn't define create and delete operations (by its nature, NSDB configuration will be implementation specific). I think Chapter 4 is the natural location for discussing the NCE, but I'll listen other opinions. -james
- [nfsv4] suggestion for section 5 Chuck Lever
- Re: [nfsv4] suggestion for section 5 James Lentini