Your IP address could not be determined at this time.

Policy Proposal Template 1.0

Note: this is an archived version of the template. For the current template, please see http://www.arin.net/policy/pdp_appendix_b.html.

Appendix B

Template: ARIN-POLICY-PROPOSAL-TEMPLATE-1.0

  1. Policy Proposal Name:
  2. Author
    1. name:
    2. email:
    3. telephone:
    4. organization:
  3. Proposal Version:
  4. Submission Date:
  5. Proposal type:
    new, modify, or delete.
  6. Policy term:
    temporary, permanent, or renewable.
  7. Policy statement:
  8. Rationale:
  9. Timetable for implementation:
  10. Meeting presenter:

END OF TEMPLATE

Guidelines for Completing the ARIN Policy Proposal Template

  1. Policy Proposal Name
    Provide a name or title which can be used to identify the policy proposal.

  2. Author
    Fill in point of contact information including name, email address, phone number and organization.

  3. Proposal Version
    This is to help the author and ARIN keep track of changes to policy proposal text. Start with 1.

  4. Submission Date
    Enter the date.

  5. Policy type
    Indicate the policy type. Is this a new policy, modification to an existing policy, or elimination of an existing policy?

  6. Policy term
    How long will the policy remain in effect? Is it intended to be temporary, permanent, or renewable?

  7. Policy Statement
    Make a clear and concise policy statement that is unambiguous and actionable. The text written here ideally should fit right in to the existing policy document.

  8. Rationale
    Briefly list the rationale or justification for the policy proposal. Suggested points to consider include the following:

    • Describe the current status.
    • Identify the perceived problem that the policy seeks to remedy.
    • Who is affected by the problem?
    • Explain how the policy proposal would fix the problem.
    • How would the policy be enforced?
    • Are there any financial and/or liability implications for the community and ARIN?
    • Identify any special conditions, fees, exceptions, etc., that may be needed.
  1. Timetable for implementation
    Indicate your recommendation for implementation, immediately, six months, etc.?
  2. Presenter
    State whether the author intends to personally present the policy proposal for discussion at the next semi-annual public policy/membership meeting, or whether the author intends to allow the ARIN Advisory Council to represent by proxy. All suggested policies which become formal policy proposals must be presented at a Public Policy Meeting.

Additional Considerations:

Policy statement

If applicable try to provide text just as it would be inserted into existing policy sections. Or list the text that you want to remove or modify.

Do not put examples in the policy statement section, those may go in the section for rationale/justification.

Be clear in your use of words such as ‘must’ and ‘should’ (see RFC 2119).

Rationale

In general consider questions of who, what, where, when, why, and how often to establish a case and urgency for action. And, consider financial and liability implications to those affected, including ARIN.

State how the policy must be justified and enforced. Present pertinent parameters that may be used to quantify and/or track justification and enforcement.

Identify any special conditions, fees, exceptions, organizational interdependencies or cooperation needed, etc., in order to ensure effectiveness of the proposed policy.

Mailing Instructions:

Send the proposal to policy@arin.net.

Your suggested policy will be handled according to the ARIN Internet Resource Policy Evaluation Process. For more information see:
http://www.arin.net/policy/irpep.html.

ARIN will post your policy proposal to the Public Policy Mailing List and to the ARIN website. The ARIN Advisory Council (AC) will conduct their initial review. The result of the AC’s initial review will be posted to the Public Policy Mailing List.

Advanced Search