Your IP address is


AFRINIC Policy Development Process Bis V1

  • Ref. Name:
  • Submitted:
    28 April 2017
  • Versions: 1.0
  • Status:
    Under Discussion
  • Author:
    Komi Abel Elitcha
    Arnaud A. A. AMELINA
    Honest Ornella GANKPA
    Alain P. AINA
  • Amends: Art. 3.0 of the Consolidated Policy Manual
  • Staff Assessment

1.0 Summary of the Problem Being Addressed by this Policy Proposal

The current Policy Development Process is shaped around a working group, which is administered by two Chairs.


The working group operations rules are not clearly defined as for:

  • Requirements for chairmanship
  • Chairs roles and responsibilities
  • How Chairs exercise their powers
  • Chairs election
  • Chairs resignation
  • Working group code of conduct

The consensus process used by the working group for decision-making is not defined, opening doors for interpretations and inactions.


The current process does not have provision for proposal adoption, which induces duplication of proposals dealing with same problem, lack of clarity of problem statements and proposals out of scope of the PDP. It also does not define a clear method for moving proposals forward.


The current PDP does not have provision for board adopting policies as per section 11.4 of the AFRINIC constitution in the varying of the process.


2.0 Summary of How this Proposal Addresses the Problem

This Policy proposal addresses these issues by:

  • Designing a policy development process around one Chair assisted by a Vice-Chair;
  • Defining the roles and responsibilities of the Chair and Vice-Chair;
  • Defining how Chair exercises his authority and powers;
  • Detailing the consensus process with regard to major and minor objections and responsibility of the Chair of the working group in gauging the consensus;
  • Providing with different phases for policy proposals:  from adoption till last call and ratification by the AFRINIC board of Directors;
  • Providing provision on how board adopts policy as per section 11.4 of the constitution that is managed in varying the PDP.
  • Clarifying disputes and appeals mechanisms


3.0 Proposal

This proposal replaces section 3.0 of the CPM (The Policy Development Process) entirely as follows:


3.0 The Policy Development Process

3.1 Scope

The Policy Development Process covers the development and modification of policies for proper and responsible usage and management of Internet Number Resources within the AFRINIC service region.

The PDP is shaped to come up with clear, technically effective and useful policies.

Policies for Internet number resource management must be evaluated for technical effectiveness against three requirements: conservation, aggregation, and registration.

Changes to the Policy Development Process itself will also follow the process.

Internet number resource policies are distinctly separate from AFRINIC general business practices and procedures. General business practices and procedures are not within the purview of the Policy Development Process.

Internet number resources consist of Internet Protocol version 4 (IPv4) address space, Internet Protocol version 6 (IPv6) address space, and Autonomous System (AS) numbers.


3.2 Policy Development Principles

All policies are developed by the Internet community following four principles: openness, transparency, fairness and bottom-up. The Internet community initiates and discusses the policy proposals. If consensus is reached on a given policy proposal, it is recommended to the AFRINIC Board of Directors to be ratified as an effective policy to be implemented within AFRINIC region.


3.2.1 Openness

All policies are developed in an open forum in which anyone may participate. There are no qualifications for participation.


3.2.2 Transparency

All aspects of the Policy Development Process are documented and publicly available via the AFRINIC website. The discussions are publicly archived. All procedures that are developed to implement the policy are documented by AFRINIC and are publicly available.


3.2.3 Fairness

The policies are to ensure fair distribution of Internet number resources and facilitate the operation of the Internet within AFRINIC Service Region.


3.2.4 Bottom-Up

The community drives policy development.


3.3 Operations of the Policy Development Working Group (PDWG)

The Policy Development Working group (PDWG) provides an open public forum to discuss Internet numbers resource management policies and related topics of interest to AFRINIC and the Internet community in the AFRINIC service region. PDWG sessions are held at AFRINIC Public policy meetings. Between meetings, discussions continue via the Resource Policy Discussions (rpd) mailing list. The PDWG is open to all interested individuals.

The Policy Development Working Group is primarily administered by one Chair and one vice-Chair. The WG Chair and Vice-Chair perform a vital role in managing the working group. The effectiveness of the PDWG is dependent on the active participation of the Chair and the Vice-Chair. The PDWG Chair and Vice-Chair undertake their work on a volunteer basis.

The PDWG Chair is responsible for coordinating the activities of the policy development working group. He guides a policy proposal through its different phases in order to gauge consensus.

The Vice-Chair helps the WG Chair to coordinate the activities of the policy development working group.

The WG Chair and Vice-Chair are expected to attend all AFRINIC Public Policy Meetings. The WG Chair and Vice-Chair must remain subscribed to the AFRINIC Policy Discussion mailing list( This e-mail address is being protected from spambots. You need JavaScript enabled to view it ) for the duration of their term. Both the PDWG Chair and Vice-Chair must also be subscribed to the AFRINIC member-discuss mailing list during their term.

