Another small IPv6 allocation policy change proposal (sanity check email)...
Dear AP-WG ;) Some time ago we come to a consensus to change the IPv6 initial allocation rules and extend the initial allocation size from /32 to whatever between /32 and /29 without additional justification needed. One of the reasons to do that was a reserved space of /29 for each previously allocated /32 and general thinking was "let them use that space that no one else will probably ever use it as it is reserved for holder of /32 at the start of that /29" So far so good, many of you requested the extension to /29 and most of you got it with no issues. But not all of you. We encountered LIRs that are operators and in the past they bought other small operators and joined for example 3 LIRs under one and now they have 3 x /32 (of course with that /29 as reserved space). When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy. The policy says: "LIRs that hold one or more IPv6 allocations are able to request extension of these allocations up to a *total* of a /29 without providing further documentation." So an LIR can extend as many allocations as they want, as long as they never end up with more than a /29 *total* 3x/32 can be extended into 1x/30 + 2x/31 = /29 Alternatively, one /32 can be returned, then both remaining /32s can be extended to a /30. When we were preparing the policy change proposal we did not read that word *total* through the "multiple LIR/32" eyes and I feel that we should somehow correct this. New suggested text would be: "LIRs that hold one or more IPv6 allocations are able to request extension of *each* these allocations up to a /29 without providing further documentation." With this email I would like to check if community thinks we should go that route and draft the policy change proposal? Is this something that nobody cares and should not be fixed? Is this a threat to someone? Anyone sees any danger in going forward with this small change? Thank you very much, Jan Zorz
On 07/11/2012 11:53, Jan Zorz @ go6.si wrote:
Is this something that nobody cares and should not be fixed? Is this a threat to someone? Anyone sees any danger in going forward with this small change?
To give some background data on this, I figure this affects 55 LIRs out of 4587 which have ipv6 allocations. Of these, 44 LIRs have exactly 2 x 32. The distribution for the rest is:
/32 /32 /30 /27 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /32 /30
Nick
Hi, I fully support this (proposal), in some cases it may make the routing table a little bit smaller... Rgds Ray On Wed, 7 Nov 2012, Jan Zorz @ go6.si wrote:
Date: Wed, 07 Nov 2012 12:53:27 +0100 From: "Jan Zorz @ go6.si" <jan@go6.si> To: "address-policy-wg@ripe.net" <address-policy-wg@ripe.net> Subject: [address-policy-wg] Another small IPv6 allocation policy change proposal (sanity check email)...
Dear AP-WG ;)
Some time ago we come to a consensus to change the IPv6 initial allocation rules and extend the initial allocation size from /32 to whatever between /32 and /29 without additional justification needed.
One of the reasons to do that was a reserved space of /29 for each previously allocated /32 and general thinking was "let them use that space that no one else will probably ever use it as it is reserved for holder of /32 at the start of that /29"
So far so good, many of you requested the extension to /29 and most of you got it with no issues. But not all of you.
We encountered LIRs that are operators and in the past they bought other small operators and joined for example 3 LIRs under one and now they have 3 x /32 (of course with that /29 as reserved space).
When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy.
The policy says:
"LIRs that hold one or more IPv6 allocations are able to request extension of these allocations up to a *total* of a /29 without providing further documentation."
So an LIR can extend as many allocations as they want, as long as they never end up with more than a /29 *total*
3x/32 can be extended into 1x/30 + 2x/31 = /29
Alternatively, one /32 can be returned, then both remaining /32s can be extended to a /30.
When we were preparing the policy change proposal we did not read that word *total* through the "multiple LIR/32" eyes and I feel that we should somehow correct this.
New suggested text would be:
"LIRs that hold one or more IPv6 allocations are able to request extension of *each* these allocations up to a /29 without providing further documentation."
With this email I would like to check if community thinks we should go that route and draft the policy change proposal?
Is this something that nobody cares and should not be fixed? Is this a threat to someone? Anyone sees any danger in going forward with this small change?
Thank you very much, Jan Zorz
-- ************************************************************ Raymond Jetten Phone: +358 3 41024 139 Senior System Specialist Fax: +358 3 41024 199 Elisa Oyj / Network Management Mobile: +358 45 6700 139 Hermiankatu 3A raymond.jetten@elisa.fi FIN-33720, TAMPERE http://www.elisa.fi ************************************************************
* Jan Zorz @ go6.si
We encountered LIRs that are operators and in the past they bought other small operators and joined for example 3 LIRs under one and now they have 3 x /32 (of course with that /29 as reserved space).
When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy.
I assume you mean "that LIR" (i.e., the single consolidated LIR) here? As I understand it, if the three LIRs had individually requested their /29 extension *before* being merged into one single LIR, they would have gotten them, and I don't believe that they would have had to give two of them back after the merger either. So they accidentally painted themselves into a policy corner by doing things in the wrong order. I would be happy to support such a proposal on the grounds that the order of things should not matter in this way. -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com
On 11/8/12 8:43 AM, Tore Anderson wrote:
* Jan Zorz @ go6.si
We encountered LIRs that are operators and in the past they bought other small operators and joined for example 3 LIRs under one and now they have 3 x /32 (of course with that /29 as reserved space).
When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy.
I assume you mean "that LIR" (i.e., the single consolidated LIR) here?
Tore, hi Well, there are probably many consolidated LIRs here. I personally know of few of them. Nick showed some numbers (thnx) - but I would suggest to ask RIPE-NCC staff for the "consolidated-LIRs-with-multiple-/32" numbers - what is this number we are talking about.
As I understand it, if the three LIRs had individually requested their /29 extension *before* being merged into one single LIR, they would have gotten them, and I don't believe that they would have had to give two of them back after the merger either. So they accidentally painted themselves into a policy corner by doing things in the wrong order.
I would be happy to support such a proposal on the grounds that the order of things should not matter in this way.
Good point, agree. We ran into small procedural inconvenience that should be fixed imho. Cheers, Jan
Hi all, Although it may not affect so many LIRs, it has to be fixed Otherwise the reserved and not allocated space between the initial /32 and the /29 will be wasted, since no one will be eligible to claim it. I agree too. George On Thu, Nov 8, 2012 at 11:10 AM, Jan Zorz @ go6.si <jan@go6.si> wrote:
On 11/8/12 8:43 AM, Tore Anderson wrote:
* Jan Zorz @ go6.si
We encountered LIRs that are operators and in the past they bought other
small operators and joined for example 3 LIRs under one and now they have 3 x /32 (of course with that /29 as reserved space).
When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy.
I assume you mean "that LIR" (i.e., the single consolidated LIR) here?
Tore, hi
Well, there are probably many consolidated LIRs here. I personally know of few of them. Nick showed some numbers (thnx) - but I would suggest to ask RIPE-NCC staff for the "consolidated-LIRs-with-**multiple-/32" numbers - what is this number we are talking about.
As I understand it, if the three LIRs had individually requested their /29 extension *before* being merged into one single LIR, they would have gotten them, and I don't believe that they would have had to give two of them back after the merger either. So they accidentally painted themselves into a policy corner by doing things in the wrong order.
I would be happy to support such a proposal on the grounds that the order of things should not matter in this way.
Good point, agree. We ran into small procedural inconvenience that should be fixed imho.
Cheers, Jan
Hi Jan, On 11/8/12 10:10 AM, Jan Zorz @ go6.si wrote:
On 11/8/12 8:43 AM, Tore Anderson wrote:
* Jan Zorz @ go6.si
We encountered LIRs that are operators and in the past they bought other small operators and joined for example 3 LIRs under one and now they have 3 x /32 (of course with that /29 as reserved space).
When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy.
I assume you mean "that LIR" (i.e., the single consolidated LIR) here?
Tore, hi
Well, there are probably many consolidated LIRs here. I personally know of few of them. Nick showed some numbers (thnx) - but I would suggest to ask RIPE-NCC staff for the "consolidated-LIRs-with-multiple-/32" numbers - what is this number we are talking about.
In total there are 64 LIRs with more than one IPv6 allocation. Of them, - 52 LIRs have 2 IPv6 allocations each, - 5 LIRs have 4 IPv6 allocations each, - 4 LIRs have 3 IPv6 allocations each, - 2 LIRs have 5 IPv6 allocations each, - 1 LIR has 10 IPv6 allocations. This data is also publicly available at: ftp://ftp.ripe.net/ripe/stats/membership/alloclist.txt Like has been mentioned on the mailing list, this is the result of mergers and acquisitions over time. I hope this helps Andrea Cima RIPE NCC
As I understand it, if the three LIRs had individually requested their /29 extension *before* being merged into one single LIR, they would have gotten them, and I don't believe that they would have had to give two of them back after the merger either. So they accidentally painted themselves into a policy corner by doing things in the wrong order.
I would be happy to support such a proposal on the grounds that the order of things should not matter in this way.
Good point, agree. We ran into small procedural inconvenience that should be fixed imho.
Cheers, Jan
On 11/9/12 11:35 AM, Andrea Cima wrote:
In total there are 64 LIRs with more than one IPv6 allocation.
Of them, - 52 LIRs have 2 IPv6 allocations each, - 5 LIRs have 4 IPv6 allocations each, - 4 LIRs have 3 IPv6 allocations each, - 2 LIRs have 5 IPv6 allocations each, - 1 LIR has 10 IPv6 allocations.
This data is also publicly available at: ftp://ftp.ripe.net/ripe/stats/membership/alloclist.txt
Like has been mentioned on the mailing list, this is the result of mergers and acquisitions over time.
Andrea, thank you for this info... So far I heard from this WG that we should fix this little issue. Any suggestion from the chairs? Cheers, Jan
Hi Jan,
Andrea, thank you for this info...
So far I heard from this WG that we should fix this little issue. Any suggestion from the chairs?
There seems to be support for this, and I haven't seen any objections. I think it's time for you to start writing a policy proposal text that we can discuss here. Emilio: can you contact Jan and help to get this started? Thanks! Sander
Hi Sander, I will contact Jan and help the process of creating a policy proposal. Thanks to all the WG for the participation in the mailing list and the clear feedback so far. Regards Emilio On 11/9/12 1:10 PM, Sander Steffann wrote:
Hi Jan,
Andrea, thank you for this info...
So far I heard from this WG that we should fix this little issue. Any suggestion from the chairs?
There seems to be support for this, and I haven't seen any objections. I think it's time for you to start writing a policy proposal text that we can discuss here. Emilio: can you contact Jan and help to get this started?
Thanks! Sander
Hi, On Wed, Nov 07, 2012 at 12:53:27PM +0100, Jan Zorz @ go6.si wrote:
When those LIRs asked for extension to /29 they received a response from IPRAs, that they can extend to /29 *in total* as written in the policy.
The policy says:
"LIRs that hold one or more IPv6 allocations are able to request extension of these allocations up to a *total* of a /29 without providing further documentation."
Actually, I think the IPRAs are reading something in there that has not been the intention by the WG (and it should be obvious from the discussions that it wasn't, because the case "what about a LIR that has more than one /32?" was never discussed) For non-native speakers (like me), the sentence above is perfectly fine to be interpreted as "... extensions of *any of these* allocations up to a total of /29..." and not "... up to a total of a /29 across all IPv6 stock the LIR has". We've been there with the "80% utilization" in IPv4, where the IPRA interpretation was more strict than what the WG intended, and it seems that this is another of these cases... Anyway, to give clear guidance to the NCC, I think having Jan and Emilio draft new text, have this be cross-checked by the NCC for interpretation leeway, and then formally accept it via the PDP, is the right way forward. Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
Am Fri, 9 Nov 2012 13:49:51 +0100 schrieb Gert Doering <gert@space.net>: ...
Actually, I think the IPRAs are reading something in there that has not been the intention by the WG (and it should be obvious from the discussions that it wasn't, because the case "what about a LIR that has more than one /32?" was never discussed)
For non-native speakers (like me), the sentence above is perfectly fine to be interpreted as "... extensions of *any of these* allocations up to a total of /29..." and not "... up to a total of a /29 across all IPv6 stock the LIR has".
From an old programmers paradigm "be liberate on what you receive and strict what you send" I would interpret the policy like the NCC (to be on the safe side). Under business and policy aspects, your reasoning absolutely makes sense to me. +1 for your suggestion. Andreas -- Andreas Schachtner afs Holding GmbH communication technologies & solutions http://afs-com.de/ Geschaeftsfuehrer Andreas Schachtner HRB 15448, Amtsgericht Dortmund
I support this proposal and as non-native speaker I would never have read it other than "you can extend all /32 you have". I think thats a perfect example of how careful one schould be reading/writing proposals, especial us non-native guys. Greetings Dan
participants (11)
-
Andrea Cima
-
Andreas Schachtner
-
Dan Luedtke
-
Emilio Madaio
-
George Giannousopoulos
-
Gert Doering
-
Jan Zorz @ go6.si
-
lir@elisa.fi
-
Nick Hilliard
-
Sander Steffann
-
Tore Anderson