Thanks David for your explanation.
 
To clarify, APNIC has never given NIRs large IPv6 blocks for sub-delegations; 
APNIC has always used direct delegation methods for IPv6 delegations to NIR 
Members. All IPv6 delegations to organizations under NIRs are directly from the 
APNIC pool, which give them the same position as APNIC direct Members in the 
IPv6 pool, to allow further growth.  
 
The change from the previous NIR block-based process to direct delegation 
methods happened in 2004 and was for IPv4 only. The purpose of the change was 
for better aggregation, as APNIC has bigger pool than NIRs. 
 
It looks like there are some confusion and APNIC will update the APNIC Blog to 
make it clearer.
 
Kind regards,
Guangliang
========== 


-----Original Message-----
From: David Conrad <[email protected]> 
Sent: Wednesday, 22 December 2021 3:07 AM
To: Gaurav Kansal <[email protected]>
Cc: RT_helpdesk <[email protected]>; Mailman_innog <[email protected]>; 
[email protected]; [email protected]
Subject: [apnic-talk]Re: Reg - IPV6 allocation method changes from block based 
to delegations based for NIR

Gaurav,

On Dec 20, 2021, at 9:56 PM, Gaurav Kansal <[email protected]> wrote:
> A big block to NIR can help in super netting the v6 announcement at NIR (or 
> at country level) , which can help in reducing the routing table size in long 
> terms

How would this work exactly, given Internet connectivity and routing 
aggregation is provider-based and does not necessarily follow geopolitical 
boundaries?

> AND can also have IPv6 allocations in consecutive order for the economies 
> where we have NIRs.

Why would this be helpful?

> APNIC still allots ASN block to NIRs for further allocation to NIR members.

ASNs are merely tags associated with a bunch of prefixes that have (in theory) 
a unique routing policy.  As such, there isn’t much need to create aggregates, 
so how they are allocated doesn’t really matter.

Regards,
-drc

_______________________________________________
apnic-talk mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to