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] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*
- Previous message (by thread): [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*
- Next message (by thread): [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Wed Jun 30 14:02:22 CEST 2021
Hi Ed, Thanks for the data, based on this I will stand by my opinion that there should be no action taken here currently. This opinion is also mainly based on the fact that it is not validated in the RIPE database. I am not sure if this is right or not, but I think it should probably not be cleaned up in RIPE-NONAUTH if it is not validated in RIPE. But once again if someone has a better reason then I could change my mind. Also if/when we get to a point that these objects are a very significant part of the remaining objects in RIPE-NONAUTH then it might be worth discussing again. I feel like in this case when there is no real personal data (afaik), we should value not breaking things we didn't think of way higher than cleaning up ~1600 route(6) objects. (Assuming the resource holders can contact the NCC to request to have them removed) -Cynthia On Wed, Jun 30, 2021 at 1:40 PM Edward Shryane <eshryane at ripe.net> wrote: > Hi Cynthia, > > On 29 Jun 2021, at 15:00, Cynthia Revström <me at cynthia.re> wrote: > > Hi Ed, > > Thanks for implementing this :) > > > Thanks for your feedback. > > I mainly wanted to give my initial take on the AS origin status part which > is in short: I don't think we should clean up based on origin AS. > This is as you do not need any technical authorization from the AS holder > to create a route(6) object. > Additionally, I don't think this is validated in RIPE AUTH, but I could be > wrong on that part. > > I might have a different opinion if it is a huge amount of objects that > could be cleaned up or if it is such a tiny amount that maybe just > contacting the maintainers manually would be enough. > Summary: I don't think it is a good idea unless it is either a very large > amount of objects, a very trivial task, or there is another good reason to > do so. > > -Cynthia > > > I found 1,577 route objects (out of 55,960) and 43 route6 objects (out of > 1,522) in the RIPE-NONAUTH database which reference an unregistered AS > number (i.e. "available" or "reserved" in any RIRs delegated stats). > > Of these, there are 169 distinct unregistered AS numbers referenced by > route(6) objects in RIPE-NONAUTH. > > As we don't validate the origin AS number in the RIPE database (apart > from excluding bogon space according to: > http://www.team-cymru.com/bogon-reference.html), I also checked route(6) > objects there. > > I found 72 routes and 20 route6 objects in the RIPE database which > reference an unregistered AS number (41 distinct AS numbers). > > Regards > Ed Shryane > RIPE NCC > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20210630/8c442eda/attachment.html>
- Previous message (by thread): [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*
- Next message (by thread): [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]