I really think that the right answer is to write an applicability statement for
6to4 that:
- refers to the existing documents about 6to4 problems
- points out use cases for 6to4 which work well, and others that work less well
- emphasizes that 6to4 is a short-term solution and was always intended to be
such
Deprecating 6to4 and declaring it Historic are premature and overkill, but an
applicability statement seems entirely appropriate to me.
Beyond that, the question of anycast advertisement for 6to4 relay routers (RFC
3068) is a tough one. I'd like to find a way to be able to keep them, because
there's a huge utility in being able to automatically configure such things.
But everybody acknowledges the problems that are caused when relay routers are
advertised in BGP that don't actually get the traffic there. If there's not a
way to weed out the bad ones that is easy for operators to implement, maybe RFC
3068 really should be deprecated.
Keith
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf