Soliciting an Author for the Informational RFC
"Robert G. Moskowitz" <0003858921@mcimail.com> Fri, 09 July 1993 21:48 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08983; 9 Jul 93 17:48 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08979; 9 Jul 93 17:48 EDT
Received: from list.nih.gov by CNRI.Reston.VA.US id aa26271; 9 Jul 93 17:48 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 1069; Fri, 09 Jul 93 17:49:15 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 1064; Fri, 09 Jul 93 17:45:12 EDT
Date: Fri, 09 Jul 1993 20:08:00 +0000
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: "Robert G. Moskowitz" <0003858921@mcimail.com>
Subject: Soliciting an Author for the Informational RFC
X-To: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9307091748.aa26271@CNRI.Reston.VA.US>
I am currently without anyone to write, as we called it, RFCI. I have asked a couple of people and am waiting for an answer. I have one person that said that if someone else can't he can squeeze it in. What is needed is someone to document the current practice in the protocol. Vendor specific features had best be covered in some special vendor documents that we publish outside of the RFC process. Perhaps our anonymous server would be the place for that. Comments on the structure of RFCI can be sent to this list. Volunteers can EMail me directly. Robert Moskowitz Chrysler Corp TN3270E WG Chair
- Soliciting an Author for the Informational RFC Robert G. Moskowitz
- Re: Soliciting an Author for the Informational RFC Robert G. Moskowitz