APNIC · RIR Watchdog
Application of the HD ratio to IPv4
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-020
- RIR
- APNIC
- Official status
- Abandoned after four week discussion on mailing list.
- Normalized status
- Abandoned
- Introduced
- Aug 4, 2004
- Last source update
- Oct 14, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Public discussion
[sig-policy] Policy SIG Proposal - HD ratio for IPv4 allocations
8 Discussion messages · 5 Entities
Source facts ↗Public discussion
RE: [sig-policy] Policy SIG Proposal - HD ratio for IPv4 allocations
2 Discussion messages · 2 Entities
Source facts ↗
Entities
- Izumi Okutani · Identity unresolvedDiscussion messages5First activityAug 5, 2004Last activityAug 26, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Anne Lord · Identity unresolvedDiscussion messages2First activityAug 11, 2004Last activityAug 23, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- Toshiyuki Hosaka · Identity unresolvedDiscussion messages1First activitySep 9, 2004Last activitySep 9, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- APNIC Secretariat · Identity unresolvedDiscussion messages1First activityAug 4, 2004Last activityAug 4, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies11
- Jeff Williams · Identity unresolvedDiscussion messages1First activityAug 10, 2004Last activityAug 10, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- Discussion messages1First activityFeb 23, 2006Last activityFeb 23, 2006First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies7Freshness: Stale
Identity verified: Sep 29, 2026
Telstra · Historical He was the Chief Internet Scientist for Telstra from 2001 until 2004.
conference.apnic.netAPNIC · Historical Geoff joined APNIC as the Research Scientist in 2004.
conference.apnic.netAPNIC · Historical Geoff Huston [APNIC]
ripe.netInternet Architecture Board · Historical He has been a member of the Internet Architecture Board from 1999 until 2005 and served as the Executive Director of the IAB from 2001 until 2005.
conference.apnic.netInternet Architecture Board · Historical He has been a member of the Internet Architecture Board from 1999 until 2005 and served as the Executive Director of the IAB from 2001 until 2005.
conference.apnic.netIETF · Historical He currently chairs IETF working groups on Routing operations and IPv6 Multi-homing.
conference.apnic.netIETF · Historical He currently chairs IETF working groups on Routing operations and IPv6 Multi-homing.
conference.apnic.netAPNIC · Historical Geoff has been a supporter of APNIC since its inception, and he has served on the Executive Council from 1996 until 2004.
conference.apnic.netVerified public profiles
- Discussion messages
- 1
- First activity
- Feb 23, 2006
- Last activity
- Feb 23, 2006
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 7
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
The retained message presents a technical report about HD-ratio implications and notes that the proposal is also under consideration in APNIC. It does not state Geoff Huston’s support or opposition to the APNIC proposal, so it cannot establish consistency or a change over time.
Application of the HD ratio to IPv4
Assessment: Insufficient evidence to assess consistency · The message shares technical analysis of HD-ratio implications and identifies the proposal as relevant to APNIC, but it does not state a personal position on the proposal. A single technical report cannot establish viewpoint consistency or inconsistency.
Conditions: The report is evidence of analysis or information sharing, not an adoption or implementation verdict.
This report was posted to the RIPE address policy mailing list
- Feb 23, 2006 · Procedural or neutral
[sig-policy] Some comments relevant to prop-020-v001.txt
Conditions:
Circulates his sensitivity analysis of replacing the uniform 80% IPv4 utilisation threshold with an HD ratio of 0.96; supplies analytical evidence without an explicit support or opposition vote.
Under the report’s constant-demand simulation, RIPE NCC address consumption increases by 46%. The hypothetical immediate adoption by all five RIRs includes a 47% increase for APNIC; these are modelled scenarios, not observed policy effects.
Highlights the disproportionate contribution of very large allocations: /9 and /10 allocations account for half the simulated increase, although they represent about 1% of allocations in the cited data.
The projected IANA exhaustion dates are historical conditional outputs in this February 2006 message, not current forecasts, actual exhaustion dates or proof that either proposal was adopted.
The report is attributed to Geoff Huston in the retained message. Its embedded heading says 22 February 2005 while the email and allocation tables reference 2006; the original wording is preserved and that date discrepancy is not silently resolved.
I trust that this report is helpful in terms of assessing some of the impacts of the proposal. … 0.96 for IPv4 address allocations made by the RIPE NCC is predicted to increase total address consumption by 46% over the existing flat 80% utilization allocation policy framework. … A related consideration is that of the adoption of such a policy proposal by all 5 RIRs. If this were the case, and the adoption of this policy was to be effective immediately, then the relative increase in overall address consumption for each RIR would be: Afrinic 39%, APNIC 47%, ARIN 46%, LACNIC 47%. … 50% of this increased address consumption is in allocations of /9 and /10 prefixes, which only account for 1% of all actual allocations, but 20% of the allocated addresses.
Source facts ↗
Per-policy stance timelines:prop-020 · Unknown · Insufficient evidence to assess consistencyprop-031 · Unknown · No explicit position statedprop-032 · Unknown · No explicit position statedprop-033 · Unknown · No explicit position statedprop-050 · Unknown · No explicit position statedprop-109 · Unknown · No explicit position statedprop-110 · Unknown · No explicit position statedExperimental Internet Resource Allocations · Unknown · No explicit position statedTotal policy messages: 22
- Discussion messages1First activitySep 9, 2004Last activitySep 9, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies6
- Paul Wilson · Identity unresolvedDiscussion messages1First activityAug 9, 2004Last activityAug 9, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther 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
- 405
- 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,689
- 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,202
- 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,158
- 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,657
- 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,653
- 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,003
- 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,282
- 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,740
- 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
- 2,847
- 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,688
- 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
- 3,865
- 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
- 9
- 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
- 2,855
- 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
- 144
- 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,711
- 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,155
- Known gaps
- 0
- apnic-measurement-apnic.net
- Earliest captured
- May 31, 2023
- Latest captured
- Mar 8, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,725
- 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
- 168
- 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
- 702
- Known gaps
- 1
- apnic-pngnog-apnic.net
- Earliest captured
- Dec 26, 2019
- Latest captured
- Oct 28, 2024
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,534
- 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,532
- 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
- 2,740
- 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,431
- 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,820
- 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,575
- 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,287
- 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,277
- 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
- 2,653
- 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.
