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]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 ]
Garry Glendown
garry at nethinks.com
Mon Oct 20 20:47:38 CEST 2008
Rob Evans wrote: > > 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. > Why would _YOU_ worry about memorizing which RIR to forward a query to? I thought that's what we have computers & programs for ;) I also agree with the proposal; amongst other things, AS regex would be a nightmare with different representation (except maybe automagically converting all 16 Bit AS to 0.x format) -garry
- 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 ]