iterate

changelogs/identity_service/newsfragments/3176.clarification

@@ -1 +1 @@
-Clarify that some identifiers may be case-folded to lowercase prior to processing, as per [MSC2265](https://github.com/matrix-org/matrix-doc/pull/2265).
+Clarify that some identifiers must be case folded prior to processing, as per [MSC2265](https://github.com/matrix-org/matrix-doc/pull/2265).

content/appendices.md

@@ -756,11 +756,11 @@ Represents E-Mail addresses. The `address` is the raw email address in
 other text such as real name, angle brackets or a mailto: prefix.
 
 In addition to lowercasing the domain component of an email address,
-implementations are expected to case fold the localpart as described
-in [the unicode mapping file](https://www.unicode.org/Public/8.0.0/ucd/CaseFolding.txt)
-prior to any processing. For example, `Strauß@Example.com` must be
-considered to be `strauss@example.com` while processing the email
-address.
+implementations are expected to apply the unicode case-folding algorithm
+as described under "Caseless Matching" in
+[chapter 5 of the unicode standard](https://www.unicode.org/versions/Unicode13.0.0/ch05.pdf#G21790).
+For example, `Strauß@Example.com` must be considered to be `strauss@example.com`
+while processing the email address.
 
 ### PSTN Phone numbers
 

proposals/2265-email-lowercase.md

@@ -23,8 +23,8 @@ Sydent.
 This proposal suggests changing the specification of the e-mail 3PID type in
 [the Matrix spec appendices](https://matrix.org/docs/spec/appendices#pid-types)
 to mandate that, before any processing, e-mail addresses must go through a full
-case folding based on [the unicode mapping
-file](https://www.unicode.org/Public/8.0.0/ucd/CaseFolding.txt), on top of
+case folding as described under "Caseless Matching" in
+[chapter 5 of the unicode standard](https://www.unicode.org/versions/Unicode13.0.0/ch05.pdf#G21790), on top of
 having their domain lowercased.
 
 This means that `Strauß@Example.com` must be considered as being the same e-mail