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/routing-wg@ripe.net/
[routing-wg]Four byte ASN notation
- Previous message (by thread): [routing-wg]Four byte ASN notation
- Next message (by thread): [routing-wg]Four byte ASN notation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Fri Dec 7 17:00:38 CET 2007
> *Now* folks need to get their tools and software adapted - and they need > to know what format to code for. For what it is worth, I agree with Gert. I can see a strong argument for storing the ASNs as an unsigned 32 bit number internally, but the user-interface and education needs to start happening now before the larger ASNs become routine. We only have just over a year until 32 bit ASNs are the default for RIR assignments. "asdot" is becoming the default, and one of the reasons for having the discussion in October was that if there was a strong desire for another representation, operators would have to express that before asdot became a fait accomplis. I was, and am, aware of George Michaelson's draft, which is why I used the terminology from it when I summed up what I felt the feeling in the room was. Cheers, Rob
- Previous message (by thread): [routing-wg]Four byte ASN notation
- Next message (by thread): [routing-wg]Four byte ASN notation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]