Comment on https://bugs.openjdk.java.net/browse/JDK-8145252 - TLS 1.3 formally adopted by IETF

Sean Mullan sean.mullan at oracle.com
Wed Mar 28 19:55:31 UTC 2018


I also made a similar change to the Risks and Assumptions section of the 
JEP.

--Sean

On 3/28/18 3:47 PM, Bradford Wetmore wrote:
> 
> On 3/28/2018 11:46 AM, R Wagner wrote:
>> I was wondering if it was possible to update this issue and make a 
>> comment that TLS 1.3 has been formally adopted.
> 
> I just added a quick comment.
> 
>  > See:
>>
>> IETF approves TLS 1.3
> 
> Just FYI:  the TLS 1.3 spec[1] still has a few more steps to go before 
> it is issued as a RFC, but the technical work is "essentially" done and 
> has been approved by the IESG.
> 
> It's currently in the RFC Editor's[2] Queue[3] for final editing, and 
> there's some IANA work (Section 11) that is still ongoing.  (BTW, at 156 
> pages, it's the longest document currently in the queue! )
> 
> The RFC Editor's FAQ says it's typically 1-2 months from this stage to 
> issuance of the RFC, but actual time varies greatly[5].
> 
> Brad
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-tls-tls13/
> [2] https://datatracker.ietf.org/help/state/draft/rfceditor
> [3] https://www.rfc-editor.org/pubprocess/
> [4] https://www.rfc-editor.org/current_queue.php?sortkey=6&sorting=ASC
> [5] https://www.rfc-editor.org/faq/#howlong
> 
> 


More information about the security-dev mailing list