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] [Moderated]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Hessler
phessler at theapt.org
Wed Nov 29 16:59:45 CET 2023
On 2023 Nov 29 (Wed) at 16:41:14 +0100 (+0100), Gert Doering wrote: :Hi, : :On Wed, Nov 29, 2023 at 12:28:04PM +0100, Peter Hessler wrote: :> I propose that we define this to be a CIDR assignment and they put in :> the number of bits of the netmask, so the above example would be :> assignment-size of /32. : :Seconded. Well spotted. : :Maybe even make the syntax require the "/", at all times, so it's visually :clear right away. "This is a /32, not a 32 which might be either" : :gert I don't mind requiring a "/", but I very much want it to stay in sync with the IPv6 syntax. If we add this to the IPv4 implementation for parity, we shouldn't change it to take it out of parity. :) -peter -- Overdrawn? But I still have checks left!
- 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] [Moderated]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]