AFRINIC · RIR Watchdog
No Reverse Unless Assigned
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-DNS-001
- RIR
- AFRINIC
- Official status
- Unknown
- Normalized status
- Unknown
- Introduced
- Apr 10, 2012
- Last source update
- Oct 12, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Registration required for a /24 reverse delegation · DRAFT-02 explicitly permits a /24 reverse delegation when at least one assignment or sub-allocation within that /24 is registered; the entire /24 need not be assigned. DRAFT-01 required registration of the relevant address space without this explicit partial-/24 rule.
Source facts −
AfriNIC will no longer grant reverse delegation of IP address space that it administers unless an assignment or sub-allocation of that address space is registered appropriately in the AfriNIC Database.Source facts ↗
Source facts +
For a /24 reverse delegation, at least one assignment or sub-allocation must be registered in the AfriNIC Database for that specific /24. The entire /24 does not have to be assigned in order for the reverse delegation to be allowed.Source facts ↗
Existing delegations: notice period and possible withdrawal · DRAFT-01 protected reverse delegations for allocations approved before ratification and limited the proposal to later allocations. DRAFT-02 replaces that protection with a 12-month period from the reminder for affected LIRs to register assignments or sub-allocations, after which AFRINIC may remove the reverse delegation. Removal is permitted, not described as automatic.
Source facts −
AfriNIC will NOT remove reverse delegation of any LIRs allocation that was approved before the date of ratification of this policy proposal by the AfriNIC Board. Only allocations made after ratification date will be affected by this proposal.Source facts ↗
Source facts +
These LIRs will have 12 (twelve) months from the date of the reminder to register their assignments or sub-allocations. 3.3) AfriNIC may remove reverse delegation of any LIRs allocation beginning 12 (twelve) months from the date of the reminder.Source facts ↗
Debate timeline
Public discussion
[AfriNIC-rpd] Draft Policy Proposal: No Reverse Unless Assigned
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
[AfriNIC-rpd] Re: Draft Policy Proposal: No Reverse Unless Assigned ID: AFPUB-2012-DNS-001-DRAFT-01
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
[AFRINIC-rpd] AFPUB-2012-V4-001-DRAFT-02
6 Discussion messages · 2 Entities
Source facts 1 ↗Source facts 2 ↗Public discussion
[AFRINIC-rpd] Re: Reminder - Policy on Last call - 2 weeks (min) passed
6 Discussion messages · 4 Entities
Source facts ↗Public discussion
[AFRINIC-rpd] Re: Policies that were on Last Call - Status
2 Discussion messages · 2 Entities
Source facts ↗
Entities
- Discussion messages9First activityJun 21, 2013Last activityMar 21, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies13
- Discussion messages7First activityApr 17, 2012Last activityJun 19, 2013First explicit stanceSupportLatest explicit stanceSupportStance changes2Viewpoint consistencyConsistentOther policies8
- Discussion messages3First activityJun 20, 2013Last activityAug 9, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies10
- Discussion messages3First activityJun 3, 2013Last activityJun 25, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies6
- Discussion messages3First activityJun 21, 2013Last activityJul 10, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies15
- Discussion messages2First activityDec 17, 2012Last activityDec 17, 2012First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies2
- SM · Identity unresolvedDiscussion messages2First activityApr 18, 2012Last activityNov 29, 2012First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies7
- AFRINIC Communication · Identity unresolvedDiscussion messages1First activitySep 19, 2014Last activitySep 19, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- JP · Identity unresolvedDiscussion messages1First activityJun 24, 2013Last activityJun 24, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies6
- Bope Domilongo Christian · Identity unresolvedDiscussion messages1First activityJun 21, 2013Last activityJun 21, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies7
- Sunday Folayan · Identity unresolvedDiscussion messages1First activityJul 10, 2013Last activityJul 10, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies6
- Discussion messages1First activityJul 10, 2013Last activityJul 10, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies9
- Discussion messages1First activityJun 24, 2013Last activityJun 24, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies8
- Discussion messages1First activityMay 5, 2012Last activityMay 5, 2012First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies6Freshness: Stale
Last research attempt: Sep 25, 2026
Identity verified: Sep 25, 2026
AFRINIC · Historical Ernest Byaruhanga RS Manager AfriNIC [email protected]
meeting.afrinic.netVerified public profiles
- Discussion messages
- 1
- First activity
- May 5, 2012
- Last activity
- May 5, 2012
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 6
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
These three communications document Ernest's procedural role: circulating a tentative agenda in 2012, reporting Board ratification in February 2015, and announcing an author's update in May 2015. None states his personal policy preference. The recurring administrative role provides context, but cannot establish substantive consistency or contradiction across these proposals.
Assessment: Insufficient evidence to assess consistency · The 2012 agenda schedules an Anycast discussion without endorsing its outcome or substance.
Conditions: One agenda entry is available; a scheduled discussion does not establish consensus.
1715 - 1800 Proposal: AfriNIC Region Anycast Assignments (McTim)
Assessment: Insufficient evidence to assess consistency · The same tentative agenda schedules No rDNS Unless Assigned. It supplies no personal position to compare over time.
Conditions: The sender acts on behalf of the PDWG chairs.
0900 - 0945 Proposal: No rDNS Unless Assigned (McTim)
Ernest (on behalf of PDWG Chairs)
Anycast resource assignments in the AFRINIC region
Assessment: Insufficient evidence to assess consistency · The February 2015 notice reports Board ratification of draft-04 and staff preparations for implementation. Reporting those institutional actions does not establish the sender's own policy preference.
Conditions: The notice does not verify that implementation was completed.
We are pleased to inform you that the AFRINIC Board has ratified the following policy proposal:
AFRINIC staff is taking appropriate measures to effect it's immediate implementation.
Out-Of-Region Use of AFRINIC Internet Number Resources
Assessment: Insufficient evidence to assess consistency · The May 2015 notice points readers to an author-supplied update and requests a changelog; it expresses no personal support or opposition.
Conditions: An announcement that a proposal will be discussed is not a decision on that proposal.
The author has provided an update to the proposal "Out-Of-Region Use of AFRINIC Internet Number Resources"
Douglas, please feel free to summarize the updates & changelog to the list for the convenience of the readers.
AFPUB-2012-V4-001-DRAFT-01 · No Reverse Unless Assigned
Assessment: Insufficient evidence to assess consistency · Putting two proposals on one agenda is evidence of meeting coordination, not agreement with either proposal or a comparison of their merits.
Conditions: These two entries come from the same communication, not two independent statements of preference.
1715 - 1800 Proposal: AfriNIC Region Anycast Assignments (McTim)
0900 - 0945 Proposal: No rDNS Unless Assigned (McTim)
AFPUB-2012-V4-001-DRAFT-01 · Anycast resource assignments in the AFRINIC region
Assessment: Insufficient evidence to assess consistency · The earlier Anycast agenda entry and the later Anycast ratification notice concern different recorded proposals and procedural stages. They do not show that Ernest changed or maintained a personal policy position.
Conditions: Do not infer continuity of draft text or completed implementation from the shared Anycast subject.
1715 - 1800 Proposal: AfriNIC Region Anycast Assignments (McTim)
ID: AFPUB-2014-GEN-003-DRAFT-04 Name: Anycast Assignments in the AFRINIC region
Anycast resource assignments in the AFRINIC region · Out-Of-Region Use of AFRINIC Internet Number Resources
Assessment: Insufficient evidence to assess consistency · Reporting ratification of Anycast and forwarding an Out-of-Region update are compatible administrative acts, but neither supplies a personal substantive position for a cross-policy consistency judgment.
Conditions: Institutional decisions and an author's update must not be attributed to the messenger as personal votes.
We are pleased to inform you that the AFRINIC Board has ratified the following policy proposal:
The author has provided an update to the proposal
- May 5, 2012 · Procedural or neutral
0900 - 0945 Proposal: No rDNS Unless Assigned (McTim)
Source facts ↗
Per-policy stance timelines:AFPUB-2012-DNS-001 · Unknown · Insufficient evidence to assess consistencyAFPUB-2012-GEN-001 · Unknown · No explicit position statedAFPUB-2012-V4-001 · Unknown · Insufficient evidence to assess consistencyAFPUB-2013-V4-001 · Unknown · No explicit position statedafpub-2014-gen-002 · Unknown · Insufficient evidence to assess consistencyAFPUB-2014-GEN-003 · Unknown · Insufficient evidence to assess consistencyAFPUB-2026-IPv4-001-DRAFT02 · Unknown · No explicit position statedTotal policy messages: 12
- im McGinnis (McTim) "> 1. Amends AFPUB-2005-v4-001 · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- AfriNIC PDWG co-chair 1. Amends AFPUB-2005-v4-001 · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- im McGinnis (McTim) "> Internet Systems Consortium · 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 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 13,116
- Known gaps
- 0
- www.afrinic.net
- afrinic-africann
- Earliest captured
- Aug 3, 2026
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,612
- Known gaps
- 0
- afrinic-afripv6-discuss
- Earliest captured
- Aug 17, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 14, 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 14, 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 14, 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 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 954
- Known gaps
- 0
- afrinic-dnssec-ops
- Earliest captured
- Aug 18, 2015
- Latest captured
- Dec 1, 2016
- Last refresh
- Oct 14, 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 14, 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 14, 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 14, 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 14, 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 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 154
- Known gaps
- 0
Coverage
Partial
Earliest captured: Aug 4, 2004
Latest captured: Oct 14, 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.
