W3C home > Mailing lists > Public > public-html@w3.org > December 2008

[Bug 6300] New: reference RFC 5322 instead of RFC 2822

From: <bugzilla@wiggum.w3.org>
Date: Thu, 11 Dec 2008 08:49:48 +0000
To: public-html@w3.org
Message-ID: <bug-6300-2495@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6300

           Summary: reference RFC 5322 instead of RFC 2822
           Product: HTML WG
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: mike@w3.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


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:

http://tools.ietf.org/html/rfc2822#section-3.2.4
http://tools.ietf.org/html/rfc5322#section-3.2.3

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) @
foo.com
<Hixie> meaning foo@foo.com
<Hixie> and then you can start introducing escapes and all kinds of stuff


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 11 December 2008 08:56:31 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:00 UTC