Re: Soliciting an Author for the Informational RFC
"Robert G. Moskowitz" <0003858921@mcimail.com> Wed, 14 July 1993 16:11 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07588; 14 Jul 93 12:11 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07584; 14 Jul 93 12:11 EDT
Received: from [128.231.64.10] by CNRI.Reston.VA.US id aa14170; 14 Jul 93 12:11 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 1433; Wed, 14 Jul 93 12:11:24 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 1428; Wed, 14 Jul 93 12:11:19 EDT
Date: Wed, 14 Jul 1993 15:57: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: Re: 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: <9307141211.aa14170@CNRI.Reston.VA.US>
On July 9th I said: >I am currently without anyone to write, as we called it, RFCI. Jon Penner of DCA has volunteered. He has already put together a general framework and is working on filling in details. Our thinking is to minimize the amount of discussion in RFCI on vendor specific details, like IBM's use of TM. I would like to figure out the best way to document vendor specific implementation items. Suggestions are welcome. Also we should review these vendor 'add ins' and design RFCS so they will not be needed. That is to say, if a vendor saw fit to add a feature in, then we should have a recommended implementation that addresses that feature. Comments? 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