Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-07.txt - software bugs

[Alexandru Petrescu <[e-mail]>]

Le 13/11/2014 20:43, Jeroen Massar a écrit :
[...]
> This is also what has been discussed on the list:
>   - deprecate anycast 6to4
>   - keep direct 6to4

YEs, I agree, and I would like to re-mention the point about software bugs.

There is one particular 6to4 implementation in the wild which has two 
different means to put up a 6to4 tunnel.  One is to just say '6to4' in 
the cli, the other is to be specific and type that IPv4 anycast address.

With the first means - it does not work.  Worse, it gets into a mode 
where packets are output destined to random IPv4 addresses.

Fix the bug.

What does this mean with respect to the deprecation effort?

Do not deprecate the IPv4 anycast address because if so then the entire 
6to4 software on that platform will no longer work.

Do not deprecate until you offer a solution satisfying a number of 
requirements (currently unsatisfied by eg tunnel brokers).

That's my oppinion.

Alex

>
>
> Hence, in the form of -07, I am in favor of making it so.
>
>
> But, as Doug notes, if there are any changes that need to be added, it
> would be great to see those in the document before doing a WGLC,
> especially for the people not sitting in a conference room on a tropical
> island (I do hope the folks there got a few days before and after to
> enjoy that apparently amazing island!)
>
> Although from reading what Brian Carpenter says those changes are likely
> minor editing notes. It would be great to see the final form though.
>
> Greets,
>   Jeroen
>
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops
>