[171530] in North American Network Operators' Group
Re: Best practices IPv4/IPv6 BGP (dual stack)
daemon@ATHENA.MIT.EDU (Mark Tinka)
Sun May 4 17:44:53 2014
X-Original-To: nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
To: nanog@nanog.org
Date: Sun, 4 May 2014 23:41:00 +0200
In-Reply-To: <61DC6BC4ABA10E4489D4A73EBABAC18B011E9A3F@EX01.swan.local>
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces@nanog.org
--nextPart2675410.lTB9N9z8X0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
On Saturday, May 03, 2014 07:24:24 PM Vitkovsk=FD Adam wrote:
> Sure it's a different transport protocol altogether,
> anyways It's interesting to see how everybody tends to
> separate the IPv4 and IPv6 AFs onto a different TCP
> sessions and still run the plethora of other AFs on the
> common v4 TCP session, maybe apart from couple of the
> big folks, who can afford running separate control-plane
> and edge infrastructure for some of the AFs, IPv6 AF
> being the first ran separately.
We run separate AF's for each family-type, i.e., IPv4=20
separate from IPv6, separate from VPNv4 separate from BGP-
based VPLS, e.t.c.
Mark.
--nextPart2675410.lTB9N9z8X0
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJTZrPsAAoJEGcZuYTeKm+GzWoQAMOjTJ0eOhBGBf3XQvgpSWWC
CGMl+2CHBTOi9fiC76VYlQem5sj81+odIMn1x0oXZWU+YtvgF0wTMekcchH9b5Wr
zgcA9OhDdfFWPAJw0ohc6zy8VQ+BbhlRpzZmza1FMvY2ulj5XCui0DMdLyoWBMoS
R5XHM7SDtgZBfnq3R2WuUm9uHqfptfFIez2jff6bMF5UZ1hOG56Z+fIVyHj3UdQV
+WSg2wgMbJWNi8zoQUe2/9xrMUqsagCrMi3NOSPQ3YMoLYzmoZvj5G0p3KpGZVWb
wHyDy1psea2cYrMcNlBbI5gA4+Oj6D4VjE1naBiUCB9kBy8t7R1U1Gp1WnU2QvwV
YNFFGKjG6zGn9PcxsC/TtPeqPgdb97i/BwqV9PKe/2NvIete7a6E30tRO6XA0R+s
DzHb5muqF29xAOdRduW6R2KQr+scCoxdi8f9MRS8ye6zCImeUtDSjPZP+b+V8zrB
6QvvBaUc0b9xlwjWvorIGjt4A2oy9n+PxF8NExPH8tgaI169ltFva2A0K4avH9Rw
NmuYbaazWjpdnbPcpN8E+WtKrJmAwIgQs9sAiXVhNmY9QJLjDMQkXQtWCUXeLaIg
9Xy1xEt4lGZSBGFB5OWOcBsw+lBVkzA3rdMTH7MfSnFP2Ko7WtWKvVTIwKbO64bh
ve0yP577NgoRd8V+ocSy
=wuQ5
-----END PGP SIGNATURE-----
--nextPart2675410.lTB9N9z8X0--
