luname_print

John C Klensin <KLENSIN@infoods.unu.edu> Fri, 04 March 1994 16:50 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07020; 4 Mar 94 11:50 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07011; 4 Mar 94 11:50 EST
Received: from list.nih.gov by CNRI.Reston.VA.US id aa10178; 4 Mar 94 11:50 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 7386; Fri, 04 Mar 94 11:46:40 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 7384; Fri, 04 Mar 94 11:46:20 EST
Date: Fri, 04 Mar 1994 11:40:07 -0500
Reply-To: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
X-Orig-Sender: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John C Klensin <KLENSIN@infoods.unu.edu>
Subject: luname_print
X-To: 3858921@mcimail.com
X-cc: tn3270e@list.nih.gov
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9403041150.aa10178@CNRI.Reston.VA.US>

Bob,

We discussed this document during yesterday's IESG teleconference.
We are very reluctant to publish a document as an RFC when you are
about to release a "better way".  Labels as "informational" or
"experimental" aren't enough--there is just too long a history of people
interpreting them as standards/recommendations and implementing them.

I would suggest the following:

 o You move ahead as efficiently as possible with the "real" extensions
     document.
 o Until that document is finished (a couple of months?) you put
     luname_print on ice as an Internet-Draft (i.e., just leave it there).
 o Once you finish the extensions document, you review luname_print
     to see if publication would still have value.  If so, you revise
     it to reflect its exact relationship to the standards-track
     extensions doc.

--john