The challenge of managing the policy development working group sessions is to balance the need for open and fair consideration of the issues against the need to make forward progress.  The working group, as a whole, has the final responsibility for striking this balance. The Working Group Chair has the responsibility for overseeing the process.

To facilitate making forward progress, the Working Group Chair may wish to decide to reject or defer the input from an individual, based upon the following criteria:



The input pertains to a topic that already has been resolved and is redundant with information previously available;



The input is new and pertains to a topic that has already been resolved, but it is felt to be of minor import to the existing decision;



The input pertains to a topic that the working group has not yet opened for discussion;



The input is outside of the scope of the working group.

Occasionally one or more individuals may engage in behavior on a mailing list that, in the opinion of the WG Chair, is disruptive to the WG process. Unless the disruptive behavior is severe enough that it must be stopped immediately, the WG Chair should attempt to discourage the disruptive behavior by communicating directly with the offending individual. If the behavior persists, the WG Chair should send at least one public warning on the RPD mailing list. As a last resort and typically after one or more explicit warnings, the WG Chair may suspend the mailing list posting privileges of the disruptive individual for a period of not more than 30 days. Even while posting privileges are suspended, the individual must not be prevented from receiving messages posted to the list. Like all other WG Chair decisions, any suspension of posting privileges is subject to appeal.


3.3.1 Responsibilities of PDWG Chair

The responsibilities of the AFRINIC PDWG Chair are listed below: Before an AFRINIC Public Policy Meeting: After a Public Policy Meeting:

  • Send report of Public Policy Meeting to the community and policy discussion mailing lists including policy proposal discussion outcomes and open action items.
  • Monitor discussion during the concluding phase for comments period.
  • Summarize discussions and, following the end of the call for comments, post the decision regarding whether the proposal has reached rough consensus or not.
  • The Chair may delegate tasks to Vice-Chair as necessary.


3.3.2 Responsibilities of PDWG Vice-Chair

Vice-Chair responsibilities include but are not limited to:

  • Attend at least one AFRINIC Public Policy Meeting held each year.
  • Remain subscribed to the policy discussion mailing list for the duration of their time as Vice-Chair
  • Monitor remote chat-room discussions during the AFRINIC Public Policy Meeting
  • Undertake any of the tasks normally performed by the PDWG Chair when requested. In the event that the PDWG Chair is unavailable to perform some of his duties, the Vice-Chair will assume these responsibilities.


3.3.3 Electing the Chair and Vice-Chair

The AFRINIC community elects a policy development working group Chair and one Vice-Chair for a two year term. The PDWG Chair and Vice-Chair’s elections occur in alternate years.

The AFRINIC NomCom appoints the PDWG Chair and Vice-Chair using the following process:

AFRINIC Staff sends a call for nominations to the policy development mailing list ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it ). The call will contain:

  • Details of the duties of the position.
  • The closing date for nominations; 30 days from the date of the call
  • A request for a short biography and description of nominees.
  • A requirement that candidates for the Chair position should be active on the AFRINIC policy mailing list and must have attended at least two (2) AFRINIC Public Policy Meetings,
  • A requirement for candidates to confirm their ability and willingness to commit to the responsibilities associated with the Chair and Vice-Chair positions.

If at least one nomination is received by closing date, an election must be held. The election must be held at the upcoming Public Policy Meeting as the first item on the agenda.

Candidates will be invited to give a short speech. Voting will take place by a count of a show of hands.

Only candidates who are present at the public policy meeting will be included in the vote. If a current Vice-Chair stands for the position of Chair and is elected, the newly vacant Vice-Chair position can be filled by one of the remaining candidates for the Chair position or by a call for volunteers at the public policy meeting.

There will be a handover period. The outgoing Chair will manage proposals reaching consensus at the current Public Policy meeting to the completion of the Policy Development Process.


3.3.4 Removing a PDWG Chair or Vice-Chair

If the PDWG Chair or Vice-Chair does not attend one in every two consecutive AFRINIC Public Policy Meeting, the Chair or Vice-Chair will be removed from their role. The process of electing a replacement will then begin.

Anyone may request the recall of a Working Group Chair at any time, upon written request with justification to the AFRINIC Board of Directors. The request must be supported by at least ten (10) other persons. The AFRINIC Board of Directors shall appoint a recall committee, excluding the persons requesting the recall and the Working Group Chair. The recall committee shall investigate the circumstances of the request for the recall and determine the outcome.

If the outcome is that the WG Chair or Vice-Chair has to be recalled then the process of electing a replacement will then begin.


3.3.5 Resignation of a Chair or Vice-Chair

