IETF Logo Mail Archive

Re: [perpass] draft-josefsson-email-received-privacy

ned+perpass@mrochek.com Thu, 22 October 2015 10:56 UTC

Return-Path: <ned+perpass@mrochek.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB4C1A1A7F for <perpass@ietfa.amsl.com>; Thu, 22 Oct 2015 03:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level:
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DJZJWzXxOvOR for <perpass@ietfa.amsl.com>; Thu, 22 Oct 2015 03:56:02 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id F25671A1A80 for <perpass@ietf.org>; Thu, 22 Oct 2015 03:56:01 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PS75B9HYOW0025Z9@mauve.mrochek.com> for perpass@ietf.org; Thu, 22 Oct 2015 03:50:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mrochek.com; s=mauve; t=1445511059; bh=ek5ZaUbmY9MbLmVfLl3VwAyjBprtokTWRtSG4Hzi388=; h=From:Cc:Date:Subject:In-reply-to:References:To; b=Pinkg8Q6R6TTDpTBwkeok7o2LPRzgx7vv4uk5T8qRsm5gi3opUPxUOVYad3zDAHuw ck9aJDEn3IEC3/NycYdq+n4K4uI2PdA1jBGD1Yj03BNb5eXvErKh+LY1qRB/ZcP5wS 1pcoRLd03Lo2njJ7piVLM3gXW7iPURwa9BOseUoQ=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PS6U7ZGVV400HE89@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for perpass@ietf.org; Thu, 22 Oct 2015 03:50:55 -0700 (PDT)
From: ned+perpass@mrochek.com
Message-id: <01PS75B6KR1W00HE89@mauve.mrochek.com>
Date: Thu, 22 Oct 2015 03:47:41 -0700
In-reply-to: "Your message dated Wed, 21 Oct 2015 21:27:02 -0700 (PDT)" <01PS6UMHPA8S01729W@mauve.mrochek.com>
References: <87r3kpmm25.fsf@nordberg.se> <01PS6UMHPA8S01729W@mauve.mrochek.com>
To: ned+perpass@mrochek.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/b5Xu7ssudAN-8EcTeVcqVYcZ0q0>
Cc: Linus Nordberg <linus@nordberg.se>, perpass@ietf.org
Subject: Re: [perpass] draft-josefsson-email-received-privacy
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 10:56:04 -0000

Correction to my previous posting: The by clause is also mandatory in
Received: fields, and contains a domain and optionally an IP address.
To the extent it represents a privacy exposure, it can be handled in the
same fashion as the from clause.

				Ned

v2.23.0 | Report a Bug | By Email