[188230] in North American Network Operators' Group
Re: Internet Exchanges supporting jumbo frames?
daemon@ATHENA.MIT.EDU (Kurt Erik Lindqvist)
Sat Mar 12 14:19:56 2016
X-Original-To: nanog@nanog.org
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <alpine.DEB.2.02.1603092212580.31096@uplift.swm.pp.se>
Date: Thu, 10 Mar 2016 09:33:00 +0000
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--Apple-Mail=_250F6DF1-3D55-4168-B5E2-21B9DD77CB60
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On 9 Mar 2016, at 21:17, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>=20
> On Wed, 9 Mar 2016, Nick Hilliard wrote:
>=20
>> Many IXPs have either looked at or attempted to build jumbo peering =
lans. You can see how well they worked out by looking at the number of =
successful deployments. The reason for this tiny number isn't due to =
lack of effort on the part of the ixp operators.
>=20
> I believe all IXP operators should offer higher MTU vlans, so that the =
ISPs who are interested can use them. If individual ISPs are not =
interested, then they don't have to use it. It's available if they gain =
interest.
In my experience many (most) IXP members don=E2=80=99t want multiple =
VLANs as default as that drives up operational complexity. I am not =
saying they are right, I am just saying that is reality.
> The whole point of an IX is to be a market place where interested =
parties can talk to each other. The IXP should not limit (to reasonable =
extent) what services the ISPs can run across the infrastructure. If two =
ISPs need higher than 1500 MTU between them, then forcing them to =
connect outside of the IXP L2 infrastructure doesn't make any sense to =
me, when it's fairly easy for the IXP to offer this service.
Most IXPs offers private VLANs and I assume these can support any MTU =
size you want.
Best Regards,
- kurtis -
--Apple-Mail=_250F6DF1-3D55-4168-B5E2-21B9DD77CB60
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iEYEARECAAYFAlbhP1AACgkQAFdZ6xrc/t4nugCcD4jfitZ76K0jfC9qu3khJdt/
w7AAoIgjWcrEyCp+DJcaRo8phnD+4JId
=+WY2
-----END PGP SIGNATURE-----
--Apple-Mail=_250F6DF1-3D55-4168-B5E2-21B9DD77CB60--