If a PDWG Chair resigns, the vice-Chair will assume the role of Chair and nominate a member of the community to exercise the role of Vice-Chair until the next Public Policy Meeting. This nomination has to be approved through non-objection by the working group via the mailing list. At least 30 days prior to the Public Policy Meeting, the AFRINIC NomCom will initiate procedures for electing the new Chair.

If a Vice-Chair resigns, the Chair shall nominate a member of the community to exercise the role of Vice-Chair until the next Public Policy Meeting. This nomination has to be approved through non-objection by the working group via the mailing list. At least one month prior to the Public Policy Meeting, the AFRINIC NomCom will initiate procedures for electing the new Chair.

If both Chair and vice Chair resign, The AFRINIC Ltd CEO shall lead the appointment by the working group of an interim Chair via the mailing list or at The Public Policy meeting.

The Interim Chair will act up to the election of the new Chair and shall be assisted by AFRINIC staff.


3.4.0 Consensus inside the PDWG

Most of the decisions in the working group operations and discussions on policy proposals are made through rough consensus, unless specified otherwise.

The PDWG consensus process is a multi-stakeholder approach to decision-making. The process is used to develop the best possible resource management policies for the AFRINIC service region.

The consensus process begins when somebody proposes a new policy.

This discussion phase begins on the mailing list and continues during the Public policy meetings.


3.4.1 Minor objections

A minor objection is one where the objector believes some problems may occur for some participants in the group if the proposal goes forward.

The PDWG participants should work together to see if the proposal can be modified to overcome minor objections.

However, it is not always possible to overcome these objections. In this case, the Chair may ask the objectors if they are prepared to acknowledge that the overall advantages of the proposal outweigh their objections and are willing to set them aside.


3.4.2 Major objections

Major objections are serious and indicate a belief that major problems will occur for parts of the community if the proposal goes forward; therefore, the proposal cannot be adopted in its current format.

The Chair should devote sufficient time for the PDWG to discuss ways to overcome major objections.

PDWG Participants, including the proponent, should work together to develop solutions that overcome major objections.

Consensus is reached on a proposal if the PDWG is able to successfully work through all objections in this way. It is not necessary for everyone to agree with the proposal. ‘Rough consensus’ is the point where all objections have been resolved or given due consideration and the PDWG believes the benefits outweigh the disadvantages.


3.4.3 Reaching consensus

In the meeting the Chair may ask for a show-of-hands, or other techniques, to gauge support for a policy proposal. The use of show-of-hands or other techniques is not a vote. It is a way of broadly measuring opinion and the Chair’s final decision takes many additional factors into account, including earlier discussions on the mailing list.

The aim of the PDWG is to carefully consider all opinions before making a decision. At the end of the discussion, the Chair will decide if the working group has reached consensus.

Consensus is achieved when everyone consents to the decision of the group. The decision may not be everyone’s first preference, but is acceptable to all participants.


3.5.0 Public Policy Meeting

Public Policy Meeting means a meeting open to the community wherein proposals for policies are discussed within the framework of the Policy Development Process (PDP)

The agenda of the meeting shall be announced by the Chair of the PDWG on the Resource Policy Discussion mailing list at least two weeks prior to the meeting. No change can be made to a policy proposal within one week of the meeting. This is so that a stable version of the policy proposal can be considered at the meeting.

The WG Chair determines whether rough consensus has been achieved during the Public Policy Meeting.

When a policy proposal has reached the Review Phase, it is placed on the agenda of an open public policy meeting.

If the Chair can’t participate in meeting, the Vice-Chair will lead the meeting assisted by AFRINIC staff.

If the Vice-Chair can’t participate in meeting, the Chair will lead the meeting assisted by AFRINIC staff.

If WG Chair and Vice-Chair can’t participate to meetings, the working group shall appoint one (1) person to lead the session and is assisted by one AFRINIC staff.

While open discussion and contribution is essential to working group success, the Chair is responsible for ensuring forward progress. When acceptable to the WG, the Chair may call for restricted participation (but not restricted attendance!) at Public Policy meetings for the purpose of achieving progress. The Working Group Chair then has the responsibility to refuse to grant the floor to any individual who is unprepared or otherwise covering inappropriate material, or who, in the opinion of the Chair is disrupting the WG process.


3.6.0 Policy proposals

Anyone can submit a policy proposal to PDWG Chair. One or all initiators of a policy proposal have the option to remain anonymous. Hence PDWG Chair has the responsibility to act as document editor or set a call for a volunteer from the WG to act as document editor on the policy proposal.

A Document Editor is responsible for ensuring that the contents of the document accurately reflect the decisions that have been made by the working group.


3.6.1 Phases of a policy proposal

A policy proposal follows four phases during its evolution through policy development process: Adoption Phase, Discussion Phase, Review Phase and the Concluding Phase. The Adoption Phase

