diff --git a/chrysn-overhaul/draft-ietf-core-transport-indication.html b/chrysn-overhaul/draft-ietf-core-transport-indication.html
index 563c717..67cf1d1 100644
--- a/chrysn-overhaul/draft-ietf-core-transport-indication.html
+++ b/chrysn-overhaul/draft-ietf-core-transport-indication.html
@@ -3240,6 +3240,12 @@
The client may then decide to discontinue using the proxy,
or to use more extensive padding options to sidestep the attack.
Both the client and the server may alert their administrators of a possible traffic misdirection.¶
+
[ While using an EDHOC EAD is suitable for connection setup,
+ such a mechanism may also be useful at a later time,
+ eg. to re-check a server's address after a name change;
+ establishing an equivalent CoAP option is being considered,
+ also oin light of the discussion around https://github.com/core-wg/corrclar/pull/40 and https://github.com/core-wg/groupcomm-proxy/issues/3.
+ ]¶
diff --git a/chrysn-overhaul/draft-ietf-core-transport-indication.txt b/chrysn-overhaul/draft-ietf-core-transport-indication.txt
index 5cc5d40..8864f77 100644
--- a/chrysn-overhaul/draft-ietf-core-transport-indication.txt
+++ b/chrysn-overhaul/draft-ietf-core-transport-indication.txt
@@ -1971,6 +1971,13 @@ Appendix D. EDHOC EAD for verifying legitimate proxies
and the server may alert their administrators of a possible traffic
misdirection.
+ [ While using an EDHOC EAD is suitable for connection setup, such a
+ mechanism may also be useful at a later time, eg. to re-check a
+ server's address after a name change; establishing an equivalent CoAP
+ option is being considered, also oin light of the discussion around
+ https://github.com/core-wg/corrclar/pull/40 and https://github.com/
+ core-wg/groupcomm-proxy/issues/3. ]
+
Appendix E. Literals beyond IP addresses
[ This section is placed here preliminarily: After initial review in