[arin-ppml] Draft Policy ARIN-2013-4: RIR Principles - revised
Jason Schiller
jschiller at google.com
Mon Jul 15 21:37:29 EDT 2013
Jimmy,
As Chris has pointed out... there are still a lot of documents that point
to
RFC2050 and reference stewardship principles, such as NRPM section 4.1.7
https://www.arin.net/policy/nrpm.html#four17
The problem is with recent updates, RFC-2050 lacks much of the
stewardship principles that people tend to point to.
This proposal is an attempt to collect these principles in one coherent
place,
and not loose the text when the original RFC2050 is deprecated.
This is the only goal of this proposal.
It is not intended to be policy, but rather is text that has guided policy
development and it is hoped will be used to continue to guide policy
development.
It has been suggested by many that an RFC is not the right place to
record these principles as they are not prescriptions that the IETF
places on the RIRs.
The PDP changes frequently, and it doesn't seem to have much
community input.
So that left placing these principles in the NRPM. A place that the
community looks after and can easily change.
It is possible, assuming there is community consensus on what the
principles should be, that they could be moved out of the NRPM
and placed in the ARIN bi-laws or some other place, but that may
take changes out the hands of the community, and make it even
more difficult to update.... I'm not sure that is a good feature.
> "For example, Conservation often requires greater consideration in
> IPv4 address distribution due to the limited size of the address
> space, Routability has a higher weight for the massive IPv6 address
> space, and AS numbers place the highest value on Registration because
> they
> come from a moderately sized pool and are not subject to aggregation."
>
>
> This is no good.... we essentially have here a policy statement
> that ARIN should apply good judgement and consideration when using
> policy.
No. We have a suggestion that the community should carefully balance
these principles an use that to guide them in forming actual policy.
__Jason
On Sat, Jul 13, 2013 at 5:21 PM, Jimmy Hess <mysidia at gmail.com> wrote:
> On 7/8/13, ARIN <info at arin.net> wrote:
> > Draft Policy ARIN-2013-4
> > RIR Principles
>
> I continue to have some objection to this draft, because it is still
> a statement of supposed principles, not policy. Per PDP 3.2
> "proposals to change policy must address a clearly defined, existing
> or potential problem with number resource policy in the region."
>
> The purpose of ARIN policy is to define policy, not goals. The number
> resource policy manual is not the ARIN charter.
>
> PDP section 4 already defines principles of ARIN policy.
>
> So there does not appear to be anything to accomplish by the draft.
>
>
> "For example, Conservation often requires greater consideration in
> IPv4 address distribution due to the limited size of the address
> space, Routability has a higher weight for the massive IPv6 address
> space, and AS numbers place the highest value on Registration because
> they
> come from a moderately sized pool and are not subject to aggregation."
>
>
> This is no good.... we essentially have here a policy statement
> that ARIN should apply good judgement and consideration when using
> policy.
>
> Since they are supposed to do that anyways, the statement is redundant.
>
> We dont' need a policy statement say "Care must be taken to ensure
> balance with these
> conflicting goals "
>
> Care must be taken to ensure fairness and technical soundness given
> any conflicting policy....
>
>
> The policy itself should be introducing conflicting circumstances:
> It's the policy's job to get updated to resolve conflicts of that
> nature.
>
> Policy should provide clear implementable guidelines, not vague
> assertions that "you need to be careful, read the author's mind, and
> do whatever that person would want....".
>
> --
> -JH
> _______________________________________________
> PPML
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>
--
_______________________________________________________
Jason Schiller|NetOps|jschiller at google.com|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20130715/42e4bbb4/attachment.htm>
More information about the ARIN-PPML
mailing list