Hi Jeff, You're right. I certainly don't want to change the specification, nor to add another ambiguity. I was just looking for a mnemonic to mitigate the confusion pointed out by Martin, to be considered between bracket (leaving the definition as is). Would "limit-blind" make sense?
Cheers, Julien On 06/01/2019 20:20, Jeff Tantsura wrote: > Hi Julien, > > Happy New Year to you too. > There’s a slight difference between limitless (e.g. unlimited) and > limit has not been been imposed (not configured/unknown/etc). > I think “limitless” doesn’t convey the exact meaning. In simple terms > - if L=1, don’t use MSD as a constraint in the path computation. > > Thanks, > Jeff > > On Fri, Jan 4, 2019 at 02:28 <julien.meu...@orange.com > <mailto:julien.meu...@orange.com>> wrote: > > Hi guys and happy new year! :-) > > Would it temper the confusion below if we added the term > "limitless" to > the L flag definition (section 5.1.1.)? > > My 2 cents, > > Julien > > > On 21/12/2018 18:14, Jonathan Hardwick wrote: > > I believe it is too late to change but I find L=1 meaning "no > limit" is *very* confusing. For me L stands for Limit and when L=1 > there is a limit, when L=0 there is none. > > > > [Jon] Agree, both that it is confusing and too late to change :-) > _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
