Thanks Mike... very useful and just what I was looking for.

...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 12:47 PM, Mike Burns <[email protected]> wrote:

>  Hi,
>
> We have brokered a transfer of legacy space from the APNIC region to a
> buyer in the APNIC region.
> As part of the process, the seller was allowed to pay a partial fee to
> temporarily attain member status.
> I think it was processed under APNIC policy for the transfer of historical
> resources.
>
> http://www.apnic.net/publications/media-library/documents/resource-guidelines/historical-transfer
>
> However they did it, APNIC did vet the seller as the owner of the address
> rights before the transfer was completed.
>
> Hope this helps.
>
> Regards,
> Mike Burns
> IPTrading.com
>
>
> ----- Original Message -----
> *From:* Owen DeLong <[email protected]>
> *To:* Skeeve Stevens <[email protected]>
> *Cc:* [email protected] ; [email protected] SIG List
> *Sent:* Tuesday, February 25, 2014 8:03 PM
> *Subject:* Re: [sig-policy] Policy Regarding Transfers of Legacy Space
>
> Argh.  Cell phone autocorrected me into the opposite of my intent.
>
>
> Legacy should be NO different. Requirements for legacy should be
> identical.
>
> The problem with allowing non-contracted parties to be the source of a
> transfer becomes one of how you verify or authenticate said party and what
> your recourse is in the event of fraud.
>
> What if person Q pretends to be authorized to sell block X which is legacy
> to organization Z, but it later turns out that organization Z doesn't know
> Q and there's no contract between anyone except APNIC and the transfer
> recipient R?
>
> Does R sue Q? X? Z? APNIC? Or all of the above? What happens to R? What
> happens to Z? What happens to the registry records when this comes to light?
>
> Owen
>
>
> On Feb 25, 2014, at 14:18, Owen DeLong <[email protected]> wrote:
>
>  Legacy should be different.
>
> Owen
>
>
> On Feb 25, 2014, at 14:07, Skeeve Stevens <[email protected]>
> wrote:
>
>  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 ;  <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
>
>  *              sig-policy:  APNIC SIG on resource management policy
>           *
> _______________________________________________
> sig-policy mailing list
> [email protected]
> http://mailman.apnic.net/mailman/listinfo/sig-policy
>
>  *              sig-policy:  APNIC SIG on resource management policy
>           *
> _______________________________________________
> sig-policy mailing list
> [email protected]
> http://mailman.apnic.net/mailman/listinfo/sig-policy
>
>  ------------------------------
>
> *              sig-policy:  APNIC SIG on resource management
> policy           *
> _______________________________________________
> sig-policy mailing list
> [email protected]
> http://mailman.apnic.net/mailman/listinfo/sig-policy
>
>
_______________________________________________
apnic-talk mailing list
[email protected]
http://mailman.apnic.net/mailman/listinfo/apnic-talk

Reply via email to