Ticket #156 (closed editorial: fixed)
Isolate TCP-specific aspects of HTTP
|Reported by:||firstname.lastname@example.org||Owned by:|
|Component:||p1-messaging||Severity:||Active WG Document|
There's a growing amount of interest in running HTTP in ways other than how it's described as using TCP in RFC2616. This includes the ongoing discussion of HTTP-over-SCTP as well as more radical approaches such as "reverse HTTP."
To make the specification of such mechanisms easier and less prone to error, p1 should be arranged so that TCP-specific connection details be isolated from the rest of the specification. An alternate approach would be to factor such aspects into a separate draft, but this is probably not necessary (i.e., as long as it's easy to identify which parts of p1 are overridden, that should be enough).