Re: draft-cameron-tmux-01.txt

Dave Crocker <dcrocker@mordor.stanford.edu> Tue, 16 November 1993 23:14 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16679; 16 Nov 93 18:14 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16675; 16 Nov 93 18:14 EST
Received: from basil.xylint.co.uk by CNRI.Reston.VA.US id aa24820; 16 Nov 93 18:14 EST
Received: from Mordor.Stanford.EDU by basil.xylint.co.uk (4.1/SMI-4.1) id AA01096; Tue, 16 Nov 93 22:33:44 GMT
Received: from localhost by Mordor.Stanford.EDU (8.6.4/inc-1.0) id OAA26395; Tue, 16 Nov 1993 14:35:20 -0800
Message-Id: <199311162235.OAA26395@Mordor.Stanford.EDU>
To: Pete Cameron <pjc@basil.xylint.co.uk>
Cc: "Beast (Donald E. Eastlake 3rd)" <beast@world.std.com>, cmp-id@xylint.co.uk
Subject: Re: draft-cameron-tmux-01.txt
Phone: +1 408 246 8253; fax: +1 408 249 6205
In-Reply-To: Your message of Mon, 01 Nov 93 21:49:56 +0000. <9311012149.AA06811@basil.xylint.co.uk>
Date: Tue, 16 Nov 1993 14:35:19 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dave Crocker <dcrocker@mordor.stanford.edu>
X-Mts: smtp

I'm only just catching up on old mail, but I've read the comments
and wanted to add my 2cents.

Loosening the language to indicate general utility certainly sounds
like a good idea.  Having text which cites terminal use then acts as a
concrete (motivating) example.

TOS and broad/multi-cast usage I would think are beyond the current
scope of thought and intent, so the spec should simply cite them
away.  As one sage at the Houston meeting (sorry for forgetting
who) observed, this is supposed to be a simple protocol to
solve a simple problem.  We should be careful not to burden it
with extras to cover the maybes and whatifs, to the extent possible.

Dave