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

Clarify how non-ASCII email addresses should be handled #67

Closed
theall38103 opened this issue Apr 3, 2018 · 1 comment
Closed

Clarify how non-ASCII email addresses should be handled #67

theall38103 opened this issue Apr 3, 2018 · 1 comment
Labels
bug Software or schema defect Project:json format CVE JSON Data Exchange Format

Comments

@theall38103
Copy link
Contributor

The three state-specific schemas currently test that email addresses match the pattern "^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$". This won't work for IDNs (Internationalized Domain Names) or Emoji domains. Should the draft spec be updated to require addresses be transcoded to ASCII using Punycode, say?

@csj0 csj0 added bug Software or schema defect Project:json format CVE JSON Data Exchange Format labels May 24, 2018
@mprpic
Copy link
Collaborator

mprpic commented Apr 24, 2024

CVE v5 JSON schema does not include this pattern so I'm assuming this is obsolete. Closing!

@mprpic mprpic closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Software or schema defect Project:json format CVE JSON Data Exchange Format
Projects
None yet
Development

No branches or pull requests

3 participants