Re: scenarios for Directory Synchronization
"Praveen Gupta, x2106" <PGUPTA@hss.hns.com> Wed, 14 June 1995 00:06 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08627; 13 Jun 95 20:06 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08623; 13 Jun 95 20:06 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa19493; 13 Jun 95 20:06 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.03447-0@haig.cs.ucl.ac.uk>; Tue, 13 Jun 1995 22:23:35 +0100
Received: from cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.03063-0@bells.cs.ucl.ac.uk>; Tue, 13 Jun 1995 22:23:18 +0100
Return-Path: <PGUPTA@hss.hns.com>
Received: from hns.com by bells.cs.ucl.ac.uk with Internet SMTP id <g.21207-0@bells.cs.ucl.ac.uk>; Tue, 13 Jun 1995 08:44:52 +0100
Received: from kanchan.hss.hns.com (hss.hns.com. [139.85.242.2]) by hnssysa.hns.com (8.6.12/8.6.9) with SMTP id DAA15872 for <osi-ds-request@cs.ucl.ac.uk>; Tue, 13 Jun 1995 03:44:40 -0400
Date: Tue, 13 Jun 1995 13:15:58 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Praveen Gupta, x2106" <PGUPTA@hss.hns.com>
To: bjjenni@somnet.sandia.gov
CC: osi-ds-request@cs.ucl.ac.uk, PGUPTA@hss.hns.com
Message-Id: <950613131558.20201094@hss.hns.com>
Subject: Re: scenarios for Directory Synchronization
Resent-To: osi-ds@cs.ucl.ac.uk
Resent-Date: Tue, 13 Jun 1995 22:23:12 +0100
Resent-Message-ID: <3061.803078592@cs.ucl.ac.uk>
Resent-From: Postmaster@cs.ucl.ac.uk
Hi Barbara, > I agree with your evaluation of Scenario-1. Scenario-2 however, > I offer caution. We had to make this 'corporate' data, i.e. owned > and managed by corporate, due to the descrepencies between LANs. > Prior to heterogeneously operative e-mail in out corporation, > many users had more than one e-mail address. Defining a 'preferred > address' was very time consuming. LAN managers, were of little or > no help because they couldn't help us identify the users preference. This is where Directory Synchronisation will help. I recommend that users SHOULD continue to use native addressing. Besides, each user has a global e-mail address to which this native address will map. Now, directory synchronisation will help maintaining this mapping as one-to-one between global address and the native address. > In some cases the users themselves were unsure of a preferred address > because this was so well hidden via menus, auto logins, etc. Eventually > is meant contacting those users with one or more account, creating a > group to provide support and maintenance of the e-mail addresses, > and a work around to allow users more than one e-mail address. Obviously, if a user has more that one e-mail accounts then he/she will be represented twice in the global directory. Of course, Directory synchronisation will have functionality of NOT TO Synchronise a specific LAN mail account. In this way, lan mail user who is not synchronised will not be accessable globally. > > Don't under estimate the problems associated with directory > sunchronization or unique e-mail addresses. Thanks and regards, Praveen
- scenarios for Directory Synchronization PGUPTA
- Re: scenarios for Directory Synchronization Barbara Jennings
- Re: scenarios for Directory Synchronization Praveen Gupta, x2106
- Re: scenarios for Directory Synchronization Colin Robbins
- Re: scenarios for Directory Synchronization Praveen Gupta, 91-11-6470831/32 x2106
- Re: scenarios for Directory Synchronization Lawrence Hutson
- Re: scenarios for Directory Synchronization Alan Wong
- Re: scenarios for Directory Synchronization Alan Wong
- Re: scenarios for Directory Synchronization Alan Wong
- Re: scenarios for Directory Synchronization Alan Wong
- Re: scenarios for Directory Synchronization Barbara Jennings