Michael, I completely agree. Question is... Is there any policy at the moment? Or should I be reading something for the next conference? ;-)
...Skeeve *Skeeve Stevens - *eintellego Networks Pty Ltd [email protected] ; www.eintellegonetworks.com Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellegonetworks ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve twitter.com/theispguy ; blog: www.theispguy.com The Experts Who The Experts Call Juniper - Cisco - Cloud - Consulting - IPv4 Brokering On Wed, Feb 26, 2014 at 9:53 AM, HENDERSON MICHAEL, MR < [email protected]> wrote: > Skeeve, > > > > First of all, there's probably going to be a lot of this: > > In a previous life, I obtained on behalf of my then employer three > adjacent "Class C" (and no, they weren't "/24"s in those days!) address > blocks. And we later inherited at least two more non-adjacent blocks from > mergers with other companies. I know that only about three or four > individual IP addresses of all these allocations are visible on the > Internet, and that the organisation quickly moved to RFC1918 private > addresses internally, so the legacy blocks are all just about completely > unused. Suddenly, their legacy space may be worth actual money. This > company is not and never has been an APNIC member. I'm sure there are lots > of other stories like mine. > > > > Secondly, I believe that pragmatism ought to, in this matter, rule over > principle: > > So, we should not say that the vendor must become an APNIC member to reap > the benefit of their 'found money', because by and large they won't bother, > thus pushing the transfers underground. > > I would say that the buyer / first intermediary must register the 'new' > block of IP addresses with (in this case) APNIC, so that it moves out of > 'legacy' space into 'regular' address space, then becomes subject to the > existing regulatory framework. I may be banging a familiar drum here, but I > don't think there should be any requirement to demonstrate 'need' for the > purchaser to be allowed to register a legacy block: in my view the > readiness to pony up some cash demonstrates sufficient 'need'. > > The difficult practical / legal issue may be: how does the vendor > demonstrate that a particular block of legacy space is in fact theirs to > sell, particularly if it's never been visible on the Internet? > > > > > > Regards > > > > > > *Mike* > > > > *Note*: The views expressed are my personal opinion and may not represent > the position (if any) of my employer > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Skeeve Stevens > *Sent:* Wednesday, 26 February 2014 11:08 a.m. > *To:* [email protected]; [email protected] SIG List > *Subject:* [sig-policy] Policy Regarding Transfers of Legacy Space > > > > Hi All, > > > > I've been contacted by a holder of some small (not relevant) legacy space > who was inquiring about selling it. > > > > But, they are not an APNIC member (or a Non-Member). > > > > Referring to: > http://www.apnic.net/publications/media-library/documents/membership/non-member-fees#Historical > under > 1.4, it talks about receiving transfers, but not making transfers. > > > > Any thoughts? > > > > ...Skeeve > > > > *Skeeve Stevens - *eintellego Networks Pty Ltd > > [email protected] ; www.eintellegonetworks.com > > Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve > > facebook.com/eintellegonetworks ; linkedin.com/in/skeeve > > twitter.com/theispguy ; blog: www.theispguy.com > > The Experts Who The Experts Call > > Juniper - Cisco - Cloud - Consulting - IPv4 Brokering > The information contained in this Internet Email message is intended > for the addressee only and may contain privileged information, but not > necessarily the official views or opinions of the New Zealand Defence > Force. If you are not the intended recipient you must not use, disclose, > copy or > distribute this message or the information in it. If you have received > this message in error, please Email or telephone the sender immediately. >
* sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list [email protected] http://mailman.apnic.net/mailman/listinfo/sig-policy
