Re: [EAI] references, was Shepherd report review of mailinglist-02

["John Levine" <[e-mail]>]

I just submitted -04 which differs from -03 only in that there is a
new sentence in the introduction with a normative referenc to RFC
6530, which describes all the EAI stuff including SMTPUTF8 and
non-ASCII addresses in mail headers, and a normative reference to RFC
6068 which describes percent encoded addresses in mailto URIs.

R's,
John

PS: Since the point of a normative reference is that a reader is
expected to be familiar with the reference to understand the document,
I'm asuming that means that readers are familiar with the normative
references in the normative references and so forth.  So now that I've
added a reference to RFC 6530, you might want to reread RFC20, RFC791,
RFC821, RFC822, RFC974, RFC1034, RFC1035, RFC1047, RFC1123, RFC1305,
RFC1652, RFC1869, RFC1870, RFC1894, RFC1970, RFC2026, RFC2028,
RFC2033, RFC2034, RFC2045, RFC2046, RFC2048, RFC2119, RFC2192,
RFC2234, RFC2244, RFC2246, RFC2277, RFC2279, RFC2327, RFC2387,
RFC2396, RFC2434, RFC2460, RFC2554, RFC2743, RFC2782, RFC2821,
RFC2822, RFC2860, RFC2978, RFC3023, RFC3190, RFC3207, RFC3280,
RFC3339, RFC3454, RFC3461, RFC3462, RFC3463, RFC3464, RFC3501,
RFC3550, RFC3551, RFC3555, RFC3629, RFC3798, RFC3848, RFC3864,
RFC3885, RFC3886, RFC3887, RFC3888, RFC3986, RFC4013, RFC4234,
RFC4288, RFC4291, RFC4409, RFC4422, RFC4467, RFC4468, RFC4646,
RFC4647, RFC4648, RFC4954, RFC5198, RFC5226, RFC5234, RFC5248,
RFC5321, RFC5322, RFC5646, RFC5890, RFC6152, RFC6409, RFC6522,
RFC6531, RFC6532, RFC6533, ISO 639, NIST SHA-1, and the Apple AIFF-C
spec.