diff --git a/draft-ietf-cose-hash-envelope.md b/draft-ietf-cose-hash-envelope.md
index 99aae7b..8854ab3 100644
--- a/draft-ietf-cose-hash-envelope.md
+++ b/draft-ietf-cose-hash-envelope.md
@@ -43,6 +43,10 @@ normative:
 
 informative:
   BCP205:
+  RFC8032:
+  FIPS-204:
+    title: "Module-Lattice-Based Digital Signature Standard"
+    target: https://doi.org/10.6028/NIST.FIPS.204
 ---
 
 --- abstract
@@ -181,6 +185,9 @@ TODO Security
 
 It is RECOMMENDED to align the strength of the chosen hash function to the strength of the chosen signature algorithm.
 For example, when signing with ECDSA using P-256 and SHA-256, use SHA-256 to hash the payload.
+It is also possible to use this specification with signature algorithms that support pre-hashing such as Ed25519ph which is described in {{RFC8032}}, or HashML-DSA which is described in {{FIPS-204}}.
+Note that when using a pre-hash algorithm, the algorithm SHOULD be registered in the IANA COSE Algorithms registry, and should be distinguishable from non-pre hash variants that may also be present.
+The approach this specification takes is just one way to perform application agnostic pre-hashing, meaning the pre hashing is not done with binding or confisderation for a specific application context, while preforming application (cose) specific signing, meaning the to be signed bytes include the cose structures necessary to distinguish a cose signature from other digital signature formats.
 
 # IANA Considerations