Hi,
I like Erik's suggestion as a simple default mechanism to deal with the looping case. It's not perfect, but would provide a default mechanism that would prevent people from hurting themselves. It does support the scenario I am interested in (/64 advertised from upstream, router/proxy, single subnet downstream with a few devices). It's easy to turn off for people who know more about their topology or perhaps the case Pekka describes.
FWIW it also support a single proxy having multiple downstream interfaces. I don't know if that is an interesting case when multiple L2 technologies are being used.
I think people are going to build things like this independent of what the IETF does and publishing this (with the changes being discussed) seems like a reasonable thing thing for the community. It will help people avoid many of the mistakes that have been discussed.
Yep.
Erik
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
