Re: Providing a DS: re:scenarios for Directory Synchronization
Alan Wong <wong@vancouver.osiware.bc.ca> Fri, 28 July 1995 02:34 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22703; 27 Jul 95 22:34 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa22699; 27 Jul 95 22:34 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa10169; 27 Jul 95 22:34 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.06512-0@haig.cs.ucl.ac.uk>; Fri, 28 Jul 1995 00:30:38 +0100
Received: from osison.osiware.bc.ca by bells.cs.ucl.ac.uk with Internet SMTP id <g.02877-0@bells.cs.ucl.ac.uk>; Fri, 28 Jul 1995 00:30:04 +0100
Received: by osison.osiware.bc.ca (4.1/SMI-4.1) id AA16987; Thu, 27 Jul 95 16:29:21 PDT
Date: Thu, 27 Jul 1995 15:48:00 -0700
X400-Trace: ca*infonet*iss; Arrival 27 Jul 95 15:48 PDT Action: Relayed
Priority: urgent
Ua-Content-Id: 950727754
P1-Message-Id: ca*infonet*iss;95072715485116592105
Original-Encoded-Information-Types: IA5-Text
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Alan Wong <wong@vancouver.osiware.bc.ca>
To: awon@vancouver.osiware.bc.ca
Cc: osi-ds@cs.ucl.ac.uk
In-Reply-To: <950614121501.20203a34@hss.hns.com>
Message-Id: <950727754*wong@vancouver.osiware.bc.ca>
Subject: Re: Providing a DS: re:scenarios for Directory Synchronization
Importance: High
>I, also, feel that Email requirements are going to >force corporations to go for X.500 directory service MUCH SOONER than >every thing else. Yes, and corporations are starting to look very closely at X.500. On the 'floor' at the recent EMA and EEMA tradeshows the talk was all about how X.500 has now arrived, particularly after the multi-vendor interworking demonstration at EEMA. Its been a long time coming but... >Further, E-mail directory service is very closely >linked with the mail gateway & Directory synchronisation products >which are build by different vendors. Different vendors for mail >gateway and Directory synchronisation products need to have a "common >vision of Directory schema". Otherwise, organisations will be stuck with >a specific vendor (just like a propietory story of legacy systems). >Hence, before an organisation starts on a directory service as >defined in Scenario-1, somehow, this piece of the puzzle has to fit >with the other corporate requirements for Directory service. One >solution is to standardize a schema for mail gateway & Direc. Synch. >requirements. There are actually two different thing here. Schema is one, and synchronisation is the other. Outside of synchronisation there are reasons to have common schema understandings between organisation, and indeed I think there is OIW work going on looking at such issues. On the synchronisation side, there need to be common agreements as to how to make data available to X.500. Such an agreement is the Directory Sync format defined by the XAPIA based upon the 1993 X.500 DISP protocol. Putting these two together, to synchronise you don't actually need schema agreements, DISP will work fine without. However, once synchronised, for an application to make use of the data you do need common schema definitions. One way to arrive at a common set of schema would be to update RFC 1274 (dated 1991) to merge in the X.500(93) schema and extend it to meet current requirements. Colin
- Providing a DS: re:scenarios for Directory Synchr… peter (p.w.) whittaker
- Re: Providing a DS: re:scenarios for Directory Sy… Colin Robbins
- RE: Providing a DS: re:scenarios for Directory Sy… Praveen Gupta, x2106
- Re: Providing a DS: re:scenarios for Directory Sy… Alan Wong