On Friday, January 27, 2012 02:30:35 AM Keegan Holley wrote:

> I agree... I think. MPLS has a better forwarding paradigm
> and the IGP only core of P routers is a plus.

Well, I'm not so sure MPLS has a better forwarding paradigm 
per se. If you're talking about raw forwarding performance, 
hardware forwarding these days makes that a non-issue, but 
you already knew that :-).

We like running it for Internet traffic because we can 
remove BGP (for v4) from the core. That's all.

On the application side, we like running it because we can 
offer those "cool" services like IPTv, l2vpn and them.

> Why not FRR everything? The control plane hit is
> negligable even if your internet users wouldn't notice,
> care about, or even understand the improvements.

We have a large-ish network, particularly in the Access 
(lots of Metro-E switches that are IP/MPLS-aware). Trying to 
run RSVP everywhere isn't feasible, when your customers are 
demanding lower and lower prices.

Given the amount of effort required for this, we relegate 
RSVP-TE to:

        o Multicast for IPTv services (we'll be using mLDP
          for data-based Multicast services). We run FRR
          here too.

        o Unequal cost routing within the core, so we don't
          have idle links when others are full. Keeping it
          in the core only reduces state.

        o Specific requests from customers who want their
          traffic to take a specific path, or failover
          within a very short time (note I don't say 50ms).
          This we charge expensively to discourage customers
          from buying it, as it's hectic to maintain, and
          overall, the differences in latency across several
          points in the country is very, very negligible.
          Moreover, we've found failover times for BFD + our
          tuned IS-IS to be reasonable for most 
          applications.


All RSVP instances run Refresh Reduction for scaling, even 
if state is relatively low due to the above.

Cheers,

Mark.

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to