<html><body bgcolor="#FFFFFF"><div><br></div><div>I am not saying otherwise.</div><div><br></div><div>as<br><br>Sent from my mobile device<div>(please excuse typos and brevity)</div><div><br></div></div><div><br>On 24 Nov 2011, at 08:56, Cameron Byrne <<a href="mailto:cb.list6@gmail.com">cb.list6@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><p><br>
On Nov 24, 2011 1:36 AM, "Arturo Servin" <<a href="mailto:arturo.servin@gmail.com"><a href="mailto:arturo.servin@gmail.com">arturo.servin@gmail.com</a></a>> wrote:<br>
><br>
><br>
> <snip><br>
><br>
> On 24 Nov 2011, at 07:20, Eugen Leitl wrote:<br>
><br>
>> as the <br>
>> fc00::/7 addresses will not be routed beyond that, correct?<br>
><br>
> <snip><br>
><br>
> Incorrect or not necessary.<br>
></p>
<p>No</p>
<p>> ULAs are just as any other unicast addresses. As technical community we had agreed to not route it in the internet, but If you leak it and somebody else routes it, you are fried.<br>
></p>
<p>No, this rfc defined behavior. Please check your facts.</p>
<p>It is the same situation as rfc 1918 leaking. Saying that it is in any way different from rfc 1918 is misleading people. Ula is not in the dfz and if it got leaked it would be fixed , just like 10/8.</p>
<p>Both ula and rfc 1918 should be part of any inter domain ingress and egress filtering. </p>
<p>If you want to keep pushing that there is an operational difference from a routing policy perspective, cite some facts </p>
<p>From rfc 4193</p>
<p> Site border routers and firewalls should be configured to not forward any packets with Local IPv6 source or destination addresses outside of the site, unless they have been explicitly configured with routing information about specific /48 or longer Local IPv6 prefixes. This will ensure that packets with Local IPv6 destination addresses will not be forwarded outside of the site via a default route. The default behavior of these devices should be to install a "reject" route for these prefixes. <br>
</p>
<p>..... And......</p>
<p> <br>
If BGP is being used at the site border with an ISP, the default BGP configuration must filter out any Local IPv6 address prefixes, both incoming and outgoing. It must be set both to keep any Local IPv6 address prefixes from being advertised outside of the site as well as to keep these prefixes from being learned from another site <br>
</p>
<p>Cb<br>
> /as<br>
><br>
></p>
</div></blockquote></body></html>