QoS for Office365

Tue Jul 9 15:07:28 UTC 2019

That's already been happening. OpenSSH pulled that stunt in 7.8.

https://www.openssh.com/txt/release-7.8

 ssh(1)/sshd(8): the default IPQoS used by ssh/sshd has changed.
   They will now use DSCP AF21 for interactive traffic and CS1 for
   bulk.  For a detailed rationale, please see the commit message:
   https://cvsweb.openbsd.org/src/usr.bin/ssh/readconf.c#rev1.284

On Tue, Jul 9, 2019 at 10:50 AM Steve Mikulasik via NANOG <nanog at nanog.org>
wrote:

> Even if QoS on the Internet was possible it would be destroyed by everyone
> marking all their traffic with the highest priority to get the best
> performance. Tragedy of the commons.
>
>
>
> -----Original Message-----
> From: NANOG <nanog-bounces at nanog.org> On Behalf Of Mark Tinka
> Sent: Monday, July 8, 2019 10:40 AM
> To: nanog at nanog.org
> Subject: Re: QoS for Office365
>
>
>
> On 2/Jul/19 23:18, Joe Yabuki wrote:
>
> > Hi all,
> >
> > How do you deal with QoS for Office365, since the IPs are subject to
> > changes ?
> >
> > How can we mark the trafic while keeping the security (I fear the
> > marking based on TCP/UDP Ports since they are not without an
> > additional risk coming from worms/virus using those ports for example,
> > and doing that directly on the PCs doesn't seem to be the best solution)
> ?
>
> Funny, I was just answering an internal question about this, last week.
>
> As with all things Internet, my stance is if you don't have end-to-end
> control, trying to do QoS is pointless.
>
> That said, I believe it should be possible to apply some kind of
> meaningful, end-to-end QoS together with Microsoft if you took up one of
> their Express Route services, given that is considered a private, premium
> service.
>
> Mark.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190709/4d9f9d5e/attachment.html>