[nfsv4] FedFS Meeting Minutes, 01/22/2009
James Lentini <jlentini@netapp.com> Thu, 22 January 2009 21:13 UTC
Return-Path: <nfsv4-bounces@ietf.org>
X-Original-To: nfsv4-archive@megatron.ietf.org
Delivered-To: ietfarch-nfsv4-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EEB2928C160; Thu, 22 Jan 2009 13:13:13 -0800 (PST)
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 29FC228C160 for <nfsv4@core3.amsl.com>; Thu, 22 Jan 2009 13:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.118
X-Spam-Level:
X-Spam-Status: No, score=-6.118 tagged_above=-999 required=5 tests=[AWL=0.481, 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 B8gqS+keQo-F for <nfsv4@core3.amsl.com>; Thu, 22 Jan 2009 13:13:12 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 3EAB73A6938 for <nfsv4@ietf.org>; Thu, 22 Jan 2009 13:13:12 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,308,1231142400"; d="scan'208";a="116934043"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 22 Jan 2009 13:12:55 -0800
Received: from jlentini-linux.nane.netapp.com (jlentini-linux.nane.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id n0MLCrE5029471 for <nfsv4@ietf.org>; Thu, 22 Jan 2009 13:12:54 -0800 (PST)
Date: Thu, 22 Jan 2009 16:12:53 -0500
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: nfsv4@ietf.org
Message-ID: <alpine.LFD.2.00.0901221612120.9000@jlentini-linux.nane.netapp.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Subject: [nfsv4] FedFS Meeting Minutes, 01/22/2009
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nfsv4-bounces@ietf.org
Errors-To: nfsv4-bounces@ietf.org FedFS Meeting Minutes, 01/22/2009
--------------------------------- Attendees --------- Dan Ellard (BBN) Craig Everhart (NetApp) Paul Lemahieu (EMC) James Lentini (NetApp) Renu Tewari (IBM/ARC) Rob Thurlow (Sun) Mario Wurzl (EMC) Minutes ------- + IETF Note Well Agreement This is a reminder that our discussions are governed by the IETF Note Well Agreement. See: http://www.ietf.org/NOTEWELL.html We will start each weeks meeting with this announcement. + Review Action Items [AI] For the group: In the second week of February we will pick a time to hold the FAST BOF. Wednesday is a likely candidate. Close. See below. [AI] James Lentini will request 4 RPC program numbers for FedFS using the procedure outlined in draft-ietf-nfsv4-rfc1831bis-10.txt Complete. We were granted the range 100418 - 100421. + Upcoming events - Connectathon - FAST '09 BOF Dan Ellard reserved a meeting time for the BOF: Wednesday, Feb. 25, 8-9 PM following the NFSv4.1/pNFS BOF. + NSDB Protocol Document Updates A visual diff of the new and old draft can be produced using this tool: http://tools.ietf.org/rfcdiff Here is a brief list of things that changed: - new IETF IPR boilerplate - global replace of "interface" with "protocol" - re-wording of introduction - replacement of short requirements paragraph with a pointer to the requirement document - removal of root fileset sections, these will be specified in a new document - local NSDB terminology cleaned up - junction key removed - ONC RPC error codes removed - LDAP schema added While reviewing the document, please consider - How to clarify section 5.3 - FSL schema modification to group fs_locations[_info] fields (currency, info) into a single field (called referral_info?). The format of this field would be dictated by the type of the FSL (NFSv4, NFSv4.1, CIFS, ....). [AI] James Lentini will check the IANA considerations Dan described the history of the annotations field. The idea was for this field to have a standard format eventually. After a while, that idea was put on hold. The intention was not to use this field for the fs_locations[_info] data. This field could be used for the administrator to make notes, for future fields, or some other use. Dan also commented on the second idea above, moving the FSL's referral specific fields into a single field. Dan pointed out that since this field will be opaque it cannot be interpreted by LDAP. This would be a disadvantage. It might end up (possibly) resulting in more accesses to an NSDB because a query will return more info and a query cache will be filled faster. _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www.ietf.org/mailman/listinfo/nfsv4
- [nfsv4] FedFS Meeting Minutes, 01/22/2009 James Lentini