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/[email protected]/
[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 ]
Maximilian Wilhelm
max at rfc2324.org
Fri Dec 15 15:32:45 CET 2023
Hi folks, Anno domini 2023 Peter Hessler scripsit: > I still support the proposal as-is. The proposed change does not > weaken any data that is in the database, and in fact may allow it to be > more obvious that these address ranges are used by end users rather than > be unclear what their status is. > > Furthermore, I will state that Denis' objections are not relevant to the > proposal. The proposers, various people on the lists (including myself), > and the RIPE NCC themselves all state the opposite of what Denis is > saying. In addition the proposers have, in my opinion, addressed the > concerns stated. +1 to what Peter said. Cheers, Max
- 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 ]