WE MUST CHANGE THE NOMENCLATURE!!

Mike O'Dell <mo@uunet.uu.net> Thu, 04 May 1995 22:15 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16566; 4 May 95 18:15 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16562; 4 May 95 18:15 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17798; 4 May 95 18:15 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16554; 4 May 95 18:15 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa16550; 4 May 95 18:15 EDT
Received: from [153.39.130.10] by CNRI.Reston.VA.US id aa17785; 4 May 95 18:15 EDT
Received: by rodan.UU.NET id QQyohw24219; Thu, 4 May 1995 17:07:27 -0400
Date: Thu, 04 May 1995 17:07:27 -0400
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mike O'Dell <mo@uunet.uu.net>
Message-Id: <QQyohw24219.199505042107@rodan.UU.NET>
To: iesg@CNRI.Reston.VA.US
Subject: WE MUST CHANGE THE NOMENCLATURE!!

I quote from the May 1, 1995 issue of Network World. Page 5, "Briefs"
section.  To wit:

     DLSw Gets a Number

     The Internet Engineering Task Force last week designated
     the Data Link Switching (DLSw) specification designed by
     the APPN Implementors Workshop as informational RFC 1795.
     The designation helps to further legitimize DLSw, which
     lets Systems Network Architecture and NETBIOS data flow
     over TCP/IP nets.



When you have major press outlets propagating the bogosity,
there is nothing you can put on the front of the document because
nobody will take the trouble to read it.

The only alternative is to kill the "RFC" where it stands.

I also note that on page 34 there is also an article on whether
RFC 1490 will doom DLSw.  hehe

     -mo