datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations
RFC 5863

Approval Announcement

Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    dkim mailing list <ietf-dkim@mipassoc.org>, 
    dkim chair <dkim-chairs@tools.ietf.org>
Subject: Document Action: 'DomainKeys Identified Mail (DKIM) Development, Deployment and Operations' to Informational RFC

The IESG has approved the following document:

- 'DomainKeys Identified Mail (DKIM) Development, Deployment and 
   Operations '
   <draft-ietf-dkim-deployment-11.txt> as an Informational RFC


This document is the product of the Domain Keys Identified Mail Working Group. 

The IESG contact persons are Pasi Eronen and Tim Polk.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dkim-deployment-11.txt
Technical Summary

   This document provides implementation, deployment, operational and
   migration considerations for DKIM.

Working Group Summary

   There are several areas where the document could provide more
   guidance, but the WG decided that more field experience is needed
   before we know what the guidance should be.

Document Quality

   This document gives guidance on implementation based on experience
   of participants and vendors who have already implemented the DKIM
   protocols.  The document has been well reviewed by participants
   with implementation/deployment experience.

Personnel

   The document shepherd is Barry Leiba, and the responsible area
   director is Pasi Eronen.

RFC Editor Note

   Please add a new paragraph to Section 1, after the first paragraph:

   The reader is encouraged to read the DKIM Service Overview document
   [RFC5585] before this document. More detailed guidance about DKIM
   and ADSP can also be found in the protocol specifications [RFC4871],
   [RFC5617], and [RFC5672].