More test cases for email format according to RFC-5321 section 4.1.2.

[gene-hightower]

No description provided.

[karenetheridge]

I have no opinion as to whether these new tests are correct. (FWIW, my implementation fails the last two - "invalid domain" and "invalid IPv4-address-literal"). However, before we merge, the tests should be added to all relevant drafts -- tests/draft*/optional/format/email.json.

[Julian]

My implementation will consider all of these to be valid, so I too have no real opinion -- this is a file in optional, and the spec allows implementations to decide whether they want to support email as a format via the exact RFC definition or some broader one -- if these merge, as an implementer I'd just skip all the ones marked invalid (so yeah I'm fine with merging these of course if others want them).

[gene-hightower]

I guess maybe I should double check which "draft" these tests should apply to? Maybe draft2019-09 is not correct, but draft2020-12 is?

[gene-hightower]

If fact, I think that is the case. The tests I think are valid for the 2020-12 draft (based on RFC-5321), but perhaps not other drafts (which may have had other advise)

[karenetheridge]

xref: #467