Mike, Is there a requirement to have it configured per delivery service? If not, would enabling global header rewrite in plugin.config would work for a specific DSCP value?
Steve On Mon, Jun 19, 2017 at 1:28 PM, Mike Sandman (misandma) <[email protected] > wrote: > Hi all, > > I’m beginning work on a feature to enable DSCP marking for traffic between > the mid and edge cache. So far the high level proposed design is: > > > 1. DSCP marking from Mid to Edge will be configurable on a per-DS > basis (like DSCP marking from Edge to Client is today). This means the Mids > will need to know what DS a particular request corresponds to (we have a > use case for two DSes pointing to the same origin) > > 2. Therefore, the Edge will need to write a new header > (Forwarded:host= as per RFC 7239<https://tools.ietf.org/html/rfc7239>) > into the request that is sent up to the Mid > > 3. The Mid will use a remap rule (like the Edge does today) to apply > a DSCP config to responses where the request has a matching Forwarded header > > 4. To accomplish this, Traffic Ops will need to generate header > rewrite rules on the Edge and remap.config on the Mid to match this > configuration scheme > > Any issues or improvements to this? Or will this work? > > Thanks, > Mike Sandman >
