Hi Tommy, Thanks for your suggestions.
On Wed, 26 Sep 2018 at 23:38, Tommy Pauly <tpa...@apple.com> wrote: > +1 to the point that the proposal for NHE is essentially a mechanism for > the ISP and/or content provider to work around a broken deployment that > they should be in a position to fix themselves, or between one another as > Tony describes. > Fair enough. I think it is worth of doing it. The part that remains interesting is suggestions for networks to collect > more reports on the relative health of IPv4 and IPv6 connections, to help > fix bugs and broken deployments. Focusing on these improvements rather than > filtering DNS answers seems like it would be a more fruitful direction. > >From the feadback of this list, now I'm think of dividing NHE draft into two pieces: One is network-side IPv6 measurment and failure reporting which is in aim to provide information to workaround broken deployment in a position to fix by ISP themselves. ISP can decide by themself to take advantege of measurement information. It can be standard track or informational. Another one is Selectively delaying AAAA record other than filtering DNS records. It served an experimental/informational case of ISP taking IPv6 mearement infromation as a feed to quickly and temporarily fix the problem if operator think it is neccesary. How does this sound ? Davey
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
