A "standard" "obsoleted" by a "proposed standard" or a "draft standard" is nonsense. A standard is obsoleted by a new standard, not a draft or a proposal. RFC 821-822 are still the standard, until their obsoleting drafts and proposals become the new standard, and are clearly identified as such.
Sent from ProtonMail Mobile On Sun, Feb 11, 2018 at 23:13, Antony Stone <antony.st...@spamassassin.open.source.it> wrote: > On Sunday 11 February 2018 at 23:04:52, Bill Cole wrote: > On 11 Feb 2018, at > 16:20 (-0500), Antony Stone wrote: > > Strange that I can't find SMTP under > > > www.rfc-editor.org/rfc/std/std-index.txt > > though, other than STD0060 > and STD0071, which are both extensions. > > STD10 is SMTP (RFC821), STD11 is > message format(RFC822). Ah, thank you. Stupid of me not to search for the > expansion of the abbreviation :) However, it's good to see confirmed that > STD0010 is "Obsoleted by RFC2821" and that STD0011 is "Obsoleted by RFC2822" > (and we already know that those have in turn been subsequently obsoleted), so > anyone still using RFC822 as the standard is just not recognising the reality > of how RFCs and Internet Standards work Antony. -- This sentence contains > exacly three erors. Please reply to the list; please *don't* CC me.
