RPKI ROAs for unallocated and unassigned APNIC address space (was: AS0 forBogons)

n its bucket

nder APNIC�s administration

create AS0(zero) ROAs for all the unallocated address space in its bucket (IPv4 and IPv6). Any resou

create AS0(zero) ROAs for all the unallocated address space (IPv4 and IPv6) for which APNIC is the current administrator. Any resou

ce holder can creat

ce holder (APNIC member) can creat

r account. A ROA is

r account/administration. A ROA is

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.

Problem statement -------------------- Address space managed by APNIC which has is either "Unallocated" or "Unassigned" is considered "Bogon address space".

See [RFC3330] and [RFC1918].

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.

As of now, there are 287 IPv4 bogons and 73 IPv6 bogons in the global routing table.

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.

Beside all these attempts the issue of Bogon Advertisement hasn't be resolved so far.

Despite these attempts, the issue of unauthorized advertisements of APNIC's address space hasn't be resolved so far.

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.

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.

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.

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.

Currently, in the absence of any ROA, these bogons are marked as �NotFound�.

Currently, in the absence of any ROA, these bogons are marked as NotFound.

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.

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.

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.

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.

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.

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.

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.

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.