Hi Uma, The ELC is used to indicate whether an LSR is capable of recognizing and popping the EL associated with the LSP which is terminated on that LSR while the E of the ERLC is used to indicate whether an LSR could perform EL-based load-balancing. In a word, ERLD<>RLD+ELC.
Best regards, Xiaohu ------------------------------------------------------------------ From:Uma Chunduri <[email protected]> Send Time:2019年9月12日(星期四) 07:28 To:Acee Lindem (acee) <[email protected]>; [email protected] <[email protected]> Cc:[email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject:Re: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08 >Because the intra-area link topology is not exposed across areas or to other >protocols. Agreed Acee. But just looking this again then: Not really clear why ELC is required in Section 4, when it’s confirmed from Stephane’s email (Sept 4th 2019) ERLD covers both reading + doing and action. Section 4 extending RFC 7794, with E bit, which is defined for prefix attributes for inter-area purposes (no ERLD value obviously). Same thing can be achieved simply if router capability with ERLD value itself is propagated (per RFC 7981). Overall, I am more confused here than earlier. But feel free to ignore my comments. -- Uma C.
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
