Proposed LIDS Working Group
Ken Weiss <krweiss@chip.ucdavis.edu> Wed, 09 March 1994 18:06 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08504; 9 Mar 94 13:06 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08498; 9 Mar 94 13:06 EST
Received: from ucdavis.ucdavis.edu by CNRI.Reston.VA.US id aa12413; 9 Mar 94 13:06 EST
Received: from localhost by ucdavis.ucdavis.edu (8.6.5/UCD2.50) id JAA24586; Wed, 9 Mar 1994 09:40:28 -0800
X-Orig-Sender: ietf-wnils-request@ucdavis.edu
Received: from chip.ucdavis.edu by ucdavis.ucdavis.edu (8.6.5/UCD2.50) id JAA22433; Wed, 9 Mar 1994 09:26:08 -0800
Received: from [128.120.80.130] by chip.ucdavis.edu (8.6.5/UCD2.50) id JAA23491; Wed, 9 Mar 1994 09:28:40 -0800
Message-Id: <199403091728.JAA23491@chip.ucdavis.edu>
X-Sender: cckweiss@bullwinkle.ucdavis.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 09 Mar 1994 09:26:24 -0800
To: ietf-wnils@ucdavis.edu, osi-ds@cs.ucl.ac.uk, solo@pamir.inria.fr
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ken Weiss <krweiss@chip.ucdavis.edu>
Subject: Proposed LIDS Working Group
Cc: wps@surfnet.nl
I strongly agree with Paul-Andre's comment that the "white pages" service should be extensible enough to serve as an index to documents as well as people. The aspect of Whois++ that interests me the most is the way the specification has evolved from a very limited white pages service to a generalized tool for publishing and managing distributed databases. Now, if the code can just catch up to the specification... :-) To accomplish this flexibility I think the protocol will need to provide a very rich set of negotiation options between the client and the server. For that reason I'm a little concerned by Erik's suggestion that the architecture, schema and search/maintenance engine efforts be separated. I think it will be difficult for the developers of the search/maintenance engine to proceed without full participation in the development of the architecture that defines the possible interactions between client and server. On the other hand, I agree that one really big workgroup probably won't get anything done at all. I guess this isn't so much a comment as a warning flag. The coordination and organization of these efforts will be a major issue, and probably ought to be addressed explicitly in the charter. --Ken ----------------------------------------------------------------------- Ken Weiss krweiss@ucdavis.edu Distributed Computing Analysis & Support 916/752-5554 (voice) 15 Olson Hall 916/752-9158 (fax) U.C. Davis Davis, CA 95616
- Proposed LIDS Working Group Tim Howes
- Re: Proposed LIDS Working Group pays
- Re: Proposed LIDS Working Group Erik Huizer (SURFnet BV)
- Re: Proposed LIDS Working Group Erik Huizer (SURFnet BV)
- Re: Proposed LIDS Working Group pays
- Re: Proposed LIDS Working Group Erik Huizer (SURFnet BV)
- Re: Proposed LIDS Working Group Tim Howes
- Proposed LIDS Working Group Ken Weiss
- Re: Proposed LIDS Working Group Erik Huizer (SURFnet BV)