Geoff Huston wrote:
> WG Chair hat off
>
>
> On 07/10/2008, at 11:25 PM, Randy Bush wrote:
>
>>> A source of a relatively complete set of individual allocations can be
>>> retrieved from http://bgp.potaroo.net/stats/nro/delegated
>>>
>>> then take a large set of updates and examine each prefix - the Route
>>> views update archive is a good source
>>>
>>> and then perform a lookup into the individual allocation list for each
>>> updates / withdrawn prefix
>>>
>>> and report anomalies that straddle multiple allocations
>>>
>>> is one way to understand the level of historical occurrence.
>>
>> again, could you give us one or two examples of this actually occurring,
>> an asn aggregating prefixes from multiple rirs, i.e. what not having
>> multiply signed roas would preclude?
>>
>> you did say "and this case, although not common, has been visible in the
>> routing table already."
>>
>
> I did say that and I based that comment on my earlier work in
> constructing the BGP report and looking at aggregation possibilities
> in the routing table and figuring out why the code was failing for
> certain advertised prefixes (its always the bugs that are more
> interesting than the working code). That was over 4 years ago, and
> after correcting (!) the code not to look for such cases where the
> prefix straddled across allocation boundaries I've not had to go back
> there again until this conversation.

Even historical examples from 4 years ago, if you can find the prefixes
in question and other attributes, would be very interesting to most
folks, I believe.
(Most of us have access to the old data too, so we can look at the
then-relevant state of the world as relates to those prefixes.)

If you have them handy, that is.

Brian

>
> So if you are after current examples, then its a case of
> reconstructing the code and running through the routing updates again.
> It may be some weeks before I can get around to this task personally.
> Others may be better situated to perform such an investigation in a
> faster timeframe.
>
>   Geoff
>
>
>
>
> _______________________________________________
> sidr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sidr

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to