[arin-ppml] Policy Proposal 119: Globally Coordinated TransferPolicy - revised
john.sweeting at twcable.com
Thu Oct 28 12:19:40 EDT 2010
As I read the AFRINIC proposal it is to keep Global Companies that have global networks and are eligible to get address space from AFRINIC can do so but only for the portion of their networks that is located in the AFRINIC region and for connectivity directly into the AFRINIC region.
On 10/28/10 12:05 PM, "Scott Leibrand" <scottleibrand at gmail.com> wrote:
I don't think it should be necessary to allow addresses to leave the AfriNIC region in order to pass this globally coordinated transfer policy. As I read it, passing both, in the absence of any local transfer policy in the AfriNIC region, would simply mean that AfriNIC does not object to other regions engaging in inter-RIR transfers, and would open up the possibility of AfriNIC participating at a later date if the community so chooses, perhaps upon exhaustion of the AfriNIC free pool.
Do you still see a conflict? If so, can you explain further?
On Oct 28, 2010, at 8:53 AM, McTim <dogwallah at gmail.com> wrote:
> FYI a proposed policy in the AfriNIC region has the following clause:
> "7.4) AfriNIC resources are for the AfriNIC geographical region. For
> each allocation or assignment made during the Exhaustion Phase, no
> more than 10% of these resources may be used outside of the AfriNIC
> region, and any use outside the AfriNIC region shall be solely in
> support of connectivity back to the AfriNIC region."
> If this reaches consensus, it would probably mean that this global
> policy (Policy Proposal 119: Globally Coordinated Transfer Policy)
> wouldn't fly in the AfriNIC region.
> "A name indicates what we seek. An address indicates where it is. A
> route indicates how we get there." Jon Postel
> On Wed, Oct 27, 2010 at 9:54 PM, Bill Darte <BillD at cait.wustl.edu> wrote:
>> Seems to me, that if addresses are unavailable with a region....that the
>> requestor is a legitimate member of (there's my problem with
>> definition), then they can make a request or another region....but that
>> their request would have to conform to the policies of both RIRs.
>> Doesn't make sense to allow a transfer from out of region if there are
>> addresses available locally.
>> Doesn't make sense to allow someone to shop around for a more favorable
>> policy than their own region.
>> Doesn't make sense to allow someone to only have to conform to the
>> 'local' policy if it is less stringent than the policy of the RIR it's
>> requesting transfer from....the RIR with available addresses would then
>> be placing their own constituents at a disadvantage.
>> If a multinational org with offices in all 5 regions needs
>> addresses...which are now only available in 1 region, they would have to
>> conform to that regions policy. No different that requesting those
>> resources today.
>>> -----Original Message-----
>>> From: arin-ppml-bounces at arin.net
>>> [mailto:arin-ppml-bounces at arin.net] On Behalf Of Owen DeLong
>>> Sent: Wednesday, October 27, 2010 1:37 PM
>>> To: Hannigan, Martin
>>> Cc: arin-ppml at arin.net List
>>> Subject: Re: [arin-ppml] Policy Proposal 119: Globally
>>> Coordinated TransferPolicy - revised
>>> On Oct 27, 2010, at 11:05 AM, Hannigan, Martin wrote:
>>>> On 10/27/10 1:12 PM, "Owen DeLong" <owen at delong.com> wrote:
>>>>> With the changes to language in this version, I can now
>>> support this
>>>>> proposal once we enact appropriate language in ARIN policy
>>>>> what is or is not an acceptable set of transfer conditions.
>>> That was English.
>>> I think that ARIN needs policy or at least an understanding
>>> in a procedural document of what transfers would or would not
>>> be agreeable to ARIN under this transfer regime. The policy
>>> leaves a lot left to the imagination, as it should on the
>>> global level, but, before enacting it globally, I'd want to
>>> have some documented idea of the in-region ramifications.
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> Please contact info at arin.net if you experience any issues.
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> Please contact info at arin.net if you experience any issues.
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
More information about the ARIN-PPML