Protocol Action: 'DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 24 June 2009 22:11 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 2804328C0E9; Wed, 24 Jun 2009 15:11:16 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)' to Proposed Standard
Message-Id: <20090624221117.2804328C0E9@core3.amsl.com>
Date: Wed, 24 Jun 2009 15:11:17 -0700
Cc: Internet Architecture Board <iab@iab.org>, dkim mailing list <ietf-dkim@mipassoc.org>, dkim chair <dkim-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jun 2009 22:11:17 -0000

The IESG has approved the following document:

- 'DomainKeys Identified Mail (DKIM) Author Domain Signing Practices 
   (ADSP) '
   <draft-ietf-dkim-ssp-10.txt> as a Proposed Standard

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-ssp-10.txt

Technical Summary

   DomainKeys Identified Mail (DKIM) defines a domain-level
   authentication framework for email to permit verification of the
   source and contents of messages.  This document specifies an
   adjunct mechanism to aid in assessing messages that do not contain
   a DKIM signature for the domain used in the author's address.  It
   defines a record that can advertise whether a domain signs its
   outgoing mail, and how other hosts can access that record.

Working Group Summary

   draft-ietf-dkim-ssp-07 is the 8th official WG draft, following on
   from 3 iterations of an individual submission draft-allman-dkim-ssp
   with the -00 version dating back to January 2006. The current draft
   has passed WGLC with solid support in the DKIM WG. Some minor
   editorial changes were make post-WGLC based on (a few) comments
   received on the -05 draft.  The DKIM WG used the rt.psg.com tracker
   for its work (queue=dkim) and processed O(50) issues for this
   document over the period.

Document Quality

   The document has undergone thorough review in the WG resulting in
   various revisions, typically removing features or renaming elements
   of the protocol, however, the basic core feature of ADSP has
   remained stable all through the process.

Personnel

   Stephen Farrell (stephen.farrell@cs.tcd.ie) is the document
   shepherd. The responsible AD is Pasi Eronen.

RFC Editor Note

   Please make the following two changes:

   Section 4.2.1:
   OLD:
     adsp-dkim-tag = %x64.6b.69.6d *WSP "=" *WSP
                     ("unknown" / "all" / "discardable")
   NEW:
     adsp-dkim-tag = %x64.6b.69.6d *WSP "=" *WSP
                     ("unknown" / "all" / "discardable" /
                      x-adsp-dkim-tag)
     x-adsp-dkim-tag = hyphenated-word   ; for future extension
     ; hyphenated-word is defined in RFC 4871

   Section 4.1:
   OLD:
      Note:   Domains MUST NOT publish ADSP records with wildcard names.
         Wildcards within a domain publishing ADSP records pose a
         particular problem, as discussed in more detail in Section 6.3.
   NEW:
      Domains MUST NOT publish ADSP records with wildcard names.
      Wildcards within a domain publishing ADSP records pose a particular
      problem, as discussed in more detail in Section 6.3.