Changes to Policy Development Process in RIPE

1. Introduction delete: </strong> delete: </h4> delete: <p align="left"> This document describes the RIPE Policy Development Process (RIPE PDP), outlining how policies relating to the operation of the Internet are developed by and for the RIPE community. The RIPE Chair is the author and owner of this document. delete: </p> delete: <p align="left"> insert: </h2>

Since its creation in 1989, RIPE has been a forum for people to decide from time to time agreed on common practices. These common practices may come in different forms and/or under different names:

• Best best common practice (BCP) delete: </li> delete: <li> Recommendations and guidelines to the community delete: </li> delete: <li> Recommendations and guidelines to the RIPE NCC delete: </li> delete: <li> Policy (or BCP), insert: </li>
insert: <li>
• recommendations to the community, insert: </li>
insert: <li>
• requests to the RIPE NCC, insert: </li>
insert: <li>
• recommendations to the RIPE NCC, insert: </li>
insert: <li>
• or just policy.

In this document refers solely to “Policy”. delete: </p> delete: <p align="left"> they are all called 'Policy'. insert: </p>

The process that results in the creation of a policy has some a few important and fundamental principles:

insert: <li>
1. it is open to all and follows an established, bottom-up process of collaboration. all. Everyone interested in the well-being of the Internet may propose a policy policy, and take part in the discussions that follow on from the proposal. delete: </li> delete: <li> It discussions. insert: </li>
insert: <li>
2. it is transparent. All discussions and resulting actions results are documented and freely available to all. delete: </li> delete: <li> Conclusions all insert: </li>
insert: <li>
3. conclusions are reached by consensus.
delete: <li> All policies are documented within RIPE Documents and placed in the RIPE Document Store. delete: </li>

This process has worked quite well over the years. This document does not describe the specific administrative or technical procedures established in order for seek to change that. insert: </p>

What this document does try to accomplish is a description of the process that will improve its management. insert: </p>

2. The Process insert: </h2>

In the process of developing a policy to be applied. Depending on the specifics of a policy, procedures can be set by the Local Internet Registries (LIRs), End Users and the RIPE NCC as required. These procedures must conform to all policies that several distinct phases are in place. delete: </p> delete: <p class=" "> RIPE Policies are also separate from RIPE NCC business practices and procedures. Business practices and procedures that the RIPE NCC follows are defined and governed by the RIPE NCC Executive Board and approved by the RIPE NCC membership. If a policy proposal would bring implementation and/or operational problems for the RIPE NCC if accepted, the RIPE NCC Executive Board is tasked to notify the RIPE community accordingly as well as to make necessary suggestions and recommendations about possible changes to the proposal. delete: </p> delete: <h4> delete: <strong> 2. The Process delete: </strong> delete: </h4> delete: <p align="left"> The process of developing a policy has four distinct phases: delete: </p> delete: <p align="left"> 1. identified: insert: </p>

insert: <li>
1. Creating a Proposal delete: </p> delete: <p align="left"> 2. insert: </li>
insert: <li>
2. Discussion Phase delete: </p> delete: <p align="left"> 3. insert: </li>
insert: <li>
3. Review Phase delete: </p> delete: <p align="left"> 4. insert: </li>
insert: <li>
4. Concluding Phase delete: </p> delete: <p align="left"> These four insert: </li>
insert: </ol>

Each of these phases are detailed below with timelines. below. insert: </p>

In the descriptions below, timelines are mentioned. They are proposed deadlines for the various stages. These proposal phases. Individual proposals may be varied for individual proposals, but choose to vary these, however the actual timescales must be documented.

