search

stoffi92 / rfc5575bis

0 stars 0 forks source link

IESG Benjamin Kaduk: Section 4.2.2.3 #192

Closed stoffi92 closed 4 years ago

stoffi92 commented 4 years ago

Section 4.2.2.3

This component uses the Numeric Operator (numeric_op) described in Section 4.2.1.1. Type 3 component values SHOULD be encoded as single octet (numeric_op len=00).

Is it well-defined how I would encode the value if I ignored the SHOULD? I, for one, am not sure what I would do...

suehares commented 4 years ago

My understanding is that we had this as "MUST" and moved it back to "SHOULD" due to existing implementations - since it was unclear in RFC5575.

Is that your recollection.

stoffi92 commented 4 years ago

My understanding is that we had this as "MUST" and moved it back to "SHOULD" due to existing implementations - since it was unclear in RFC5575.

Is that your recollection.

This is correct.

stoffi92 commented 4 years ago

//doc The SHOULD here is because the value could also be encoded as multiple octets as of Section 4.2.1.1. it is less efficient but still possible. RFC5575 did not give any advice on the encoding length of the values. The -bis does, but using MUST did not find consensus because of the deployed implementations making some "non-compliant".