Best practices IPv4/IPv6 BGP (dual stack)

Mark Tinka mark.tinka at seacom.mu
Sun May 4 21:41:00 UTC 2014


On Saturday, May 03, 2014 07:24:24 PM Vitkovsk√Ĺ 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 
separate from IPv6, separate from VPNv4 separate from BGP-
based VPLS, e.t.c.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140504/7d85ba6e/attachment.pgp>


More information about the NANOG mailing list