On Thu, Dec 14, 2017 at 12:39 PM, Mukund Sivaraman <[email protected]> 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. >
<no hats, other than author on the original doc.> As I'm sure you know / remember, getting the first version though was quite a slog. I suspect that, seeing as there seems to be good support for the initial version, getting a new one done will be much simpler, but the obvious question is: How would ECS2 differ, and how would it interact with ECS1 / backward compatibility? W </no hats> > Mukund > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
