Reply to MHS-DS: Changing the tree (OUCH)

"Kevin E. Jordan" <Kevin.E.Jordan@cdc.com> Tue, 01 March 1994 14:56 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03540; 1 Mar 94 9:56 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03536; 1 Mar 94 9:56 EST
Received: from [129.179.88.193] by CNRI.Reston.VA.US id aa07206; 1 Mar 94 9:56 EST
Received: by mercury.udev.cdc.com; Tue, 1 Mar 94 08:55:51 -0600
X-From: kej@mercury.udev.cdc.com Tue Mar 1 08:55 CST 1994
Received: from wally.udev.cdc.com by mercury.udev.cdc.com; Tue, 1 Mar 94 08:55:49 -0600
Received: from mercury91.udev.cdc.com by wally.udev.cdc.com; Tue, 1 Mar 94 08:48:03 +0600
To: "Harald T. Alvestrand" <Harald.T.Alvestrand@uninett.no>
cc: mhs-ds@mercury.udev.cdc.com
Subject: Reply to MHS-DS: Changing the tree (OUCH)
In-reply-to: Your message of "Tue, 01 Mar 94 14:59:39 +0100" <2d734a55190a002@zeus.cdc.com>
Date: Tue, 01 Mar 1994 08:55:38 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Kevin E. Jordan" <Kevin.E.Jordan@cdc.com>
Message-Id: <2d7355a31d39002@wally.udev.cdc.com>

> Other documents should remain basically unchanged, but the examples
> need to be examined with care.
> What do people think?

I think that it is a simple and clean solution, and the proposed editorial
changes show that it is consistent with handling of special ADMD names.  Your
suggestion of using aliases to create backward compatibility is also quite
clever.