Hi,
As defined in draft-ietf-mpls-spring-entropy-label, advertising an ERLD means
that the node is defacto ELC (so advertising ELC separately is not necessary):
" The Entropy Readable Label Depth (ERLD) is defined as the number of
labels a router can both:
a. Read in an MPLS packet
Gunter,
I have nothing to add to Les' comments, 100% agree.
Cheers,
Jeff
On 6/13/18, 08:42, "Idr on behalf of Les Ginsberg (ginsberg)"
wrote:
Gunter -
I strongly support Option #2 and strongly support Ketan's recommendation
that an MSD sub-type be used to advertise ERLD.
Chris,
I'm not aware of any IPR outside of that already disclosed.
Thanks,
Jeff
Cheers,
Jeff
On 6/13/18, 06:37, "Christian Hopps" wrote:
[Sigh, I quoted the wrong email and mixed things up -- thanks Bruno!]
Authors,
The original WGLC requested the authors indicate if
Gunter -
I strongly support Option #2 and strongly support Ketan's recommendation that
an MSD sub-type be used to advertise ERLD.
This is the unified framework that the MSD advertisement has been designed to
support.
The following documents provide a unified definition of this mechanism:
[Sigh, I quoted the wrong email and mixed things up -- thanks Bruno!]
Authors,
The original WGLC requested the authors indicate if they were aware of any
additional IPR. This seems to have gotten lost in a bunch of comments that
followed.
Can each author reply to this email (and the list)
Authors,
The original WGLC requested the authors indicate if they were aware of any
additional IPR. This seems to have gotten lost in a bunch of comments that
followed. I failed to ask again during this second WGLC. So...
Can each author reply to this email (and the list) indicating if they
Hi Gunter,
In that case, I concur with you that option (2) is better than the others. My
only difference in opinion is that ERLD not have its own separate TLV but
instead get advertised as a new MSD sub-type - it is just a different encoding.
Thanks,
Ketan
-Original Message-
From: Van
Indeed, the debate that made BGP-LS to go down the ERLD path is of pragmatic
motivation.
The major Readable Label Depth use-case is entropy. Hence, if the ERLD TLV is
available, then ELC can be implicitly assumed. No pragmatic reason to signal
separately, as it just make things more complex
