Can we start sending multipath frames earlier?

[flub]

quinn_proto::Connection::is_multipath_enabled strictly wants the handshake to be completed. However the server knows multipath is successfully negotiated earlier, it processes the peer transport parameters after it has written the handshake packet (but before it is sent!). It then also calls Connection::issue_first_cids which are sent in NEW_CONNECTION_ID frames in a Data-packet space right after the Handshake packet is sent.

Only once the server has received the client's Handshake packet does it consider the handshake fully completed and will it start issuing PATH_NEW_CONNECTION_ID frames for all outstanding paths.

This seems needlessly late. I wonder if the text of when you can start sending these frames from the spec was misinterpreted. There seems very little harm for the server to start sending the PATH_NEW_CONNECTION_ID frames right after the Handshake packet is sent, at the time it currently sends NEW_CONNECTION_ID frames.