In this process, the RIPE NCC (the RIPE community's secretariat) gives administrative support by: support, such as:

• Publishing administering proposals and related discussions insert: </li>
insert: <li>
• publication on relevant webpages delete: </li> delete: <li> Tracking web pages insert: </li>
insert: <li>
• tracking deadlines
delete: <li> Making announcements to the RIPE community delete: </li> delete: <li> Providing insert: </ul>

Anyone that wants to draft a policy proposal may seek assistance in drafting policy proposals if requested delete: </li> delete: <li> Providing from the RIPE NCC. The RIPE NCC will provide relevant facts and facts, statistics delete: </li> delete: <li> Publishing and an impact analysis that points to the possible effects of the proposed policy and assessment of the work that would be involved in implementation of a proposal. The RIPE NCC will also assist with the drafting of text if its implementation. delete: </li> delete: </ul> delete: <p align="left"> editorial services are required. insert: </p>

The process flow is illustrated in a diagram, attached as delete: <a href="#appendixa" data-linktype="anchor" data-val="2"> diagram in insert: <a href="#appendixa" data-linktype="anchor" data-val="0"> Appendix A .

2.1 Creating a Proposal delete: </strong> delete: </p> delete: <p align="left"> Discussions may be started by anyone insert: </h3>

Anyone can start a discussion at any time. Participants are welcome to discuss broad ideas as well as to make detailed policy proposals. Proposals are made using the a Policy Proposal template, attached as delete: <a href="#appendixb" data-linktype="anchor" data-val="3"> Template [ insert: <a href="#appendixb" data-linktype="anchor" data-val="1"> TEMPLATE Appendix B . delete: </p> delete: <p align="left"> ]. insert: </p>

The template forms a structure for the proposal. It details the reason for the proposal and any perceived consequences of the proposal.

A proposal is discussed publicly in the relevant RIPE Working Group (WG)[ delete: <a href="#r1"> 1 delete: </a> ]. The proposal is usually submitted via the chair of that WG. If the proposer [ delete: <a href="#r2"> 2 delete: </a> ] is not certain which WG is Chair of the relevant RIPE Working Group or via the RIPE Chair. insert: <br />
insert: <br />
The RIPE NCC identifies proposals with a number and publishes them in the appropriate for discussion of the proposal, they can send the proposal to the RIPE Chair at delete: <a href="mailto:[email protected]"> [email protected] delete: </a> . In some cases, a proposal may need more than one WG's input. In such cases, before the proposal is published, section of the relevant WG chairs will discuss the situation and decide the WG most suited to discussion of the proposal. Necessary announcements will be made to the other WG(s) so they can follow the discussions. delete: </p> delete: <p align="left"> The RIPE NCC gives each proposal its own unique identifier and publishes it on a dedicated RIPE webpage. This webpage contains working groups web pages. insert: </p>

The page will indicate the version history and the status of all proposals. A proposal can have one of the following statuses at any given time: proposals:

• delete: <strong> Open for Discussion: delete: </strong> Meaning that the proposal is still being discussed within the RIPE PDP. delete: </li> delete: <li> delete: <strong> Accepted: delete: </strong> Meaning that the RIPE community accepted the proposal after Discussion; insert: </li>
insert: <li>
• Agreed; or insert: </li>
insert: <li>
• Withdrawn. insert: </li>
insert: </ul>

The RIPE NCC will also maintain a web page with an overview of all stages of the RIPE PDP were completed. delete: </li> delete: <li> delete: <strong> Withdrawn: delete: </strong> Meaning that the proposal is withdrawn either by the proposer or by the WG chairs at one of the decision-making points. delete: </li> delete: </ul> delete: <p class=" "> delete: <br /> delete: <strong> outstanding policy proposals. insert: </p>

2.2 Discussion Phase delete: </strong> delete: </p> delete: <div> insert: </h3>

Once a proposal is has been submitted, it is will be announced on the Policy Announce Mailing List ( a dedicated mailing list to which anybody can subscribe: [email protected] ), which anyone can subscribe to. . This announcement will also indicates indicate where discussion on the this proposal will take place. This is usually sent to Usually this will be the relevant WG working group mailing list. The WG insert: </p>

Where discussion leads to an amendment of a proposal, an amended proposal will be published highlighting the changes. If there is significant comment and change suggested there may be multiple iterations of this process. Each published revision of a proposal will contain a history of changes to document this process. insert: </p>

The Working Group chair sets the will set a limited time period for the Discussion Phase and this is at least discussion phase, not usually less than four weeks. delete: </div> delete: <p align="left"> At the end of the Discussion Phase, the proposer, with the agreement of the WG chair, decides whether the proposal will move to the next phase (Review Phase) or if it should be withdrawn from the RIPE PDP, depending on the feedback received. This should be done no more than four weeks after the end of the Discussion Phase. If the proposer does not communicate this decision to the WG chair within four weeks, the WG chair can withdraw the proposal due to lack of response from the proposer. delete: </p> delete: <p align="left"> If significant comments or changes are suggested during the Discussion Phase, the proposer will edit the proposal and the new version of the proposal will be published. A new Discussion Phase will then start for the new version of the proposal. delete: </p> delete: <p align="left"> If the suggested comments and changes are not so significant to require a new Discussion Phase, the proposer and WG chair can decide to move the proposal to the next phase (Review Phase) with a new version of the proposal incorporating the necessary edits. delete: </p> delete: <p align="left"> Each version of the proposal is publicly archived to transparently show the history of changes to the proposal. delete: </p> delete: <p align="left"> If the proposer decides to take the proposal to the next phase, the draft RIPE Document should be prepared within four weeks. A policy proposal can result in the modification of an existing RIPE Document or can result in publication of a completely new RIPE Document. If the proposal is a modification of an existing policy or it is a new policy that needs to be documented in an existing RIPE Document, then a draft RIPE Document clearly pointing to the changes to the existing document will be published. If the proposal requires a completely new RIPE Document to be published, the draft should be produced before the proposal can be moved to the Review Phase. delete: </p> delete: <p align="left"> The RIPE NCC will also conduct and publish an impact analysis about the proposal before it can be moved to the Review Phase. The goal of this analysis is to provide relevant supporting information to facilitate the discussions about the proposal and provide some projections about the possible impact if it were to be accepted. This analysis will contain the following points: delete: </p> delete: <ul> delete: <li> The RIPE NCC's understanding of the proposed policy delete: </li> delete: <li> Impact on the registry and addressing systems (including Internet resource consumption, aggregation and fragmentation) delete: </li> delete: <li> Impact on RIPE NCC operations/services delete: </li> delete: <li> Legal impact delete: </li> delete: </ul> delete: <div> delete: <strong>   delete: </strong> delete: </div> delete: <p class=" "> delete: <strong> insert: </p>

2.3 Review Phase delete: </strong> delete: </p> delete: <p align="left"> The purpose of the Review phase is to review the full draft RIPE Document compiled at the end of the Discussion Phase so that the final documentation the proposal will lead to and all modifications made to that document are transparent to the community. During the Review Phase, insert: </h3>

Following the conclusion of the discussion of the proposal can continue, also in the light of the impact analysis that is published at the beginning of this phase, and within the context of the proposal, further modifications can still be suggested regarding the draft RIPE Document. The Review Phase should last for a maximum of four weeks. delete: </p> delete: <p align="left"> At the end of the Review Phase, the WG chair the RIPE Working Group Chair determines whether the WG working group has reached rough consensus. If the WG chair decides that consensus has not been reached, then the WG chair can proposer may decide to withdraw the proposal. Alternatively, the WG chair can send the proposal back to the Discussion Phase if the proposer is willing to continue to author the proposal and make the necessary changes to the proposal according to the feedback received from the community. The WG chair can also decide to a new round of discussion and documentation may occur. insert: </p>

The review phase will have the draft RIPE Document edited and start a new Review Phase with a new version of the proposal. delete: </p> delete: <p align="left">   delete: </p> delete: <p align="left"> delete: <strong> a limited time period, but not more than four weeks. insert: </p>

2.4 Concluding Phase delete: </strong> delete: </p> delete: <p align="left"> If the WG chair insert: </h3>

When the RIPE Working Group Chair determines that the WG working group has reached consensus at the end of the Review Phase, the WG chair a consensus, s/he moves the proposal to a "Last Last Call for Comments" and the Concluding Phase starts. The Last Call period lasts four weeks. Comments. The Last Call announcement is also posted to the WG working group mailing list, the Last Call announcements mailing list and to the Policy Announce Mailing List ( delete: <a class="email-link" title="" href="mailto:[email protected]" target="_self"> [email protected] delete: </a> ). delete: </p> delete: <p align="left"> The purpose of this Last Call period is to provide the community with a final opportunity to comment on the proposal. This is mainly intended for those who missed the previous two phases and want to oppose the proposal. It gives time to the community after the relevant WG chair declares rough consensus at the end of the Review Phase so that suggestions for any final changes or objections to the proposal can be sent to the WG mailing list. At this stage, objections need to be justified just as in the other phases for them to be taken into account. delete: </p> delete: <p align="left"> Chairs of all working groups. At the end of the Last Call period, the WG chair will evaluate the feedback received during this period and working group chairs will decide together whether a consensus has been achieved. insert: </p>

The last call period will last four weeks. insert: </p>

If there is no feedback from the community at this stage, this is likely to be regarded as consensus and it will mean the previous call of rough consensus from the WG chair at the end of the Review Phase still holds. delete: </p> delete: <p align="left"> If a consensus has been achieved, the RIPE NCC will announce the decision of the WG chair and, RIPE Working Group Chairs and implement the policy, if necessary, implement the policy. delete: </p> delete: <p align="left"> needed. insert: </p>

If consensus has not been achieved, the WG chair can decide to either withdraw the proposal or send it back to one of the previous phases. The achieved the proposer (or anyone else) is free to return the proposal to the WG working group for further discussion after a withdrawal. delete: </p> delete: <h4> delete: <strong> 3. Appealable Actions delete: </strong> delete: </h4> delete: <p class=" "> delete: <strong> 3.1 Discussion Phase delete: </strong> delete: </p> delete: <p align="left"> During the Discussion Phase, anyone who has a complaint or other concern about the policy proposal or how it is being handled in the WG should first raise the matter with the chair of that WG. If the dispute cannot be resolved with the WG chair, the Appeals Procedure can be invoked. delete: </p> delete: <p align="left">   delete: </p> delete: <p class=" "> delete: <strong> 3.2 Review & Concluding Phases delete: </strong> delete: </p> delete: <p align="left"> At these stages of the process – i.e. after the WG chair has declared initial consensus or the proposal is in Last Call – complaints should not be about the policy proposal itself unless there are exceptional extenuating circumstances. delete: </p> delete: <p align="left"> Anyone who believes that the proposal has not been handled correctly or that the WG chair has made an incorrect determination of consensus should first raise the matter with the WG chair. If the dispute cannot be resolved with the WG chair, the Appeals Procedure can be invoked. delete: </p> delete: <h4> delete: <strong> 4. Appeals Procedure delete: </strong> delete: </h4> delete: <p align="left"> If a grievance cannot be resolved with the chair of the WG the matter can be brought to the attention of the Working Group Chairs Collective (WGCC). Anyone may submit an appeal. This must be submitted to the relevant WG mailing list(s) and to the Policy Announce Mailing List ( delete: <a class="email-link" title="" href="mailto:[email protected]" target="_self" data-val="ce5bd2a58a1d897afc19b8658879dbce" data-linktype="internal"> [email protected] delete: </a> ). The appeal will also be published by the RIPE NCC at appropriate locations on the RIPE web site. Any appeal should include a detailed and specific description of the issues and clearly explain why the appeal was submitted. An appeal must be submitted no later than four weeks after the appealable action has occurred. delete: </p> delete: <p align="left"> The WGCC will decide by consensus whether to uphold or reject appeals which have been submitted. The decision of the WGCC should be reached no later than four weeks of an appeal being made. Interested parties shall recuse themselves from any discussion or decision within the WGCC relating to the appeal. delete: </p> delete: <p align="left"> If the dispute cannot be resolved by the decision of the WGCC, the issue should be brought to the RIPE Chair. The decision of the RIPE Chair will be final. delete: </p> delete: <h4> delete: <strong> References delete: </strong> delete: </h4> delete: <p align="left"> delete: <a id="r1"> delete: </a> [1] The RIPE community has formed a number of working groups to deal with issues and topics affecting the Internet community. Every RIPE Working Group has at least one chair (some working groups may have co-chairs). They are responsible for chairing discussions in the working group and, where necessary, making decisions in the Policy Development Process. delete: </p> delete: <p align="left"> delete: <a id="r2"> delete: </a> [2] A proposal can have more than one author. delete: </p> delete: </div> delete: <h4> discussion. insert: </p>

Appendix A: A - The Policy Development Process Diagram delete: </h4> delete: <p> delete: <img class="image-inline" src="resolveuid/ce5bd2a58a1d897afc19b8658879dbce" alt="RIPE Policy Development Process" width="500" height="599" /> delete: </p> delete: <p align="left"> delete: <strong> NOTE: delete: </strong> The actual timelines of individual proposals may vary. They are documented and announced per proposal delete: </p> delete: <h4> insert: </h2>

insert: <img class="img-100" src="../../../resolveuid/59cf005f268c4d81b5c3ab2a7da1fceb" alt="" data-linktype="image" data-scale="" data-val="59cf005f268c4d81b5c3ab2a7da1fceb" /> insert: </p>

Appendix B: B - Policy Submission Template insert: </h2>

insert: <li>
1. Number: (The RIPE NCC will assign this) insert: </li>
insert: <li>
2. Policy Proposal Template delete: </h4> delete: <p> 1. delete: <strong> Number (assigned by the RIPE NCC) delete: </strong> delete: <br /> 2. delete: <strong> Policy Name: insert: </li>
insert: <li>
3. Author: insert: <br />
   a. name: insert: <br />
   b. e-mail: insert: <br />
   c. organisation: insert: </li>
insert: <li>
4. Proposal Name delete: </strong> delete: <br /> 3. delete: <strong> Author Details delete: </strong> delete: </p> delete: <p style="padding-left: 30px;"> a. name delete: </p> delete: <p style="padding-left: 30px;"> b. email delete: </p> delete: <p style="padding-left: 30px;"> c. organisation delete: </p> delete: <p> 4. delete: <strong> Proposal Version (assigned by the RIPE NCC) delete: </strong> delete: <br /> 5. delete: <strong> Version: (Usually this will be version 1.0 for a new submission) insert: </li>
insert: <li>
5. Submission Date delete: </strong> delete: <br /> 6. delete: <strong> Date: insert: </li>
insert: <li>
6. Suggested RIPE WG Working Group for discussion and publication delete: </strong> delete: <br /> 7. delete: <strong> publication: insert: </li>
insert: <li>
7. Proposal Type delete: </strong> delete: </p> delete: <p style="padding-left: 30px;"> type: insert: <br />
   a. new, modification modify, or deletion delete: </p> delete: <p> 8. delete: <strong> delete. insert: </li>
insert: <li>
8. Policy Term delete: </strong> delete: </p> delete: <p style="padding-left: 30px;"> term: insert: <br />
   a. Temporary (time period) delete: </p> delete: <p style="padding-left: 30px;"> b. Indefinite delete: </p> delete: <p> 9. delete: <strong> temporary, permanent, or renewable. insert: </li>
insert: <li>
9. Summary of Proposal delete: </strong> delete: <br /> 10. delete: <strong> proposal: insert: </li>
insert: <li>
10. Policy Text delete: </strong> delete: </p> delete: <p style="padding-left: 30px;"> text: insert: <br />
    a. Current policy text (if modification) delete: </p> delete: <p style="padding-left: 30px;"> modify): insert: <br />
    b. New policy text delete: </p> delete: <p> 11. delete: <strong> Rationale delete: </strong> delete: </p> delete: <p style="padding-left: 30px;"> New: insert: </li>
insert: <li>
11. Rationale: insert: <br />
    a. Arguments supporting the proposal delete: </p> delete: <p style="padding-left: 30px;"> insert: <br />
    b. Arguments opposing the proposal delete: </p> delete: <h4> delete: <strong> Acknowledgements delete: </strong> delete: </h4> delete: <p align="left"> This document was edited by Fergal Cunningham. delete: </p> delete: <p align="left"> RIPE Working Group Chairs have reviewed and commented on the document before it was published. delete: </p> insert: </li>
insert: </ol>