Magic

Co-authored-by: Jana Iyengar <jri.ietf@gmail.com>

draft-ietf-quic-transport.md

@@ -1928,9 +1928,10 @@ consider the peer address to have been validated.
 
 Additionally, an endpoint MAY consider the peer address validated if the peer
 uses a connection ID chosen by the endpoint and the connection ID contains at
-least 64 bits of entropy.  For the client, the value of the Destination
-Connection ID field in its first Initial packet also fulfills this requirement,
-such that successfully processing any packet validates the server address.
+least 64 bits of entropy. A client can consider the server address validated on
+successfully processing any packet received from the server, since for
+encrypting its Initial packets, the server uses the Destination Connection ID
+field from the client's first Initial packet; see Section 5.2 of {{QUIC-TLS}}.
 
 Prior to validating the client address, servers MUST NOT send more than three
 times as many bytes as the number of bytes they have received.  This limits the