I have a pre-ICANN Class-C and its currently advertised on an ASN owned by a hosting company (and I tunnel it to other location(s)) -- I don't think we need an ASN to delegate, but lets explore it further and weigh the plusses and minuses.
------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 http://k7ve.org/blog http://twitter.com/#!/john_hays http://www.facebook.com/john.d.hays
On Tue, Jun 5, 2012 at 11:04 AM, Don Fanning don@00100100.net wrote:
(Please trim inclusions from previous messages) _______________________________________________
On Tue, Jun 5, 2012 at 10:52 AM, Tim Pozar pozar@lns.com wrote:
The organization "Amateur Radio Digital Communications" (see whois.arin.net) already has 44/8. Anyone that has an ASN can announce this space in full or part as along as this is blessed by the "owner". In fact, I announce /24s and /16 for folks that got their address space also from Jon Postel (pre-ICANN).
I was wondering how that worked for LEGACY. But isn't it sort of a chicken/egg issue? If you have an ASN , you can advertise 44/8. But if you don't, you have to meet the current ARIN standards? So really it's just the legal aspect that needs to be addressed so that the delegates aren't permanently transferred when delegated.
Also I see a hardware aspect that needs to be addressed to make the cloud more robust with multiple core routers in different datacenters around the world should southern california ever take the big drink into the pacific.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net