Reply to More on implications of 22.2

Urs Eppenberger </c=CH/admd=ARCOM/prmd=SWITCH/o=switch/ou=chx400/s=eppen/@x400-gw.udev.cdc.com> Wed, 06 July 1994 07:22 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21553; 6 Jul 94 3:22 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa21549; 6 Jul 94 3:22 EDT
Received: from mercury91.udev.cdc.com by CNRI.Reston.VA.US id aa13079; 6 Jul 94 3:22 EDT
Received: by mercury.udev.cdc.com; Wed, 6 Jul 94 02:22:06 -0500
X-From: /c=CH/admd=ARCOM/prmd=SWITCH/o=switch/ou=chx400/s=eppen/@x400-gw.udev.cdc.com Wed Jul 6 02:22 CDT 1994
Received: from wally.udev.cdc.com by mercury.udev.cdc.com; Wed, 6 Jul 94 02:22:00 -0500
Received: by wally.udev.cdc.com; Wed, 6 Jul 94 01:48:11 -0500
X400-Received: by /c=us/admd=attmail/prmd=cdc/; Relayed; 06 Jul 94 01:52:33 -0500
X400-Received: by /c=US/admd=/prmd=XNREN/; Relayed; 06 Jul 94 06:52:33 Z
X400-Received: by /c=Ch/admd=Arcom/prmd=Switch/; Relayed; 06 Jul 94 06:52:02 Z
X400-Received: by /c=CH/admd=ARCOM/prmd=SWITCH/; Relayed; 06 Jul 94 08:51:59 +0200
X400-Received: by mta MTAwally in /c=us/admd=attmail/prmd=cdc/; Relayed; 06 Jul 94 01:48:02 -0500
X400-Received: by mta cdc.us in /c=us/admd=attmail/prmd=cdc/; Relayed; 06 Jul 94 01:52:33 -0500
X400-MTS-Identifier: [/c=Ch/admd=Arcom/prmd=Switch/; chx400.swi.442:06.07.94.06.52.02]
Content-Identifier: Reply to More...
Content-Return: Allowed
X400-Content-Type: P2-1984 ( 2 )
Conversion: Allowed
Priority: normal
Disclose-Recipients: Prohibited
Alternate-Recipient: Allowed
X400-Originator: /c=CH/admd=ARCOM/prmd=SWITCH/o=switch/ou=chx400/s=eppen/@x400-gw.udev.cdc.com
X400-Recipients: non-disclosure;
Message-Id: <"14474 Wed Jul 6 08:52:18 1994"@chx400.switch.ch>
Date: Wed, 06 Jul 1994 08:51:59 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Urs Eppenberger </c=CH/admd=ARCOM/prmd=SWITCH/o=switch/ou=chx400/s=eppen/@x400-gw.udev.cdc.com>
X-Orig-Sender: /c=CH/admd=ARCOM/prmd=SWITCH/o=switch/ou=chx400/s=eppen/@x400-gw.udev.cdc.com
To: mhs-ds@mercury.udev.cdc.com
Subject: Reply to More on implications of 22.2

Hello Steve and Kevin,
I just write to the list so you both know that you are not discussing this
issue alone, we're watching too!
The MHS-DS work has, in my view, the primary goal of easing the administration
of X.400 systems. It is of no use at all if we just move the problem to the
Directory administrators. Since the Directory is decoupled from the
real mail hosts and user accounts, it is much easier to have a messed up
Directory than a messed up user configuration on a mail host. And the
latter is already difficult enough.
I suggest that much care has to be taken to ease the administration.
The implementors of X.500 applications need to think a little bit harder
to offer fast reponses, but that's their hard luck, and there are much
less developers than mail and directory system administrators.

I think one of the problems of lacking envolvement of the MHS managers
in hte MHS-DS work is that we have a nice concept on paper but severely
lack any clear view on how to use this to ease the daily work, at the moment
it looks definitely as much more trouble.

Maybe I'm a little to negative because I'm growing too old and like to
stick to the configuration tables I (almost) understand in the mean time. ;-)

Kind regards,

Urs.