To give some context:
Only 14 LIRs have more than 50 /29 allocations (see
https://labs.ripe.net/author/marco_schmidt/ipv6-stockpiling-a-trojan-horse-in-our-midst/)
About 100 LIRs have more than 10 /29 allocations, and around 1,000 have
more than 2 allocations.
I don't see a major issue with allowing LIRs with two allocations to
extend both to a /28 (assuming the allocations were made after 2006, as
earlier allocations may not be contiguous).
With RIPE NCC enforcing stricter rules on organizations with multiple
LIRs ,particularly preventing additional /29 requests when existing
allocations aren't announced, the stockpiling problem should not worsen.
The core intent of this "Only one LIR can get /28" rule is to prevent
the top 100 "stockpilers" from getting a /28 instead of a /29.
To be clear, I support the rule of limiting each LIR or organization to
one /28 extension. However, we should also consider that all those /29s
that are reserved will remain unusable because they are blocked.
regards,
Rinse Kloek
On 15-10-2024 18:44, Tobias Fiebig via address-policy-wg wrote:
I think per LIR would already suffice to deal with the 100s of /29s
issue; Per organization might even be better.
On Tue, 2024-10-15 at 13:31 +0200, jordi.palet--- via address-policy-wg
wrote:
The point may be a single extension to /28 for each original
allocation per organization instead of per LIR?
Regards,
Jordi
@jordipalet
El 14 oct 2024, a las 20:02, Tobias Fiebig via address-policy-wg
<[email protected]> escribió:
Moin,
Anyway, I understood from Marco presentation in the previous
meeting,
that this is being already managed assuming that in those cases,
you
need to justify the need, which is not the case for the initial
allocation. Happy to be corrected here and to incorporate some
text
for that if needed in our follow up proposal.
My understanding is that a /29 transferred prior to the more strict
handling by the NCC still remains an "IPv6 allocation originally
issued
directly by the RIPE NCC" after having been transferred. This means
that several organizations holding 100+ /29s might expand these.
On the other hand, my /29 would not qualify, as I originally
received a
/32 and then expanded the initial allocation to a /29 under current
policy.
It would be good if Marco could weigh in on that.
I would argue that it would make more sense to phrase this as 'one
/29
-> /28 per LIR once', using a mechanic similar to the one discussed
in
the PI proposal 2024-1, i.e., a needs reevaluation upon
transfer/enlargement combined with a single /28 being the maximum
no-
justification size per LIR, or limiting the maximum allocation
without
justification to a /28 (i.e., if you have two(+) /29, you can hand
one
(or the others except for one) back and get the other one expanded
to a
/28 without justification.
With best regards,
Tobias
-----
To unsubscribe from this mailing list or change your subscription
options, please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an
account with the email matching your subscription before you can
change your settings.
More details at:
https://www.ripe.net/membership/mail/mailman-3-migration/
**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company
This electronic message contains information which may be privileged
or confidential. The information is intended to be for the exclusive
use of the individual(s) named above and further non-explicilty
authorized disclosure, copying, distribution or use of the contents
of this information, even if partially, including attached files, is
strictly prohibited and will be considered a criminal offense. If you
are not the intended recipient be aware that any disclosure, copying,
distribution or use of the contents of this information, even if
partially, including attached files, is strictly prohibited, will be
considered a criminal offense, so you must reply to the original
sender to inform about this communication and delete it.
-----
To unsubscribe from this mailing list or change your subscription
options, please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account
with the email matching your subscription before you can change your
settings.
More details at:
https://www.ripe.net/membership/mail/mailman-3-migration/
-----
To unsubscribe from this mailing list or change your subscription options,
please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
