Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding email normalization statement #1448

Open
csieber opened this issue Nov 15, 2024 · 0 comments
Open

Regarding email normalization statement #1448

csieber opened this issue Nov 15, 2024 · 0 comments

Comments

@csieber
Copy link

csieber commented Nov 15, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant