Caution against treating data on a connection as part of a not-yet-is…

…sued request

Fixes #26.

draft-ietf-httpbis-messaging-latest.xml

@@ -1739,6 +1739,11 @@ https://www.example.org
    ordered request that has not yet received a final (non-<x:ref>1xx</x:ref>)
    response.
 </t>
+<t>
+   If a HTTP/1.1 client receives data on a connection that doesn't have any
+   outstanding requests, it &MUST-NOT; consider them to be a response to a
+   not-yet-issued request; it &SHOULD; silently discard them.
+</t>
 </section>
 
 <section title="Persistence" anchor="persistent.connections">
@@ -3348,6 +3353,7 @@ Upgrade: HTTP/2.0
 <ul>
    <li>In <xref target="status.line"/>, explain why the reason phrase should be ignored by clients (<eref target="https://github.com/httpwg/http-core/issues/60"/>).</li>
    <li>Add <xref target="associating.response.to.request"/> to explain how request/response correlation is performed (<eref target="https://github.com/httpwg/http-core/issues/145"/>)</li>
+   <li>In <xref target="associating.response.to.request"/>, caution against treating data on a connection as part of a not-yet-issued request (<eref target="https://github.com/httpwg/http-core/issues/26"/>)</li>
 </ul>
 </section>