Hi Les, If all information about the link requires two TLVs the following is sent: > > > > * <22, Neighbor System ID, IPv4 Local/Remote Address and IPv6 > Local/Remote Addresses> + object info* > > * <22, Neighbor System ID, IPv4 Local/Remote Address and IPv6 > Local/Remote Addresses> + additional object info* >
I have a question - actually related to some testing I am doing - for a change not related to keys debate :) 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 ? Many thx, Robert
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
