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/routing-wg@ripe.net/
[routing-wg] AS201640
- Previous message (by thread): [routing-wg] AS201640
- Next message (by thread): [routing-wg] AS201640
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Sun Nov 9 17:42:50 CET 2014
Hi Ronald, >> Having IP addresses is not a requirement for getting an ASN. There are >> many legitimate cases where an ASN may be used to announce address space >> belonging to someone else. For example an ISP announcing address space >> belonging to its customer. Or a transit provider. > > OK, that's a good point. But I'm not sure that it fully negates the > possible value of my question. > > Everybody is _supposed_ to have working e-mail address contacts in their > IP allocation records within the WHOIS data bases of the various RiRs, > yes? So suppose that there had been a protocol in place that required > an affirmative e-mail response from at least one legitimate IP address > block registrant (in some/any region) before the allocation of an AS > number would proceed. Such a protocol would have forestalled the > situation that we now see with AS201640, would it not? It is a possible implementation but one that only has a one-time check. It wouldn't keep track of changes to resources in other regions. The working group asked the RIPE NCC to look into the possibilities and report back to the working group. Let's see if there is a easy to use solution that makes sure we don't import data into our database that then end up being invalid or outdated. Cheers, Sander
- Previous message (by thread): [routing-wg] AS201640
- Next message (by thread): [routing-wg] AS201640
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]