During this phase, the PDWG Chair will assess the clarity and the relevance of the problem statement in accordance to the scope of the PDP and the existing policies.

PDWG Chair or AFRINIC staff can work with the initiator(s) to redefine the problem statement if need be.

For policy proposals which are out of scope of AFRINIC PDP, or addressing the same issue as another policy proposal already adopted, the PDWG Chair shall dissuade the initiator(s) from submitting to the working group.

In case of disagreement or doubt the PDWG Chair may consult the working group on whether or not the working group is willing to adopt the proposal for discussion based on its problem statement.

Once adopted by the working group, the initiator(s) grants all rights to the working group and the proposal becomes a community document.

In all matters of intellectual property rights and procedures, the intention is to benefit the community and the public at large, while respecting the legitimate rights of others.

The adoption phase should last maximum of two weeks. At the term of two weeks, based on consensus, PDWG Chair declares the beginning of the Discussion phase or declares the rejection of the policy proposal.

The initiator(s) of the policy proposal can reformulate their problem statement and go back to the adoption phase. The Discussion Phase

Once the PDWG Chair declares the adoption of a policy proposal for discussion, the Discussion Phase begins on the RPD Mailing List ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it ). The PDWG Chair should set the period for the Discussion Phase and this must be for at least four weeks.

During the discussion phase, the working group evaluates the policy proposal and comments are made. Politeness and courtesy must lead discussions, PDWG Chair should emphasize this each time it is relevant.

At the end of the Discussion Phase, the PDWG Chair provides a summary of the discussion highlighting the close and open issues.

Once the working group agrees on the summary, which can be edited according to feedbacks, the PDWG Chair decides whether the policy proposal should move to the next phase (Review Phase), go to an extended discussion phase or should be withdrawn. The decision to move forward will be announced on RPD mailing list.

If significant comments or modifications are suggested during the Discussion Phase, the policy proposal initiators will review the proposal and a new version will be published. A new Discussion Phase will then start for the new version of the proposal. This new Discussion Phase should last at least two weeks.

If the suggested comments or modifications are not so significant to require a new Discussion Phase, the PDWG Chair can decide to move the proposal to the next phase (Review Phase) with a new version of the proposal incorporating the necessary changes.

Each version of the proposal is publicly archived to transparently show the history of changes to the proposal and published on AFRINIC web site.

The new version of the policy proposal should be announced on AFRINIC RPD mailing list and website before the proposal can be moved to the Review Phase.

The PDWG Chair shall request the AFRINIC Ltd CEO to 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:

AFRINIC Ltd’s understanding of the proposed policy

Impact on the registry and Internet Number Resources

Impact on AFRINIC Ltd’s operations/services

Legal impact The Review Phase

The goal of this phase is to review the full draft policy proposal compiled at the end of the Discussion Phase. Hence, the final documentation of the proposal will lead to rough consensus; all modifications made to that document should be transparent to the working group. During the Review Phase, discussion of the draft proposal can continue, also in the light of the impact analysis, and within the context of the proposal, further modifications can still be suggested regarding the draft proposal. The Review Phase should last for a maximum of four weeks.

At the end of the Review Phase, the PDWG Chair determines whether the working group has reached rough consensus. In the case the PDWG Chair decides that consensus has not been reached, then the PDWG Chair can send the draft proposal back to the Discussion Phase if the initiators are willing to make an improvement of their proposal and make the necessary changes according to the feedback received from the community.

A draft proposal sent back to discussion phase automatically lost its status of draft proposal.

The PDWG Chair can also decide to have the draft proposal edited and start a new Review Phase with a new version of the proposal or otherwise the proposal shall be withdrawn. The Concluding Phase

In the case, the Chair determines that the WG has reached consensus at the end of the Review Phase, the PDWG Chair moves the draft proposal to a "Last Call for Comments" and the Concluding Phase starts. The Last Call period lasts at least two weeks. The Last Call shall be announced on policy discussions mailing list.

The purpose of this Last Call period is to provide the community with a final opportunity to comment on the draft proposal. This is especially intended for those who missed the previous two phases and want to oppose the proposal or make substantial remark. The "Last Call for Comments" gives time to the community after the PDWG 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.

At the end of the Last Call period, the PDWG Chair will assess the feedback received during this period and decide whether consensus has been achieved. If there is no feedback from the community at this stage, this is regarded as consensus.

If rough consensus is achieved, the PDWG Chair will announce the decision and initiate the process of the draft proposal ratification by AFRINIC board of directors.

If consensus has not been achieved, the PDWG Chair can decide to either send back the proposal to the previous phases of Discussion or Review, otherwise the proposal shall be withdrawn.

The initiators of a policy proposal (or anyone else) are free to return the proposal to the RPD mailing list for further discussion after a withdrawal.


3.6.2 Policy Ratification

