* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #156 (closed editorial: fixed)

Opened 7 years ago

Last modified 4 years ago

Isolate TCP-specific aspects of HTTP

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/8E241CE2-4630-4290-BE78-06037FD451D8@mnot.net


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).

Change History

comment:1 Changed 4 years ago by mnot@pobox.com

  • Priority set to normal
  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.