Hi SPRING WG, draft-ietf-isis-mpls-elc defines an IS-IS extension to allow the use of MPLS entropy labels in SR-MPLS networks. https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-05
As a reminder, entropy label has been defined in RFC 6790 by the MPLS WG. It improves load-balancing / allows the effective use of parallel paths. It requires a signaling and RFC 6790 defined it for LDP, RSVP-TE and BGP. As segment routing does not uses LDP nor RSVP-TE, an IGP extension is indeed required. https://tools.ietf.org/html/rfc6790 As of today (-05) the IGP encoding chosen by draft-ietf-isis-mpls-elc: - may support inter-area/level deployments, albeit with additional complexity (currently not specified) - does not support inter-AS and inter-protocol deployments. (Inter-protocol being the redistribution of prefixes/segments from a protocol (instance) to another IGP protocol (instance)) Following some discussions, this restriction is not an IGP technical issue as it would be easy to allow for this feature by using a different IGP encoding. It's a question of requirements so it would be better discussed in the SPRING WG. I'd like to see a discussion on whether this restriction is a good or a bad thing from a SPRING requirement standpoint. In other words, do we want to allow (or not) the use of entropy label in inter-AS and inter-protocol deployments or do we accept this regression compared to LDP and RSVP-TE? Thanks, Regards, --Bruno _________________________________________________________________________________________________________________________ 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.
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
