Re: [TLS] TLS Charter Revision

Time to first byte is extremely important to web content - so any kind of
latency-scaled overhead is viewed as a serious cost. TLS induced latency is
one factor that currently weighs against deploying content over https:// --
That is a dynamic most on this list would like to change I am sure.

Reducing setup overhead of all types is vitally important to that
constituency. That's not just assertion - we see that reflected (sometimes
indirectly) in ongoing efforts such as false start, snap start, stapling,
session tickets, iw 10, tcp fast open, http/2, tail loss probe, and quic.

A robust discussion can be had about cost-benefits of various approaches to
RTT elimination, but the demand side of the ledger should be clear.

On Thu, Dec 12, 2013 at 10:33 AM, Michael Sweet <msweet@apple.com> wrote:

> FWIW, one of the big features of HTTP/2.0 is the ability to run multiple
> simultaneous requests over a single connection which mitigates most of the
> effects of extra RTT. What's left is the initial connection setup time -
> important for benchmarks, perhaps, but definitely down in the noise for
> most web pages...
>
>
> On Dec 12, 2013, at 10:22 AM, Salz, Rich <rsalz@akamai.com> wrote:
>
> > I agree with Marsh that PFS should be included.
> >
> > I am concerned about the 'political' emphasis on reducing round trips.
> One of the arguments heard I hear against 'https everywhere' is that the
> extra round-trips' cause too much latency and impact customer's web
> experience. If we can work to reduce RTT without sacrificing security, then
> that's great and I would like to see "while maintaining security features"
> or some such added.
> >
> > I would like to add a bullet that says backward compatibility with
> previous  versions is not a requirement. Given all that downgrade fallback
> issues that continually arise here, we should strongly consider if the
> right thing to do is just break the chain.
> >
> >       /r$
> >
> > --
> > Principal Security Engineer
> > Akamai Technology
> > Cambridge, MA
> >
> > _______________________________________________
> > TLS mailing list
> > TLS@ietf.org
> > https://www.ietf.org/mailman/listinfo/tls
>
> _______________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>