[arin-ppml] Staff proposing policy.
George, Wes E [NTK]
Wesley.E.George at sprint.com
Mon May 2 10:10:56 EDT 2011
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Chris Grundemann
Sent: Saturday, April 30, 2011 3:05 PM
To: Stephen Sprunk
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] Staff proposing policy.
On Thu, Apr 28, 2011 at 23:48, Stephen Sprunk <stephen at sprunk.org> wrote:
> IMHO, staff should be free to ask the community (via PPML or any other
> appropriate means) about our intent and goals, but I'm not comfortable
> with staff telling us what our intent or goals should be.
> Staff should also be free to point out when current or proposed policy
> does not appear to meet our intent or goals, as discovered above, or
> hard facts that are relevant to ongoing discussions. And, when one
> points out a problem, it's polite to also offer one or more possible solutions.
Is everyone aware that staff performs and publishes an assessment of all policy proposals that make it onto the AC's docket? These
assessments often include potential problems with the text, questions regarding intent, and sometimes even suggestions for making
the text more clear / less likely to be misunderstood.
[WEG] yes, but as this is only regarding existing proposed policy, this still creates a potential gap. Staff's review of policy
implemented at each meeting is mainly focused on new policies (either pending or recently implemented). I think that there are times
when existing policy (or lack of a policy to provide guidance) would be important to highlight, instead of simply focusing on
reviewing the last round of passed policy and the pending policy work. That said, this may be more effective as an update to the
existing method of providing feedback rather than formalizing the ability for staff to propose policy.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6753 bytes
Desc: not available
More information about the ARIN-PPML