prop-132: RPKI ROAs for unallocated and unassigned APNIC address space (was: AS0 for Bogons)
Address space managed by APNIC which has is either “Unallocated” or “Unassigned” is considered “Bogon address space”. 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.
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. 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.
|Relevant forum||Policy SIG|
|Status at other RIRs||No such policy in any region at the moment.|
|09 August 2019||Version 1 posted to the Policy SIG mailing list for discussion and community development.|
|22 August 2019||Version 2 posted to the Policy SIG mailing list for discussion and community development.|
|03 September 2019||Version 3 posted to the Policy SIG mailing list for discussion and community development.|
|12 September 2019||Reached consensus at APNIC 48.|
|18 September 2019||Start of Final Comment Period announcement.|
|18 October 2019||End of Final Comment Period announcement.|
|04 December 2019||Endorsed by APNIC EC.|
|07 January 2020||Editorial comment period announcement.|
|04 February 2020||End of editorial comment period. Policy published as apnic-127-v008.|
|02 September 2020||Implemented announcement|