IMHO The Encrypted field never was adequately specified. If 2026
criteria had been in effect when rfc 822 was published, 822 would have
had to been revised to remove Encrypted in order to move it to Draft.
so yes it's obsolete, but not because it was omitted from 2822. do you
have a status "fatally flawed"?
On Apr 30, 2004, at 10:08 AM, Graham Klyne wrote:
In response to an off-list comment, I'm making a small revision of the
mail message header registry draft [1] to mark header fields defined
in RFC822 (as well as RFC2822) as standard rather than just
"standards-track". This raised two questions:
1. Are there any other mail header fields that have achieved full
standard status?
2. RFC2822 dropped the "Encrypted" header field which was defined in
RFC822. I take that to mean it is regarded as obsolete; would this
be correct? My current proposed entry for this is:
[[
<http://id.ninebynine.org/wip/2002/IETF/HeaderField#Encrypted>
a hdr:HeaderField ;
hdr:fieldName "Encrypted" ;
hdr:label "Message encryption information" ;
hdr:protocol hdr:Protocol_mail ;
hdr:status "obsolete" ;
hdr:author hdr:Author_IETF ;
hdr:controller hdr:Author_IETF ;
hdr:specification hdr:RFC822 ;
hdr:comment
"""Defined by RFC 822, but removed in RFC 2822.
Current practice is to use separate encryption, such
as S/MIME or OpenPGP, possibly in conjunction with
RFC 1847 MIME security multiparts.
""" .
]]
#g
--
[1] http://www.ietf.org/internet-drafts/draft-klyne-hdrreg-mail-04.txt
------------
Graham Klyne
For email:
http://www.ninebynine.org/#Contact