#10: 8.4. Defining Additional Error Codes
Changes (by barryleiba@…):
* status: new => closed
* resolution: => wontfix
--
+---
Reporter: Eran Hammer-Lahav |Owner:
Type: sugges
#10: 8.4. Defining Additional Error Codes
Comment(by barryleiba@…):
Comment from Alexey:
I am wondering if the ACAP vendor name registry (RFC 6075), the OID vendor
names, or DNS names can be recommended for the prefix (to satisfy the
"SHOULD be prefixed by an identifying name when possible"
#10: 8.4. Defining Additional Error Codes
Description changed by barryleiba@…:
Old description:
> Pending Consensus:
>
> 8.4. Defining Additional Error Codes
>
> In cases where protocol extensions (i.e. access token types, extension
> parameters, or extension grant types) require additional erro
#10: 8.4. Defining Additional Error Codes
Description changed by barryleiba@…:
Old description:
> Pending Consensus:
>
> 8.4. Defining Additional Error Codes
>
> In cases where protocol extensions (i.e. access token types, extension
> parameters, or extension grant types) require additional erro
#10: 8.4. Defining Additional Error Codes
Pending Consensus:
8.4. Defining Additional Error Codes
In cases where protocol extensions (i.e. access token types, extension
parameters, or extension grant types) require additional error codes to be
used with the authorization code grant error re
