Re: [sig-policy] [Sig-policy] prop-062-v001: Use of final /8
- To: David Woodgate <David.Woodgate at telstra dot net>
- Subject: Re: [sig-policy] [Sig-policy] prop-062-v001: Use of final /8
- From: Philip Smith <pfs at cisco dot com>
- Date: Sun, 27 Jul 2008 15:57:27 +1000
- Authentication-results: hkg-dkim-2; header.Fromemail@example.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; );
- Cc: 'APNIC Policy SIG List' <sig-policy at apnic dot net>
- Delivered-to: sig-policy at mailman dot apnic dot net
- In-reply-to: <200807220410.m6M4ALha073419 at burn dot telstra dot net>
- List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy>
- List-help: <mailto:firstname.lastname@example.org?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:email@example.com>
- List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:firstname.lastname@example.org?subject=subscribe>
- List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:email@example.com?subject=unsubscribe>
- Organization: Cisco Systems
- References: <firstname.lastname@example.org> <200807160431.m6G4VA28084482@burn.telstra.net> <49ADDDED-D274-4F3C-A16B-696240DB0E29@iroute.org> <200807170100.m6H10NP8099257@burn.telstra.net> <ED13462B-15CF-4916-91B0-1F0522F9AACF@jonnynet.net> <487F2F65.email@example.com> <firstname.lastname@example.org> <200807220410.m6M4ALha073419@burn.telstra.net>
- User-agent: Thunderbird 188.8.131.52 (Macintosh/20080707)
Hi David, David Woodgate said the following on 22/7/08 14:10: >
My main problem is that prop-062 seems to risk locking up the majority of the last /8, and therefore does not share it at all, let alone in a fair and equitable fashion.
I don't see how it is locking up the majority of the final /8. Would you please explain this.
If the tying of the allocation size to APNIC's minimum allocation at the time the allocation is requested is causing some concern, would you perhaps explain what might be a more useful quantity to choose, and why.
I'd be more sympathetic to a proposal which:- Was more aligned with the LACNIC proposal - that is, it reserved a smaller amount of space (the LACNIC proposal only specifies a /12) for *only* new businesses, based on a reasonable demand forecast model.
LACNIC's new policy applies to a /12 when LACNIC can no longer get address space from the IANA. There is no reason why something like this cannot be proposed for the APNIC region.
The authors' goal for prop-062 was to propose something constructive assuming the success of prop-055. If prop-055 fails, I see no need for prop-062. But I would then agree there would be need for a LACNIC style /12 policy.
- Considered reservations on the basis of associations between IPv4 allocations and IPv6 deployment or other technical requirements - an example (but not the only possible idea) is ARIN proposal 2008-5 (authored by Alain Durand)
Again, no reason why this cannot be proposed for the APNIC region.
- Identified that any part of the /8 not covered by these reservations would be available for demand-based allocation under the APNIC's normal allocation policies.
Which reservations does this point refer to?The only reservation made in prop-062 is for a /16 for future unforseen needs - and when the remainder of the final /8 is used, then the /16 would also be available for distribution.