8.2.2 auth-token definition duplicate requirements

[brianjmiller]

There are duplicated requirements from the overview in section 8.2.1,

The fetch URL MUST return a JSON structure using a Content-Type of "application/json".

In 8.2.2

The response MUST have a Content-Type of "application/json".

[MrBillMcDonald]

The group agreed that section 8.2 Authorization Token Fetch URL be re-organized to combine the request and possible responses into one section and eliminate duplicate requirement statements. Brian will proposed new wording.

[MrBillMcDonald]

Per the June 24th meeting. The proposed change would be to move the following from 8.2.2 to 8.2.1

The response MUST have a Content-Type of "application/json". The HTTP status code MUST be "200" for a valid request (including one that generates error as described in section 8.2.3).

And then remove this redundant phrase in 8.2.1:

using a Content-Type of "application/json"

[MrBillMcDonald]

Per Feb 16th Meeting - a PR against existing Repo is pending. (including #620)