How should a corrupt TLV be handled?
It would be great if the protocol could give guidance on what should be done if we receive a correct data message that contains a corrupt TLV. This should only happen if the peer is using a buggy client, or is actively being hostile.
A reasonable way of dealing with it is to immediately stop processing TLVs if a corrupt TLV is encountered, but the spec is silent on the matter.
(from redmine: created on 2015-08-14)