[ietf-dkim] Protocol Action: 'DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)' to Proposed Standard

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

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3880B3A6FFF for <ietfarch-ietf-dkim-archive@core3.amsl.com>; Wed, 24 Jun 2009 16:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N7OJjvR3bgqW for <ietfarch-ietf-dkim-archive@core3.amsl.com>; Wed, 24 Jun 2009 16:11:28 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7147]) by core3.amsl.com (Postfix) with ESMTP id 84EDD3A6FFA for <ietf-dkim-archive@ietf.org>; Wed, 24 Jun 2009 16:11:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [127.0.0.1]) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n5ON91qZ006687; Wed, 24 Jun 2009 16:09:14 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=mipassoc.org; s=k00001; t=1245884971; bh=bgtl4tmFQuGqvFDCx3qCOmliHm8=; h=From:To:Message-Id: Date:Cc:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:MIME-Version:Content-Type: Content-Transfer-Encoding:Sender; b=YLUdnjfYJlaIqHt8uY7SHTx1iR0g1d L579pPCN/GYt5YPJcvhI60WEuc8ar6wHbTSjPh7xOg8kpnnVMKpZKuDDYtHgaVMVwNO EznGXyxv9R3ebddWC42M2gLAw2j+oJN0xwn6N7Yi10FViJytHOnJb4FrzbU05Jq6lR9 4jnmlGE=
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20]) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n5ON8sFL006677 for <ietf-dkim@mipassoc.org>; Wed, 24 Jun 2009 16:09:00 -0700
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>
Message-Id: <20090624221117.2804328C0E9@core3.amsl.com>
Date: Wed, 24 Jun 2009 15:11:17 -0700
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (sbh17.songbird.com [127.0.0.1]); Wed, 24 Jun 2009 16:09:31 -0700 (PDT)
X-Greylist: Delayed for 00:57:17 by milter-greylist-4.0 (sbh17.songbird.com [IPv6:2001:470:1:76:0:ffff:4834:7146]); Wed, 24 Jun 2009 16:09:00 -0700 (PDT)
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>
Subject: [ietf-dkim] Protocol Action: 'DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)' to Proposed Standard
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org

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.

_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html