On Thu, Dec 14, 2017 at 11:09:13PM +0530, Mukund Sivaraman wrote:
> Any appetite for it? Don't throw things at me.. I ask because the
> current thing is slowly getting more widely deployed and there are
> design issues that can do with a ECS2 that breaks from ECS1 protocol. I
> ask because I'm once again having to deal with myriad implementation
> cases and dislike it.
Could you elaborate what you dislike most? The biggest thing we are noticing
is that while it does great things to getting to a server the content
provider likes, it unavoidably drives doen cache hitrates a lot, introducing
a latency penalty.
The operators we see deploying ECS have tens of thousands of subnets
which all need to be mapped to only a few servers. But you still end up
with tens of thousands of cache entries and therefore tiny cache hitrates.
Such things could be addressed by answering with lists of subnet masks to
which this answer would also apply, but this makes little sense
operationally I think.
Can you share your ideas for ECS2?
Bert
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
