Activity Summary
- 4748 days inactive
- 4748 days old
- sig-policy@lists.apnic.net
- 2 participants
- 1 comments
j
: Next unread message k
: Previous unread message j a
: Jump to all threads
j l
: Jump to MailingList overview
Hi, Terry,
Thanks for your comments.
as a polite request can you please distinguish your posts as either SIG chair or co-author when and where confusion might occur?
I will declare it very clear if there might be confusion.
I really don't think that a differentiation of assignment or allocation is needed. It will require effort on the secretariat and it is simpler, easier and less burden to just >make the /22 call. Given the secretariat resources are member funded, I think any effort to reduce administrative work load is a good thing - which essentially >means the member gets the allocation faster.
As I said before, current policy permit assignments as well as allocations, I don't see any extra administrative work load will be incurred if we keep these assignments policy in the final /8 phase, let alone to say, some small multihoming ,IXP and Critical infrastructure applicants may not be able to justify a /22 requirement, so the current minimum assignment size is /24 or lower.
Regards
Terence Zhang
On 02/02/2010, at 7:15 PM, Terence Zhang YH(CNNIC) wrote:
Andy,
Prop-081 doesn't in any way violate the concept of give everyone a single small block of IPv4 from the final /8, It's just that under current final /8 policy it's impossible to make IPv4 addresses assignments to end users, we propose that change in order to makes it consistent in dealing with allocation and assignment in the final /8 phase.
Current IPv4 policy permit assignments as well as allocations, I don't see any extra administrative work load will be incurred if we keep that consistence in the final /8 phase. I also don't think we should exclude assignments in the final /8 phase in order to reduce administrative work load.
Regards
Terence Zhang
----- Original Message ----- From: "Andy Linton" asjl@lpnz.org To: sig-policy@lists.apnic.net Sent: Tuesday, February 02, 2010 11:04 AM Subject: Re: [sig-policy] prop-081: Eligibility for assignments from the final /8
- Summary of the current problem
The current final /8 policy [1], only permits allocations to account holders to be made. This means that during the final /8 phase, it will be impossible to make IPv4 addresses assignments to end users under multihoming, Internet Exchange Point (IXP) and Critical infrastructure policies.
From my recollection of the discussion around this policy we chose to
give everyone exactly the same size block (the minimum allocation size).
This was to make the process simple and fair - everybody got one more allocation (in today's terms, a /22) when we got to the last /8 - no ifs, no buts, no maybes.
I don't support this change which makes the administration of the policy more complex.
andy
sig-policy: APNIC SIG on resource management policy *
sig-policy mailing list sig-policy@lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy
sig-policy: APNIC SIG on resource management policy *
sig-policy mailing list sig-policy@lists.apnic.net http://mailman.apnic.net/mailman/listinfo/sig-policy
Hi Terence,
On 04/02/2010, at 7:02 PM, Terence Zhang YH(CNNIC) wrote:
as a polite request can you please distinguish your posts as either SIG chair or co-author when and where confusion might occur?
I will declare it very clear if there might be confusion.
Appreciated :-)
I really don't think that a differentiation of assignment or allocation is needed. It will require effort on the secretariat and it is simpler, easier and less burden to just >make the /22 call. Given the secretariat resources are member funded, I think any effort to reduce administrative work load is a good thing - which essentially >means the member gets the allocation faster.
As I said before, current policy permit assignments as well as allocations,
sure. But is it necessary to take that into the final /8? While I do not have a crystal ball I see very little benefit to anyone in breaking down the last /8 into small chunks for whatever reason. I think it just serves to confuse on several layers.
I don't see any extra administrative work load will be incurred if we keep
it's not about "extra", it's the last /8 - we should be making less ipv4 work and pushing ipv6.
these assignments policy in the final /8 phase, let alone to say, some small multihoming ,IXP and Critical infrastructure applicants may not be able to justify a /22 requirement, so the current minimum assignment size is /24 or lower.
O.k lets be serious here.. are you suggesting that any of: * root domain name system (DNS) server; * global top level domain (gTLD) nameservers; * country code TLD (ccTLDs) nameservers; * IANA; * Regional Internet Registry (RIRs); and * National Internet Registry (NIRs).
will actually require address space under the last /8 policy? are they that shortsighted to fall into this category? really? I don't buy it.
Secondly IXPs. Same question. I can't see that they will have major issues here given MLPA appears (*) to be falling out of favour and IX participants are doing direct sessions with interesting participants that are present.
(*) I am not an expert on IXPs
lastly, small multi-homers (who already have LIR space). Shouldn't we suggest that they head to v6 over trying to multi-home in v4? and if we do foster /24s in the last /8 all I see is a marshland of prefix lengths, given conservation is then moot (nothing left to conserve) wouldn't aggregation be the next best ideal to follow?
lets face it, we are already scraping the barrel with 1/8.
Sorry, I still don't support this proposal and I cant see that changing.
Cheers Terry