[137665] in North American Network Operators' Group
RE: Internet Exchange Point(IXP) questions
daemon@ATHENA.MIT.EDU (Michael K. Smith - Adhost)
Thu Feb 17 21:17:57 2011
From: "Michael K. Smith - Adhost" <mksmith@adhost.com>
To: "Yaoqing(Joey) Liu" <joey.liuyq@gmail.com>, "nanog@nanog.org"
<nanog@nanog.org>
Date: Fri, 18 Feb 2011 02:17:48 +0000
In-Reply-To: <AANLkTi==qXjvwJf+WNBJNwOVBhF30bZOi+k75mmtqb1H@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> -----Original Message-----
> From: Yaoqing(Joey) Liu [mailto:joey.liuyq@gmail.com]
> Sent: Thursday, February 17, 2011 6:03 PM
> To: nanog@nanog.org
> Subject: Internet Exchange Point(IXP) questions
>=20
> 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 routi=
ng,
> 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 subne=
t
> required by Ethernet rules. Is possible that the subnet IP prefixes belon=
g
> to some private IP address space, such as 192.168.x.x? How often does thi=
s
> happen? If the subnet only contains public IP addresses, how are the
> addresses announced?
>=20
> Thanks,
> Yaoqing
Hello:
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 pe=
ople that announce it. Those addresses aren't the destination for any traf=
fic, they are merely part of the transport to a destination, so there is no=
need for them to be in the DFZ.
Regards,
Mike
--
Michael K. Smith - CISSP, GSEC, GISP
Chief Technical Officer - Adhost Internet LLC mksmith@adhost.com
w: +1 (206) 404-9500 f: +1 (206) 404-9050
PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)
