Code change:
These are suggested changes for a quite trivial issue. Please, take a look at my explanation in URL for more details.
URL URL " An example successful response: HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Cache-Control: no-store Pragma: no-cache" Pretty sure application/json shouldn't have a charset (see note at end of section URL) and I've long thought that "Pragma: no-cache" shouldn't be there (see URL ) Note that these apply to most of the example responses in the draft. Examples in RFC 6750 and RFC 6749 as well as some normative text in section of RFC 6749 use a "Pragma: no-cache" HTTP response header. However, both RFC 2616 and the shiny new RFC 7234 make special note along the lines of the following to say that it doesn't work as response header: 'Note: Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control: no-cache" in them.' The header doesn't hurt anything, I don't think, so having it in these documents isn't really a problem. But it seems like it'd be better to not further perpetuate the "Pragma: no-cache" response header myth in actual published RFCs. So with that said, two questions: 1) Do folks agree that 6747/6750 are using the "Pragma: no-cache" response header inappropriately? 2) If so, does this qualify as errata?
Been working on this on and off for a while now (it's not exactly short at 80+ pages, various other priorities, etc.) but wanted to share my thoughts from an initial review of the OAuth 2.1 draft before the interim next week where it is on the agenda URL So for better or worse, here's that review: Abstract: "replaces and obsoletes the OAuth 2.0 Authorization Framework described in RFC 6749." I think "replaces" is probably unnecessary here and, to be pedantic, is arguably inaccurate because published RFCs don't ever go away or get replaced. Probably should also consider using the official "obsoletes" attribute marker too for 6749 URL and probably also "updates"/"obsoletes" for others based on the scope of the rest of the document (not sure how this even works with a BCP or if you can or would want to update or obsolete a BCP) if this work proceeds. That scope could be better described in the abstract too as discussed somewhat in the thead URL and also the 1st paragraph of URL What is and isn't in scope is another larger question that I"m not even sure how to ask. What's included vs. what's referenced? Should this doc be incorporating bits of BCP 212 - OAuth 2.0 for Native Apps? Seems kinda antithetical to what a BCP is supposed to be but it's also a bit hard to tell how much was used. I mean, what happens if/when the BCP is updated? And that kinda begs the question of if it should also incorporate parts of or even replace the browser based apps draft? I guess that's a TBD circa page 68. There was talk about the device grant being in scope but I'm not seeing it (not saying it should or shouldn't be there but it was talked about). I dunno exactly but those are some scope questions that come to mind. Speaking of obsoleting, I do want to ensure that existing extensions and profiles of RFC 6749 that use legitimate extension points still present and unchanged in OAuth 2.1 aren't inadvertently impacted by this effort. I'm not sure how that should work in practice but want to be aware of it as/if this work progresses. URL "is designed for use with HTTP ([RFC2616])." I was momentarily proud of myself for knowing that RFC 2616 is obsolete but then remembered that the nits tool can automate the check for other obsolete or problematic references URL so take a look at those issues. Probably should also check the errata of any documents this one intends to update/obsolete or just borrowed a lot of text from to see if anything should be applied. URL "The interaction between the authorization server and resource server is beyond the scope of this specification." Don't want to try and change the scope but perhaps a mention that things like RFC 7662 Token Introspection and self-contained tokens a la JWT exist here (or sec 1.4 or 7 or...) would be worthwhile. URL " Steps (3), (4), (5), and (6) are outside the scope of this specification, as described in Section 7." But Section 7 incorporates parts of RFC 6750 so being out of scope isn't really true. URL Not too sure about this section in this document but seems that it should at least reflect the fact that some things like RFC 8414 Authorization Server Metadata do now exist. URL All the cool drafts are doing BCP 14 [RFC2119] [RFC8174] these days. URL Mentioning the existence of RFC 7591 Dynamic Client Registration here seems appropriate. And I think it's be super useful to say that even when RFC 7591 isn't being used directly, it (and registered extensions to it URL) imply a common general data model for clients that's pretty widely used and useful even with so called static registration that "typically involve end-user interaction with an HTML registration form." URL "Authorization servers SHOULD NOT allow clients to influence their "clientid" or "sub" value or any other claim if that can cause confusion with a genuine resource owner." This text taken from draft-ietf-oauth-security-topic is out of context and somewhere between meaningless and confusing here in this document. Removing it or maybe something like this might be more appropriate: "Authorization servers SHOULD NOT allow clients to influence their "clientid" value in such a way that it might cause confusion with the identifier of a genuine resource owner during subsequent protocol interactions." URL "The client MAY omit the [clientsecret] parameter if the client secret is an empty string." Let's remove that sentence. As Michael Peck noted in his review, it doesn't even make sense in the context of this section describing authentication of confidential clients using a password/client secret. And that sentence has been the source of some other problems. More detail is in this thread URL URL "Other Authorization Methods" should be "Other Authentication Methods" It's probably worthwhile to note or reference the other client authentication methods that have been specified since this text was written in 6749 and/or point to the OAuth Token Endpoint Authentication Methods registry URL for them and also maybe mention that, despite the Token Endpoint in the name, they are general methods of client auth to the AS when making direct requests. URL "The means through which the client obtains the location of the authorization endpoint are beyond the scope of this specification, but the location is typically provided in the service documentation." Maybe add something like "or in the authorization server's metadata document [RFC8414]." "Request and response parameters MUST NOT be included more than once." please clarify that sentence to say: "Request and response parameters defined by this specification MUST NOT be included more than once." URL " The authorization server MUST compare the two URIs using simple string comparison as defined in [RFC3986], Section 6.2.1." There's absolutely no context here for understanding what two URIs are being compared. Mandating full redirecturi comparison is maybe more appropriate in 4.1.1 with the redirecturi parameter somewhere. And 3.1.2.3. and 3.1.2.2 needs some attention with respect to this too. But also an exception (for the port part) to full redirecturi comparison is needed for loopback redirecturis on native clients as in URL and URL and URL URL As Michael Peck noted in his review, it's probably okay now to just mandate TLS for HTTP redirect URIs. Although custom scheme or loopback redirect URIs for native apps wouldn't use or require TLS. URL and URL Seem to still allow for registration of partial redirection URIs. Which isn't gonna work with an exact match requirement. URL "Request and response parameters MUST NOT be included more than once." please clarify that sentence to say: "Request and response parameters defined by this specification MUST NOT be included more than once." " The means through which the client obtains the location of the token endpoint are beyond the scope of this specification, but the location is typically provided in the service documentation." Maybe add something like "or in the authorization server's metadata document [RFC8414]." URL "Client authentication is critical when an authorization code is transmitted to the redirection endpoint over an insecure channel or when the redirection URI has not been registered in full." Isn't full registration of redirection URI now required (other than maybe the port for native apps) by virtue of requiring a full comparison be done when validating the authz request? And other than a native app using the loopback, maybe it's time to move to require that redirection URIs be accessed via secure channel? URL "Clients are permitted to use "plain" only if they cannot support "S256" for some technical reason and know via out-of-band configuration that the server supports "plain"." With codechallengemethodssupported from Authorization Server Metadata / RFC 8414 it doesn't have to be out-of-band anymore. URL " Typically, the "codechallenge" and "codechallengemethod" values are stored in encrypted form in the "code" itself but could alternatively " 'Typically' - really? URL " ensure that the "redirecturi" parameter is present if the "redirecturi" parameter was included in the initial authorization request as described in Section 4.1.1, and if included ensure that their values are identical." The reference should be to 4.1.1.3. URL " An example successful response: HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Cache-Control: no-store Pragma: no-cache" Pretty sure application/json shouldn't have a charset (see note at end of section URL) and I've long thought that "Pragma: no-cache" shouldn't be there (see URL ) Note that these apply to most of the example responses in the draft. URL " specifying the grant type using an absolute URI (defined by the authorization server) as the value of the "granttype" parameter" The words in the parenthetical have led to questions in AD review of documents making use of the grant type extension point (see https://mozphab-URL) and I think "understood by the authorization server" might be better phrasing or even removing the parenthetical all together. RFC7522 is mentioned here as an example extension grant but maybe worth also including mention of others like RFC7523, RFC8628, RFC8693, and maybe even non IETF ones. URL " Sender-constrained refresh tokens: the authorization server cryptographically binds the refresh token to a certain client instance by utilizing [I-D.ietf-oauth-token-binding] or [RFC8705]." Given the relative immaturity of ways to do this, maybe something more open ended would be appropriate? This reads like token-binding or MTLS are the only ways allowed. I'd think wording that would allow for DPoP or some yet-to-be-defined method would be better here. Also maybe drop the token-binding reference all together (it's long expired and doesn't look like that's gonna change). URL The SHOULDs/RECOMMENDEDs in this section seem a little overzealous and/or too specific. URL Seems to be a lot of overlap and duplication between 9.4. Access Tokens (under 9. Security Considerations) and section 7.4. Access Token Security Considerations, which could/should maybe be reconciled. "(#poptokens)" hints that some text was copied from elsewhere but the markdown references weren't fixed/updated URL "(#refreshtokenprotection)" same thing about markdown references not fixed/updated URL "(#insufficienturivalidation)", "(#mixup)", "(#openredirectoronclient)","(#csrfcountermeasures)", again "(#mixup)", and "(#redirect307)" URL "Attacker A4 in (#secmodel)" "The use of PKCE is RECOMMENDED to this end." PKCE is required elsewhere so this doesn't seem quite right. Similar comments about text ijn URL that talks as though PKCE might not be there. URL "(#rediruriopenredir)" URL "(#clientimpersonating)" URL " * Redirect URIs must be compared using exact string matching as per Section 4.1.3 of [I-D.ietf-oauth-security-topics]" Should that maybe be qualified to cover dynamic ports on ephemeral local http servers used for redirect URI with native clients? BTW, does [I-D.ietf-oauth-security-topics] need to make a similar allowance? URL "TBD" Given the potentially high visibility of an OAuth 2.1 effort, I think it'd be worthwhile to list organizational affiliations of individuals here in the acknowledgements along with their names. Something like what was done in the first part of URL This can help with visibility and justification of (sometimes not insignificant) time spent on the work by non-authors/editors. CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._

Related discussion:
text: The authorization server MUST include the HTTP "Cache-Control" response header field RFC7234 with a value of "no-store" in any response containing tokens, credentials, or other sensitive <del> information, as well as the "Pragma" response header field RFC7234 with a value of "no-cache". </del> <ins> information. </ins> For example: