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]/
[members-discuss] Complaints against LIRs ignored by NCC
- Previous message (by thread): [members-discuss] Complaints against LIRs ignored by NCC
- Next message (by thread): [members-discuss] Complaints against LIRs ignored by NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Knell
david.knell at gmail.com
Thu Nov 21 19:06:59 CET 2013
On Thu, Nov 21, 2013 at 10:51 AM, Gert Doering <gert at space.net> wrote: > Hi, > > Don't try to speak for "most here". I, for one, have met Lu Heng in > person, > have seen him actively take part in the address policy discussions, and > do trust the RIPE NCC to very closely check whether such a big allocation > can be backed by numbers and documentation. So I most certainly do not > see "CLEARLY" that there would be a violation of RIPE policies - and > even if it's currently announced from elsewhere, that doesn't mean it's > not actually *used* in the RIPE service region (think "VPN services"), > which is the key issue - address space being *used*, and not siphoned > off elsewhere. Even though the latter point is a bit moot nowadays. > > Agreed. However: nmap -n -sn -PE -T4 37.222.0.0/15 Nmap done: 131072 IP addresses (406 hosts up) scanned in 210.43 seconds --Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20131121/b3fd644a/attachment.html>
- Previous message (by thread): [members-discuss] Complaints against LIRs ignored by NCC
- Next message (by thread): [members-discuss] Complaints against LIRs ignored by NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]