Re: [sig-policy] prop-085: Eligibility for critical infrastructureassign
- To: sig-policy at lists dot apnic dot net
- Subject: Re: [sig-policy] prop-085: Eligibility for critical infrastructureassignments from the final /8
- From: Izumi Okutani <izumi at nic dot ad dot jp>
- Date: Fri, 20 Aug 2010 11:28:32 +0900
- Delivered-to: sig-policy at mailman dot apnic dot net
- In-reply-to: <4C6D3CF2.4010100 at lahai dot com>
- List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy>
- List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:sig-policy@lists.apnic.net>
- List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
- List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
- References: <482182673.27379@cnnic.cn> <2D01DAA7-A036-4532-8D31-D3F632EEAA33@terrym.net> <4C6D1D42.5030801@nic.ad.jp> <4C6D3CF2.4010100@lahai.com>
- User-agent: Thunderbird 2.0.0.24 (Windows/20100228)
>> from this reserved block after regular APNIC pool runs out, so I can see >> that it's worth explicitly defining this. > > Yes, that was my point as well. Critical Infrastructure assignments from > the final /8 should only happen after the current reserved blocks runs out. Actually, my suggestion was slightly different. What I meant to say was, we should make it clear in the policy that we continue assignments for Critical Infrastructure from 203.119.0.0/16 block until it runs out, even during the final /8 phase. (which is ambiguous from the current policy) No need to make additional reservation from the final /8. Izumi