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]/
[routing-wg]Representation of four byte AS numbers.
- Previous message (by thread): [routing-wg]Representation of four byte AS numbers.
- Next message (by thread): [routing-wg]Representation of four byte AS numbers.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Mon Oct 20 15:36:39 CEST 2008
Hi Wilfried, > But... Just as a reminder or marker - who or which group is expected > to update the (relevant) tools these days? And, do we have an common > understanding of the term "relevant" in this context? :-) I'm not sure, what do you think of as the relevant tools? :-) I assume the RIPE NCC will update the database software and associated documentation to adhere to whichever standards develop. IRRToolset is moving to a more open development platform, which we will also have a presentation on during the Routing WG session. I'm sure patches for this will be more than welcome from whoever wishes to contribute them (such is the open source model). Other tools, such as 'irrd' are probably out of the scope of the RIPE working groups, but the maintainers of those utilities presumably keep up with developments in the standardisation bodies. I don't think the RPSL/RPSL-NG specifications specify the range of valid AS numbers, just the format of AS<number>. ...but perhaps I'm misunderstanding the question... All the best, Rob
- Previous message (by thread): [routing-wg]Representation of four byte AS numbers.
- Next message (by thread): [routing-wg]Representation of four byte AS numbers.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]