Regarding email normalization statement

[csieber]

In https://google.aip.dev/129#rationale-for-normalizations it is stated:

For the email [email protected] a client may choose to specify [email protected], [email protected], or [email protected]. These are semantically identical and should all be accepted by the service. The service then may choose to normalize the email address for storage and retrieval through downcasing or canonicalization.

Considering this is up to the provider to decide the statement seems dangerous. That is not common but I would guess there are systems out there making that distinction. RFC5321 [1] states :

The local-part of a mailbox MUST BE treated as case sensitive.

[1] https://datatracker.ietf.org/doc/html/rfc5321#section-2.4

[noahdietz]

Hi @csieber thanks for the issue. Looking back at AIP-129, we don't even have a format for email defined in AIP-202, so I think we should 1. remove the item from the list of example formats and 2. change the example in the rationale since it is not a supported format and the example is fraught, as you point out.

If you're up for sending a PR, it would be appreciated! Sorry for the delayed response.

cc @slevenick