Re: OT was Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sunday, January 12, 2014 08:37:16 PM Curtis Villamizar 
wrote:

> Perhaps if you actully worked for a company that made
> line cards you would not make the above statement.

I work for an operator that pays real money to deploy and 
use those line cards, and I make it my business to know what 
I'm paying for.

> Many of the big router vendors use the same TCAM hardware
> for MPLS lookups as they do for IP lookups.  Doing the
> lookup is not the rate limiting factor even in hardware
> that has an ILM SRAM table and some form of radix based
> lookup.  All of the hardwre I've seen in the last 15
> years or so forwards MPLS and IP at the same rate.

Which was exactly my point - unless you somehow missed that.

> ...
> Except IPv6 before they decided to waste the lower half
> of the address space with 40 quintilion host in a
> bridged subnet and you really did have to look at the
> whole 128 bits.

It is no secret that forwarding of IPv6 packets on some 
vendor equipment is about half the rate of IPv4 or MPLS. But 
then again, because MPLS control planes are IPv4-driven 
today, I'm hoping I didn't have to be explicit about not 
including IPv6 in that group, on this list.

> Back when forwarding was done in
> software (circa 1995) your statement would have been
> true if MPLS preceeded forwarding ASICs which it did
> not.

You might not know that line cards from C like the LSP 
(Label Switch Processor) and much of the PFE from J's PTX 
are forwarding engines that have been made cheaper by 
reducing the IP FIB on the assumption that all traffic will 
be carried in MPLS. This is, obviously, an assumption I do 
not support because:

	- I run IPv6 natively, and at the moment, there are
	  no production-grade IPv6 control planes for MPLS.

	- It assumes providers will run 6PE (in which case,
	  IPv6 traffic enjoys MPLS and IPv6 wire rate
	  forwarding speeds).

I do not buy such line cards because for anyone running 
native IPv6, you could potentially run out of FIB slots to 
host IPv6 routes.

That is why I say MPLS has allowed vendors to put out 
cheaper line cards compared to the costs of those which have 
large IPv4/IPv6 scale. Because MPLS forwarding is so 
mainstream, there is no additional cost associated with 
forwarding rates similar to IPv4. So much of the cost of 
line cards is in QoS queues and routing FIB slots (and MPLS-
biased line cards are stripped of that, hence making them 
cheaper).

> Also the statement "Current-generation ASIC's have no
> problem forwarding MPLS frames at wire rate" is not true
> for most (or all) hardware with 40 byte payloads (even
> with plus 4 with TCP SACK plus 4 if MPLS) and 100 Gb/s
> interfaces.  It is true for "average packet size"
> traffic and on most hardware only true if bursts of 40
> byte packets are very limited in duration.

C'mon, Curtis. Everybody knows this already. Moreover, real 
world IP traffic is not all 40 bytes.

If operators have doubts about what forwarding engines can 
do below 128 bytes, that is what PoC labs are for before you 
buy. And even then, several operators accept the 
restrictions up to a certain point, because the lab and real 
life vary significantly.

Mark.

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


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]