Ok Thx to both of you ...

So it was very clear that we MUST skip what we do not recognize :)  I was
not sure if we should at that point bail out from further parsing of a
given TLV or trying next sub-TLV. I guess there is no mandate of that in
the spec and implementations should/may try to continue to parse.

Also is my understanding correct that the subject draft does not allow to
split sub-TLVs itself ? Meaning that any sub-TLV must fit one part of the
TLV. I found some text allowing duplication of sub-TLVs in multiple parts
of TLV if sender choose to do such thing - but I assume this says that
sub-TLV is still a complete one in each part ?

Thx,
R.

On Fri, Feb 21, 2025 at 5:28 PM Les Ginsberg (ginsberg) <[email protected]>
wrote:

> Robert -
>
> I am certain that Tony and I are in complete agreement - but I found his
> response a bit cryptic.
>
> So, to provide more context, RFC 8918 is relevant - particularly Section
> 3.3.
>
> HTH
>
>    Les
>
>
> > -----Original Message-----
> > From: Tony Li <[email protected]> On Behalf Of Tony Li
> > Sent: Friday, February 21, 2025 8:07 AM
> > To: Robert Raszuk <[email protected]>
> > Cc: Les Ginsberg (ginsberg) <[email protected]>; lsr <[email protected]>
> > Subject: Re: [Lsr] [Last-Call] 答复: Re: 【Can you concatenate several
> pieces
> > together without one "explicit key" to identify them belong to the same
> > segment】Re: Rtgdir last call review of draft-ietf-lsr-multi-tlv-08
> >
> >
> > Hi Robert,
> >
> > > If a peer happens not to recognize content of a sub-TLV within the
> first or N-
> > th part of the multi part TLV what is the expected behaviour ... is it
> to stop
> > parsing any subsequent content of given MP-TLV or skip unrecognized sub-
> > TLV and keep trying to decode the rest of them if of course it can get
> the length
> > of it correctly and move to the next one ?
> >
> >
> > The beauty of TLVs is that you don’t have to parse everything to make
> > progress.
> >
> > So you do.
> >
> > T
> >
>
>
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to