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]/
[db-wg] blocking '23456' as value for the origin attribubte in route/route6 objects?
- Previous message (by thread): [db-wg] blocking '23456' as value for the origin attribubte in route/route6 objects?
- Next message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Wed Jul 7 23:27:53 CEST 2021
Cynthia Revström via db-wg wrote on 07/07/2021 15:44: > I think that AS23456 should be excluded as I can't think of any good > reason for having such a route object and seemingly no one else either > as there are none currently. at one point years ago, before asn32s-capable software was widely available, it occasionally made sense to encode AS23456 in various objects. These days, there is no reason for it, and it would be better if AS23456 didn't appear in IRR objects. This brings up Niall's point about making sure that objects like this can't reappear if they're deleted. Nick
- Previous message (by thread): [db-wg] blocking '23456' as value for the origin attribubte in route/route6 objects?
- Next message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]