This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6300 - [references] reference RFC 5322 instead of RFC 2822
Summary: [references] reference RFC 5322 instead of RFC 2822
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P5 trivial
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2008-12-11 08:49 UTC by Michael[tm] Smith
Modified: 2010-10-04 14:31 UTC (History)
5 users (show)

See Also:


Description Michael[tm] Smith 2008-12-11 08:49:46 UTC
The HTML5 draft currently references RFC 2822 in order to define what a "valid e-mail address" is.

"A valid e-mail address is a string that matches the production dot-atom "@" dot-atom where dot-atom is defined in RFC 2822 section 3.2.4, excluding the CFWS production everywhere. [RFC2822]".

A newer RFC, RFC 5322, is intended to obsolete RFC 2822.
The "dot-atom" production seems to be define identically in RFC 5322 and RFC 2822:

Also, just for the record, some notes about why the HTML5 draft doesn't just reference the "addr-spec" production instead of dot-atom "@" dot-atom:

<Hixie> addr-spec doesn't match user expectations
<Hixie> e.g. iirc something like this matches addr-spec:    "foo" (bar) @
<Hixie> meaning
<Hixie> and then you can start introducing escapes and all kinds of stuff
Comment 1 Julian Reschke 2008-12-30 16:08:20 UTC
"A newer RFC, RFC 5322, is intended to obsolete RFC 2822."

Nit: it *does* obsolete RFC2822.
Comment 2 Maciej Stachowiak 2010-03-14 13:16:01 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.