Discovery: Typos in draft 05

Typos in draft-mobile-discovery-05.

p1

Ping Identity ->
Yubico

August 08, 2015 ->
(should be updated properly)

p1, Abstract, the 1st paragraph

ip-addresses ->
IP addresses

p1, Abstract, the 2nd paragraph

mobile contry code ->
mobile country code

p2 and following pages, page header

OIDC Mobile Discoery Profile 1.0 ->
OIDC Mobile Discovery Profile 1.0

p2, Introduction

how a OpenID ->
how an OpenID

for a identifier ->
for an identifier

p2, 1.2. Terminology

"Client Identifier",and ->
"Client Identifier", and

and Relying Party (RP) ->
and "Relying Party (RP)"

p3, 2. Overview

guided by to following requirements: ->
guided by the following requirements:

some RPs will either already are in posession of MSISDNs or may obtain it ->
RPs are already in possession of MSISDNs or may obtain them

p3, 2.1. Redirect-based flow, section title

Redirect-based flow ->
Redirect-based Flow

by server-side web application ->
by server-side web applications

p4. Figure 1

The diagram is broken when the XML file is converted to "TEXT as PDF" at xml2rfc. See the attached file "draft-mobile-discovery-05-2_1-figure-1.png".

p4, (B)

If an user account ->
If a user account

a pseudonym user id ->
a pseudonym user ID

MNO's OPs openid configuration ->
OpenID configuration of the MNO's OpenID Provider
or ->
MNO's OP's configuration

p4, (C)

by way of an client id ->
by way of a client ID

p5, (G)

the URL refering to ->
the URL referring to

OpenID server ->
OpenID Provider

p5, (H)

meta data ->
metadata

p5, after (H), the 1st paragraph

specified in sections Section 3.1 and Section 3.2 , respectively ->
specified in Section 3.1 and Section 3.2, respectively

p5, after (H), the 2nd paragraph

meta data ->
metadata

steps (G) and (H) ->
steps G and H

section 4 ->
Section 4

sucessfully ->
successfully

p5, after (H), the 3rd paragraph

meta data ->
metadata

using the openid configuration ->
using the OpenID configuration

p5, 2.2. POST-based flow, section title

POST-based flow ->
POST-based Flow

p6, Figure 2

The diagram is broken when the XML file is converted to "TEXT as PDF" at xml2rfc. See the attached file "draft-mobile-discovery-05-2_2-figure-2.png".

p6, (A)

(MNC/MCC,IMSI, or MSISDN) ->
(MNC/MCC, IMSI or MSISDN)

p6, (C)

the URL refering to ->
the URL referring to

p6, (D)

meta data ->
metadata

p7, 3.1.1. Request, the 1st paragraph

User Interaction endpoint ->
User Interaction Endpoint

p7, 3.1.1. Request, state

XSRF ->
CSRF

p7, 3.1.1. Request, mcc

by ITU-T E.212 ->
by ITU-T E.212.

(A period at the end of the sentence.)

p7, 3.1.1. Request, mnc

by ITU-T E.212 ->
by ITU-T E.212.

(A period at the end of the sentence.)

p8, 3.1.2. Response

The example of an HTTP response is broken when the XML file is converted to "TEXT as PDF" at xml2rfc. See the attached file "draft-mobile-discovery-05-3_1_2_Response-example.png".

p10, client_secret

been issued issued ->
been issued

p10, redirect_uri

If the parameter "code is present. ->
If the parameter "code" is present.

the user interaction endpoint ->
the User Interaction Endpoint

p10, mcc

by ITU-T E.212 ->
by ITU-T E.212.

(A period at the end of the sentence.)

p10, mnc

by ITU-T E.212 ->
by ITU-T E.212.

(A period at the end of the sentence.)

p10, after msisdn, the 2nd paragraph

If code is present ->
If "code" is present

p10, the example of a request at the bottom of the page

The width of the example is wider than the section body. See the attached file "draft-mobile-discovery-05-3_2_1_Request-example.png".

p11, 3.2.2. Response, login_hint_token

A Encrypted JSON ->
An encrypted JSON

the user interaction endpoint ->
the User Interaction Endpoint

p11, 3.2.2. Response, the example of a response

The width of the example is wider than the section body. See the attached file "draft-mobile-discovery-05-3_2_2_Response-example.png".

p11, 3.2.3. Error Response, the 1st paragraph

The discovery server respondes with ->
The discovery server responds with

p12, after error_uri

of a error response ->
of an error response

p12, the example of a response

The example should be indented. See the attached file "draft-mobile-discovery-05-3_2_3_Error_Response-example.png".

p13, 5.1. AC Chooser, the 1st paragraph

Web server clients use ->
Web clients use

the users preferred account ->
the user's preferred account

p13, 5.1. AC Chooser, after the script

an HTTP POST ->
an HTTP POST request

the client has to to implement ->
the client has to implement

p13, the list of the five parameters

Should be indented.

p14, the example of an HTTP POST request

The first line of the example is not indented, and the request body is indented too much. See the attached file "draft-mobile-discovery-05-5_1_AC_Client-example.png".

p14, 5.2. AC Identity Provider, the 1st paragraph

local storrage ->
local storage

a successful loggin ->
a successful login

p14, 5.2. AC Identity Provider, the 2nd paragraph

the Browsers local ->
the browser's local

p15, the example of a script

Should be indented.

Comments (4)