On Thu, May 04, 2017 at 01:21:43PM -0700, Colm MacCárthaigh wrote: > On Thu, May 4, 2017 at 12:39 PM, Nico Williams <n...@cryptonector.com> > wrote: > > The SHOULD should say that the server-side needs to apply a replay cache > > OR fallback onto a full exchange when the 0-rtt data payload involves a > > non-idempotent operation. > > I don't mean to be dismissive with this but TLS stands for "Transport Layer > Security". The transport layer just isn't aware of what the operations are, > and whether then can be idempotent (99% of the time, the answer is "no"). > Only the application can tell, but this violation of layers is what leads > to so many problems. I don't think it's workable.
I don't mean to be dismissive, but it doesn't matter what "TLS" stands for. It does what we make it do via Standards Action at the IETF. We follow our rules for everything to do with development of Internet Standards and publication of Experimental, Informational and BCP RFCs. We have a process. If you don't like what we're doing, you can voice your opinion. If you don't like the outcome of consensus calls and/or IESG decisions, you can appeal those. Thanks, Nico -- _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
