Re: List of Old Standards to be retired

Eliot Lear wrote:

> If you see a document on the list below and you know it to be in use, 
> would you please reply to this message indicating the RFC number, and 
> whether you believe the doc should be advanced beyond proposed?  Also, 
> if you know of work to update anything on the list below, please include 
> that.  A note along these lines is generally sufficient to remove a 
> document from the list below.

I am a fairly good contact point for most things "TELNET".  Back in June 
1999 the Application Area Directors, Keith Moore and Patrik Falstrom, 
performed a review of TELNET RFCs to move unused ones to HISTORIC.  This 
was done in consultation with the subscribers to the telnet-wg@bsdi.com 
mailing list.  All of the remaining Telnet options were determined to be 
implemented in various widely deployed implementations.

> RFC0698       Telnet extended ASCII option
> RFC0726       Remote Controlled Transmission and Echoing Telnet option
> RFC0727       Telnet logout option
> RFC0735       Revised Telnet byte macro option
> RFC0736       Telnet SUPDUP option
> RFC0749       Telnet SUPDUP-Output option
> RFC0779       Telnet send-location option
> RFC0885       Telnet end of record option
> RFC0927       TACACS user identification Telnet option
> RFC0933       Output marking Telnet option
> RFC0946       Telnet terminal location number option
> RFC1041       Telnet 3270 regime option
> RFC1043       Telnet Data Entry Terminal option: DODIIS implementation
> RFC1053       Telnet X.3 PAD option
> RFC1372       Telnet Remote Flow Control Option

Since the requirement for moving to historic under the cruft draft is 
that it is not widely implemented, all of these options must remain.
If there is desire to move these options to historic, then the guideline 
must be altered.

Jeffrey Altman

Re: List of Old Standards to be retired

Attachment: smime.p7s