APNIC · RIR Watchdog
RPKI ROAs for unallocated and unassigned APNIC address space (was: AS0 forBogons)
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-132
- RIR
- APNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Aug 9, 2019
- Last source update
- Oct 12, 2026
- Coverage
- Partial
Who actually shaped the debate?
9Total participants
9Discussion contributors
1Formal actors
22Discussion messages
6.2Effective participants
81.8%Top-five discussion share
3People covering 50%
5People covering 80%
Policy evolution
Objective—description of APNIC-administered unallocated address space · The objective replaces the informal description of unallocated address space as being “in its bucket” with the more specific description “under APNIC’s administration.”
Proposed policy—scope of APNIC-created AS0 ROAs · The proposed scope changes from all unallocated IPv4 and IPv6 address space “in its bucket” to unallocated IPv4 and IPv6 address space for which APNIC is the current administrator.
Source facts −
create AS0(zero) ROAs for all the unallocated address space in its bucket (IPv4 and IPv6). Any resouSource facts ↗
Source facts +
create AS0(zero) ROAs for all the unallocated address space (IPv4 and IPv6) for which APNIC is the current administrator. Any resouSource facts ↗
Proposed policy—resource holders permitted to create AS0 ROAs · The unqualified term “Any resource holder” is narrowed or clarified to “Any resource holder (APNIC member).”
Proposed policy—resources under a holder’s control · The resource-holder provision expands the wording from resources under the holder’s account to resources under the holder’s account or administration.
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Problem statement -------------------- Bogons are defined in RFC3871, A "Bogon" (plural: "bogons") is a packet with an IP source address in an address block not yet allocated by IANA or the Regional Internet Registries (ARIN, RIPE NCC, APNIC, AFRINIC and LACNIC) as well as all addresses reserved for private or special use by RFCs.Source facts ↗
Source facts +
Problem statement -------------------- Address space managed by APNIC which has is either "Unallocated" or "Unassigned" is considered "Bogon address space".Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts +
Bogons are defined in RFC3871, A "Bogon" (plural: "bogons") is a packet with an IP source address in an address block not yet allocated by IANA or the Regional Internet Registries (ARIN, RIPE NCC, APNIC, AFRINIC and LACNIC) as well as all addresses reserved for private or special use by RFCs. As of now, there are XXX IPv4 and YYY IPv6 routes in the global Internet routing table which cover address space ma naged by APNIC, but which is not allocated or assigned by APNIC.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
As of now, there are 287 IPv4 bogons and 73 IPv6 bogons in the global routing table.Source facts ↗
Source facts +
As of now, there are XXX IPv4 and YYY IPv6 routes in the global Internet routing table which cover address space ma naged by APNIC, but which is not allocated or assigned by APNIC.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Beside all these attempts the issue of Bogon Advertisement hasn't be resolved so far.Source facts ↗
Source facts +
Despite these attempts, the issue of unauthorized advertisements of APNIC's address space hasn't be resolved so far.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Objective of policy change ----------------------------- The purpose of creating AS0 (zero) ROAs for unallocated address space by APNIC is to resolve the issue of Bogon announcement.Source facts ↗
Source facts +
Objective of policy change ----------------------------- The purpose of creating RPKI ROAs with Origin AS 0 for APNIC's unallocated and unassigned address space is to restrict the propagation of BGP announcements covering such bogon space.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
When APNIC issues an AS0 ROA for unallocated address space under APNIC�s administration then it will be marked as �Invalid� if someone tries to advertise the same address space.Source facts ↗
Source facts +
When APNIC issues a ROA with AS 0 for unallocated address space under APNIC's administration, BGP announcements covering this space will be marked as Invalid by networks doing RPKI based BGP Origin Validation using APNIC's TAL.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Currently, in the absence of any ROA, these bogons are marked as �NotFound�.Source facts ↗
Source facts +
Currently, in the absence of any ROA, these bogons are marked as NotFound.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Since many operators have implemented ROV and either planning or already discarding �Invalid� then all the AS0 ROAs which APNIC will create for unallocated address space will be discarded as well.Source facts ↗
Source facts +
Since many operators have implemented ROV and either planning or already discarding Invalid, then all the AS0 ROAs which APNIC will create for unallocated address space will be discarded as well.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Proposed policy solution --------------------------- APNIC will create AS0(zero) ROAs for all the unallocated address space (IPv4 and IPv6) for which APNIC is the current administrator.Source facts ↗
Source facts +
Proposed policy solution --------------------------- APNIC will create AS0 (zero) ROAs for all the unallocated and unassigned address space (IPv4 and IPv6) for which APNIC is the current administrator.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
A ROA is a positive attestation that a prefix holder has authorised an AS to originate a route for this prefix whereas, a ROA for the same prefixes with AS0 (zero) origin shows negative intent from the resource holder that they don't want to advertise the prefix(es) at this point but they are the rightful custodian.Source facts ↗
Source facts +
A RPKI ROA is a positive attestation that a prefix holder has authorised an AS to originate a route for this prefix whereas, a RPKI ROA for the same prefixes with AS0 (zero) origin shows negative intent from the resource holder that they don't want to advertise the prefix(es) at this point but they are the rightful custodian.Source facts ↗
Policy text · Astra identified a substantive wording change in this retained policy section.
Source facts −
Only APNIC has the authority to create ROAs for address space not yet allocated to the members and only APNIC can issue AS0 (zero) ROAs.Source facts ↗
Source facts +
Only APNIC has the authority to create RPKI ROAs for address space not yet allocated to the members and only APNIC can issue AS0 (zero) RPKI ROAs.Source facts ↗
Debate timeline
Public discussion
Re: [sig-policy] prop-132-v001 AS0 for Bogons
10 Discussion messages · 5 Entities
Source facts 1 ↗Source facts 2 ↗Source facts 3 ↗Source facts 4 ↗Source facts 5 ↗Source facts 6 ↗Source facts 7 ↗Source facts 8 ↗Source facts 9 ↗Source facts 10 ↗Public discussion
Re: [sig-policy] prop-132-v002: AS0 for Bogons
6 Discussion messages · 4 Entities
Source facts 1 ↗Source facts 2 ↗Source facts 3 ↗Source facts 4 ↗Source facts 5 ↗Source facts 6 ↗
Entities
Freshness: Stale
- Srinivas Chendi · Identity unresolvedDiscussion messages6First activityAug 26, 2019Last activitySep 2, 2020First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies23
- Discussion messages4First activityAug 15, 2019Last activityAug 30, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies5
- Discussion messages3First activityAug 30, 2019Last activitySep 7, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Discussion messages3First activityAug 16, 2019Last activityAug 21, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies10
- Md. Abdul Awal · Identity unresolvedDiscussion messages2First activityAug 15, 2019Last activityAug 15, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies5
- Satoru Tsurumaki · Identity unresolvedDiscussion messages1First activitySep 2, 2019Last activitySep 2, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies14
- Job Snijders · Identity unresolvedDiscussion messages1First activityAug 30, 2019Last activityAug 30, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Hiroki Kawabata · Identity unresolvedDiscussion messages1First activitySep 6, 2019Last activitySep 6, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies8
- Andrew Dul · Identity unresolvedDiscussion messages1First activityAug 15, 2019Last activityAug 15, 2019First 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,500
- 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,855
- 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,147
- 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,578
- 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,694
- 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,544
- 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,719
- 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
- 4
- 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,706
- 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
- 119
- 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,567
- 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,029
- 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,563
- 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
- 130
- 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
- 642
- 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,381
- 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,389
- 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,153
- 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,143
- 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,492
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 1, 2001
Latest captured: Oct 12, 2026
Freshness
Freshness: Stale · Last refresh:
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.