Re: [ietf-822] We need a DKIM Policy Working Group

S Moonesamy <sm+ietf@elandsys.com> Wed, 30 April 2014 18:27 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6863D1A6FFF for <ietf-822@ietfa.amsl.com>; Wed, 30 Apr 2014 11:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i0CaP_0QHVk3 for <ietf-822@ietfa.amsl.com>; Wed, 30 Apr 2014 11:27:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 314851A096B for <ietf-822@ietf.org>; Wed, 30 Apr 2014 11:27:02 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.232.234]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3UIQl8p021967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Apr 2014 11:26:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398882419; bh=URxv0YBYejTLF8jV/GAZe/OjDuDkrfkm2ONKz51I2Po=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qMW+WSIwJNTGPJN9LsFJ6C+pMALTg4jnVgz/kG0Qi+z9Ku6XiRcdqxSpSBHh/RAOm lXWzH8hbWzkEEYs/OuMcd3ZvhknBLji0E9NBtry47R4xRWabs4xqW8kFN8ks+DvMBJ 9fh0RTMBQGvoB3C4IEezKM8GCb2Ek/W0fIpaDVbI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398882419; i=@elandsys.com; bh=URxv0YBYejTLF8jV/GAZe/OjDuDkrfkm2ONKz51I2Po=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CkPtZOCn0jduGR6CgBxIjjB6HqX8xdGKHMrmwAlS3Z7p3J1rFz0evQTzv/K/XZoyA CP+0RUDW1BlroOtFk3MvjM6Jjy5nYUevrKz7Ahje6YmeFOWZUiHQS/nutMbRmKovpF cNiC3AVROBvHs4f6MK9oyt+2pD2GoPwCOOj4Kfto=
Message-Id: <6.2.5.6.2.20140430111450.0bb39aa0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Apr 2014 11:23:21 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <53613CA8.1090003@isdg.net>
References: <535646AA.2080400@pscs.co.uk> <20140422202403.42908.qmail@joyce.lan> <01P6Y9IJSOEG000052@mauve.mrochek.com> <535B8B07.6090307@tana.it> <01P73EQM1PKQ000052@mauve.mrochek.com> <535BED95.6090304@tana.it> <01P73LU0RT9I000052@mauve.mrochek.com> <53611CCE.3010302@qti.qualcomm.com> <53613CA8.1090003@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/WVwRNTPUMv3wgfxsCO9QcLBsB64
Cc: ietf-822@ietf.org
Subject: Re: [ietf-822] We need a DKIM Policy Working Group
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 18:27:03 -0000

Hi Hector,
At 11:10 30-04-2014, Hector Santos wrote:
>If you are talking about a resigner kludge that could bypass policy, 
>then I am against that.  Any solution must be permission based. I 
>believe that may have been your first design assumption.
>
>I suggest spinning up a DKIM POLICY working group to begin updating:
>
>      RFC5016 Requirements for a DKIM Signing Practices Protocol
>      http://tools.ietf.org/html/rfc5016
>
>We need to revisit and reconfirm what are the possible policies. 
>What predictably started this mess was the last minute inclusion of 
>section 5.3, item 10:

The steps for setting up such a working group would be:

   1. Someone writes a draft charter

   2. A group of people agree to that draft charter

   3. Contact relevant Area Director for next steps

I would not volunteer to write the draft charter as I don't want that headache.

Regards,
S. Moonesamy