IETF Logo Mail Archive

[ietf-dkim] Urgent: draft-ietf-dkim-ssp-10 and RFC 5451

Barry Leiba <barryleiba@computer.org> Thu, 28 May 2009 13:48 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 4EAB83A6DD4 for <ietfarch-ietf-dkim-archive@core3.amsl.com>; Thu, 28 May 2009 06:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.116
X-Spam-Level:
X-Spam-Status: No, score=-2.116 tagged_above=-999 required=5 tests=[AWL=-0.139, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 eKJ4-GWulIcq for <ietfarch-ietf-dkim-archive@core3.amsl.com>; Thu, 28 May 2009 06:48:13 -0700 (PDT)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 184F23A6884 for <ietf-dkim-archive@ietf.org>; Thu, 28 May 2009 06:48:12 -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 n4SDm0Cr012787; Thu, 28 May 2009 06:48:06 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=mipassoc.org; s=k00001; t=1243518498; bh=usiDfY6RK1iWDIzNXV0Mn43Vta0=; h=MIME-Version:Date: Message-ID:From:To:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Content-Type: Content-Transfer-Encoding:Sender; b=OM/iueMHfgq31LGbYu4Tx7nf2rJAsS EoQGhOWG3y7R96ByyyEFMCPCLw57Dumc6sKfXYo4+pZO0oIb2TSF5WJ057Kkr4fwti0 ydJrzjrrucEVK/HrtI8rzCdWuP2UkhrrchJBBliReBFmFtCC3cqD6FOyVemr6VoEIN8 DrU87bs=
Received: from mail-fx0-f214.google.com (mail-fx0-f214.google.com [209.85.220.214]) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n4SDlrkU012781 for <ietf-dkim@mipassoc.org>; Thu, 28 May 2009 06:47:58 -0700
Authentication-Results: sbh17.songbird.com; dkim=pass (1024-bit key) header.i=@gmail.com
Received: by fxm10 with SMTP id 10so5427044fxm.3 for <ietf-dkim@mipassoc.org>; Thu, 28 May 2009 06:47:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.163.5 with SMTP id n5mr115254hbd.18.1243518470231; Thu, 28 May 2009 06:47:50 -0700 (PDT)
Date: Thu, 28 May 2009 09:47:50 -0400
X-Google-Sender-Auth: 0d543f3a0779ff88
Message-ID: <6c9fcc2a0905280647n4d7b194cu889629bca2d26037@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: IETF DKIM WG <ietf-dkim@mipassoc.org>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (sbh17.songbird.com [127.0.0.1]); Thu, 28 May 2009 06:48:18 -0700 (PDT)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.70]); Thu, 28 May 2009 06:47:59 -0700 (PDT)
Subject: [ietf-dkim] Urgent: draft-ietf-dkim-ssp-10 and RFC 5451
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org

Pasi is putting draft-ietf-dkim-ssp-10 on the 4 June telechat.  But...

This version has added registry entries for RFC 5451
(Authentication-Results), which had been removed from that document to
avoid having its publication block on a reference-wait from ADSP.
Only, I can't find any discussion that the WG had about making that
change.

While I think this change will not likely fuel any controversy, we
can't publish this without having it approved by the working group.
So, ASAP, please:

1. If someone can find documentation of WG discussion about this, reply here.

2. If anyone objects to its inclusion (see sections 5.3 and 5.4 of
draft-ietf-dkim-ssp-10), reply here.

3. A few "Yes, adding this is groovy," messages would be good and all.

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

v2.23.0 | Report a Bug | By Email