AFRINIC · RIR Watchdog
Regional Internet Registry Privacy | AFPUB-2012-GEN-002-DRAFT-02
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- AFPUB-2012-GEN-002
- RIR
- AFRINIC
- Official status
- Withdrawn by Author
- Normalized status
- Withdrawn
- Introduced
- Unknown
- Last source update
- Oct 1, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Public discussion
[AfriNIC-rpd] Regional Internet Registry Privacy
4 Discussion messages · 3 Entities
Source facts ↗
Entities
- Discussion messages2First activityMay 5, 2012Last activityMay 16, 2012First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyConsistentOther policies9
- Discussion messages1First activityMay 11, 2012Last activityMay 11, 2012First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyConsistentOther policies8Freshness: Stale
Last research attempt: Sep 25, 2026
Identity verified: Sep 25, 2026
RIPE NCC · Historical RIPE NCC staff – IP Analyst/Hostmaster/LIR Trainer (2002-2005)
www.arin.netInternet Systems Consortium · Historical Internet Systems Consortium, Education Manager and Lead Trainer (2012)
www.arin.netAFRINIC · Historical Former AFRINIC Policy Development Working Group Co-chair
www.arin.netVerified public profiles
- Discussion messages
- 1
- First activity
- May 11, 2012
- Last activity
- May 11, 2012
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Consistent
- Other policies
- 8
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Consistent
The No Reverse contributions preserve the objective of encouraging assignment registration while revising the mechanism and leaving withdrawal conditional on community agreement. The anycast contributions show support for discussion and later clarification, without enough supplied text to compare every version. Clarification and conditional willingness to withdraw are not evidence of an unexplained reversal.
Assessment: Insufficient evidence to assess consistency · The author introduces the anycast proposal as a strawman and invites feedback. This establishes advocacy of a discussion starting point, not endorsement of every subsequent version or a sequence of positions on this particular proposal.
Conditions: The retained message does not reproduce the substantive proposed anycast terms.
It is somewhat of a "strawman" in that it gives us a starting point for discussion.
Assessment: Consistent · The sequence begins with a tentative enforcement proposal, moves to revised wording with discretionary removal after notice, and ends with willingness to withdraw if the community rejects the approach. The stated registration objective persists. The end-user clarification explains that assignments already entered by staff satisfy the registration condition, although the broad draft wording could benefit from that explanation.
Conditions: The change to MAY is a real revision of the enforcement mechanism, not unchanged wording. · The /24 condition requires at least one registered assignment or sub-allocation, not registration of the entire /24. · The end-user explanation relies on the author's recollection of staff registration practice; it is not an independent verification of all end-user records. · The June message offers withdrawal conditionally and reports the author's perception of feedback; it does not prove actual withdrawal or absence of community views. · A draft identifier announcement is procedural and does not establish adoption.
I am hoping it will spur discussion and perhaps someone will have a better idea
I have used a "MAY" instead of a "SHALL" or a "MUST"
3.3 AfriNIC may remove reverse delegation of any LIRs allocation beginning 12 (twelve) months from the date of the reminder.
Since End-User assignments are already entered into the Db by the RIR staff (IIRC), then they can get reverse delegation if they so choose.
If there is no consensus that this is the way to rectify the problem of getting people to register their assignments, I would be happy to withdraw this proposal
Anycast resource assignments in the AFRINIC region
Assessment: Consistent · Support for Alan's clarification and future-proofing is followed by an explicit favorable last-call response. No withdrawal of support is present, but the short final response does not independently establish whether every earlier suggestion entered the final text.
Conditions: The exact intervening drafts are not reproduced in these two messages. · A favorable response is the author's vote, not proof of community consensus or adoption.
I would support the change that Alan suggests in the interests of clarity.
in favor.
AFPUB-2012-V4-001-DRAFT-01 · Anycast resource assignments in the AFRINIC region
Assessment: Insufficient evidence to assess consistency · The earlier anycast strawman and the later support for clarification are compatible in direction, but the first message contains no substantive terms. They cannot establish detailed consistency across all allocation conditions or revisions.
Conditions: Do not infer that submitting the initial strawman endorses every later anycast text.
Below is the proposal on Anycast I submitted to pdwg last week.
sure, I am all for future proofing as APB suggests.
No Reverse Unless Assigned · Anycast resource assignments in the AFRINIC region
Assessment: Consistent · Revising No Reverse in response to concerns and accepting clarifying anycast wording both show willingness to refine proposals during discussion. Conditional withdrawal of an enforcement approach does not contradict support for a different resource-assignment proposal.
Conditions: This comparison concerns the stated handling of feedback, not identical substantive rules in the two policies.
Please find my revisions to the "No Reverse" proposal below, taking into account all of your concerns (I hope):
I would support the change that Alan suggests in the interests of clarity.
- May 11, 2012 · Unknown
[AfriNIC-rpd] Regional Internet Registry Privacy
Validated evidence is unavailable.
Source facts ↗
Per-policy stance timelines:AFPUB-2008-GEN-001 · Unknown · No explicit position statedAFPUB-2012-DNS-001 · Support · ConsistentAFPUB-2012-GEN-002 · Unknown · No explicit position statedAFPUB-2012-V4-001 · Support · Insufficient evidence to assess consistencyAFPUB-2013-GEN-001 · Unknown · No explicit position statedAFPUB-2013-V4-001 · Unknown · No explicit position statedAFPUB-2014-GEN-003 · Support · Consistentafpub-2014-gen-004 · Unknown · No explicit position statedAFPUB-2026-IPv4-001-DRAFT02 · Unknown · No explicit position statedTotal policy messages: 71
- Kris Seeburn · Identity unresolvedDiscussion messages1First activityMay 17, 2012Last activityMay 17, 2012First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- S. Moonesamy · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
Sources and coverage
Official policy sources
Public discussion archives
- afrinic-rpd
- Earliest captured
- Aug 4, 2004
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 13,099
- Known gaps
- 0
- www.afrinic.net
- afrinic-africann
- Earliest captured
- Aug 3, 2026
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,620
- Known gaps
- 0
- afrinic-afripv6-discuss
- Earliest captured
- Aug 17, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,538
- Known gaps
- 0
- afrinic-announce
- Earliest captured
- Aug 18, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,497
- Known gaps
- 0
- afrinic-community-discuss
- Earliest captured
- Sep 11, 2015
- Latest captured
- Dec 29, 2019
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,127
- Known gaps
- 0
- afrinic-dbwg
- Earliest captured
- Aug 4, 2026
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 965
- Known gaps
- 0
- afrinic-dnssec-ops
- Earliest captured
- Aug 18, 2015
- Latest captured
- Dec 1, 2016
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 307
- Known gaps
- 0
- afrinic-icp2-review
- Earliest captured
- Apr 10, 2025
- Latest captured
- Nov 10, 2025
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-measurement-wg
- Earliest captured
- Feb 1, 2018
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 138
- Known gaps
- 0
- afrinic-mira
- Earliest captured
- Nov 17, 2020
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-ois-wg
- Earliest captured
- Sep 9, 2021
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-rpki-discuss
- Earliest captured
- Jan 15, 2016
- Latest captured
- Apr 23, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 154
- Known gaps
- 0
Coverage
Partial
Earliest captured: Aug 4, 2004
Latest captured: Oct 15, 2026
Freshness
Known gaps
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-rpd: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-africann: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-afripv6-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-announce: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-community-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-dbwg: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-dnssec-ops: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-measurement-wg: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-rpki-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
