[Leaving this discussion out of the bug report, as it has no place
there, since it has nothing to do with the bug.]
On Sat, Jun 20, 2009 at 10:09:53AM -0000, Mutt wrote:
> Replying to [comment:7 Derek Martin]:
> > It is likewise explicitly allowed in RFCs 2822, and 822, and 733.
> >
> > Note that 822 and 733 are standards; the more recent ones are not (not
> > that it matters in this case).
>
> No, RFC 2822 is a ''proposed standard'' therefore '''is a standard'''.
The language you quoted is poorly phrased and contradicts other IETF
documentation; not everyone who writes RFCs does a good job (which is
yet another very good reason not to take RFCs as gospel).
A proposed standard is just that: proposed. It is not a standard
until it is *accepted* and "elevated" by the IETF. Proposed, Draft,
and Internet Standards are 3 levels of maturity of specifications
written with the *intent* of becoming standards (i.e. Internet
Standards). A proposed standard is expected to change, as is a draft
standard (though to lesser degree). The IETF's document BCP 9
explains in much greater detail what the maturity levels describe, and
states (in section 4, "The Internet Standards Track"):
Specifications that are intended to become Internet Standards
evolve through a set of maturity levels known as the "standards
track". These maturity levels -- "Proposed Standard", "Draft
Standard", and "Standard" -- are defined and discussed in section
4.1.
The IETF herein acknowledges that such specifications are *intended*
to become standards (but are not yet, necessarily). It also states
(sec 4.1.3, "Internet Standard"):
A specification for which significant implementation and
successful operational experience has been obtained may be
elevated to the Internet Standard level. An Internet Standard
(which may simply be referred to as a Standard) is characterized
by a high degree of technical maturity and by a generally held
belief that the specified protocol or service provides significant
benefit to the Internet community.
Only Internet Standards are Standards, as described therein, though in
common usage, we leave off the capital S, just as we commonly do with
the word calorie (calories printed on food packaging in the U.S. are
actually kilocalories, or Calories, but everyone just writes
calories, and many people don't even know that such a distinction
exists). The other two are just wannabe standards, they are not yet
approved to "Standard" state. RFC 2822 will likely never become a
standard, because it is obsoleted by later RFCs, which also are not
(yet) standards, and also may never be.
You can assume that, at least when *I* say it, "standard" means
Internet Standard. I was incorrect about one thing though; RFC 733 is
not a standard. RFC 822 is (STD 11).
--
Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address. Replying to it will result in
undeliverable mail due to spam prevention. Sorry for the inconvenience.
Attachment:
pgprf4ygMnUqM.pgp
Description: PGP signature