Templin, Fred L wrote:
Which won't work, as ULA-C's are not in the routing tables, they won't pass
uRPF checks and thus those packets of yours will get dropped to the floor.
When you got gear you are going to attach to the internet request a PI or a
PA block and use a global unicast address.
Which Internet? The existing IPv4 one, or a future IPv6 one?
Or, to ask the question another way, does it make sense to use uRPF to
drop packets sourced from ULA-C blocks? Our current implementations of
loose uRPF are rooted in IPv4 justifications, most notably that private
IP space (RFC 1918) is non-unique, so we have no idea where the packet
came from, so we might as well drop it. I'm not sure that applies in
the IPv6 world, where an ICMP packet can be sourced from ULA-C space or
non-routed PI space and can have perfectly valid DNS and whois
information associated with its source address.
-Scott
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
