IETF Logo Mail Archive

Re: [nfsv4] [FedFS] Meeting Minutes, 12/10/2009

Nicolas Williams <Nicolas.Williams@sun.com> Wed, 16 December 2009 22:23 UTC

Return-Path: <Nicolas.Williams@sun.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 6F8E23A68F5 for <nfsv4@core3.amsl.com>; Wed, 16 Dec 2009 14:23:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.01
X-Spam-Level:
X-Spam-Status: No, score=-5.01 tagged_above=-999 required=5 tests=[AWL=-0.776, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, SARE_SPEC_REPLICA_OBFU=1.812]
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 6Cw+DYsORJlK for <nfsv4@core3.amsl.com>; Wed, 16 Dec 2009 14:23:31 -0800 (PST)
Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by core3.amsl.com (Postfix) with ESMTP id 9E0DF3A68C8 for <nfsv4@ietf.org>; Wed, 16 Dec 2009 14:23:31 -0800 (PST)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id nBGMNHF1019771 for <nfsv4@ietf.org>; Wed, 16 Dec 2009 22:23:17 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id nBGMNHqu013023 for <nfsv4@ietf.org>; Wed, 16 Dec 2009 15:23:17 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id nBGMFlFh005605; Wed, 16 Dec 2009 16:15:47 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id nBGMFliq005604; Wed, 16 Dec 2009 16:15:47 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 16 Dec 2009 16:15:47 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: James Lentini <jlentini@netapp.com>
Message-ID: <20091216221547.GP1516@Sun.COM>
References: <alpine.LFD.2.00.0912101628360.18058@jlentini-linux.nane.netapp.com> <20091214233450.GR1516@Sun.COM> <alpine.LFD.2.00.0912161619560.18058@jlentini-linux.nane.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.00.0912161619560.18058@jlentini-linux.nane.netapp.com>
User-Agent: Mutt/1.5.7i
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] [FedFS] Meeting Minutes, 12/10/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: Wed, 16 Dec 2009 22:23:32 -0000

On Wed, Dec 16, 2009 at 04:48:01PM -0500, James Lentini wrote:
> I like the idea of passing the NSDB cert in the ONC/RPC Admin 
> protocol. I will start working on an update to the Admin protocol with 
> this capability.
> 
> Are there alternatives to publishing the replica certs in the NSDB? I 
> can't think of a natural place for these certs in our current schema 
> and DIT structure.

You can always define such a schema.  There's a standard schema defining a
certificate attribute; all you need to add is a schema for identifying
objects that have a certificate attribute and which represent replicas.

(There's an altServer standard attribute of the rootDSE, but it
identifies replicas by URI, not by DN, so it's not good enough to find
objects whose certificate attribute values are the NSDB's servers'
certs.)

Nico
--

v2.23.0 | Report a Bug | By Email