On 26/03/2017, 13:59, Michael Welzl wrote:
On Mar 26, 2017, at 12:13 PM, Gorry (erg) wrote:
This reply is just about the DSCP and QoS.
Everything you say about TAPS trying to set DSCP values seems consistent with
normal diffserv use to me: Just because an app sets a DSCP does not mean the
a
> On Mar 26, 2017, at 12:13 PM, Gorry (erg) wrote:
>
>
> This reply is just about the DSCP and QoS.
>
> Everything you say about TAPS trying to set DSCP values seems consistent with
> normal diffserv use to me: Just because an app sets a DSCP does not mean the
> actually sent packets are as
This reply is just about the DSCP and QoS.
Everything you say about TAPS trying to set DSCP values seems consistent with
normal diffserv use to me: Just because an app sets a DSCP does not mean the
actually sent packets are assigned a PHB along the path, it simply marks them
for this treatme
Ahh, sorry, no … I ALWAYS try to carefully check everything and THEN a thought
appears immediately after pressing the “send” button. About aborting vs.
closing:
>> ---
>> Abort without delivering...
>>
>> Abortis currently specified for SCTP and TCP. If one assumes the bound
>> semantics for
Hi,
Thanks a lot for reading and commenting!
> On Mar 24, 2017, at 8:29 AM, Gorry Fairhurst wrote:
>
> This looks like good progress. A few very specific comments below:
>
> ---
> I see phrase:
> " Because QoS is out of scope of TAPS, this document assumes a "best
> effort" service model
