Why was section 6 "String Search Filter Definition" changed to say that "all octets greater than 0x7f" must be escaped?
Shouldn't that at least be "MUST" esacpe them when generating filters, but SHOULD (or MAY) recognize them unescaped, for backwards compatibility?
> Also, the change should be noted in Appendix A.
Also,
7. Examples (1.3.6.1.4.1.1466.0;binary=\04\02\48\69)
;binary has been removed from [Protocol].
Good catch.
-Mark