On 19/05/16 02:16, Alia Atlas wrote:
> Alia Atlas has entered the following ballot position for
> draft-ietf-tls-falsestart-02: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tls-falsestart/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> For Stephen, yes, I noticed :-)

Great. Sean's is better though:-)

> 
> In support of Kathleen's comment and based on the shepherd's write-up,
> why is this experimental and what is
> the experiment?

There's no good answer, sorry. I knew folks would ask, so I asked
the WG and it seems to me to be a case that nobody cares really so
they just picked one and aren't much energised to talk more about
it. That's not too unreasonable. See the thread at [1] for some
more.

Given that this is widely deployed and a similar feature is being
included in TLS1.3, there is no real experiment here, what the WG
care about is that this RFC be not-PS I reckon.

S.

[1] https://mailarchive.ietf.org/arch/msg/tls/UDiFtVrQhjP9MXMW45tiYHrCDn8

> 
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
> 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to