- From: Mike Belshe <mike@belshe.com>
- Date: Wed, 2 Jul 2014 07:17:44 -0700
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>
Received on Wednesday, 2 July 2014 14:18:19 UTC
On Wed, Jul 2, 2014 at 5:12 AM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: > In message <CABaLYCs4a= > zidQac0+gVHdLqoXfgxeRNV2NhakFQSMySK_XxKg@mail.gmail.com> > , Mike Belshe writes: > > >We learned that transport > >protocols had an upgrade problem, but application protocols did not. > > So why is FF and Chromium not supporting Upgrade: ? > This has all been hashed out before. > > >So we should all feel great about this - multiplexed streams were trapped > >for over a decade inside SCTP, and h2 is finally unlocking it for http. > > This is a huge learn-from-history victory. > > That is very much a matter of perspective. > > Taking the fight and using HTTP to push SCTP adoption, would have given > us so much more than than the current drafts erzats-framing does. > Again, this has all been hashed out. Read my presentations from 4 yrs ago to learn why this would not have worked. I don't have time to go back to remedial basics with you over and over again. mike > > Anycast for instance. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. >
Received on Wednesday, 2 July 2014 14:18:19 UTC