Yoav Nir writes: > Issue #165 - Incorrect wording on Transform Attributes > ====================================================== > 3.3.5: "Attributes described as fixed length MUST NOT be encoded > using the variable-length encoding." This cannot be correct, a new > 4-octet attribute will have to be encoded as variable-length. It > won't fit into the other format.
Yes, the fixed length should be changed to TV format. and variable-length needs to be changed to TLV format. > I agree with this. How about: > The only currently defined attribute type (Key Length) is fixed > length; the variable-length encoding specification is included only > for future extensions. Attributes described as fixed length MUST NOT > be encoded using the variable-length encoding, unless that length > exceeds two bytes. Variable-length attributes MUST NOT be encoded as > fixed-length even if their value can fit into two octets. NOTE: This > is a change from IKEv1, where increased flexibility may have > simplified the composer of messages, but certainly complicated the > parser. I think it is better to change the way I proposed in the list earlier: The only currently defined attribute type (Key Length) is using TV encoding; the TLV encoding specification is included only for future extensions. Attributes described as using TV encoding MUST NOT be encoded using the TLV encoding. Attributes described as using TLV encoding MUST NOT be encoded as using TV encoding even if their value can fit into two octets. NOTE: This is a change from IKEv1, where increased flexibility may have simplified the composer of messages but certainly complicated the parser. -- [email protected] _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
