Re: draft-cameron-tmux-01.tx
"Donald E. Eastlake 3rd (Beast)" <dee@skidrow.lkg.dec.com> Wed, 17 November 1993 14:00 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02406; 17 Nov 93 9:00 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02402; 17 Nov 93 9:00 EST
Received: from basil.xylint.co.uk by CNRI.Reston.VA.US id aa08913; 17 Nov 93 9:00 EST
Received: from inet-gw-2.pa.dec.com by basil.xylint.co.uk (4.1/SMI-4.1) id AA28024; Wed, 17 Nov 93 13:32:58 GMT
Received: by inet-gw-2.pa.dec.com; id AA25481; Wed, 17 Nov 93 05:27:09 -0800
Received: by skidrow.lkg.dec.com (5.57/fma-100391/rcb-930105) id AA28186 for cmp-id@xylint.co.uk; Wed, 17 Nov 93 08:27:03 -0500
Message-Id: <9311171327.AA28186@skidrow.lkg.dec.com>
To: Dave Crocker <dcrocker@mordor.stanford.edu>
Cc: "Beast (Donald E. Eastlake 3rd)" <beast@world.std.com>, cmp-id@xylint.co.uk
Subject: Re: draft-cameron-tmux-01.tx
In-Reply-To: Your message of "Tue, 16 Nov 93 14:41:45 PST." <199311162241.OAA26442@Mordor.Stanford.EDU>
Date: Wed, 17 Nov 1993 08:27:03 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Donald E. Eastlake 3rd (Beast)" <dee@skidrow.lkg.dec.com>
X-Mts: smtp
Dave, Well, of course it is up to the sending host. But if that host thought it worth while to set the TOS on the original datagrams, I would think the default would be that it would want the multiplexed message to have only compatible datagrams and to have the same TOS as they do. I don't agree that TOS is useless. Unused perhaps, but not useless. Donald From: Dave Crocker <dcrocker@mordor.stanford.edu> To: "Beast (Donald E. Eastlake 3rd)" <beast@world.std.com> Cc: cmp-id@xylint.co.uk Phone: +1 408 246 8253; fax: +1 408 249 6205 In-Reply-To: Your message of Tue, 02 Nov 93 02:56:17 -0500. <199311020756.AA00203@world.std.com> >well, I *thought* that I had read all the notes. > >More on TOS. > >You are, of course, correct that TOS is mandated. However, it is a >bloody useless field and there is no expectation that it will change >anytime soon. > >Further, this is the originating host doing the ignoring. It ought to >know how important any of that stuff is. To the extent the spec should >comment on TOS (and I suspect that your raising the issue is a good >indicator that the spec should say something specific) then it should >caution the TMUX creator to synthesize and "appropriate" TOS value from >those of the clients. > >Note that we've heard of TMuxing FTP and Telnet traffic. They have >different expected TOSs, yet the sender decides to multiplex them. The >sending TMux then gets to decide how to set the TOS value for the >resulting single datagram. > >Dave
- Re: draft-cameron-tmux-01.tx Beast (Donald E. Eastlake 3rd)
- Re: draft-cameron-tmux-01.tx Dave Crocker
- Re: draft-cameron-tmux-01.tx Donald E. Eastlake 3rd (Beast)