[address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Previous message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrey Semenchuk
andrey at trifle.net
Thu Jun 27 13:50:41 CEST 2013
On 06/27/13 13:22, Gert Doering wrote: > Indeed. I want a light-weight process that can be implemented while > it's still relevant (aka "we still have 16 bit ASNs to worry about"). If ASN assigned by RIPE and used by the End User according with RIPE's policy - it's nothing to worry about. If ASN returned to the pool - it's nothing to worry about too: we can't worry about something that does not exists (ASN does not assigned). > The more heavyweight "full database consistency cross-check, including > references to AS numbers that are not from the RIPE region(!)" needs > to very carefully considered - if we make it too complicated to > register policy, people will just stop doing so, and what have we > gained then? And this part of your opinion I fully support - we shouldn't make any complicated solutions for the simple task: If the ASN assigned - the ASN holder may use it. If the ASN does not assigned (or was assigned but was returned to the pool) - any reference that violates this should be deleted. And it's not the RIPE or community problem -- Best wishes, Andrey Semenchuk Trifle Internet Service Provider (056) 731-99-11 www.trifle.net
- Previous message (by thread): [address-policy-wg] [db-wg] Guidance Requested: Reassigning Referenced ASNs
- Next message (by thread): [address-policy-wg] Guidance Requested: Reassigning Referenced ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]