Re: MHS-DS & ISO/IEC Oslo output (1991)

"Harald T. Alvestrand" <Harald.T.Alvestrand@uninett.no> Wed, 14 September 1994 13:35 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03183; 14 Sep 94 9:35 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03179; 14 Sep 94 9:35 EDT
Received: from alias-129-179-91-61.cdc.com by CNRI.Reston.VA.US id aa06857; 14 Sep 94 9:35 EDT
Received: from sequoia.udev.cdc.com by mhub61.udev.cdc.com; Wed, 14 Sep 94 08:40:19 -0600
Received: from mercury91.udev.cdc.com by sequoia.udev.cdc.com; Wed, 14 Sep 94 08:33:46 -0600
Received: by mercury.udev.cdc.com; Wed, 14 Sep 94 08:34:27 -0500
X-From: Harald.T.Alvestrand@uninett.no Wed Sep 14 08:34 CDT 1994
Received: from zeus.cdc.com by mercury.udev.cdc.com; Wed, 14 Sep 94 08:34:18 -0500
Received: from domen.uninett.no by zeus.cdc.com; Wed, 14 Sep 94 07:49:00 -0500
Received: from localhost by domen.uninett.no with SMTP (PP) id <23118-0@domen.uninett.no>; Wed, 14 Sep 1994 14:47:16 +0200
To: Steve Kille <S.Kille@isode.com>
cc: J.C.H.Martin@frec.bull.fr, mhs-ds@mercury.udev.cdc.com
Subject: Re: MHS-DS & ISO/IEC Oslo output (1991)
In-reply-to: Your message of "Tue, 06 Sep 1994 13:59:21 BST." <8314.778856361@glengoyne.isode.com>
Content-type: Text/plain; charset=ISO-8859-1
Content-transfer-encoding: 8bit
Date: Wed, 14 Sep 1994 14:47:14 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Harald T. Alvestrand" <Harald.T.Alvestrand@uninett.no>
Message-Id: <2e76f13d1c8a002@zeus.cdc.com>

I spent most of the Oslo meeting working with Rob Willmott to get
the architecture of the drafts into closer alignment with each other.

My feeling at the moment is that it is best to gather some experience
with the MHS-DS way of doing things before progressing the ISO work.

But it would be good to plan for a meeting that has ISO blessing in
order to input the MHS-DS experiences into the ISO work, so that the
experiences learned can be shared.

(parenthesis: there is no formal reason, I think, why the ISO work that
uses X.500 cannot simply be replaced by the MHS-DS documents - but the
ISO work also covers usage of CMIP and some environments where X.500 is
not available. This means that MHS-DS can replace only part of the ISO
work, and that an "integration" effort must be done even if the MHS-DS
work is perfect - which it probably isn't; nothing is)

              Harald A