Hi Vivek,
I 100% understand and, within reason, support the EC resolution 2021-09. I
have attended many presentations on this topic and have gone through the
process to acquire custodianship of my Historical Resources, and as such am
not personally concerned about my situation.
I just can't see anywhere in the existing APNIC Internet Number Resources
Policy that the secretariat currently has the power on the 1st of Jan 2023
to place Historical Resources advertised on the Internet into Reserved
status. I may have misread or misinterpreted, and I'm happy to be proved
wrong here.
Can you please advise where in the Policy APNIC is currently empowered to
take this action?
Regard,
Brett
On Fri, Sep 9, 2022 at 8:35 PM Vivek Nigam <[email protected]> wrote:
> Hi Jordi, Aftab,
>
>
>
> I have summarised the process APNIC uses to add/remove prefixes from APNIC
> AS0 ROA. This may help explain why you did not find some of the prefixes in
> AS0 ROA.
>
>
>
> Once a prefix is marked as 'reserved' it is added into AS0 ROA after 7
> days to cause as little disruption as possible and avoid any inadvertent
> actions. Where possible, we also aggregate the prefixes that are added into
> AS0 ROA. When a prefix is delegated to a Member, it is removed from AS0
> within 5 minute window.
>
>
>
> As per our implementation of APNIC EC resolution 2021-09, any historical
> resources that are not maintained under an APNIC account will be removed
> from whois and marked as reserved on 1 January, 2023. 7 days after that,
> those reserved prefixes will be added into AS0 ROA.
>
>
>
> Thanks
>
> Vivek
>
>
>
> *From: *JORDI PALET MARTINEZ via sig-policy <[email protected]>
> *Date: *Wednesday, 7 September 2022 at 6:51 pm
> *To: *[email protected] <[email protected]>
> *Subject: *[sig-policy] Re: prop-147-v001: Historical Resources Management
>
> Question for the staff on this. Is the AS0 proposal not sufficient to
> comply with Aftab observation, or it is just something in the backlog of
> pending secretariat activities, or what is the reason for that?
>
>
>
>
>
>
>
> Regards,
>
> Jordi
>
> @jordipalet
>
>
>
>
>
>
>
> El 30/8/22, 3:48, "Aftab Siddiqui" <[email protected]> escribió:
>
>
>
> Hi Vivek,
>
>
>
> On Mon, 29 Aug 2022 at 18:15, Vivek Nigam <[email protected]> wrote:
>
> Hi Aftab,
>
>
>
> APNIC creates RPKI ROAs with origin AS0 for all undelegated address space
> (marked as “Available” and “Reserved” in the
> delegated-apnic-extended-latest stats file. It may be worth noting that
> APNIC publishes these AS0 ROAs in a different Trust Anchor (AS0 TAL) and
> recommends its Members use APNIC AS0 TAL as a routing information service
> only.
>
>
>
>
> https://www.apnic.net/community/security/resource-certification/apnic-limitations-of-liability-for-rpki-2/
>
>
>
>
>
> That is incorrect, there are more than 160 IPv4 prefixes (I haven't
> checked v6 yet) which are marked as either "reserved" or "available" in the
> APNIC delegation file and they don't exist in AS-0 ROA. So there must be
> some policy which is in place.
>
>
>
> delegate file: 2.3|apnic|20220830|158240||20220829|+1000
>
> AS0 ROA: SigningTime: 2022-08-30T01:10:15Z
>
>
> Regards,
>
> Aftab A. Siddiqui
>
>
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
> _______________________________________________
> sig-policy - https://mailman.apnic.net/[email protected]/
> To unsubscribe send an email to [email protected]
>
_______________________________________________
sig-policy - https://mailman.apnic.net/[email protected]/
To unsubscribe send an email to [email protected]
