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] End User Agreement question
- Previous message (by thread): [ncc-services-wg] End User Agreement question
- Next message (by thread): [ncc-services-wg] End User Agreement question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hank Nussbacher
hank at efes.iucc.ac.il
Tue Mar 19 15:39:12 CET 2013
At 11:48 19/03/2013 +0100, Janos Zsako wrote: >>In our context the End User wants us to "park" an ASN under our >>LIR. Your interpretatio of "use" - "used to to identify a host" - does >>not cover the ASN instance. > >Therefore it is clear that an ASN is not intended to be used "internally", >moreover, >you are not supposed to "park" it. Obviously you did not understand what I meant by "park". There are many resources out there - listed in the RIPE whois DB, actively being used, announced and routed on the Internet, but due to historical reasons, those resources are not listed under any LIR - they are just free hanging. RIPE NCC has been sending out hundreds (thousands?) of emails to all those "hanging" resources (mainly historical ones) - informing them that the resource has to be listed under a LIR and if not, it will be revoked. For lack of a better term, for a resource that exists, and is being used , and merely needs to be "assigned" to some LIR, I have used the term " to park". Regards, Hank
- Previous message (by thread): [ncc-services-wg] End User Agreement question
- Next message (by thread): [ncc-services-wg] End User Agreement question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]