Following up on the discussion at IETF122, I reviewed draft-ietf-oauth-identity-chaining-04. Overall, I am happy with the document.
I filed one issue <https://github.com/oauth-wg/oauth-identity-chaining/issues/143> regarding editorial content in the introduction, and published two PRs. The first <https://github.com/oauth-wg/oauth-identity-chaining/pull/144> PR is a minor fix where it appears Domain A and B were inadvertently swapped in the text. The second PR <https://github.com/oauth-wg/oauth-identity-chaining/pull/145> was more substantial. I found the text in Appendix B1 difficult to follow and the language unwieldy. To simplify the reading, I suggest the authors name the authorization servers and resource servers based upon their domains (e.g. an AS in Domain A is ASᴬ, an AS in Domain B is ASᴮ). If the authors have any questions, please reach out. Thanks, -dhs -- Dean H. Saxe, CIDPRO <https://idpro.org/cidpro/> (he/him) Principal Engineer Office of the CTO Beyond Identity dean.s...@beyondidentity.com
_______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
