On Mon, 17 May 2004, Kurt Erik Lindqvist wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On 2004-05-11, at 23.55, Dean Anderson wrote: > > > On Tue, 11 May 2004, Joe Abley wrote: > > > >> For the benefit of less-operational people here who don't see humour > >> in this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay > >> Area. > > > > This block is assigned to EP.NET. > > I work for an IXP. Are you trying to say that that means that all > traffic that passes an IXP means that I am the upstream for that > traffic? It doesn't work this way. It certainly does when you've assigned them IP addresses. But, I do find it rather funny that some (very few) people running exchange points (which are the simplest of ISPs) don't think they provide transit services. For the less technical, an exchange point is a place that provides rack space and a Local Area Network of some sort (think ethernet, but ethernet has long been replaced by faster technologies). Other people (usually ISPs, but not always) come in to an exchange point and establish BGP peering sessions with other exchange point customers. Sometimes this is over the LAN provided by the exchange point, sometimes they pull their own cable between their racks. The only thing that is different is that an exchange point doesn't need to have it's own AS number, nor does it need to run BGP. The lack of a BGP session doesn't have any impact on whether there is a relationship with the customers of the exchange point, nor on whether traffic is transited by an exchange point. When customers pull their own cable, one can't necessarilly tell that those customers connected at an exchange point. That type of connection is totally private. But LAN connections provided by the exchange point and assigned IP addresses are just regular network connections, subject to the rules and AUP of the service provider (exchange point). An exchange point is expected to behave just like other ISPs with respect to abuse and AUPs. Most exchange points do have AUPs, and most do handle abuse by their customers. --Dean _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf