-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AD Review Text Updates #513
Conversation
✅ Deploy Preview for gnap-core-protocol-editors-draft ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
draft-ietf-gnap-core-protocol.md
Outdated
@@ -1431,7 +1431,8 @@ its capabilities and what is allowed to fulfill the request. | |||
|
|||
In this non-normative example, the client instance is indicating that it can [redirect](#request-interact-redirect) | |||
the end user to an arbitrary URI and can receive a [redirect](#request-interact-callback-redirect) through | |||
a browser request. | |||
a browser request. Note that the client instance does not accept a push-style callback. This pattern | |||
is common for web-based client software. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would clarify "This redirect pattern" (to make sure we don't misunderstand with the note on push style callback that comes just before)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all makes sense and is aligned with the explanations on the mailing list
Update text based on AD review of core specification:
https://mailarchive.ietf.org/arch/msg/txauth/9Z-nHJsHEDhREiXFl1hDatizb7Q/