Hi Randy, On 10/06/12 8:30 AM, "Randy Bush" <ra...@psg.com> wrote:
>> before the wanderings, there were three announcements.
>> A 10.0.0.0/8
>> C 10.42.0.0/16
>> G 10.42.2.0/2
> /24
>
>> gonna be hard to convince C to become chopped liver so that G can be
>> independent. also gonna be a bit of pollution.
>
Can you define 'pollution'? in what sense? In C no longer going to announce
the full /16 aggregate? Is the goal here routing security, or bgp table
growth limitation?
Why does 'C' having their resource certificate list specifically what
resources they are in control of ("chopped liver") and therefore what they
can announce/route have any bearing on something that is a) the antecedent
for routing security, and B) something that is mostly machine generated and
machine parsed?
Cheers
Terry
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
