Re: Proposed revised OSI-DS charter
Sylvain Langlois <Sylvain.Langlois@der.edf.fr> Tue, 09 March 1993 15:42 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04901; 9 Mar 93 10:42 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04897; 9 Mar 93 10:42 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa07264; 9 Mar 93 10:42 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.02301-0@haig.cs.ucl.ac.uk>; Tue, 9 Mar 1993 14:36:55 +0000
Via: uk.ac.uknet-relay; Tue, 9 Mar 1993 14:36:48 +0000
Received: from mcsun.EU.net by ben.uknet.ac.uk via EUnet with SMTP (PP) id <sg.10237-0@ben.uknet.ac.uk>; Tue, 9 Mar 1993 14:36:27 +0000
Received: from chenas.inria.fr by mcsun.EU.net with SMTP id AA03562 (5.65b/CWI-2.209); Tue, 9 Mar 1993 15:36:21 +0100
Received: from edf.edf.fr by chenas.inria.fr (5.65c8d/92.02.29) via Fnet-EUnet id AA01793; Tue, 9 Mar 1993 15:36:00 +0100 (MET)
Received: from cli51jo.der.edf.fr by edf.edf.fr with SMTP id AA06353 (5.65c8/IDA-1.4.4); Tue, 9 Mar 1993 15:37:19 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Sylvain Langlois <Sylvain.Langlois@der.edf.fr>
Reply-To: Sylvain.Langlois@der.edf.fr
To: Erik Huizer <Erik.Huizer@surfnet.nl>
Cc: Steve Hardcastle-Kille <S.Kille@isode.com>, osi-ds@cs.ucl.ac.uk
Subject: Re: Proposed revised OSI-DS charter
In-Reply-To: Erik Huizer's message of 09 Mar 93 11:11:37 +0000. <9303091110.AA11987(a)survival.surfnet.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 09 Mar 1993 15:37:43 +0100
Message-Id: <5777.731687863@cli51jo.der.edf.fr>
Original-Sender: sylvain@cli51jo.der.edf.fr
X-Orig-Sender: sylvain@cli51jo.der.edf.fr
> > The WG will not be directly concerned with piloting > > and service activities, but will liaise with such activities. Are we sure we don't want piloting here. From what has been discussed at the Washington meeting, MHS-DS will start pilot MHS use of the Directory. I think it is good. There are two steps in piloting: 1) defining the role and objectives of the pilot 2) making the pilot run (a third phase would be the final analysis of the pilot). I think OSI-DS would be the right place to define pilot operations. The whole infrastructure (funding, admin., ...) will certainly not be part of OSI-DS scope. Scope and goals definition is (at the same level as metrics definitions done so far and stated below! > Tasks and Issues [...] > 2. Describe X.500 test strategies; Specifically define metrics for measuring > and comparing DSA and DUA performance. An already existing ID deals with national character sets. Shouldn't this be a well identifed task? > > Goals and Milestones: Do we all agree on the milestones (i.e. priorities)? The priority issue has been raised in Washington, but I'm not sure any decision was taken other than listing the important goals. Sylvain ---------------- Sylvain.Langlois@der.edf.fr
- Proposed revised OSI-DS charter Steve Hardcastle-Kille
- Re: Proposed revised OSI-DS charter Erik Huizer
- Re: Proposed revised OSI-DS charter Sylvain Langlois
- Re: Proposed revised OSI-DS charter Edwards Reed
- Re: Proposed revised OSI-DS charter Erik Huizer
- Re: Proposed revised OSI-DS charter Steve Hardcastle-Kille