All, Observing this discussion I have a question why the draft as well as this discussion is only limited to one solution for efficient load balancing across parallel links in the network - namely entropy labels ?
Let's observe that unlike in general MPLS label allocation per FEC in SPRING labels are allocated per much more contained number of segment node properties. Therefor an alternative of using any form of entropy labels in data plane all together would be to allocate a SID blocks (say 64 or 128 wide) and allow SPRING header imposition to use such pools of SIDs per group of flows to effectively allow for efficient load balancing in the network. Moreover this solution does not put any additional requirements on MPLS hardware and can be easily supported today by most of shipping routers. Best, r. On Thu, Jul 24, 2014 at 8:31 AM, <ruediger.g...@telekom.de> wrote: > Hi Rob, > > I agree, a single ELI/EL deeper in the stack as proposed by §3.1 is the > most useful target solution also from my point of view. > > Regards, > > Ruediger > > -----Message----- > From: spring [mailto:spring-boun...@ietf.org] Rob Shakir > > Hi Sri! > > [snip] > > rjs> Addressing the final goal - as per Stephane's comments - I would like > to recommend that we specify §3.1 as the target option (such that we have a > single ELI/EL deeper in the stack) as the "ideal" option. It then seems to > me that a debate as to whether the forwarding behaviour in §3.3 is possible > with most h/w today (both mean that either we change the number of > operations that are required on a forwarding device when popping/swapping > labels as far as I can see), or whether the approach in §3.4 (with the > caveats noted above) is the best way forward. > > Thanks for your consideration. > r. > > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