After a draft proposal has reached rough consensus, AFRINIC board of Directors have the obligation to check if process have been followed very well.

In the case of a rejection, the AFRINIC board of directors must justify and publish the reason on the resources policy discussion list ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it ) and on the AFRINIC website, and ask the working group to rectify the issue.

After ratification, AFRINIC board of Directors, announce their decision to the working group and this activates implementation of the policy by AFRINIC staff.


3.7.0 Appeals

3.7.1 Appealable Actions Suspension of posting privileges

Anyone whose privileges of posting to the Resources Policy Discussion mailing list have been suspended by the WG Chair may file an appeal against the decision to the AFRINIC board of directors. The board shall investigate the circumstances of the justification as prescribed and determine the outcome. During the Discussion Phase

During the Discussion Phase, anyone who has a complaint or other concern about the policy proposal or how it is being handled on the policy development mailing list should first raise the matter with the PDWG Chair. If the dispute cannot be resolved with the PDWG Chair, the appeals Procedure can be invoked. During the Review & Concluding Phases

At these stages of the process – i.e. after the PDWG 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.

Anyone who believes that the proposal has not been handled correctly or that the PDWG Chair has made an incorrect determination of consensus should first raise the matter with the PDWG Chair. If the dispute cannot be resolved with the WG Chair, the Appeals Procedure can be invoked.


3.7.2 Appeals procedure

An appeal can only be filed if it is supported by three (3) individuals from the Working Group who have participated in the discussions to an Appeal committee appointed by the AFRINIC Board of Directors. The appeal must be submitted within two weeks of the public knowledge of the decision. The Appeal Committee shall issue a report on its review of the complaint to the Working Group. The Appeal Committee may direct that the Chair decision be annulled if the Policy Development Process has not been followed.


3.8.0 Varying the Process

3.8.1 Variance by the PDWG

The process outlined in this document may vary in the case of an emergency. Variance is for use when a one-time waiving of some provision of this document is required. The decision to vary the process is taken by the Working Group Chair. There must be an explanation about why the variance is needed. The discussion, review and concluding period shall not be less than four weeks. If there is consensus, the policy is approved and it must be presented at the next Public Policy Meeting.


3.8.2 Variance by the AFRINIC board of Directors

As per section 11.4 of the AFRINIC constitution, AFRINIC board of Directors may adopt policies regarding the management of Internet number resources where it considers that the same is necessary and urgent, having regard to the proper and responsible usage of these resources.

The decision to vary the process is presented to the Working Group. There must be an explanation about why the variance is needed. The Board of Directors shall allow the working group to review the proposal for a period of not less than two weeks.

While the board of Directors is encouraged to take into consideration the comments and suggestions from this review, these comments and suggestions are not binding.

The working group at the following public policy meeting will endorse any such adopted policy as per section 11.5 of the bylaws,


4.0 Revision History


Date Revision
28 April 2017 Version 1 posted to rpd



5.0 References


This proposal is mainly based on the intensive discussions we had on the current PDP during 2016 and 2017 on the RPD mailing list. It addresses issues by referring to best practices from the IETF and the PDPs of other RIRs.



***Staff Assessment***

Proposal AFPUB-2017-GEN-002-DRAFT-01
Title AFRINIC Policy Development Process BIS
Assessed 19/May/2017

1.0 Staff Understanding of the Proposal

The proposal is a revision of the Policy Development Process (Sec 3 of the CPM).

2.0 Staff Comments

Observations from staff mostly concern clarity:

  1. There should be a provision for new policy proposals to be edited (for clarity, better presentation, English grammar, numbering, etc.) by the PDWG chair and vice-chair, working with the staff, and with other persons that they choose to assist them.
  2. Every paragraph should be numbered for ease of reference.
  3. Under “Phases of a policy proposal”, the idea appears to be that the problem statement and description is agreed in the Adoption Phase, the outline of the solution is agreed in the Discussion Phase, and the wording of the proposal is agreed in the Review Phase, but this is not clear.
  4. Under “Consensus inside the PDWG”, staff suggests using the term "rough consensus", while pointing to a public document where that is defined.
  5. The current PDP specifies a timeline around implementation of a ratified policy proposal (CPM 3.4.5), which provision is not included in this proposal.
  6. The PDP should allow staff reasonable time to conduct an assessment of a new policy proposal.


3.0 Comments from Legal Counsel

a. Under “Variance by the AFRINIC board of Directors”, the Bylaws currently give the Board the right to make policy without waiting for the 2 weeks indicated in the proposal. The Board's actions under the Bylaws 11.4 appear to be constrained by the PDP in this proposal.

This wording therefore puts a restrictive effect on the power of the Board to act under the provisions of existing Art 11.4 of the by-laws, whose purport is to give the Board (in matters of urgency) some leeway/flexibility to address those urgent matters on its own and without being hamstrung by any other process, such as the PDP.

