Tentative schedule for the new Telnet implementation for the TIP
Implementation schedule for the TIP's new Telnet protocol
Walden, D.C., "Tentative schedule for the new Telnet implementation for the TIP", RFC 688, DOI 10.17487/RFC0688, June 1975, <https://www.rfc-editor.org/info/rfc688>.
@misc{rfc688,
series = {Request for Comments},
number = 688,
howpublished = {RFC 688},
publisher = {RFC Editor},
doi = {10.17487/RFC0688},
url = {https://www.rfc-editor.org/info/rfc688},
author = {D.C. Walden},
title = {{Tentative schedule for the new Telnet implementation for the TIP}},
pagetotal = 1,
year = 1975,
month = jun,
} RFC text
Network Working Group David C. Walden
RFC # 688 BBN
NIC # 32655 June 4, 1975
Tentative Schedule for the New
TELNET Implementation for the TIP
Implementation of the New TELNET Protocol has now become the top
priority item on the TIP development queue. Because what is done in the
TIP potentially affects what is done at a number of hosts, below we give
the implementation schedule to which we hope to adhere.
- July 18, 1975 -- Done with the basic design. A version of the TIP
which has a general version of the option negotiator, but refuses
all options, operational.
- Mid-September, 1975 -- Design of the options done. A version of
the TIP which includes any modifications that are necessary to
support the options operational.
- Mid-November -- Operational version of the TIP with the basic set
of options implemented (Binary Transmission, Echo, Suppress Go-
Ahead, Timing Mark, RCTE).
- End of 1975 -- Any problems with hosts worked out, any necessary
revisions done, and a solid version of the TIP up and running the
TELNET Protocol with options.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 10/99 ]
AI ELI5
On this page
§1The TIP's New Telnet Implementation
RFC 688 is a schedule from BBN for implementing the new Telnet protocol in the TIP (Terminal Interface Processor). The TIP was a network access device that allowed terminal users to log into other hosts on the ARPANET.
The RFC explains that implementing the new Telnet protocol had become the top priority for the TIP development team. Because what the TIP did affected how many hosts could serve remote users, the team shared its implementation schedule publicly so the network community could coordinate.
The TIP was a box that let people use terminals to reach computers on the network. The team shared their work plan publicly because so many people depended on it.
§2The Four-Phase Schedule
The implementation plan had four major milestones, each with a target completion date in 1975. First, by July 18, the team would finish the basic design with a version that could negotiate Telnet options but refused all of them. Next, by mid-September, the design of the options themselves would be complete. Third, by mid-November, a working version supporting the basic option set would run on the TIP: Binary Transmission, Echo, Suppress Go-Ahead, Timing Mark, and RCTE. Finally, by the end of 1975, the team would resolve any problems with host interactions and deploy a stable version of the TIP running the complete Telnet protocol.
The schedule had four steps with dates from mid-1975 to year end. Each step added more features until the whole Telnet protocol worked on the TIP.
§3Impact on the Network
Because the TIP served many hosts and users, delays in its implementation could slow adoption of the new Telnet protocol across the network. By making this schedule public, BBN allowed other host administrators and system planners to anticipate when the TIP would support the new protocol and to schedule their own transitions accordingly. This kind of coordinated planning was essential for maintaining network interoperability during major protocol changes.
Many computers on the network relied on the TIP, so its schedule mattered to everyone. Publishing the dates helped everyone else plan their own work.