Additional Readme Text in Protocol Features
@@ -18,7 +18,13 @@ QUIC has many benefits when compared to existing TLS over TCP scenarios:
* Improved (compared to TCP) congestion control and loss recovery.
* Exchange application data in the first round trip (0-RTT).
* Survives a change in the clients IP address or port.
- * Easily extendable for new features (such as unreliable delivery).
+ * Easily extendable for new features and extensions.
+ * Unreliable application data.
+ * Stateless load balancing.
+
+> **Important** The QUIC spec is currently in IETF last call and should move to IESG review by Nov 2020. From there it will likely take a few months before it is finalized to RFC.
+
+Drafts: [Transport](https://tools.ietf.org/html/draft-ietf-quic-transport), [TLS](https://tools.ietf.org/html/draft-ietf-quic-tls), [Recovery](https://tools.ietf.org/html/draft-ietf-quic-recovery), [Datagram](https://tools.ietf.org/html/draft-ietf-quic-datagram), [Load Balancing](https://tools.ietf.org/html/draft-ietf-quic-load-balancers)
> **Important** Several QUIC protocol features are not yet fully implemented:
>
