CARVIEW |
Select Language
HTTP/2 200
date: Thu, 17 Jul 2025 01:23:24 GMT
content-type: text/html; charset=utf-8
content-security-policy: default-src 'self' 'unsafe-inline' data: https://datatracker.ietf.org/ https://www.ietf.org/ https://ietf.org/ https://analytics.ietf.org https://static.ietf.org; frame-ancestors 'self' ietf.org *.ietf.org meetecho.com *.meetecho.com
cross-origin-opener-policy: unsafe-none
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=3600; includeSubDomains
vary: Cookie, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
cf-cache-status: REVALIDATED
expires: Thu, 17 Jul 2025 05:23:24 GMT
cache-control: public, max-age=14400
server: cloudflare
cf-ray: 9605ef0b4d26e084-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
RFC 593 - Telnet and FTP implementation schedule change
Report a datatracker bug
Network Working Group Alex McKenzie Request for Comments: 593 BBN Jon Postel MITRE Telnet and FTP Implementation Schedule Change Telnet and FTP Implementation Schedule Change We have been contacted by several Telnet implementers and concerned users regarding the scheduled changeover from old to new Telnet. There is a good deal of concern about accomplishing a coordinated changeover especially in light of the potential incompatibilities (RFC 559, NIC18482). Therefore the changeover is reformulated as follows. New Telnet implementations are to be ready 1 Jan 74 (as before), but are to use ICP socket 23 (decimal). That is the server Telnet will listen on socket 23, and user Telnet programs will connect to socket 23. It will also be useful for the user program to let the user optionally select the server socket, as many user Telnet programs currently do. It will also be useful for implementers to consider a server Telnet program capable of dealing with both protocols as MIT- DMCG has done (RFC 559). This will provide an opportunity for testing and debugging the new programs in a way that does not interfere with normal use. During January we will survey the technical liaisons to determine the status of the Telnet implementations. As soon as we determine that the Telnet implementations have reached a point where the changeover can be made without disruption of user services the technical liaisons will be notified. In light of this change in the Telnet implementation schedule, the FTP schedule is also modified. New FTP implementations are to be ready by 1 Feb 74 (as before), but will continue to use ICP socket 21 (decimal) until we can determine that a changeover is appropriate. References Telnet Protocol NIC 18639 File Transfer Protocol NIC 17759 [This RFC was put into machine readable form for entry ] [into the online RFC archives by Mirsad Todorovac 5/98 ] McKenzie & Postel [Page 1]
Datatracker
RFC 593
RFC
- Unknown
Document | Document type |
RFC
- Unknown
November 1973 Report errata
This RFC is labeled as "Legacy"; it was published before a formal source was recorded.
This RFC is not endorsed by the IETF and has no formal standing in the
IETF standards process.
|
|
---|---|---|---|
Select version | |||
Authors |
Email authors |
||
RFC stream | Legacy | ||
Other formats |