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] 2014-03 two cents on multi homing ASN requirement
- Previous message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Saku Ytti
saku at ytti.fi
Sat Aug 16 19:53:16 CEST 2014
On 16 August 2014 20:45, Nick Hilliard <nick at inex.ie> wrote: > It would be better to bring this up as an agenda item at the next NCC GM > and get this problem fixed rather than putting conditionals into the policy. > >> 2) We limited the number of AS Number assignments per LIR to one >> thousand. > > Please let's not create policy by application of comfortingly round numbers. I agree, the policy is (and should) be simple and without contrived complexity to fix real issue in wrong place. The abuse potential is in current policy as well. so it should not factor in here either, they can be tackled separately, but I definitely support tackling the problem. It is such a simple, elegant and obvious way to manage finite resources, put non-zero cost to them. It fixes other complex problems as well, not just arbitrary policy abuse. -- ++ytti
- Previous message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]