Internet Exchange Point(IXP) questions
Michael K. Smith - Adhost
mksmith at adhost.com
Fri Feb 18 12:43:29 CST 2011
Michael K. Smith - CISSP, GSEC, GISP
Chief Technical Officer - Adhost Internet LLC mksmith at adhost.com
w: +1 (206) 404-9500 f: +1 (206) 404-9050
PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)
From: Yaoqing(Joey) Liu [mailto:joey.liuyq at gmail.com]
Sent: Thursday, February 17, 2011 7:04 PM
To: Michael K. Smith - Adhost
Cc: nanog at nanog.org
Subject: Re: Internet Exchange Point(IXP) questions
On Thu, Feb 17, 2011 at 8:17 PM, Michael K. Smith - Adhost <mksmith at adhost.com> wrote:
> -----Original Message-----
> From: Yaoqing(Joey) Liu [mailto:joey.liuyq at gmail.com]
> Sent: Thursday, February 17, 2011 6:03 PM
> To: nanog at nanog.org
> Subject: Internet Exchange Point(IXP) questions
> I'm doing some research on multiple origin AS problems of IXPs. As I know,
> generally there are two types of IXPs
> type 1: use exchange routers, which works in layer 3
> type 2: use switches and Ethernet topology, which works in layer 2.
> So I have a couple of qustions:
> 1. For type 1, the exchange routers may use several IP prefixes for routing,
> how often does the IP prefixes have their own AS?
> 2. For type 2, all peers connected to the IXP must work in the same subnet
> required by Ethernet rules. Is possible that the subnet IP prefixes belong
> to some private IP address space, such as 192.168.x.x? How often does this
> happen? If the subnet only contains public IP addresses, how are the
> addresses announced?
>On the Seattle Internet Exchange (SIX) we have ARIN-assigned addresses that we use on the Layer 2 fabric (your type 2 above). Hopefully the addresses aren't being announced at all, although >we sometimes have to chase down people that announce it. Those addresses aren't the destination for any traffic, they are merely part of the transport to a destination, so there is no need for >them to be in the DFZ.
>But I just checked the IXP prefix list, and found SIX owns prefix 126.96.36.199/23. And it has been announced by three ASNs, AS11537(Internet 2), AS3130(RGnet, LLC) and AS25973(Mzima >Networks, Inc). I'm not sure if my info is correct. Does SIX own its own ASN other than the three above?
Sorry for the misfire on my last email. The 188.8.131.52/23 network is assigned to the SIX from ARIN. In general, we don't want people to announce that space to the DFZ, so the three providers listed above are not filtering their announcements properly. It is, as others have said, a good idea to announce the exchange block to your customers, but not out to the DFZ.
More information about the NANOG