Re: [TLS] (draft) WG adoption call: draft-bmoeller-tls-falsestart

[Bodo Moeller <[e-mail]>]

Paul Hoffman <[e-mail]>:


> > There’s been some interested expressed in having
> http://datatracker.ietf.org/doc/draft-bmoeller-tls-falsestart/ adopted as
> a TLS WG item.  If you would like for this draft to become a WG document,
> and you are willing to review drafts as it moves through the process please
> indicate as much on this thread.  If you are opposed to this being a WG
> document, please say so (and say why). Thanks in advance.
>


> If the adopted draft becomes clearer that it is for TLS 1.2 (and possibly
> 1.1) only, but not for 1.3 (since we don't know what that will look like),
> I support its adoption.
>

Right, it makes complete sense to update the document to capture existing
deployment: in particular, explicitly exclude TLS 1.3 from its scope (not
just because we don't know what TLS 1.3 will look like but also because TLS
1.3 can speak for itself), and remove server-side False Start unless we
find any implementations.

(I'm not sure that we have to explicitly *disallow* False Start for
versions below TLS 1.2 as Brian Smith has suggested. After all, servers may
still encounter it with older clients, so that's a part of the reality of
existing deployments. The current *recommendation* could be made stronger,
though.)

Bodo