Hello,
Thanks for your work on draft-ietf-tls-record-limit. I just requested
IETF last call, so that should start soon. The draft looks ready to
go, I'm just wondering if you could add in text into the introduction
to state the level of constrained device this is intended to help?
If text is ad
The difference here is that this LC includes all of the downrefs according to
the process described in [0]. Including the downward references to
non-stardards track RFCs will ensure we’re not delayed due to process issues.
Most of these are as a result of how we publish algorithm drafts, i.e.,
The IESG has received a request from the Transport Layer Security WG (tls) to
consider the following document: - 'The Transport Layer Security (TLS)
Protocol Version 1.3'
as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. P
Reviewer: Rich Salz
Review result: Ready
I have discovered an elegant little proof that shows TLS 1.3 is not secure,
unfortunately I do not have the room to fit it in this textbox. I will send
email tomorrow...
No, seriously, this protocol has been designed with the help of world-class
cryptogra
For those not steeped in IETF process, the IETF LC is two weeks. IETF LC also
kicks off the directorate review process; we are likely to receive General Area
and Transport Areas as well as our own Security Directorate review; you can see
the reviews on this page
(https://datatracker.ietf.org/d
