QoS for Office365

Tue Jul 9 14:16:52 UTC 2019

On Tue, 9 Jul 2019 at 17:05, Tom Beecher <beecher at beecher.cc> wrote:

> Generally speaking, I agree that making QoS features work consistently on an external network you do not control is a fool's errand.
>
> But if that language was inserted into the contracts, and you can demonstrably prove it's not being done, enforcing contract terms should always be done. Depending on the strength of the remedy, could have been a lot of free service, enough financial incentive for them to MAKE it work correctly, or leverage to open renegotiations for more favorable terms for you.
>
> You know that in reverse they would have done the same to you. :)

In previous life working with L3 MPLS VPN with deliveries far
exceeding on-net size we bought access from partners and had QoS
contracts in place, which were tested and enforced and they worked
after some ironing during field trials.
Usually contract was bidirectional, with partner also using our
network for extending reach of their network, so both had incentive to
offer working QoS with network-edge translation of marking.

-- 
  ++ytti