IETF Logo Mail Archive

Re: [ietf-822] A permission to re-sign header

Pete Resnick <presnick@qti.qualcomm.com> Sat, 19 April 2014 22:58 UTC

Return-Path: <presnick@qti.qualcomm.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 66D831A0102 for <ietf-822@ietfa.amsl.com>; Sat, 19 Apr 2014 15:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.673
X-Spam-Level:
X-Spam-Status: No, score=-1.673 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
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 sUHZ3TPaxjfL for <ietf-822@ietfa.amsl.com>; Sat, 19 Apr 2014 15:58:03 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 920C51A00D3 for <ietf-822@ietf.org>; Sat, 19 Apr 2014 15:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397948279; x=1429484279; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=pKuo+7yrc+OhxN1b8AiCugiiSAyAIPUetHpuDnYHBXs=; b=iInhPIhiTZqvMKQ4dRh/SREmk7d5E/ONse6bde0aHojzGo8RU1S+dvkq 2H/FWKwK7/Qs07aVKvRcuNVCTbYFdWg526gmKWpo8RFGWLQo9++jW2juy 7Pl4RcsaPIeteKOz9A5GYIJGqbUZcgB+98fAu9p3YXkmoajSssBv8eCvb k=;
X-IronPort-AV: E=McAfee;i="5400,1158,7413"; a="62224086"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 19 Apr 2014 15:57:59 -0700
X-IronPort-AV: E=Sophos;i="4.97,890,1389772800"; d="scan'208";a="628186931"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Apr 2014 15:57:59 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 19 Apr 2014 15:57:58 -0700
Message-ID: <5352FF75.3020605@qti.qualcomm.com>
Date: Sat, 19 Apr 2014 17:57:57 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Theodore Ts'o <tytso@mit.edu>
References: <20140418021925.2979.qmail@joyce.lan> <53516FA7.3020507@qti.qualcomm.com> <alpine.BSF.2.00.1404181500430.5575@joyce.lan> <6411.1397912723@sandelman.ca> <20140419155241.GD31552@thunk.org>
In-Reply-To: <20140419155241.GD31552@thunk.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/rtyQ8CM_OuK8oPwhrs03REOci-8
Cc: ietf-822@ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: [ietf-822] A permission to re-sign header
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: Sat, 19 Apr 2014 22:58:04 -0000

On 4/19/14 10:52 AM, Theodore Ts'o wrote:

> There are mailing lists that want to "fix" broken messages, yes, but
> if we need to provide end-to-end assurance that the message really
> came from the originator...
>    

Providing end-to-end assurance that the message really came from the 
originator is not the stated goal. It would be nice if we could do that, 
but so far there are operational and deployment problems with 
accomplishing that. I've got ideas about how we might improve that 
situation, but they will take much longer to deploy than the things we 
are talking about here.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

v2.23.0 | Report a Bug | By Email