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] IXP pool lower boundary of assignments
- Previous message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
- Next message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Thu Oct 27 16:23:20 CEST 2022
Hi, > Marco pointed out in the WG session, that we should probably start a discussion on the lower boundary of assignments from the IXP pool. I would like to kick off this discussion with this post. To add to this discussion: I took this to the Connect WG, and the initial feedback I got from there is that they have no problem with reevaluating this every 8 or so years (what seems to be the current rate of use of the IXP pool), and that they would be perfectly happy with not doing anything right now and reevaluating this in 2027 or so. This will be taken to the Connect WG mailing list, so let's keep an eye on that to see whether action is necessary at all. Cheers! Sander
- Previous message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
- Next message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]