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

Dave CROCKER <dhc@dcrocker.net> Tue, 23 August 2011 01:02 UTC

Return-Path: <dhc@dcrocker.net>
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 7551021F8565 for <yam@ietfa.amsl.com>; Mon, 22 Aug 2011 18:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.359
X-Spam-Level:
X-Spam-Status: No, score=-6.359 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 We00MwCme8Li for <yam@ietfa.amsl.com>; Mon, 22 Aug 2011 18:02:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CF8ED21F8563 for <yam@ietf.org>; Mon, 22 Aug 2011 18:02:13 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7N13Eiq017686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <yam@ietf.org>; Mon, 22 Aug 2011 18:03:20 -0700
Message-ID: <4E52FC51.90603@dcrocker.net>
Date: Mon, 22 Aug 2011 18:03:13 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: yam@ietf.org
References: <6.2.5.6.2.20110822151213.0aea6018@elandnews.com> <01O55Q930Q4A00VHKR@mauve.mrochek.com> <4E52F947.7020200@qualcomm.com>
In-Reply-To: <4E52F947.7020200@qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 22 Aug 2011 18:03:20 -0700 (PDT)
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
Reply-To: dcrocker@bbiw.net
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 01:02:14 -0000

On 8/22/2011 5:50 PM, Pete Resnick wrote:
> On 8/22/11 6:52 PM, Ned Freed wrote:
>> 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.
>
> So, I hadn't considered the possibility of simply weakening the current language
> so it's strictly explanatory and had no 2119 language.

Indeed, it doesn't make much sense to have normative language for something that 
is merely highlighting an issue and encouraging attention to it.

Perhaps:


     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.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net