Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsds-infotree-05, draft-ietf-mhsds
Mark Crispin <MRC@panda.com> Sat, 09 July 1994 22:15 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04022; 9 Jul 94 18:15 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04010; 9 Jul 94 18:14 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa11258; 9 Jul 94 18:14 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04001; 9 Jul 94 18:14 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03979; 9 Jul 94 18:13 EDT
Received: from tomobiki-cho.cac.washington.edu by CNRI.Reston.VA.US id aa11238; 9 Jul 94 18:13 EDT
Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA08689; Sat, 9 Jul 94 15:13:32 -0700
Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA21974; Sat, 9 Jul 94 15:13:20 -0700
Date: Sat, 09 Jul 1994 15:01:04 -0700
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Crispin <MRC@panda.com>
X-Orig-Sender: Mark Crispin <mrc@ikkoku-kan.panda.com>
Subject: Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsds-infotree-05, draft-ietf-mhsds
To: Alyson L Abramowitz <ala@lunacity.com>
Cc: "Donald E. Eastlake 3rd (Beast)" <dee@skidrow.lkg.dec.com>, ietf@CNRI.Reston.VA.US
In-Reply-To: <LyP8oc3w165w@LunaCity.com>
Message-Id: <MailManager.773791264.18656.mrc@Ikkoku-Kan.Panda.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"
Alyson, I also remember you telling me 10 or so years ago that X.400 was going to kill RFC-822; that *EVERY* vendor was solidly behind X.400 and eager to kill RFC-822 mail. Perhaps in this question, too, you are jumping the gun. I do not see how a decision made inside the OSI context affects the IETF context in the absence of the agreement of the IETF. The 1985-88 decision was not a decision of the IETF; and whether that decision is ratified or rejected by the IETF remains to be seen. I think that Don's point was that using the unqualified term ``The Directory'' in IETF documents implies a fait accompli. There are individuals who dispute this point. Pending a formal IESG decision that the term ``The Directory'' in the IETF sense refers exclusively to the X.500 sense, it seems to me to be preferable to use greater qualification. Attempts to present a matter as a fait accompli are likely to stiffen and strengthen opposition. It won't be the first time that a proposal has been rejected because the proponents were perceived as attempting to ram it through without judgement or recourse. -- Mark --
- draft-ietf-mhsds-subtrees-05, draft-ietf-mhsds-in… Theodore Ts'o
- re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Donald E. Eastlake 3rd (Beast)
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Iain K. Hanson
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Mike O'Brien
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Donald E. Eastlake 3rd (Beast)
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Sylvain Langlois
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Donald E. Eastlake 3rd (Beast)
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Christian Huitema
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Alyson L Abramowitz
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Donald E. Eastlake 3rd (Beast)
- re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… David Herron
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Mark Crispin
- Re: draft-ietf-mhsds-subtrees-05, draft-ietf-mhsd… Lars-Johan Liman SUNET