This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] IPv4 PA assignments policy change draft proposal
- Previous message (by thread): [address-policy-wg] IPv4 PA assignments policy change draft proposal
- Next message (by thread): [address-policy-wg] IPv4 PA assignments policy change draft proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Sun May 15 14:55:08 CEST 2022
Hi,
On Sun, May 15, 2022 at 01:55:33PM +0200, James Kennedy wrote:
> The DBTF didn't identify a need to change the policy for LIRs
> registering/documenting blocks of PA that they issue to third parties
> in the RIPE Database. But we did see the need to change the policy for
> LIR Infrastructure PA Assignments - some LIRs flood the Database with
> huge volumes of very small infrastructure PA Assignments that would be
> extremely difficult to keep up-to-date, and the TF recommends
> "limiting and discouraging the use of the RIPE Database as an
> enterprise IPAM solution".
This policy proposal would be the wrong vehicle to achieve any outcome
towards *that* account - assignment-to-self would still be possible, just
no more mandatory.
This sounds more like a task for the training department or for the ARCs
than for a policy change to me.
OTOH: from a database utilization perspective, why would "I put all of
my /22 in the DB in form of /29 and /30" be worse than "I use a /16
for customer assignments, /30../24, and register them all (as I MUST
do)"? The latter would be many times more objects...
Are we no longer aiming for accurate registration, because the DBTF finds
that too resource consuming? I'm not sure I understand that line of
argument.
(Especially if used as an enterprise IPAM - or, more likely, as a mirror
of the IPAM - accuracy is likely higher than if someone just manually puts
aggregates into the DB whenever he feels like it. No?)
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/address-policy-wg/attachments/20220515/18bdea13/attachment.sig>
- Previous message (by thread): [address-policy-wg] IPv4 PA assignments policy change draft proposal
- Next message (by thread): [address-policy-wg] IPv4 PA assignments policy change draft proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]