A Readable Specification of TLS 1.3

To be clear, it doesn&#x27;t look like this is written any different from the actual RFC, just formatted and organized more nicely.<p>For actually understanding the RFCs, I&#x27;ve found it useful to crack open wireshark and then look at an actual TLS connection, and then cross reference the RFC to figure out what&#x27;s going on. It makes everything more concrete in my opinion.

If this is something you are interested in, but you are looking for a slightly higher-level intro to TLS, albeit TLS 1.2, I highly recommend reading through <a href="http:&#x2F;&#x2F;blog.fourthbit.com&#x2F;2014&#x2F;12&#x2F;23&#x2F;traffic-analysis-of-an-ssl-slash-tls-session" rel="nofollow">http:&#x2F;&#x2F;blog.fourthbit.com&#x2F;2014&#x2F;12&#x2F;23&#x2F;traffic-analysis-of-an-...</a>.

I&#x27;ll never understand why rfc&#x27;s, arguably the underpinnings of internet technology, are styled to appear as TYPEWRITTEN pages in HTML. Seriously. Literal pages of typewritten text, on the web.<p>I mean, they take significant effort to devise these standards and write them up, presumably with modern tools, AND THEN force weird typewriter CSS upon them? It looks awful. I can&#x27;t understand it.

this is a good reference.