On 3 November 2015 at 17:19, Adam Vitkovsky <[email protected]> wrote: > But I like your example with the Entropy label. > What if the topmost label value or even better the VPN/VC label could > indicate how to parse the remainder of the packet. > And if a middle node or end node(in case of a VPN/VC label) doesn't > understand the encoding it would just label switch the packet blindly. > It should be very simple to implement and also to adjust the label-space so > that it doesn't conflict with anything else > So all nodes that support the feature would start allocating with: > 847.... MPLS-UNSPECIFIED > 848.... MPLS-IP > 849.... MPLS-ETH > And so forth..
What benefit would L3/L4 keys give, if there is useful per stream entropy in MPLS labels? -- ++ytti _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
