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 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Previous message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Next message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Hessler
phessler at theapt.org
Mon Sep 11 19:28:25 CEST 2023
On 2023 Sep 11 (Mon) at 19:14:05 +0200 (+0200), denis walker wrote: :On Mon, 11 Sept 2023 at 18:33, Peter Hessler <phessler at theapt.org> wrote: :> :> On 2023 Sep 11 (Mon) at 16:09:58 +0000 (+0000), Brian Storey wrote: :> :Does this not contradict other purposes / objectives of the registry, including the principles of registering public networks or am I missing something? :> : :> :> This behaves the same as the IPv6 version, which has not had this :> problem yet. : :Maybe because IPv4 is still dominant for networks... : That should not be a blocker for this policy. And if a solution is needed/found, then it should be in a different policy that fixes it for both. -- Just remember: when you go to court, you are trusting your fate to twelve people that weren't smart enough to get out of jury duty!
- Previous message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Next message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]