Re: [tsv-area] Transport negotiation

[Lloyd Wood <[e-mail]>]

On 25 Nov 2008, at 22:43, Joe Touch wrote:
> Right. The trick is that there is no such thing as HTTP; it's HTTP  
> over
> TCP. What you want is "HTTP by any means"; whether the DNS supports  
> this
> is less the issue than the fact that IANA doesn't really define such a
> thing.

Worth mentioning a couple of drafts contemplating HTTP running over
something other than TCP:
Preethi Natarajan's HTTP over SCTP, with modifications to Apache,  
which got talked about in Minneapolis:
http://tools.ietf.org/html/draft-natarajan-http-over-sctp

Our proposal to use HTTP for peer-to-peer rather than client-server
transfers, and to layer it over whatever transport is suitable for
the local environment:

http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery
(presented at IETF 71 in Philadelphia.)

I'd be interested in knowing of other, similar, work and seeing
what commonalities there are.

On choosing transport, couldn't http:// just map to http/<whatever-is- 
favoured>:// ?

Explicitly asking for http/tcp:// or http/sctp:// would produce
different behaviour. I don't see a need to involve DNS here -
but I'd quite like to be able to specify http/tcp/ipv6:// or
http/sctp/ipv4:// to force behaviour in the browser, while
knowing that http:// just works.

L.

introducing the world's surfers to layering is just a bonus.

DTN work: http://info.ee.surrey.ac.uk/Personal/L.Wood/saratoga/

<http://info.surrey.ac.uk/Personal/L.Wood/><[e-mail]>