This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] source: field for non RIPE address space

Previous message (by thread): [db-wg] source: field for non RIPE address space
Next message (by thread): [db-wg] source: field for non RIPE address space

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Job Snijders job at instituut.net
Tue Nov 25 00:34:34 CET 2014

On Tue, Nov 25, 2014 at 08:28:55AM +0900, Randy Bush wrote:
> > Correct route object prefix length, wrong origin & visible in BGP DFZ: 
> 
> is this not legitimate in a make before break origin transfer?  of
> course, many will forget to clean old up afterward.

Yes, good remark.

I have not attempted to figure out why those route objects are there.

One could for instance take a wider time window for the BGP data (6
months?) and run the correlations to assess which are in transfer/mbb
and which potentially are stale garbage.

Kind regards,

Job

Previous message (by thread): [db-wg] source: field for non RIPE address space
Next message (by thread): [db-wg] source: field for non RIPE address space

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]