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] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Thu Feb 7 08:49:56 CET 2019
On Wed, 6 Feb 2019, Kai 'wusel' Siering wrote: (...) > I'd rather hand that /21 as two /22 to two new LIRs instead of eight /24 > to eight new LIRs, since a /24 is basically useless anyway. I really don't agree with the former. The spirit of 2019-02 is precisely that a /24 is the minimum usable allocation, mostly due to global routability. An ORG/LIR might get a second /24 if needed (through a new LIR account), but it needs to go back into the queue... (if there is any at some point). (...) > IIRC, billing discussions are out of scope for the APWG. Besides, billing is not per resource currently, is it? Here we are 200% in agreement :-) Cheers, Carlos > Regards, > -kai > > >
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]