On 27/Feb/15 07:34, Izumi Okutani wrote: > We would know which organization the ASNs are assigned to, as those > upstream ASNs are already used. > > We don't have a formal mechanism to check the authenticity of the POCs > but usually check the e-mails provided are reachable. We would find it > suspicious if the domain name of the e-mail provided is different from > the domain used for the organization or free e-mail accounts. > > It's not formal in the sense that we request upstream ASNs to register a > POC. I suppose therefore you can still forge domain name, etc, but it is > sufficient in our case to give credibility above a certain level.
In the AFRINIC region, the membership have been mostly frustrated by this added step by the AFRINIC hostmasters. But personally, I support if they can always enforce it, as it adds some kind of "proof" that the application information is reasonably genuine and the chances of faking needs are somewhat reduced (which is better than not being reduced). Of course, an applicant could collude with the ISP to let them claim the applicant is, in fact, going to buy services that warrant the allocation of resources. However, this comes back to the integrity of the ISP. Not 100% foolproof, but a step in some direction. Mark. * sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list sig-policy@lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy
