Tentative schedule for the new Telnet implementation for the TIP
A tentative schedule for adding the new TELNET protocol and options to the TIP.
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 ]
ISO Plain Language
On this page
§1Why the TIP Schedule Was Shared
David Walden says implementation of the new TELNET protocol had become the top priority in the TIP development queue. Since TIP work could affect what other hosts did, BBN shared the schedule it hoped to follow.
The schedule is described as tentative. It gives target dates and planned capabilities rather than reporting completed work.
Changes to the TIP could affect other hosts, so BBN published its planned work dates. The RFC presents them as targets, not as completed milestones.
§2Design and Option Milestones
By July 18, 1975, the basic design was to be complete and a TIP version with a general option negotiator was to be operational, though it would refuse all options. By mid-September, the design of the options was to be complete, with an operational version containing necessary option support.
These milestones move from basic negotiation capability to the design work needed to support options.
The first target is a working negotiator that refuses all options. A later target completes the design of the options themselves.
§3The Planned Option Set and Final Version
By mid-November, BBN hoped to have an operational TIP version with Binary Transmission, Echo, Suppress Go-Ahead, Timing Mark and RCTE options. By the end of 1975, the schedule aimed to resolve host problems, make necessary revisions and have a solid TIP version running the TELNET protocol with options.
The RFC gives these as intended milestones and does not include a later progress report.
The planned option set included Binary Transmission, Echo, Suppress Go-Ahead, Timing Mark and RCTE. The final target was a stable version by the end of 1975, after host issues were addressed.