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] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Previous message (by thread): [address-policy-wg] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Next message (by thread): [address-policy-wg] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Wed Nov 29 17:35:39 CET 2023
Hi Tore, > On 29 Nov 2023, at 13:33, Tore Anderson <tore at fud.no> wrote: > ... > > (I also suggest that while the NCC is at it, they should document > assignment-size as being a CIDR prefix length for inet6num as well. As > you point the formal definition is not crystal clear there either, > which was a bit of a surprise to me, honestly. But all current inet6num > objects have an assignment-size within the range 31-128, so I guess > LIRs simply get it - unless the database software enforces it by > rejecting updates with values above 128.) > > Tore > I confirm that the verbose help text for "assignment-size:" currently states: assignment-size Specifies the size of blocks assigned to end users from this aggregated inet6num assignment. Specifies a numeric value. We will update the text to include CIDR prefix length for inet6num. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [address-policy-wg] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Next message (by thread): [address-policy-wg] 2023-04 Review Phase (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]