nanog mailing list archives
Re: QoS for Office365
From: Saku Ytti <saku () ytti fi>
Date: Tue, 9 Jul 2019 18:22:29 +0300
Hey Tom
That's already been happening. OpenSSH pulled that stunt in 7.8.
OpenSSH always coloured interactive and non-interactive SSH. They just used original TOS definition, which no one has used in the field, not in the last 20 years at any rate. And which devices actually cannot even match for (They can match PREC, DSCP definition of TOS, not original). But it took some time of convincing OpenSSH people that reading original RFC isn't going to give sufficient understanding of how TOS is used in real network. I applaud this change. In home use your WIFI actually does honour QoS and many enterprise networks do. And they mostly will align with this default. So it's good default. Home user internet experience would be vastly superior if WAN would also do some rudimentary QoS, one silver bullet is to prioritise small packets during congestion. Makes so much better experience on people who regularly have their WAN uplink congested. Sadly not widely done and impossible in most cases to do for NET=>Customer direction. Would be terrific if CPE could tell far-end what QoS policy to use, so residential users could decide on their end the far end QoS config. -- ++ytti
Current thread:
- Re: QoS for Office365, (continued)
- Re: QoS for Office365 Mark Tinka (Jul 08)
- Re: QoS for Office365 Warren Kumari (Jul 08)
- RE: QoS for Office365 adamv0025 (Jul 08)
- Re: QoS for Office365 Mark Tinka (Jul 08)
- Re: QoS for Office365 Brandon Martin (Jul 09)
- Re: QoS for Office365 Mark Tinka (Jul 09)
- RE: QoS for Office365 Steve Mikulasik via NANOG (Jul 09)
- Re: QoS for Office365 Mark Tinka (Jul 09)
- Re: QoS for Office365 Tom Beecher (Jul 09)
- Re: QoS for Office365 Saku Ytti (Jul 09)
- Re: QoS for Office365 Tom Beecher (Jul 09)
- Re: QoS for Office365 Saku Ytti (Jul 09)
- Re: QoS for Office365 Tom Beecher (Jul 09)
- Re: QoS for Office365 Mark Milhollan (Jul 10)