Close #10: "request URI" not defined

[cabo]

No description provided.

[chrysn]

From interim: It's only distinct in responses to multicast request, but there is a related ~"base for URI references in the response body" term. Possibly there'll be some more text in core-responses that this can point to.

[chrysn]

groupcomm-bis would also be easier with that defined: Currently, it has to bend around the involved URIs saying

A client sending a GET or FETCH group request MAY use a response received from a server, to satisfy a subsequent sent request intended to that server on the related unicast request URI. In particular, the unicast request URI is obtained by replacing the authority component of the request URI with the transport-layer source address of the cached response message.

[cabo]

Merging this with a big PENDING so we can have -04 for the interim tomorrow