APNIC · RIR Watchdog
A proposal to lower the IPv4 minimum allocation size and initialallocation criteria in the AsiaPacificregion
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
- prop-014
- RIR
- APNIC
- Official status
- Unknown
- Normalized status
- Unknown
- Introduced
- Jan 19, 2004
- Last source update
- Oct 15, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Entities
- Discussion messages3First activityJan 26, 2004Last activityJan 26, 2004First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies3Freshness: Stale
Last research attempt: Sep 28, 2026
Identity verified: Sep 28, 2026
RIPE NCC · Unknown Randy Bush Executive Board Member
www.ripe.netVerified public profiles
- Discussion messages
- 3
- First activity
- Jan 26, 2004
- Last activity
- Jan 26, 2004
- First explicit stance
- Oppose
- Latest explicit stance
- Oppose
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 3
First explicit stance: Oppose → Latest explicit stance: Oppose · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
The January 2004 routing discussion contains an objection to Secretariat-led prescription of ISP routing followed by technical contributions, with no withdrawal of that objection. The May 2008 NIR message is a jointly signed invitation to review another author's proposal. It does not establish a personal position on the NIR criteria to compare with the earlier objection.
Assessment: Consistent · The initial institutional objection is followed by distinctions between routing and forwarding tables and by evidence about forwarding-table update costs. These technical contributions neither endorse the disputed policy approach nor retract the objection.
Conditions: A change from an opposing comment to technical discussion is not, by itself, a change from opposition to support. · The technical claims are the author's contributions, not an independently verified assessment of every router implementation.
putting forth a policy proposal (i just love that apnic bottom-up policy development) that tells isps how we should run our routing?
on most i know, only forwarding tables are on line cards and routing tables are more centralized
updating the fibs when a rib changed (due to ospf link change), took the majority of the time, i.e., more than spf calculation.
Change in the criteria for the recognition of NIRs in the APNIC region
Assessment: Insufficient evidence to assess consistency · Circulating the NIR proposal and inviting support, opposition and suggested changes is a procedural act. It provides no personal vote on the recognition criteria and no sequence of substantive positions from which to assess consistency.
Conditions: The invitation is jointly signed; it must not be converted into separate personal endorsements by the chairs. · The proposal attributed to Kusumba Sridhar is not treated as the chairs' authored position.
We invite you to review and comment on the proposal on the mailing list before the meeting.
A proposal to lower the IPv4 minimum allocation size and initialallocation criteria in the AsiaPacificregion · Change in the criteria for the recognition of NIRs in the APNIC region
Assessment: Insufficient evidence to assess consistency · An objection to Secretariat prescription of ISP routing in 2004 is not contradicted by inviting community review of NIR criteria in 2008. The latter supplies no substantive stance, so these different roles and subjects do not establish a cross-policy reversal or broad consistency.
Conditions: Distinguish a personal criticism from a chair's invitation to an open policy discussion.
putting forth a policy proposal (i just love that apnic bottom-up policy development) that tells isps how we should run our routing?
We invite you to review and comment on the proposal on the mailing list before the meeting.
- Jan 26, 2004 · Oppose
Re: [sig-policy]Proposal prop-014-v001.txt - Lowering minimum allocation size and criteria
are you saying that what we have here is the apnic secretariat putting forth a policy proposal (i just love that apnic bottom-up policy development) that tells isps how we should run our routing? and am i misreading that you are being pejorative about our routing in some way that the exec-com does not like? puhleeze!
Source facts ↗ - Jan 26, 2004 · Procedural or neutral
Re: [sig-policy]Proposal prop-014-v001.txt - Lowering minimum allocation size and criteria
maybe they are on some router models. on most i know, only forwarding tables are on line cards and routing tables are more centralized (but still possibly somewhat distributed on very large and/or redundant systems).
Source facts ↗ - Jan 26, 2004 · Procedural or neutral
Re: [sig-policy]Proposal prop-014-v001.txt - Lowering minimum allocation size and criteria
it may be worth noting the work of greenberg et al., which showed that, for one vendor with whom you may be familiar, updating the fibs when a rib changed (due to ospf link change), took the majority of the time, i.e., more than spf calculation.
Source facts ↗
Per-policy stance timelines:prop-014 · Oppose · Consistentprop-033 · Unknown · No explicit position statedprop-050 · Unknown · No explicit position statedprop-060 · Unknown · Insufficient evidence to assess consistencyTotal policy messages: 34
- APNIC Secretariat · Identity unresolvedDiscussion messages2First activityMay 17, 2004Last activityJul 15, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies11
- Jeff Williams · Identity unresolvedDiscussion messages1First activityJan 27, 2004Last activityJan 27, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- Discussion messages1First activityJan 28, 2004Last activityJan 28, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies5
- Ahmad Alkazimy · Identity unresolvedDiscussion messages1First activityDec 18, 2003Last activityDec 18, 2003First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyConsistentOther policies0
- APNIC Secretariat · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
Sources and coverage
Official policy sources
Public discussion archives
- apnic-sig-policy
- Earliest captured
- Jun 1, 2001
- Latest captured
- Sep 21, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 697
- Known gaps
- 36
- apnic-sig-policy
- Earliest captured
- Jun 1, 2001
- Latest captured
- Sep 21, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,842
- Known gaps
- 1
- www.apnic.net
- conference.apnic.net
- apnic-academy-talk-apnic.net
- Earliest captured
- Jan 12, 2023
- Latest captured
- Jan 19, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,242
- Known gaps
- 1
- apnic-afg-community-apnic.foundation
- Earliest captured
- Sep 27, 2023
- Latest captured
- Jun 24, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,190
- Known gaps
- 0
- apnic-apac-ict-women-apnic.net
- Earliest captured
- Oct 22, 2024
- Latest captured
- Aug 11, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,715
- Known gaps
- 0
- apnic-apix-chair-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- apnic-apix-secretary-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 1
- apnic-apix-treasurer-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1
- Known gaps
- 0
- apnic-apnic-alumni-apnic.net
- Earliest captured
- Feb 14, 2024
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,913
- Known gaps
- 0
- apnic-apnic-announce-apnic.net
- Earliest captured
- Jun 11, 2025
- Latest captured
- Sep 3, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,260
- Known gaps
- 0
- apnic-apnic-foundation-discuss-apnic.foundation
- Earliest captured
- Sep 12, 2022
- Latest captured
- Mar 11, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,415
- Known gaps
- 0
- apnic-apnic-services-apnic.net
- Earliest captured
- Aug 31, 2020
- Latest captured
- Aug 4, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,845
- Known gaps
- 0
- apnic-apnic-talk-lists.apnic.net
- Earliest captured
- Apr 15, 2004
- Latest captured
- Sep 8, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,120
- Known gaps
- 0
- apnic-apnic-transfers-apnic.net
- Earliest captured
- Sep 21, 2012
- Latest captured
- Feb 22, 2025
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,790
- Known gaps
- 1
- apnic-bgp-stats-lists.apnic.net
- Earliest captured
- Aug 30, 2026
- Latest captured
- Sep 15, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 4,008
- Known gaps
- 0
- apnic-community-elections-apnic.net
- Earliest captured
- Nov 12, 2021
- Latest captured
- Nov 22, 2021
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 14
- Known gaps
- 2
- apnic-community-events-apnic.net
- Earliest captured
- May 9, 2025
- Latest captured
- Aug 19, 2025
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,098
- Known gaps
- 1
- apnic-diversity-in-leadership-apnic.net
- Earliest captured
- Jun 9, 2026
- Latest captured
- Jul 8, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 153
- Known gaps
- 0
- apnic-ianaxfer-apnic.net
- Earliest captured
- Mar 27, 2014
- Latest captured
- Jul 11, 2019
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,921
- Known gaps
- 0
- apnic-icp-2review-apnic.net
- Earliest captured
- Apr 24, 2025
- Latest captured
- Sep 1, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,317
- Known gaps
- 0
- apnic-measurement-apnic.net
- Earliest captured
- Dec 21, 2022
- Latest captured
- Mar 8, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,913
- Known gaps
- 0
- apnic-mvnog-apnic.net
- Earliest captured
- Feb 5, 2026
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 167
- Known gaps
- 0
- apnic-orbit-discuss-apnic.net
- Earliest captured
- Sep 13, 2022
- Latest captured
- Nov 13, 2022
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 666
- Known gaps
- 1
- apnic-pngnog-apnic.net
- Earliest captured
- Nov 21, 2019
- Latest captured
- Oct 28, 2024
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,708
- Known gaps
- 1
- apnic-security-discuss-apnic.net
- Earliest captured
- Mar 27, 2024
- Latest captured
- Aug 16, 2024
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,682
- Known gaps
- 0
- apnic-sig-cooperation-apnic.net
- Earliest captured
- Jan 15, 2015
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,003
- Known gaps
- 1
- apnic-sig-guidelines-review-apnic.net
- Earliest captured
- Jun 3, 2026
- Latest captured
- Sep 2, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,349
- Known gaps
- 1
- apnic-sig-nir-lists.apnic.net
- Earliest captured
- May 13, 2004
- Latest captured
- Sep 4, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,985
- Known gaps
- 2
- apnic-sig-routingsecurity-apnic.net
- Earliest captured
- Apr 3, 2020
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,648
- Known gaps
- 1
- apnic-user-feedback-group-apnic.net
- Earliest captured
- Sep 12, 2022
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,367
- Known gaps
- 0
- apnic-wg-pdr-apnic.net
- Earliest captured
- Mar 29, 2021
- Latest captured
- Sep 21, 2022
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,444
- Known gaps
- 1
- apnic-youth4ig-lists.apnic.net
- Earliest captured
- Feb 19, 2020
- Latest captured
- Jul 28, 2023
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,018
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 1, 2001
Latest captured: Oct 15, 2026
Freshness
Known gaps
- www.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- conference.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-academy-talk-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-afg-community-apnic.foundation: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apac-ict-women-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apix-chair-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apix-secretary-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apix-treasurer-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-alumni-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-announce-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-foundation-discuss-apnic.foundation: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-services-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-talk-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-transfers-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-bgp-stats-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-community-elections-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-community-events-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-diversity-in-leadership-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-ianaxfer-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-icp-2review-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-measurement-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-mvnog-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-orbit-discuss-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-pngnog-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-security-discuss-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-cooperation-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-guidelines-review-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-nir-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-routingsecurity-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-user-feedback-group-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-wg-pdr-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-youth4ig-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
