<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [arin-ppml] Policy Proposal 119: Globally Coordinated Transfer Policy - revised</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>John, all,<BR>
<BR>
So you would look at 'current policy' in each RIR to assess conformance with the specifics outlined in 205O associated with conservation, routability and registration? Assuming that conforming policy existed in an RIR, what mechanism would you presume that would document that conformance in establishing a needs basis for transfers?<BR>
<BR>
That is, if a requester in another RIR wants addresses from a constituent in the ARIN region, how would ARIN assess that the request conforms to the policy of ARIN for allocation?...or would ARIN simply assess that the RIR from which the request comes from, has needs-based policy...and therefore the request must be legitimate?<BR>
<BR>
The reverse of course would be much simpler as the ARIN constituent requesting address space from another RIR's constituent would have to qualify under ARIN policy and be vetted accordingly, yes?<BR>
<BR>
bd<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: arin-ppml-bounces@arin.net on behalf of cja@daydream.com<BR>
Sent: Wed 11/24/2010 4:13 AM<BR>
To: John Curran<BR>
Cc: arin-ppml@arin.net List<BR>
Subject: Re: [arin-ppml] Policy Proposal 119: Globally Coordinated Transfer Policy - revised<BR>
<BR>
Thanks John.. so basically you would sort of "certify" other RIRs based on<BR>
their adherence to "principles of RFC 2050" and then go forward allowing<BR>
transfers and periodically review whether each RIR still meets that<BR>
requirement. That sounds fair to me.<BR>
<BR>
----Cathy<BR>
<BR>
On Wed, Nov 24, 2010 at 2:29 AM, John Curran <jcurran@arin.net> wrote:<BR>
<BR>
> On Nov 24, 2010, at 3:28 AM, cja@daydream.com wrote:<BR>
><BR>
> > Who decides whether the " two<BR>
> > RIRs agree and exercise Internet stewardship and the values expressed in<BR>
> > RFC2050." ?<BR>
> ><BR>
> > Who makes the process for that? What happens if they don't agree?<BR>
><BR>
> Cathy -<BR>
><BR>
> Short of any additional guidance in the policy, I can explain how ARIN<BR>
> staff would implement that language. In the case of ARIN, we would<BR>
> maintain of a list of RIRs which we've reviewed and concur implement<BR>
> the principles in RFC 2050. I imagine that the other RIRs would make<BR>
> similar assessments & lists, and in the case of mutual alignment, then<BR>
> inter-RIR transfers would be possible.<BR>
><BR>
> This actually shouldn't be too difficult, since it is common for the RIRs<BR>
> to reference these principles in their policy framework and further that<BR>
> each RIR has agreed to them as part of setting the ICANN ICP-2 global<BR>
> policy for recognition of an Regional Internet Registry.<BR>
><BR>
> The language appears to be far more likely relevant if a RIR to abandon<BR>
> the stewardship principles in the future, as then we would not be able to<BR>
> participate in transfers via that entity (i.e. whether such an entity<BR>
> would<BR>
> still qualify as an RIR under such circumstances is a different question)<BR>
><BR>
> Does this address your question?<BR>
><BR>
> /John<BR>
><BR>
> John Curran<BR>
> President and CEO<BR>
> ARIN<BR>
><BR>
><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>