[c-nsp] 6PE FIB usage on 6500/7600

[Mark Tinka]

On Thursday, January 02, 2014 02:19:55 PM Phil Mayers wrote:
 
> Sure; SR looks like a more natural fit for MPLS than LDP
> ever was in hindsight. That said, it looks better for
> IS-IS users than OSPF, due to needing OSPF & OSPFv3 or
> OSPFv3 dual-AF which is not well supported.

OSPFv3 is much more scalable than OSPFv2.

IMHO, OSPFv3 should have been designed to support IPv4 
without needing an IPv6 link layer, simply because it scales 
as well as IS-IS in terms of feature set expansions. But 
that's just me.

That said, when OSPFv3 becomes more mainstream (because IPv6 
will be more prevalent than it is today), I'm not sure 
whether it will be more useful for all vendors to support 
the IPv4 address family for OSPFv3, given that some may see 
IPv4 as a protocol on its way out (although I would support 
vendors looking to collapse both address families into 
OSPFv3, like IS-IS does).

Or, this may make the case for some who want to migrate to 
IS-IS for this particular reason. Then again, if OSPFv3 is 
upgraded as I mention above, then there really only might be 
just one major difference between both IGP's - the fact that 
one has an Area 0 restriction and the other doesn't (for 
those that feel the differences between them still matter). 

> Obviously people will have to move their vpnv6 BGP AFs to
> their IPv6 BGP RR sessions, which is a bit of a drag,
> but that's what peer templates are for (on sensible
> OSes).

My otherwise uninformed guess is that folk who have deployed 
6PE or 6VPE today will be less inclined to migrate to native 
MPLSv6 unless they are running into some resource issue 
brought on by 6PE or 6VPE, and it's cheaper to turn on 
MPLSv6 than to buy more resources.

I'll keep everything native, and will continue to carry 
BGPv6 in my core until I can safely remove it a la BGPv4 
with an IPv6-signaled MPLS.

Cheers,

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: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20140102/7214dafd/attachment.sig>