Re: Proposed Telnet MPX Option

[[e-mail]]

Two questions:

	1.  While the problem statement is credible, it seems
	    strange to attempt its solution within the context
	    of a Telnet option as opposed to creation of a new
	    service on a new WKS.  It is also difficult to see
	    any advantages to inverting the structure in this
	    way.  The disadvantages seem too numerous to list,
	    but one interesting one is the apparent difficulty
	    in preserving the Telnet Synch functionality as descr
	    in RFC854 pp 8-10, and particularly preserving inter
	    operability of any URGENT functions at all given that
	    at least some systems must use the bizarre URGENT
	    processing concept propounded by Comer & Stevens.
	    	Since these objections must have been foreseeable
	    there must be a sound rationale for postulating this
	    as a TELNET option instead of postulating a protocol
	    for multiplexing data streams SIMILAR to those moved
	    by TELNET.  It would help to hear this rationale.
	
	2.  Per Section 6, an echo request every 10 seconds?????\
	    For each host/terminal mux pair active?  Across WANs?

A comment:

> 4. Motivation for the option.
> On most of the UNIX (tm) machines implementing the ARPA protocol
>     stack, the application traffic is character mode oriented.

--- What decade is this???

Constructively yours - Greg Bailey