[frr] Fwd: Re: [PATCH net-next 0/4] net: mpls: Allow users to configure more labels per route

bruno.decraene at orange.com bruno.decraene at orange.com
Sun Mar 26 23:22:46 EDT 2017

My 2 cents on SR:

 > From: David Ahern [mailto:dsa at cumulusnetworks.com]
 > Sent: Sunday, March 26, 2017 5:23 PM
 > On 3/26/17 11:02 AM, Thomas Morin wrote:
 > > Hi David,
 > >
 > > [adding my colleague Bruno to the list, he may correct things I might
 > > have oversimplified on segment routing, or have a idea about 12]
 > >
 > > 2017-03-25, David Ahern:
 > >> Eric's question below is basically adding labels at tunnel ingress vs
 > >> while traversing the LSP. I was generically increasing both to more than
 > >> 2 labels. Opinions?
 > >
 > > An MPLS packet may in transit receive additional labels. I most cases
 > > (all?), this will be most properly seen as a LSP hierarchy (tunneling
 > > one LSP into another LSP), so closer to a notion of ingress rather than
 > > something related to the initial LSP. But I don't know if the
 > > distinction is of importance.
 > >
 > > The cases that comes to mind would be:
 > > - tunneling into a fast-reroute bypass LSP (possibly a segment routing
 > > LSP, see segment routing TI LFA)
 > > - seamless MPLS
 > > - carrier's carrier type of deployment
 > >
 > > In these cases a router could receive an MPLS packet, and possibly after
 > > popping the topmost, push a stack of labels onto the packet.
 > And that's my takeaway from past discussions on this topic (number of
 > labels).
 > >
 > > About the email below:
 > > - how did 12 end up being considered "covering all currently known
 > > segment routing use cases" ? it seems that SR could use an arbitrary
 > > number of labels  (not saying 12 is a bad number, but...)
 > I believe the consensus was 8 but Olivier had a use case for more.

TL;DR: the more labels, the better.

SR has no theoretical max number of labels. Worst case is the use of a strict ERO/path. In this case " crossing 15 nodes, means stacking 15 labels to encode the  SR tunnel."
In addition, one may push entropy labels (2 labels:ELI, EL). In worst case, there may need to push multiple couple of entropy labels. e.g. when the first one would be too deep to be visible from transit node (aka LSR).

12 labels seem relatively reasonable, but may not cover all cases. IIRC, this is the order of magnitude that a good hardware implementation can perform. I would expect that a software implementation could do better and that we would want to accommodate for next generations of hardware. IOW, if the max is "for free" on a software plateform, I would call for a higher max (e.g. 16 or 20). 

> The
 > way I have this coded means the performance impact is to users adding
 > more and more labels - which is expected and appropriate.
Looks good.

 > > - I'm not sure what Eric's idea of "running the packet a couple of times
 > > through the mpls table to get all of the desired labels applied" would
 > > mean: after the first lookup, what data would be used as key for the
 > > following lookup ?
 > no idea. I need him to clarify.
 > > - back to your question, which seems to imply one could possibly
 > > increase number of labels for ingress without increasing number of
 > > labels for transit: isn't the same datastructure used in both to
 > > represent an mpls next hop (in RFC3031, both the ILM and FTN point to
 > > NHLFE entries, but I haven't digged enough to identify how these maps to
 > > the kernel implementation)
 > no. Ingress is handled by a lightweight tunnel infrastructure. In 'ip'
 > terms the route specifies lwt with mpls encap. LSP MPLS is handled as a
 > typical protocol family with its own route database.
 > > - would a concept of a linked list of mpls_nh make sense, each with one
 > > label to impose, make sense, so that no hard limit is put on the label
 > > stack depth?
 > each nexthop has its own label stack. The nexthops are essentially an
 > array at the end of the mpls route.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

More information about the dev mailing list