What changed
No policy change can be established from the supplied verified facts because the policy chronology is empty and no proposal text, amendment sequence, procedural milestone, or implementation record is provided.
AFRINIC · RIR Watchdog
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
Who actually shaped the debate?
BTW Analysis
No policy change can be established from the supplied verified facts because the policy chronology is empty and no proposal text, amendment sequence, procedural milestone, or implementation record is provided.
The substance of the debate cannot be reconstructed. No messages, participants, stance timelines, arguments, proposals, interests, or institutional incentives are recorded in the supplied dataset.
Neither a discussion outcome nor a formal decision is established. The snapshot records zero messages, zero discussion participants, zero formal actors, zero active days, and no adoption, rejection, withdrawal, consensus, ratification, or implementation record.
The zero top-message shares, HHI, effective-participant count, and core-participant counts describe an empty observed population, not broadly distributed participation. With zero messages and zero participants, concentration cannot be meaningfully assessed.
No procedural, institutional, or participant chokepoint can be identified because the supplied chronology and stance timelines are empty and the participation snapshot records no discussion or formal-actor activity.
Public discussion
11 Discussion messages · 9 Entities
Source facts ↗Public discussion
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
19 Discussion messages · 11 Entities
Source facts ↗Public discussion
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
2 Discussion messages · 2 Entities
Source facts ↗Last research attempt: Oct 2, 2026
Identity verified: Oct 2, 2026
Lead Instructor, African Network Operators Groupwww.itu.int
serving as Special Project Manager at AfriNIC since 2006.www.itu.int
Verified public profiles
First explicit stance: Support with changes → Latest explicit stance: Support with changes · Stance changes: 2
Viewpoint consistency: Insufficient evidence to assess consistency
The four December 2014 anycast messages consistently advocate explicit best-practice references with a reasoned exception for future changes. The newly recovered July 2006 message asks about a copied regional eligibility clause in a different IPv6 PI proposal. It adds no second substantive position on that proposal and does not establish a contradiction with the later use of external best practices.
Anycast resource assignments in the AFRINIC region
Assessment: Consistent · The author first conditions multiple-subnet use on a BCP126 reference and proposes BCP169 for ASNs, then defends the clarity and abuse-prevention rationale and supplies replacement clauses. The clauses develop the same preference rather than withdrawing support for the mechanism.
Conditions: This is support for the specified conditions, not an unconditional endorsement of every policy provision. · The offered wording does not establish adoption or consensus.
As discussed at the meeting, using multiple subnets is ok as far as reference to BCP126 is in there.
So references to best practices is good. In this case one for the v4/v6 and one for ASN
These resources must be used for the sole purposes of providing anycast services or GRX (GPRS Roaming Exchanges) as recommended in BCP126 and BCP169 respectively.
Anycast resource assignments in the AFRINIC region
Assessment: Consistent · The later preference for following replacement BCPs without a new PDP extends the earlier instruction that implementers should adjust as best practices change. The author explicitly preserves an exception when there is reason to do otherwise, so this is not an unconditional transfer of all policy decisions to future BCP authors.
Conditions: The RFC2026 passage is attributed supporting material, not a separate personal vote. · The messages do not specify who would decide that an exception is justified.
Best practices changes over time and implementer shall adjust
The policy should follow new BCPs( which update, replace old ones) without going through PDP unless we have reasons to do otherwise.
Either we add the requirements in the policy or we refer to the BCP. I support the last option.
Provider-Independent (PI) IPv6 Assignments for End-User-Organizations
Assessment: Insufficient evidence to assess consistency · The author asks why RIPE NCC IPv4 qualification criteria appear in an AFRINIC IPv6 PI proposal. This identifies a concrete regional-applicability question; it is not a general rejection of provider-independent assignments or of every external reference. One question supplies no sequence of personal positions to compare.
Conditions: The quoted eligibility clause belongs to the draft under discussion, not to a rule the author independently endorses. · The proposed regional-name correction in the reply is another participant's explanation.
Can someone (jordi or others) explains to me what why should RIPE NCC actual IPV4 policy applied for AfriNIC region in the IPv6 IP assignement ?
Provider-Independent (PI) IPv6 Assignments for End-User-Organizations · Anycast resource assignments in the AFRINIC region
Assessment: Insufficient evidence to assess consistency · Questioning an apparently miscopied region-specific eligibility rule in 2006 and supporting explicit technical best-practice references for anycast in 2014 concern different kinds of reference. The supplied messages show no necessary contradiction, but the long gap and absence of a comparable PI position prevent a broad claim of consistent policy preferences across the two proposals.
Conditions: A concern about which registry's rules apply cannot be generalized into opposition to all externally maintained standards. · Only the named messages and proposals are covered.
what why should RIPE NCC actual IPV4 policy applied for AfriNIC region in the IPv6 IP assignement ?
So references to best practices is good. In this case one for the v4/v6 and one for ASN
unless we have reasons to do otherwise.
[rpd] New proposal - "Mandatory requirements for registering assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)
Validated evidence is unavailable.
Source facts ↗[rpd] AnyCast assignments - Update
As discussed at the meeting, using multiple subnets is ok as far as reference to BCP126 is in there. … To add Multiple ASNs on this, i suggest, reference to BCP 169
Source facts ↗[rpd] AnyCast assignments - Update
So references to best practices is good. In this case one for the v4/v6 and one for ASN … Ressources must be used on need basis and with trust. Best practices changes over time and implementer shall adjust
Source facts ↗[rpd] AnyCast assignments - Update
This proposal allows an organization to receive an IPv4/IPv6 allocation or assignment and/or an AS Number purely for anycast or GPRS Roaming Exchange (GRX) usage in line with the provisions of BCP126 and BCP169 respectively. … These resources must be used for the sole purposes of providing anycast services or GRX (GPRS Roaming Exchanges) as recommended in BCP126 and BCP169 respectively.
Source facts ↗[rpd] AnyCast assignments - Update
The policy should follow new BCPs( which update, replace old ones) without going through PDP unless we have reasons to do otherwise. … Either we add the requirements in the policy or we refer to the BCP. I support the last option.
Source facts ↗Total policy messages: 11
Partial
Earliest captured: Aug 4, 2004
Latest captured: Oct 13, 2026