Considerations for DKIM Policy Language
draft-hallambaker-pcon-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Phillip Hallam-Baker | ||
| Last updated | 2006-06-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
If we are going to change the current DKIM policy language as deployed in any way including definition of a new DNS RR we should do the job properly and define a layered infrastructure that is capable of other uses.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)