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]Idea about AS-usage on IXPs
- Previous message (by thread): [routing-wg]Idea about AS-usage on IXPs
- Next message (by thread): [routing-wg]Idea about AS-usage on IXPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Volodymyr Yakovenko
vovik at dumpty.org
Sun Dec 3 22:09:20 CET 2006
On Fri, Dec 01, 2006 at 02:18:40PM +0100, Kurt Kayser wrote: >Hi Randy, > >Randy Bush wrote: >>>Is inter-IXP-traffic really typical/necessary? >> >>>from a router on IX A, i want a nice clean traceroute to a router on IX >>B, and only have access to that IX via my friend's network on IX A. > >If the router is not an IXP-owned router, each participating router is in a >"normal" AS. > >But I might be really wrong in order to save a couple of 2-Byte AS-numbers, >but somehow I have the feeling that 2-Byte space is out much faster that >anticipated. >So how far are we in globally reachable 4-Byte AS-numbers yet? (different >topic). According to RIPE-389 (http://www.ripe.net/docs/asn-assignment.html#19): 1.9 4-Byte AS Numbers RIPE NCC will assign 4-Byte AS Numbers according to the following timeline: * From 1 January 2007 the RIPE NCC will process applications that specifically request 4-byte only AS Numbers and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 4-byte only AS Number, a 2-byte only AS Number will be assigned by the RIPE NCC. * From 1 January 2009 the RIPE NCC will process applications that specifically request 2-byte only AS Numbers and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 2-byte only AS Number, a 4-byte only AS Number will be assigned by the RIPE NCC. * From 1 January 2010 the RIPE NCC will cease to make any distinction between 2-byte only AS Numbers and 4-byte only AS Numbers, and will operate AS Number assignments from an undifferentiated 4- byte AS Number allocation pool. Terminology "2-byte only AS Numbers" refers to AS Numbers in the range 0 - 65535 "4-byte only AS Numbers" refers to AS Numbers in the range 1.0 - 65535.65535 (decimal range 65,536 - 4,294,967,295) "4-byte AS Numbers" refers to AS Numbers in the range 0.0 - 65535.65535 (decimal range 0 - 4,294,967,295) -- Regards, Volodymyr.
- Previous message (by thread): [routing-wg]Idea about AS-usage on IXPs
- Next message (by thread): [routing-wg]Idea about AS-usage on IXPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]