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] New AS Number block allocated to the RIPE NCC
- Previous message (by thread): [routing-wg]Re: [address-policy-wg] New AS Number block allocated to the RIPE NCC
- Next message (by thread): [routing-wg]peering change on route-views.routeviews.org
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Tue Mar 10 11:00:22 CET 2009
> Weird... I thought the NCC was only allocating 32-bit AS numbers now. Globally the default is 32 bit, 16 bit on request. 32 bit only from next January. Statistics presented at the APNIC meeting a couple of weeks ago suggest that most of the actual assignments this year have fallen into the "on request" bucket. Reasons why are left as an exercise for the reader (or discussion on one of these lists). :) Rob
- Previous message (by thread): [routing-wg]Re: [address-policy-wg] New AS Number block allocated to the RIPE NCC
- Next message (by thread): [routing-wg]peering change on route-views.routeviews.org
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]