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]Re: [address-policy-wg] 2008-09 New Policy Proposal (ASPLAIN Format for the Registration of 4-byte ASNs)
- Previous message (by thread): [routing-wg]Re: [address-policy-wg] 2008-09 New Policy Proposal (ASPLAIN Format for the Registration of 4-byte ASNs)
- Next message (by thread): [routing-wg]Re: [address-policy-wg] 2008-09 New Policy Proposal (ASPLAIN Format for the Registration of 4-byte ASNs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
internetplumber at gmail.com
Mon Oct 20 17:43:37 CEST 2008
Hi Nick, > - "ASDOT is more easily remembered" > > For the foreseeable future, after the first 10k assignments of ASN32s in a > particular 16 bit ASN block range (e.g. AS3.x), both ASDOT and ASPLAIN > formats will be represented using similar numbers of digits. I agree, both with your sentiment and the proposal, but the "more easily remembered" tag is a bit more than irrelevant. Whilst the low-order 16 bits might not be memorable, it might be quite easy to keep up with which registries have used which upper 16 bits for a little while, so manual 'whois' queries can be directed to the appropriate server. Cheers, Rob
- Previous message (by thread): [routing-wg]Re: [address-policy-wg] 2008-09 New Policy Proposal (ASPLAIN Format for the Registration of 4-byte ASNs)
- Next message (by thread): [routing-wg]Re: [address-policy-wg] 2008-09 New Policy Proposal (ASPLAIN Format for the Registration of 4-byte ASNs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]