IPv6 ingress filtering

Brian Carpenter brian.e.carpenter at gmail.com
Wed May 15 11:51:48 CEST 2019

Anycast 6to4 needed to be assassinated, and that has more or less happened.
If classical unicast 6to4 is still working for a few people, I don't really
see any harm in it. Of course I agree that native is better.

    (via tiny screen & keyboard)

On Wed, 15 May 2019, 19:00 Gert Doering, <gert at space.net> wrote:

> Hi,
> On Tue, May 14, 2019 at 11:08:21PM +0200, JORDI PALET MARTINEZ wrote:
> > 6in4 needs manual configuration (or a TB).
> >
> > 6to4 is 6in4 with automatic configuration.
> You might not have noticed, but I have done a bit of IPv6 over time,
> so yes, I understand.  And thus: 6to4 needs to die.  In flames.
> > Living in a perfect world is ideal (I will love to have just one ISP
> with IPv6 in every country). But is not real.
> This is not solved by poor-quality tunnels.  All these tunnels do is
> "make IPv6 look bad", so people get to learn "IPv6 has more latency, more
> packet loss, and I can not even call customer support if it does not
> work, so better avoid it".
> This was already accepted truth 10+ years ago.
> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael
> Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20190515/1d754499/attachment-0001.html 

More information about the ipv6-ops mailing list