MUSTs and other feedback 4

[mnot@…]

For historical reasons, senders MUST only use the quoted-string syntax.

Perhaps this can be relaxed to "MUST only generate", especially since another MUST prohibits proxies from modifying WWW-Authenticate and Authorization header fields.

And here is a list of requirements that are missing an explicit actor on which the requirement is placed. Even though it is often possible to guess the actor, most of these should be easy to rephrase to place the requirement on the intended actor explicitly (e.g., "A proxy MUST" instead of "a header field MUST":

each parameter name MUST only occur once per challenge

This response MUST include a WWW-Authenticate header

The 407 (Proxy Authentication Required) response message [...] MUST include a Proxy-Authenticate header field

information necessary to authenticate a request MUST be provided in the request

It MUST be included as part of a 407 (Proxy Authentication Required) response.

It MUST be included in 401 (Unauthorized) response messages

Please be careful with "send" and "generate" when fixing the above actorless rules so that the proxies do not accidentally become responsible for policing traffic where unnecessary.

[julian.reschke@…]

From [2289]:

tune a MUST regarding use of quoted-string in realm param (see #481)

[julian.reschke@…]

Fixed the first issue; do not agree with the need to fix the other parts. Please review the generic requirements defined in P1; or alternatively suggest concrete text.