[arin-ppml] ARIN-prop-139 No reassignment without networkservice
owen at delong.com
Wed Apr 13 01:33:09 EDT 2011
There is not a single ARIN policy for which you are completely unable to engineer a sufficient workaround so as to violate its intent while still preserving some appearance of being close to the letter of the policy.
This is a consensus-based policy process where adherence to the policy is largely voluntary and where the community functions primarily on the expectation that most entities will act in good faith.
Refusing to make policy more accurately and clearly describe operational practice will
benefit the community. Refusing to do so merely because you cannot strictly and
reliably enforce the policy in a handful of corner cases, doesn't make much sense.
Sent from my iPad
On Apr 12, 2011, at 9:42 PM, Scott Helms <khelms at zcorum.com> wrote:
> I think the point here is that any such definition is effectively unenforceable since tunneling is acceptable in your proposal. As long as that is true you're not creating any more or any less of a relationship (i.e. some tracking back to the originating LIR) than a normal reallocate or reassign already does.
>> I tend to doubt it. That's not "network service", that's "service over a network". Certainly the intent of the policy is to preclude
>> such a workaround.
>> 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.
More information about the ARIN-PPML