[188137] in North American Network Operators' Group
Re: Internet Exchanges supporting jumbo frames?
daemon@ATHENA.MIT.EDU (Nick Hilliard)
Wed Mar 9 17:22:10 2016
X-Original-To: nanog@nanog.org
X-Envelope-To: nanog@nanog.org
Date: Wed, 09 Mar 2016 22:21:43 +0000
From: Nick Hilliard <nick@foobar.org>
To: Saku Ytti <saku@ytti.fi>
In-Reply-To: <CAAeewD9FPg=tCVXW5C-_bMoD6g+CLRjQZVDsDr=R5vE1KOStUg@mail.gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Saku Ytti wrote:
> Member may puke L2 loop to IXP, you must have some channel to deal
> with your customers.
First, mac filters. Second, if someone l2 loops and it causes problems
because of hardware failure on our side, we reserve the right to pull
connectivity:
https://www.inex.ie/technical/maintenance
> In the case of emergencies, INEX reserves the right to perform
> critical maintenance on a 24x7x365 basis without prior notification
> to INEX members. Emergencies are defined as situations where:
[...]
> - member port misconfiguration or hardware/software bug causes loss of
> service or down-time for other INEX members, in the potential
> situation where this is not prevented by INEX port security measures
Fortunately, it's only rarely that this happens.
Third, someone puking an l2 loop to the IXP is a problem which may
affect the ixp infrastructure. This is not the case when people muck up
their MTU config. There is a demarcation line here: one is an IXP
problem; the other is not.
Nick
