[181014] in North American Network Operators' Group
Re: Enterprise network as an ISP with a single huge customer
daemon@ATHENA.MIT.EDU (=?utf-8?B?TcOlbnM=?= Nilsson)
Sat Jun 13 19:18:10 2015
X-Original-To: nanog@nanog.org
Date: Sun, 14 Jun 2015 01:17:58 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Stepan Kucherenko <twh@megagroup.ru>
In-Reply-To: <557B120D.9000904@megagroup.ru>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
--Cy+5HEalSgyXkpVS
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Enterprise network as an ISP with a single huge customer Date: Fri=
, Jun 12, 2015 at 08:08:29PM +0300 Quoting Stepan Kucherenko (twh@megagroup=
=2Eru):
> Hello,
>=20
> I'm sure lots of you work for big enterprises, and some of you work
> for biggest of them.
>=20
> How many of you architect your network as an ISP, with that
> enterprise as the biggest customer ? Office networks in l3vpn,
> VPLS/EVPN on top of your own network for DCI, etc ? Or is it usually
> just a single IGP domain with no unnecessary bells and whistles ?
We do at $dayjob (public service radio station network). We try to stay
away from the TE side of MPLS, but the other knobs are in pretty much use.
A lot of our newer uses for the network are realtime audio in
hi-fi quality. Latency is our enemy, and so we don't do TCP, we skip
retransmits, buffers to be able to wait for a late packet are so short
it rarely matters, etc. That means a lot of prioritisation being done. It
is easier in our "isp-type" network.
=20
As a very distributed company (in meatspace, but at the same time very
unified in infrastructure) we sure need the flexibility. Doing
this on usual VLAN/routing would not fly very well. A lot of the devices
we run aren't really fit for living with other networked devices,
especially those devices fondled by Users. We usually just push them in
another VRF.
=20
> Do you think one approach is better than the other ? If so, why ?
I'd love to have a single flat routing domain. But I do not think it
works with the kind of legacy stuff (some of it brand new...) we run.
> I understand that it usually comes down to specific circumstances
> and most likely scale but I'd still love to hear about your
> experience.
--=20
M=C3=A5ns Nilsson primary/secondary/besserwisser/machina
MN-1334-RIPE +46 705 989668
Concentrate on th'cute, li'l CARTOON GUYS! Remember the SERIAL
NUMBERS!! Follow the WHIPPLE AVE. EXIT!! Have a FREE PEPSI!! Turn
LEFT at th'HOLIDAY INN!! JOIN the CREDIT WORLD!! MAKE me an OFFER!!!
--Cy+5HEalSgyXkpVS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlV8uiYACgkQ02/pMZDM1cX4zwCeKGlTz1H2Hmvx+7AFdmI80a5d
AWUAni6pXyfrwaqnpqgYl8n5GdT/UrXC
=+7E+
-----END PGP SIGNATURE-----
--Cy+5HEalSgyXkpVS--
