<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 16, 2019 at 1:20 PM Sander Steffann <<a href="mailto:sander@steffann.nl">sander@steffann.nl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi David,<br>
<br>
> While I happen to agree with you 2002::/16 SHOULD NOT be filtered, and RFC 7526 is quite clear that 2002::/16 is still valid. However, it is perfectly permissible to filter it, if that is the policy a network operator wishes to enforce.<br>
<br>
With the 6to4 anycast relays deprecated the only 6to4 traffic should be src 2002::/16 and dst 2002::/16. Sites that are not using 6to4 themselves can filter 2002::/16. Everybody else will only see IPv4+proto41 traffic, which is not impacted by that filter.<br></blockquote><div><br></div><div>NO! RFC3056 Includes a gateway functionality it is just not Anycast. It is possible to locally gateway traffic to native IPv6 and then you would get traffic sourced from 2002::/16 and then you need to send traffic to a return gateway. Now, most traffic you are seeing is probably coming from the public anycast gateways that are still running, but it doesn't have to be. As I said elsewhere in the thread, it complicated and filtering is easy. Read RFC7526 very carefully, if you care, if you don't just filter it.</div></div><br clear="all"><div>Thanks</div>-- <br><div dir="ltr" class="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div></div>