Aleksi Thank you for the TREX document. It would certainly help traceback if all parties adopted locally administered MAC addresses like this. I encourage all IX's to consider this as at least a recommendation to members. Of course, the IX itself has visibility via its switches, but members do not see that information so easily. So this would be advice to members themselves for their own (mutual) benefit. It certainly has less overhead then creating additional databases. Regards Steve ------ Original Message ------ From: "Aleksi Suhonen" <ripe-ml-2015@ssd.axu.tm> To: "snash" <snash@arbor.net> Cc: connect-wg@ripe.net Sent: 10/09/2015 11:20:18 Subject: Re: [connect-wg] Programmatic way to answer, "Who is sending me this stuff?"
Hello,
On 09/09/2015 01:13 PM, snash wrote:
If I receive some traffic at an IXpeering router interface, I might want to know how I got it.
How do I find out who did send it to me? If I capture a sample packet I could see the source MAC address. Now I have to identify who owns the device with that MAC.
There is no unified method for doing what you want apart from the above that would work on all IXPs.
Some IXPs enforce a policy that their members have to use certain pre-determined MAC addresses. Here's an example: (scroll to bottom)
http://www.trex.fi/service/unicast.html
There are also some IXPs that use an SDN core where they are able to filter L2 traffic based on either IRR registered peering relationships or actual BGP negotiated routes. I remember seeing nice presentations about these at Euro-IX Fora, but I couldn't quickly find information about them in the wild.
Both of the above examples are rare and both have problems which hinder their real world adoption.
-- Aleksi Suhonen
() ascii ribbon campaign /\ support plain text e-mail