ietf
[Top] [All Lists]

Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard

2013-03-26 06:40:49
On 3/26/13 12:13 PM, "Martin Rex" <mrex(_at_)sap(_dot_)com> wrote:

Adding 3 more OCSPResponseStatus error codes { no_authoritative_data(7),
single_requests_only(8), unsupported_extension(8) } with well-defined and
conflict-free semantics to the existing enum would be perfectly backwards
compatible.

Of course it is backwards compatible with the standard, but not with the
installed base.

What would happen to the installed base of clients if OCSP responders
would change from current "unauthorized" to one of your new error codes?

/Stefan


<Prev in Thread] Current Thread [Next in Thread>