The two weeks’ consultative period is not only against the notion of urgency as envisaged by existing (by-laws) Art 11.4, but it also ushers in a new situation where the Board has to give explanation/justification to and seek approval of PDWG chair and vice chair.


b. On whether or not there are limitations (in this proposal) to the Board's right to consider matters external to the PDP when deciding to ratify a proposal – the Board is bound by other legal instruments such as the Companies’ Act and other relevant laws of the Republic of Mauritius. If a proposal would place the directors in contravention of the duties which they owe to the Company, then ratification could be withheld as a matter of law, notwithstanding the PDP.

The Board cannot be bound, therefore - for the ratification process, only to the PDP.


c. Period for Appeal: The proposal provides for appeal which “...must be submitted within two weeks of the public knowledge of the decision”.  The term “public knowledge of the decision” needs to be precisely clarified by authors in order to avoid unnecessary misunderstandings as to the start of this appeal period.

Discussions are taking place on the policy working group mailing list if you want to subscribe to the mailing send your subscription request to rpd-request [at] with 'Subscribe' as subject line

Mailing list archives can be found at

Profile Information

Application afterLoad: 0.001 seconds, 0.71 MB
Application afterInitialise: 0.058 seconds, 2.70 MB
Application afterRoute: 0.098 seconds, 5.95 MB
Application afterDispatch: 0.224 seconds, 7.87 MB
Application afterRender: 2.143 seconds, 11.18 MB

Memory Usage


