APNIC · RIR Watchdog
prop-168: Increase to maximum IPv4 delegations
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-168
- RIR
- APNIC
- Official status
- For discussion at APNIC 62 OPM
- Normalized status
- Under discussion
- Introduced
- Dec 18, 2025
- Last source update
- Oct 14, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Public discussion
[sig-policy] Re: Copyright and Acceptable Use Terms for APNIC Directory Services
2 Discussion messages · 2 Entities
Source facts ↗
Entities
- teddyap · Identity unresolvedDiscussion messages1First activityAug 17, 2026Last activityAug 17, 2026First explicit stanceSupport with changesLatest explicit stanceSupport with changesStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- Bikram Shrestha · Identity unresolvedDiscussion messages1First activityAug 12, 2026Last activityAug 12, 2026First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies5
- Discussion messages1First activityAug 11, 2026Last activityAug 11, 2026First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies4Freshness: Stale
Identity verified: Sep 11, 2026
· Historical Current status Implemented Author Christopher Hawker Relevant forum Policy SIG Previous versions prop-156-v001 Secretariat impact assessment Impact assessment for v001.
www.apnic.netVerified public profiles
- Discussion messages
- 1
- First activity
- Aug 11, 2026
- Last activity
- Aug 11, 2026
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 4
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
The retained evidence is one email addressing three proposals, not three independent occasions. Hawker distinguishes their scope and argues for more development time for prop-165. His conditional resource-pool argument is coherent within that email, but this record cannot establish consistency or a change of position over time.
prop-168: Increase to maximum IPv4 delegations
Assessment: Insufficient evidence to assess consistency · Hawker identifies himself as the prop-168 author and uses expected pool depletion to question the usefulness of prop-165. One conditional forecast does not establish his longer-term position or prove that depletion occurred.
Conditions: The forecast is expressly qualified by possible author bias and expectations about adoption and depletion. · Three observations of the same email must not be counted as three separate statements.
Acknowledging the potential for author bias, there is a reasonable expectation that Prop-168 that I have submitted, will deplete the available address pool within 6 months.
prop-165: Provision of IPv4 Address Space to IPv6-only Networks for Transitional Purpose
Assessment: Insufficient evidence to assess consistency · He asks for withdrawal or postponement of prop-165 and gives procedural, sunset-clause and policy-development reasons. He also says additional time could improve its chance of consensus; this is a qualified recommendation about the present proposal, not evidence of a reversal.
Conditions: Only one dated email is supplied. · Respect for an author’s effort is compatible with requesting postponement.
This recommendation is not to minimise the importance of the author's proposal in any way or to undervalue the time they have invested in its drafting, its more so to show that greater time is required to ensure that this proposal is shaped in a way that affords it the best chance of reaching consensus, and that as a result other proposals should be considered a "greater priority".
Assessment: Insufficient evidence to assess consistency · The WHOIS Privacy proposal appears as a scope comparison with a directory-services acceptable-use submission. That comparison does not state support for or opposition to WHOIS Privacy and cannot establish a position history.
Conditions: Different directory-service subjects should not be treated as interchangeable policies.
Prop-162 is based on WHOIS Privacy, the proposal submitted (based on the title) is regarding Acceptable Use Terms for APNIC Directory Services.
prop-168: Increase to maximum IPv4 delegations · prop-165: Provision of IPv4 Address Space to IPv6-only Networks for Transitional Purpose
Assessment: Consistent · Within this email, the expectation that prop-168 could exhaust the remaining pool is used consistently as a conditional argument that prop-165 could become redundant. Supporting his own allocation proposal while questioning the usefulness and timing of another does not, by itself, establish a contradiction.
Conditions: This is internal coherence of a single argument, not proof of consistency across time. · The predicted depletion and redundancy are not verified outcomes.
Acknowledging the potential for author bias, there is a reasonable expectation that Prop-168 that I have submitted, will deplete the available address pool within 6 months.
This, in and of itself, would render Prop-165 redundant.
prop-162: WHOIS Privacy · prop-165: Provision of IPv4 Address Space to IPv6-only Networks for Transitional Purpose
Assessment: Insufficient evidence to assess consistency · The email distinguishes WHOIS Privacy from acceptable-use terms while questioning the agenda treatment of prop-165. It supplies no comparable substantive position on WHOIS Privacy, so a cross-policy reversal cannot be assessed.
Conditions: Agenda access, proposal maturity and substantive policy preference are different questions.
Prop-162 is based on WHOIS Privacy, the proposal submitted (based on the title) is regarding Acceptable Use Terms for APNIC Directory Services.
On what basis was the decision made to reinstate a proposal that was withdrawn, instead of presented as a new proposal?
- Aug 11, 2026 · Question or clarify
[sig-policy] Re: Copyright and Acceptable Use Terms for APNIC Directory Services
Could I please ask, how the Chairs have determined
Source facts ↗
Per-policy stance timelines:prop-156 · Unknown · No explicit position statedprop-162 · Unknown · Insufficient evidence to assess consistencyprop-164 · Unknown · No explicit position statedprop-165 · Unknown · Insufficient evidence to assess consistencyprop-168 · Unknown · Insufficient evidence to assess consistencyTotal policy messages: 3
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,673
- 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,173
- Known gaps
- 1
- apnic-afg-community-apnic.foundation
- Earliest captured
- Sep 27, 2023
- Latest captured
- Jun 24, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,130
- Known gaps
- 0
- apnic-apac-ict-women-apnic.net
- Earliest captured
- Oct 22, 2024
- Latest captured
- Aug 11, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,625
- Known gaps
- 0
- apnic-apix-chair-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 14, 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
- 1
- Known gaps
- 1
- apnic-apix-treasurer-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- apnic-apnic-alumni-apnic.net
- Earliest captured
- Feb 14, 2024
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,635
- Known gaps
- 0
- apnic-apnic-announce-apnic.net
- Earliest captured
- Jun 11, 2025
- Latest captured
- Sep 3, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,985
- Known gaps
- 0
- apnic-apnic-foundation-discuss-apnic.foundation
- Earliest captured
- Sep 12, 2022
- Latest captured
- Mar 11, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,266
- Known gaps
- 0
- apnic-apnic-services-apnic.net
- Earliest captured
- Aug 31, 2020
- Latest captured
- Aug 4, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,721
- Known gaps
- 0
- apnic-apnic-talk-lists.apnic.net
- Earliest captured
- Apr 15, 2004
- Latest captured
- Sep 8, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,829
- Known gaps
- 0
- apnic-apnic-transfers-apnic.net
- Earliest captured
- Sep 21, 2012
- Latest captured
- Feb 22, 2025
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,671
- Known gaps
- 1
- apnic-bgp-stats-lists.apnic.net
- Earliest captured
- Aug 30, 2026
- Latest captured
- Sep 15, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,848
- 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
- 6
- 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,837
- Known gaps
- 1
- apnic-diversity-in-leadership-apnic.net
- Earliest captured
- Jun 9, 2026
- Latest captured
- Jul 8, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 143
- Known gaps
- 0
- apnic-ianaxfer-apnic.net
- Earliest captured
- Mar 27, 2014
- Latest captured
- Jul 11, 2019
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,694
- Known gaps
- 0
- apnic-icp-2review-apnic.net
- Earliest captured
- Apr 24, 2025
- Latest captured
- Sep 1, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,140
- Known gaps
- 0
- apnic-measurement-apnic.net
- Earliest captured
- May 31, 2023
- Latest captured
- Mar 8, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,706
- Known gaps
- 0
- apnic-mvnog-apnic.net
- Earliest captured
- Feb 5, 2026
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 159
- 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
- 695
- 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,507
- Known gaps
- 1
- apnic-security-discuss-apnic.net
- Earliest captured
- Mar 27, 2024
- Latest captured
- Aug 16, 2024
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,516
- 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,723
- 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,419
- 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,803
- 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,559
- Known gaps
- 1
- apnic-user-feedback-group-apnic.net
- Earliest captured
- Sep 12, 2022
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,272
- Known gaps
- 0
- apnic-wg-pdr-apnic.net
- Earliest captured
- Mar 29, 2021
- Latest captured
- Sep 21, 2022
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,262
- Known gaps
- 1
- apnic-youth4ig-lists.apnic.net
- Earliest captured
- Feb 19, 2020
- Latest captured
- Jul 28, 2023
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,635
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 1, 2001
Latest captured: Oct 14, 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.
