BoringSSL and OpenSSL have are draft versions which use different version
numbers from the final RFC, so as not to collide. Early experimental
deployment is generally useful to help inform the final standard and flush
out any non-compliant TLS 1.2 implementations that may cause deployment
difficult
The IESG has approved the draft, but it still needs to complete the RFC editor
phase where copy editing, changing of the boilerplate, assigning an RFC #, etc
gets done to make it an RFC. You can see the RFC editor’s queue here:
https://www.rfc-editor.org/current_queue.php
spt
> On May 3, 2018