14 queries logged

  1. SELECT m.*, c.`option` AS component
      FROM www3menu AS m
      LEFT JOIN www3components AS c
      ON m.componentid =
      WHERE m.published = 1
      ORDER BY m.sublevel, m.parent, m.ordering
  2. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
      AND jf_content.published=1
      AND jf_content.reference_id IN(1,11,20,304,324,262,231,275,340,393,791,661,12,51,348,805,831,13,52,154,795,14,24,53,793,15,797,16,62,803,17,799,68,97,27,387,619,191,221,172,170,76,171,337,418,521,845,175,174,177,237,176,499,511,455,481,523,547,671,184,185,188,423,837,527,179,181,204,235,156,158,159,384,475,675,629,160,161,162,157,192,621,268,270,266,321,264,265,338,416,483,519,843,276,283,278,282,477,677,279,631,280,281,429,277,382,305,306,307,308,424,835,317,330,318,319,320,325,326,327,328,529,341,342,343,345,350,349,408,351,354,745,489,509,356,479,525,549,673,388,400,403,404,405,406,419,513,399,394,396,397,395,617,615,663,665,801,414,163,731,733,735,737,715,739,741,789,743,269,271,272,292,289,290,291,293,294,339,295,420,386,807,811,285,286,288,819,383,287,515,567,809,817,415,284,633,763,315,312,561,563,565,767,314,380,517,332,333,334,335,336,370,346,347,311,378,787,352,364,362,365,833,719,366,367,368,411,412,453,825,379,357,358,359,360,361,371,431,459,463,467,469,471,473,531,533,537,539,541,543,545,599,609,601,605,485,487,491,493,495,497,551,553,557,559,841,573,575,577,579,581,583,585,591,589,777,779,813,749,751,753,755,747,757,759,761,783,373,374,375,376,721,417,829,669,353,413,461,535,781,727,667,611,597,603,815,769,635,637,639,641,645,643,647,649,651,653,655,657,659,785,821,823,827,697,701,703,705,707,709,711)
      AND jf_content.reference_table='menu'
  3. SELECT *
      FROM www3rokcandy
      WHERE published=1
  4. SELECT template
      FROM www3templates_menu
      WHERE client_id = 0
      AND (menuid = 0 OR menuid = 312)
      ORDER BY menuid DESC
      LIMIT 0, 1
  5. SELECT a.*, AS author, u.usertype, cc.title AS category, s.title AS SECTION, CASE WHEN CHAR_LENGTH(a.alias) THEN CONCAT_WS(":",, a.alias) ELSE END AS slug, CASE WHEN CHAR_LENGTH(cc.alias) THEN CONCAT_WS(":",, cc.alias) ELSE END AS catslug, AS groups, s.published AS sec_pub, cc.published AS cat_pub, s.access AS sec_access, cc.access AS cat_access  
      FROM www3content AS a
      LEFT JOIN www3categories AS cc
      ON = a.catid
      LEFT JOIN www3sections AS s
      ON = cc.SECTION
      AND s.scope = "content"
      LEFT JOIN www3users AS u
      ON = a.created_by
      LEFT JOIN www3groups AS g
      ON a.access =
      WHERE = 2083
      AND (  ( a.created_by = 0 )    OR  ( a.state = 1
      AND ( a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2024-02-20 22:29:08' )
      AND ( a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2024-02-20 22:29:08' )   )    OR  ( a.state = -1 )  )
  6. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
      AND jf_content.published=1
      AND jf_content.reference_id IN(2083)
      AND jf_content.reference_table='content'
  7. UPDATE www3content
      SET hits = ( hits + 1 )
      WHERE id='2083'
  8. SELECT *
      FROM www3jcomments_settings

      WHERE lang = 'en-GB'
  9. SELECT id, title, module, POSITION, content, showtitle, control, params
      FROM www3modules AS m
      LEFT JOIN www3modules_menu AS mm
      ON mm.moduleid =
      WHERE m.published = 1
      AND m.access <= 0
      AND m.client_id = 0
      AND ( mm.menuid = 312 OR mm.menuid = 0 )
      ORDER BY POSITION, ordering
  10. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
      AND jf_content.published=1
      AND jf_content.reference_id IN(79,330,35,326,331,304,347,345,329,292,335,303,188)
      AND jf_content.reference_table='modules'
  11. SELECT AS id, s.title AS title
      FROM www3sections AS s
      WHERE s.published=1  
      AND IN (12,18)
  12. SELECT DISTINCT AS id, c.title AS title, c.SECTION AS SECTION,
                            CASE WHEN CHAR_LENGTH(c.alias) THEN CONCAT_WS(":",, c.alias) ELSE END AS catslug
      FROM www3categories AS c, www3content AS a
      WHERE a.catid =
      AND a.state = 1
      AND c.published=1
      AND c.SECTION IN (12,18)
      ORDER BY c.ordering ASC
  13. SELECT AS id, a.title AS title, a.catid AS catid, a.sectionid AS sectionid,
                                                        CASE WHEN CHAR_LENGTH(a.alias) THEN CONCAT_WS(":",, a.alias) ELSE END AS slug,
                                                        CASE WHEN CHAR_LENGTH(b.alias) THEN CONCAT_WS(":",, b.alias) ELSE END AS catslug
      FROM www3content AS a, www3categories AS b
      WHERE a.catid =
      AND a.state = 1
      AND a.access <= 0
      ORDER BY a.ordering ASC
  14. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
      AND jf_content.published=1
      AND jf_content.reference_id IN(712,688,134,187,193,170,708,214,223,2279,266,267,292,306,676,668,314,715,775,793,1315,1115,816,830,834,835,2005,853,870,871,875,885,1399,938,953,961,963,1163,1099,2059,1191,1197,1237,1421,1249,1305,1511,1669,1733,2273,1885,1903,1939,2001,2077,2091,2143,2133,2167,2173,2207,2269,2263,2351,2371,2401,2413,2439,2447,2519,2463,2479,2495,2491,2521,2547,2549,2551,278,2399,116,186,192,169,195,707,784,216,2277,1941,265,284,291,710,677,675,667,313,689,748,761,783,790,802,829,833,836,852,863,869,877,916,939,951,960,962,977,1097,1199,1235,1275,1303,1423,1833,1883,1891,2165,1999,2019,2271,2087,2127,2153,2199,2267,2259,2261,2281,2411,2435,2449,2461,2467,2477,2543,2545,117,674,698,145,153,157,168,191,184,196,706,257,654,241,1943,283,290,312,662,862,690,694,747,1337,765,801,815,828,832,851,868,881,2317,1889,921,942,1095,1153,1263,1299,1403,1509,1673,1881,1969,2201,2089,2093,2145,2129,2195,2245,2265,2289,2347,2427,2459,2539,2541,197,198,256,146,148,151,152,156,190,705,1349,232,260,261,276,282,289,311,661,691,901,746,769,800,808,814,827,831,867,923,1297,1151,1321,1671,1715,1745,1879,1905,1963,2015,2063,2065,2083,2203,2243,2255,2345,2457,2537,2535,2051,785,199,158,189,219,228,281,288,310,1149,660,692,745,752,799,807,813,826,864,876,925,1091,1295,1207,1215,1219,1395,1431,1575,1607,1803,1831,1847,1877,1961,2125,2161,2253,2333,2425,2475,2533,2045,255,154,188,200,212,673,1147,659,704,693,2043,744,788,780,806,812,825,866,874,926,1175,1089,1397,1409,1539,1569,1605,1829,1875,2079,2107,2123,2159,2205,2239,2387,2415,2531,166,150,202,213,296,672,331,658,697,743,781,805,811,873,927,1087,1109,1127,1145,1285,1391,1429,1439,1603,1627,1873,1971,1997,2025,2029,2073,2105,2121,2223,2529,167,201,2359,295,671,657,696,742,774,804,810,872,928,1363,1085,1125,1273,1413,1483,1535,1601,1611,1851,1871,1995,2221,2321,2527,700,1123,203,1863,670,656,725,803,809,849,929,1075,989,1083,1387,1393,1599,1827,1849,1869,2027,1959,2331,1993,2185,2525,165,204,221,251,669,727,2011,850,1731,934,965,1081,1335,1379,1385,1597,1623,1739,2523,1991,2183,2197,2313,141,205,230,271,724,1079,796,838,845,1333,1383,1499,1595,1689,1729,1931,1989,2075,2137,2241,2517,136,206,262,270,2231,285,714,733,750,844,1177,1593,1819,1687,1929,1987,2135,2247,2515,135,207,269,279,695,720,787,840,2513,1591,1817,1685,1927,1985,2023,2067,2235,133,229,268,208,275,795,776,1233,1589,1683,1983,2021,2233,2511,132,185,263,274,2007,1173,1587,1625,1665,1666,1865,1923,2509,131,147,210,264,273,717,1531,1585,1643,1947,1965,1921,2507,130,217,226,243,329,653,1517,1583,1629,1813,1937,1919,2505,149,218,1507,1573,1581,1861,1917,2061,2503,127,194,220,1293,277,1503,1815,1859,1915,2501,121,124,225,955,1257,1457,1781,1857,2499,125,180,914,987,1489,1779,1855,2055,2497,115,126,227,798,1453,1741,1777,1853,2493,113,1809,123,293,719,1785,2489,111,122,286,294,1157,1737,1773,2487,110,664,1243,1727,1771,2485,678,1255,1725,2483,666,1259,1609,1723,1767,2481,679,1241,1721,1765,2473,680,1719,1231,1763,2471,681,1133,1701,1761,2469,114,701,683,1699,1759,2465,684,933,1661,1757,2455,685,2453,908,1659,1755,687,842,1657,2445,878,1655,1751,2443,857,1749,1653,2441,856,1651,1717,2437,841,1051,2433,753,2431,794,918,2429,244,911,2423,242,910,2421,247,837,909,2417,250,773,789,2409,258,772,2407,699,771,722,702,770,2403,259,713,721,2397,233,2395,234,2393,112,239,2391,238,2389,236,2383,237,2381,235,2379,240,2377,142,2375,246,2373,245,2369,144,2367,140,2365,252,2363,253,2361,254,2357,143,2355,248,2353,249,2343,2341,2339,2337,2335,2329,2327,2325,2323,2319,2315,2311,2309,2307,2305,2303,2301,2299,2297,2295,2293,2291,2287,2285,2283,2275,2257,2251,2249,2237,2229,2227,2225,2219,2217,2215,2211,2209,2193,2191,2187,2181,2179,2177,2175,2169,2163,2157,2155,2151,2149,2147,2141,2139,2131,2119,2117,2111,2101,2099,2097,2095,2085,2081,2057,2053,2049,2047,2041,2039,2037,2035,2033,2031,2013,2009,2003,1981,1979,1977,1975,1973,1967,1957,1955,1953,1951,1949,1945,1935,1933,1911,1909,1907,1899,1897,1895,1893,1887,1867,1845,1843,1841,1839,1837,1835,1825,1823,1821,1811,1807,1805,1801,1799,1797,1795,1793,1791,1789,1787,1783,1747,1743,1735,1713,1711,1709,1707,1705,1703,1695,1693,1691,1681,1679,1677,1675,1663,1649,1647,1645,1639,1633,1631,1615,1613,1579,1577,1571,1567,1565,1533,1563,1529,1525,1523,1519,1513,1497,1495,1493,1491,1487,1475,1473,1471,1469,1467,1463,1461,1455,1451,1449,1445,1443,1441,1437,1433,1427,1425,1419,1417,1415,1411,1407,1405,1401,1389,1381,1361,1359,1357,1355,1353,1351,1347,1345,1343,1341,1331,1329,1327,1325,1323,1319,1317,1313,1309,1307,1301,1311,1291,1289,1287,1277,1269,1267,1265,1251,1247,1245,1239,1229,1225,1223,1221,1217,1213,1211,1209,1203,1201,1193,1189,1187,1185,1181,1179,1171,1169,1165,1159,1155,1183,1137,1143,1139,1135,1141,1129,1131,1119,1117,1113,1107,1105,1103,1101,1049,1047,1045,1037,1029,1027,1025,1023,1021,1017,1015,1013,1005,1001,999,997,995,993,991,983,981,979,970,968,966,958,956,952,950,949,948,947,946,945,944,941,940,932,931,930,922,917,913,912,779,907,906,905,903,902,900,894,887,884,883,880,865,859,839,792,791,786,764,751,723,726,728,729,730,738,732,737,739,740,307,741,736,735,734,173,172,175,174,858,920)
      AND jf_content.reference_table='content'

Language Files Loaded

Untranslated Strings Diagnostic


Untranslated Strings Designer