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/ncc-services-wg@ripe.net/
[ncc-services-wg] Feature request
- Previous message (by thread): [ncc-services-wg] Feature request
- Next message (by thread): [ncc-services-wg] Feature request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Fri Sep 16 17:09:24 CEST 2005
> To be honest, I don't think it is resonable for the ISP to remove the > inetnum's from the RIPE db, as the customer 'owns' the resources. So the > ISP can drop the routing, they can drop any route-records they have, but > I don't think they can really drop the PI space inetnum objects. > > But please correct me if I am wrong. Correct only if I provide connectivity to my user. In that case, there is PA space, not PI. And of course, it can't be applied for ASNs. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [ncc-services-wg] Feature request
- Next message (by thread): [ncc-services-wg] Feature request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]