[nfsv4] FedFS Meeting Minutes, 10/15/2009
James Lentini <jlentini@netapp.com> Thu, 15 October 2009 19:08 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 C0EB53A694D for <nfsv4@core3.amsl.com>; Thu, 15 Oct 2009 12:08:26 -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 NtozahrocBhx for <nfsv4@core3.amsl.com>; Thu, 15 Oct 2009 12:08:25 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 9EFDC3A690D for <nfsv4@ietf.org>; Thu, 15 Oct 2009 12:08:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,567,1249282800"; d="scan'208";a="258824161"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 15 Oct 2009 12:08:29 -0700
Received: from jlentini-linux.nane.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 n9FJ8Sji013591 for <nfsv4@ietf.org>; Thu, 15 Oct 2009 12:08:28 -0700 (PDT)
Date: Thu, 15 Oct 2009 15:08:26 -0400
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.0910151507330.11932@jlentini-linux.nane.netapp.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [nfsv4] FedFS Meeting Minutes, 10/15/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/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, 15 Oct 2009 19:08:26 -0000
FedFS Meeting Minutes, 10/15/2009 --------------------------------- Attendees --------- Andy Adamson (NetApp) Sorin Faibish (EMC) Paul Lemahieu (EMC) James Lentini (NetApp) Chris Stacey (EMC) Renu Tewari (IBM) 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 week's meeting with this announcement. + Austin NFS Bake-a-thon Wrap-up James reported on his activities at the Bake-a-thon. NFS servers were able to retrieve FSN and FSL information from the LDAP directory James setup with the -03 NSDB schema. Trond posted his Linux FedFS NFS server implementation on linux-nfs.org. Sorin reported on lock testing. + Requirements Draft Update Available at: http://jlentini.users.sourceforge.net/draft-ietf-nfsv4-federated-fs-reqts-05.txt and diff at: http://jlentini.users.sourceforge.net/draft-ietf-nfsv4-federated-fs-reqts-rfcdiff.html Plan is to post to IETF website on 10/16. We discussed the new security considerations text. Renu asked about the paragraph beginning "FSNs are likely to be long lived resources." James explained that this incorporated the discussion on this thread http://www.ietf.org/mail-archive/web/nfsv4/current/msg07436.html + NSDB Draft Update - Adds support for an arbitrary NSDB search base (NSDB Container Entry) As we discussed last week, the requirement that the NSDB's LDAP DIT is rooted at "o=fedfs" will be removed to allow for more flexibility in configurations. To accomplish this, the distinguished name of the LDAP entry containing the FedFS subtree becomes a new NSDB attribute. We discussed names for this entry. The current proposal is to call this the NSDB Container Entry (NCE). NCE appears to convey the intended meaning and doesn't collide with another relevant acronym. - New attributes for fls_info fields Nico suggested breaking the fedfsNfsInfo attribute into its individual fields at the Bake-a-thon. This sounds like a good idea. It allows searching on the individual fields. James is preparing this for the next NSDB draft update. - Updates examples Some reviewers have asked for clarifications on the examples. James did a pass over the example text and clarified a few points. + Admin Draft Update - Trust Anchors Nico suggested that the Admin protocol either include support for trust anchor management or reference a protocol like TAMP: http://www.ietf.org/id/draft-ietf-pkix-tamp-03.txta His concern is that there be a secure channel for an administrative node to communicate TA information (especially self-signed NSDB certificates) from the NSDB to the fileserver. We'll need to discuss how to meet this requirement. + NFSv4 Migrations We reviewed how migrations work in NFSv4 and discussed the differences between the fs_locations information in NFSv4 and the fs_locations_info information in NFSv4.1.
- [nfsv4] FedFS Meeting Minutes, 10/15/2009 James Lentini