Dave Crocker <[EMAIL PROTECTED]> writes:

> What is the reason for Historic, rather than Informational?
>
> I am prety sure that historic has never been applied to a specification that 
> was
> not previously an IETF standard.  The usual means of labeling an RFC that
> specifies a popular, proprietary protocol is Informational.

Maybe because the aim is that DKIM will obsolete DomainKeys with the
hope that implementations currently experimenting with DomainKeys will
'upgrade' to using DKIM.
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html

Reply via email to