-
assigned issue to
CIBA: typos in draft 06
Typos in draft-mobile-client-initiated-backchannel-authentication-06 which was updated on Oct. 30, 2018.
p1, Title
(unless the lower case is intentional)
Client initiated ->
Client Initiated
p2, the 3rd paragraph
(unless the lower case is intentional)
Client initiated ->
Client Initiated
p2, the 4th paragraph
semantic ->
semantics
p3, the 1st line
semantic ->
semantics
p3, 2. Terminology, the 1st paragraph
the term "client" ->
the term "Client"
OAuth 2.0 Authentication Servers ->
OAuth 2.0 Authorization Servers
p3, 2. Terminology, Consumption Device
or the CD is a SP ->
or the CD is an SP
p4, 3., Ping Mode
a callback uri ->
a callback URI
p4, 3., Push Mode
a callback uri ->
a callback URI
p5, Client Metadata, backchannel_token_delivery_mode
Add a period at the end of the sentence.
p5, Polling and Pairwise Identifiers
ownership and it use it ->
ownership and uses it
p6, the 1st line
the client ->
the Client
p6, the 2nd paragraph, the 5th line
uri to set as a "sector_identifier_uri" ->
URI to set as a "sector_identifier_uri"
p6, the 3rd paragraph
one of this two mechanisms ->
one of the following two mechanisms
p8-p9, diagrams
- 'AD' should be centered in the box.
- The space after '(2) User interactions' should be removed.
p9, 7.1. Authentication Request, the 1st line
(unless the lower case is intentional)
Client initiated ->
Client Initiated
p10, acr_values
the Authorization Server ->
the OpenID Provider
p10, id_token_hint
by the authorization server ->
by the OpenID Provider
p11, the 2nd line
by the client ->
by the Client
p11, the 3rd line
the client MUST ->
the Client MUST
p11, the 3rd line
decrypt the signed ID Token contained within the encrypted ID Token ->
decrypt the encrypted ID Token to extract the signed ID Token contained in it.
p11, login_hint
A hint to the authorization server ->
A hint to the OpenID Provider
the client before ->
the Client before
p11, binding_message
a visual cue the end-user ->
a visual cue for the end-user
p11, the 2nd last paragraph
(unless the lower case is intentional)
Client initiated ->
Client Initiated
p12, 7.1.1., aud
must contain ->
MUST contain
p12, 7.1.1., iss
must be ->
MUST be
p14, 7.2.
Remove a redundant empty line between the first item and the second item.
p15, 5.
as per section ->
as per Section
p16, 8., the 2nd paragraph
As in OAuth2 ->
As in OAuth 2.0
p16, 8., the 3rd paragraph
(unless the lower case is intentional)
Client initiated ->
Client Initiated
p17, the 2nd paragraph
(unless the lower case is intentional)
Client initiated ->
Client Initiated
p17, 9., the 2nd paragraph
Client Notification Authentication Endpoint ->
Client Notification Endpoint
p17, 9., the 4th paragraph
id_token, access_token and, optionally, refresh token ->
ID Token, an Access Token and, optionally, a Refresh Token
p17, 10., the 2nd paragraph
A client ->
A Client
p17, 10.1.
If the Client registered ->
If the Client is registered
p18, the 4th paragraph
in Ping mode, may also ->
in Ping mode may also
as if was registered ->
as if it were registered
p21, the 1st line
a succesful token ->
a successful token
p23, the 4th paragraph
is like to ->
is likely to
p23, 11., the 1st paragraph
according to the section ->
according to Section
p23, 11., authorization_pending
the end-user ->
the End-User
p24, access_denied
The end user denied ->
The End-User denied
p24, the 4th paragraph
If the Client has registered ->
If the Client is registered
p25, the 2nd paragraph
the following two parameters ->
the following three parameters
p27, 15., the 3rd paragraph
id_token_hint is listed in the the ->
id_token_hint is listed in the
key rotation, however, the the OP ->
key rotation, however, the OP
a valid hint will likely be ->
a valid hint will be likely to be
p27, 16.
(unless the lower case is intentional)
Client initiated ->
Client Initiated
Appendix A., the 1st paragraph
This a non-normative ->
This is a non-normative
Comments (3)
-
-
pull request #40
-
- changed status to resolved
- Log in to comment