IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Fri, 18 April 2014 19:06 UTC

Return-Path: <johnl@taugh.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 D31FF1A0454 for <ietf-822@ietfa.amsl.com>; Fri, 18 Apr 2014 12:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] 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 25JquJNq5vlk for <ietf-822@ietfa.amsl.com>; Fri, 18 Apr 2014 12:06:00 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id D9D6E1A043F for <ietf-822@ietf.org>; Fri, 18 Apr 2014 12:05:59 -0700 (PDT)
Received: (qmail 88593 invoked from network); 18 Apr 2014 19:05:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=15a10.53517793.k1404; bh=DdTd1ARG5zLDVB2iFJV2NSm+8dCOM0eyyNY3RQ6/haU=; b=NsoZ/iVyeW4YRLitcCYaBKx6292L+PKdni5WwUqWQ//KA81ziOLA9+tk08WpVK8ywflzmIwKgxz1cQzC156fm7TAAlsSid9r5F19MEjIFC0OHPqNJANzm8O4PrndyK10X4D2GeYoLll30QuIe2HoXJ0coBaRPBl+664va0lAu74DX2WD4iG75fcnTLwVmbreo2VjUmBdoE4BYWhhwPIHinINPC5exvAdPZzXt624Xwuco+f9q39F1jpMCTSNvgrj
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=15a10.53517793.k1404; bh=DdTd1ARG5zLDVB2iFJV2NSm+8dCOM0eyyNY3RQ6/haU=; b=UrT4+rbJxf3FP0PauHHuRoGH7Z6kqfoj316RPIuOfvBswDe2v7NZNVt5aBeLnDd8SxtGwfsxfXOOcRrqunYIQrb6HDgwZPw7fC1Q16DuZBy68jre2WNdgANjXUh3Xk6meAzCCun01kFsRwGZsUEN778CTyAudzFTEJzBGwyN9I6p1aNFeBx4Ee/8raoG0UA6BA7W/yy8h4XmLyP/tB2vd19OY0LrzZk9FRg21y3bUItOmOKBoYHam3ywiupe7tyL
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 18 Apr 2014 19:05:55 -0000
Date: Fri, 18 Apr 2014 15:05:54 -0400
Message-ID: <alpine.BSF.2.00.1404181500430.5575@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
In-Reply-To: <53516FA7.3020507@qti.qualcomm.com>
References: <20140418021925.2979.qmail@joyce.lan> <53516FA7.3020507@qti.qualcomm.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg="sha1"; BOUNDARY="3825401791-2135309306-1397847955=:5575"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/REHffwTp0WVXCKsg3edDCgIC510
Cc: ietf-822@ietf.org
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: Fri, 18 Apr 2014 19:06:05 -0000

> First of all, "permission to re-sign" seems to me to be the wrong semantics. 
> This is simply "originally sent from here to there". The originating site 
> (example.com) wants to say, "This message came from example.com and got sent 
> to somebody@foo.example.net", in a way that someone who receives a message 
> from foo.example.net can check.

It has to be more than that, it has to say that it's OK for 
foo.example.net to pass it along in modified form.

I suppose it doesn't have to be re-signed, foo.example.net could do SPF 
path authentication, but that mixes message and path authentication in a 
way that makes me nervous.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email