Hi, On Mon, Jun 18, 2018 at 06:23:28PM -0500, David Farmer wrote: > If you receive packets sourced from 2002::/16 where do you plan to send > responses? They are valid IPv6 packets and addresses.
I can see only two ways to handle those
- run a local relay to send 2002::/16 -> ipv4 world
- drop these packets, hard
> If you don't want to provide your customers with a route to 2002::/16 that
> is your business, but recommending that 2002::/16 is a bogon mean no one
> should accept or advertise the route which means no one can effectively use
> 6to4. I'm happy to say that, but not without some data to back it up.
No one *can* effectively use anycast 6to4, which was the whole point of
the depreciation RFC.
It needs to die, horribly, in flames. Anyone using it needs to feel the
pain of enabling a broken protocol. ISPs need to have their customers
call the help desk if they enable 6to4 on customer routers or in their
own network, instead of deploying proper IPv6.
(Note that 6rd is not "anycast 6to4" and as thus not subject to this
rant)
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
signature.asc
Description: PGP signature
