jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-thomson-http-oblivious

Commentary: If the key identifier is n't known to the oblivious request resource , or the message ca n't be decrypted , it probably wants to send a clear signal . The signal is definitely not encapsulated at that point , so clients have limited options available to them . As a first - order suggestion , a 4xx status code generally indicates to the client that it might want to review the information it used . However , more specific error codes might help in specific cases that we deem important or common . Top of the list : when the identified key has been decommissioned . 
 How does sound in terms of saying " the content was unusable " . We could go further and recommend the use of if you think more detail is needed .
An oblivious request resource needs to have a plan for replacing
keys.  This might include regular replacement of keys, which can be
assigned new key identifiers.  If an oblivious request resource
receives a request that contains a key identifier that it does not
understand or that corresponds to a key that has been replaced, the
server can respond with an HTTP 422 (Unprocessable Content) status
code.
A server can also use a 422 status code if the server has a key that
corresponds to the key identifier, but the encapsulated request
cannot be successfully decrypted using the key.