Re: [yam] AD DISCUSS about Section 8 of draft-ietf-yam-rfc4409bis-02 - Message Modifications

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 23 August 2011 08:51 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: yam@ietfa.amsl.com
Delivered-To: yam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D9821F86DD for <yam@ietfa.amsl.com>; Tue, 23 Aug 2011 01:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level:
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETxbXoFSm4Op for <yam@ietfa.amsl.com>; Tue, 23 Aug 2011 01:51:24 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 2947521F86B1 for <yam@ietf.org>; Tue, 23 Aug 2011 01:51:24 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TlNqTgALhBNH@rufus.isode.com>; Tue, 23 Aug 2011 09:52:30 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4E536A4D.4030600@isode.com>
Date: Tue, 23 Aug 2011 09:52:29 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20110822151213.0aea6018@elandnews.com> <4E52EBE4.9010700@dcrocker.net> <6.2.5.6.2.20110822212849.08fcabf8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20110822212849.08fcabf8@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: yam@ietf.org
Subject: Re: [yam] AD DISCUSS about Section 8 of draft-ietf-yam-rfc4409bis-02 - Message Modifications
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 08:51:24 -0000

S Moonesamy wrote:

> At 16:53 22-08-2011, Dave CROCKER wrote:
>
>> This is a pretty classic case of avoiding a problematic Discuss, 
>> through an easy expedient.
>
> If YAM WG participants view it as such a case, they can voice their 
> concern.
>
> At 16:52 22-08-2011, Ned Freed wrote:
>
>> See above - I think pointing out the possibility of client signatures is
>> important and the text should be retained, but without the compliance 
>> language. I think deleting it weakens the document and therefore I 
>> object to its total
>> removal. That said, I can live with it going if not removing it will 
>> prevent
>> the move to full standard.
>
> Ok.
>
> Dave suggested the following text:
>
>    "Message modification can affect the validity of an existing message
>     signature, such as by DKIM [DKIM], PGP [RFC4880], and can render the
>     signature invalid.  This, in turn, can affect message handling by 
> later
>     receivers, such as filtering engines that consider the presence or 
> absence
>     of a signature"
>
> As an individual comment, the "that consider ..." could be dropped as 
> the text mentions that validity can affect message handling.
>
> Dave and Ned are in favor of including some text and Pete is for 
> removal.  I would appreciate some more feedback.

I am against removing the text, as it will be a disservice to the 
community. I am Ok with weakening it and possibly adding examples. 
Dave's suggestion looks good to me.