APNIC · RIR Watchdog
Expansion of the initial allocation space for existing IPv6 address spaceholders
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-021
- RIR
- APNIC
- Official status
- Endorsed by APNIC EC. Awaiting formal implementation but requests accepted immediately.
- Normalized status
- Accepted
- Introduced
- Aug 1, 2004
- Last source update
- Oct 12, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Public discussion
[sig-policy] Final call for comments: [prop-021-v001] "Expansion of the initial allocation space for existing IPv6 address space holders"
5 Discussion messages · 4 Entities
Source facts 1 ↗Source facts 2 ↗
Entities
- fujisaki · Identity unresolvedDiscussion messages4First activityAug 4, 2004Last activitySep 21, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Philip Smith · Identity unresolvedDiscussion messages3First activityAug 5, 2004Last activityAug 19, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- APNIC Secretariat · Identity unresolvedDiscussion messages2First activitySep 17, 2004Last activityNov 22, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies11
- Jeff Williams · Identity unresolvedDiscussion messages2First activitySep 18, 2004Last activitySep 22, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- (Tomohiro -INSTALLER-Fujisaki/$BF#:j(B $BCR9((B ) · Identity unresolvedDiscussion messages1First activitySep 21, 2004Last activitySep 21, 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
- Discussion messages1First activitySep 9, 2004Last activitySep 9, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies6Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
Last research attempt: Oct 4, 2026
Identity verified: Oct 4, 2026
JPNIC · Historical Manager of both the IP Department and the Internet Policy Department at JPNIC
conference.apnic.netAPNIC · Historical Chair: Toshiyuki Hosaka
conference.apnic.netJPNIC · Historical 2002年から2008年までJPNIC事務局員としてIPアドレス事業に従事。
www.nic.ad.jpQTnet · Historical 現在、株式会社QTnet執行役員経営企画部長。
www.nic.ad.jpJPNIC · Historical 2018年よりJPNIC理事(地域・非営利分野担当)。
www.nic.ad.jpVerified public profiles
- Discussion messages
- 1
- First activity
- Sep 9, 2004
- Last activity
- Sep 9, 2004
- 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
The sole retained observation is a meeting summary that records group consensus outcomes for four proposals. It does not provide Toshiyuki Hosaka’s own positions or a second statement, so it cannot establish longitudinal or cross-policy viewpoint consistency for these records.
A proposal to prevent the routing of “dark” address space
Assessment: Insufficient evidence to assess consistency · The message reports that the dark-address-space proposal did not reach consensus. It is a meeting summary and does not establish Toshiyuki Hosaka’s own position; one record cannot establish consistency or a change over time.
Conditions: The record reports a group or process outcome and does not establish the participant’s personal support, opposition, adoption, or implementation view.
- Consensus was not reached.
Application of the HD ratio to IPv4
Assessment: Insufficient evidence to assess consistency · The message reports no clear consensus on applying the HD ratio to IPv4 and says the proposal should remain open. This is a process summary rather than a stated personal position, and one record cannot establish consistency or a change over time.
Conditions: The record reports a group or process outcome and does not establish the participant’s personal support, opposition, adoption, or implementation view.
- There was no clear consensus.
Expansion of the initial allocation space for existing IPv6 address spaceholders
Assessment: Insufficient evidence to assess consistency · The message reports that the proposal to expand initial IPv6 allocations reached consensus. The report does not state Toshiyuki Hosaka’s own view, so one record cannot establish consistency or a change over time.
Conditions: The record reports a group or process outcome and does not establish the participant’s personal support, opposition, adoption, or implementation view.
- Consensus was reached.
Assessment: Insufficient evidence to assess consistency · The message reports consensus on the revised IANA IPv6 allocation policy with parameter flexibility. This is a meeting outcome reported by the co-chair, not a substantiated personal position, and one record cannot establish consistency or a change over time.
Conditions: The record reports a group or process outcome and does not establish the participant’s personal support, opposition, adoption, or implementation view.
- Consensus reached for the revised proposal, with some flexibility of parameters. Flexibility is left for consensus of other regions
A proposal to prevent the routing of “dark” address space · Expansion of the initial allocation space for existing IPv6 address spaceholders
Assessment: Insufficient evidence to assess consistency · The summary reports different group outcomes for two proposals, but it does not provide Toshiyuki Hosaka’s own positions on either proposal. The comparison therefore cannot establish a cross-policy consistency or inconsistency finding.
Conditions: The comparison concerns reported group outcomes, not a verified personal viewpoint.
- Consensus was not reached.
- Consensus was reached.
- Sep 9, 2004 · Procedural or neutral
[sig-policy] Summary report of APNIC 18 Policy-SIG
(3) prop-021-v001: Expansion of the initial allocation space for existing IPv6 address space holders - Proposal summary: To expand IPv6 address space for existing IPv6 address holders without satisfying the subsequent allocation requirements, with IPv6 deployment plan and/or with IPv4 infrastructure information. - Consensus was reached.
Source facts ↗
Per-policy stance timelines:prop-005 · Unknown · Insufficient evidence to assess consistencyprop-020 · Unknown · Insufficient evidence to assess consistencyprop-021 · Unknown · Insufficient evidence to assess consistencyprop-023 · Unknown · Insufficient evidence to assess consistencyprop-026 · Unknown · No explicit position statedprop-042 · Unknown · No explicit position statedprop-048 · Unknown · No explicit position statedTotal policy messages: 6
- Tomohiro Fujisaki · 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 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,545
- Known gaps
- 0
- www.apnic.net
- conference.apnic.net
- apnic-academy-talk-apnic.net
- Earliest captured
- Jan 12, 2023
- Latest captured
- Jan 19, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,068
- Known gaps
- 0
- apnic-afg-community-apnic.foundation
- Earliest captured
- Sep 27, 2023
- Latest captured
- Jun 24, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,024
- Known gaps
- 0
- apnic-apac-ict-women-apnic.net
- Earliest captured
- Oct 22, 2024
- Latest captured
- Aug 11, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,511
- Known gaps
- 0
- apnic-apix-chair-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 12, 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 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- apnic-apix-treasurer-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 12, 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 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,499
- Known gaps
- 0
- apnic-apnic-announce-apnic.net
- Earliest captured
- Jun 11, 2025
- Latest captured
- Sep 3, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,854
- Known gaps
- 0
- apnic-apnic-foundation-discuss-apnic.foundation
- Earliest captured
- Sep 12, 2022
- Latest captured
- Mar 11, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,146
- Known gaps
- 0
- apnic-apnic-services-apnic.net
- Earliest captured
- Aug 31, 2020
- Latest captured
- Aug 4, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,577
- Known gaps
- 0
- apnic-apnic-talk-lists.apnic.net
- Earliest captured
- Apr 15, 2004
- Latest captured
- Sep 8, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,693
- Known gaps
- 0
- apnic-apnic-transfers-apnic.net
- Earliest captured
- Sep 21, 2012
- Latest captured
- Feb 22, 2025
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,543
- Known gaps
- 0
- apnic-bgp-stats-lists.apnic.net
- Earliest captured
- Aug 30, 2026
- Latest captured
- Sep 15, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,718
- Known gaps
- 0
- apnic-community-elections-apnic.net
- Earliest captured
- Nov 12, 2021
- Latest captured
- Nov 22, 2021
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1
- Known gaps
- 0
- apnic-community-events-apnic.net
- Earliest captured
- May 9, 2025
- Latest captured
- Aug 19, 2025
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,705
- Known gaps
- 0
- apnic-diversity-in-leadership-apnic.net
- Earliest captured
- Jun 9, 2026
- Latest captured
- Jul 8, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 114
- Known gaps
- 0
- apnic-ianaxfer-apnic.net
- Earliest captured
- Mar 27, 2014
- Latest captured
- Jul 11, 2019
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,566
- Known gaps
- 0
- apnic-icp-2review-apnic.net
- Earliest captured
- Apr 24, 2025
- Latest captured
- Sep 1, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,028
- Known gaps
- 0
- apnic-measurement-apnic.net
- Earliest captured
- May 31, 2023
- Latest captured
- Mar 8, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,562
- Known gaps
- 0
- apnic-mvnog-apnic.net
- Earliest captured
- Feb 5, 2026
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 129
- Known gaps
- 0
- apnic-orbit-discuss-apnic.net
- Earliest captured
- Sep 13, 2022
- Latest captured
- Nov 13, 2022
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 641
- Known gaps
- 0
- apnic-pngnog-apnic.net
- Earliest captured
- Dec 26, 2019
- Latest captured
- Oct 28, 2024
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,380
- Known gaps
- 0
- apnic-security-discuss-apnic.net
- Earliest captured
- Mar 27, 2024
- Latest captured
- Aug 16, 2024
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,390
- 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,589
- Known gaps
- 0
- apnic-sig-guidelines-review-apnic.net
- Earliest captured
- Jun 3, 2026
- Latest captured
- Sep 2, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,335
- Known gaps
- 0
- apnic-sig-nir-lists.apnic.net
- Earliest captured
- May 13, 2004
- Latest captured
- Sep 4, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,689
- Known gaps
- 0
- apnic-sig-routingsecurity-apnic.net
- Earliest captured
- Apr 3, 2020
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,446
- Known gaps
- 0
- apnic-user-feedback-group-apnic.net
- Earliest captured
- Sep 12, 2022
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,154
- Known gaps
- 0
- apnic-wg-pdr-apnic.net
- Earliest captured
- Mar 29, 2021
- Latest captured
- Sep 21, 2022
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,144
- Known gaps
- 0
- apnic-youth4ig-lists.apnic.net
- Earliest captured
- Feb 19, 2020
- Latest captured
- Jul 28, 2023
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,493
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 1, 2001
Latest captured: Oct 12, 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.
