[j-nsp] Limit on interfaces in bundle

[Adam Vitkovsky]

>

        Adam Vitkovsky
        IP Engineer

T:      0333 006 5936
E:      Adam.Vitkovsky at gamma.co.uk
W:      www.gamma.co.uk

This is an email from Gamma Telecom Ltd, trading as “Gamma”. The contents of this email are confidential to the ordinary user of the email address to which it was addressed. This email is not intended to create any legal relationship. No one else may place any reliance upon it, or copy or forward all or any of it in any form (unless otherwise notified). If you receive this email in error, please accept our apologies, we would be obliged if you would telephone our postmaster on +44 (0) 808 178 9652 or email postmaster at gamma.co.uk

Gamma Telecom Limited, a company incorporated in England and Wales, with limited liability, with registered number 04340834, and whose registered office is at 5 Fleet Place London EC4M 7RD and whose principal place of business is at Kings House, Kings Road West, Newbury, Berkshire, RG14 5BY.


-----Original Message-----
> From: Jesper Skriver [mailto:jesper at skriver.dk]
> Sent: Monday, November 02, 2015 5:14 PM
>
>
> Right, on those types of platforms it can be done - assuming there are spare
> bits in the meta data that goes with the packet, enough free instruction
> space etc - but it will come at a performance impact as it will require more
> cycles per packet, unless on the particular platform there is still headroom for
> adding more cycles without affecting the ability to be linerate ...
>
Talking about lookup performance isn't the number of cycles negligible compared to memory access times please?
Even the high-end platforms of all vendors will cripple performance when features are enabled.

> Which is why I in my original reply said that it would not be practical. For it to
> be useful all routers in the path needs to support it, otherwise as soon as it
> hits one that doesn't all the various MPLS sub-types will get mixed together
> again.
> Features which require network wide support are quite hard to get off the
> ground.
>
Maybe this could get shoehorned along with segment routing.


adam