Satoru-san,

Many participants felt that the proposal still does not clearly explain why the 
current minimum allocation size of /32 is no longer appropriate.

Per the proposal text, network operators with longer than a /32 cannot 
redelegate address space from this space to their customers. They also cannot 
create sub-records within Whois for assigned space apart from the parent 
record. This may not accurately reflect how the space is used.

Several participants questioned whether WHOIS/RDAP registration accuracy is 
sufficient justification for changing the IPv6 allocation policy.

It is not the only reason, see above.

Some felt that the proposal focuses only on address conservation, while 
overlooking other long-standing policy objectives such as aggregation and 
minimizing routing overhead.

This proposal does not discuss or even mention "conservation", so it is unclear 
how this view/opinion is formed.

The rationale for introducing nibble-boundary allocations was considered 
unclear. Participants requested concrete operational benefits and use cases.

If a network operator requests a /45 but policy says they are to receive a /44, 
and they receive said /44, it makes no difference operationally to their 
network. This is to maintain clear and easy calculation and delegation of 
address space.

Some participants noted that changing a long-established allocation size 
requires stronger justification than currently provided.

This proposal is not a global first. ARIN's policy manual permit allocations of 
a /40 on request, seeĀ 
https://www.arin.net/participate/policy/nrpm/#6-5-2-1-size.
As a proposal author, I would also encourage members from the JPOPF to directly 
share their concerns with the Policy SIG. I note that it was stated that 17 
members from the Japanese community were in attendance, however, references 
such as "several participants questioned" and "some participants noted" are 
used, which makes it difficult to gauge how many members expressed these 
concerns and whether it is significant enough to justify making changes.
Regards,Christopher Hawker
_______________________________________________
SIG-policy - https://mailman.apnic.net/[email protected]/
To unsubscribe send an email to [email protected]

Reply via email to