- From: Ryan Hamilton <rch@google.com>
- Date: 2013年8月29日 09:18:13 -0700
- To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
- Cc: Mike Belshe <mike@belshe.com>, Michael Welzl <michawe@ifi.uio.no>, William Chan <willchan@google.com>, Yoav Nir <ynir@checkpoint.com>, HTTP Working Group <ietf-http-wg@w3.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
- Message-ID: <CAJ_4DfR=pZQQDjgvFdc6uGX-BZqnsENgUPJ9NzFDDjb7bCQ+rA@mail.gmail.com>
On Thu, Aug 29, 2013 at 8:40 AM, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote: > None of this is a goal. I like to understand which services/features/properties > are considered to be useful or required by the HTTP people. Then we can see > which protocol fits best (maybe TCP, maybe TCP Minion, maybe SCTP with extensions, > maybe QUIC, maybe something which doesn't exist yet). Evaluation at this > step really requires prototyping. I agree completely here. >> >> Useful goals would be: >> - making web pages load 10x faster >> - making servers that scale to 1B users >> - making the web accessible to more 10x people >> - eliminating privacy leaks, phishing scams, etc > I agree to all of them. But we have to find a way from these goals to > technical features of the protocols... Perhaps the best way to do this is to build a protocol and demonstrate that it achieves these goals? Cheers, Ryan
Received on Thursday, 29 August 2013 16:18:40 UTC