Re: [Shutup] Proposed Charter for the "SMTP Headers Unhealthy To User Privacy" WG

"Robert A. Rosenberg" <> Mon, 07 December 2015 03:00 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5A6101ACD8F for <>; Sun, 6 Dec 2015 19:00:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NWqmyPE9W57a for <>; Sun, 6 Dec 2015 19:00:44 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A46411ACD93 for <>; Sun, 6 Dec 2015 19:00:44 -0800 (PST)
Received: from [] ( []) by (Postfix) with ESMTPA id 8B6B3178C2; Sun, 6 Dec 2015 22:00:43 -0500 (EST)
Mime-Version: 1.0
Message-Id: <p0624040ad28a9f432d8e@[]>
In-Reply-To: <>
References: <> <> <05b301d1304c$bf6f3880$3e4da980$> <> <> <>
X-Mailer: Eudora for Mac OS X 6.2.4 (MacOS 10.5.8)
Date: Sun, 6 Dec 2015 21:54:06 -0500
To: Chris Lewis <>
From: "Robert A. Rosenberg" <>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Archived-At: <>
Subject: Re: [Shutup] Proposed Charter for the "SMTP Headers Unhealthy To User Privacy" WG
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMTP Headers Unhealthy To User Privacy <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 07 Dec 2015 03:00:46 -0000

At 19:15 -0500 on 12/06/2015, Chris Lewis wrote about Re: [Shutup] 
Proposed Charter for the "SMTP Headers Unhealt:

>On 12/06/2015 04:10 PM, Martijn Grooten wrote:
>>On Sun, Dec 06, 2015 at 02:59:54PM -0500, Chris Lewis wrote:
>>>I was never so glad as to see something as the wide-scale deployment
>>>of callerid a few years later.
>>But for Caller ID to work in cases like the one you describe, you
>>wouldn't need to know the phone number (which often includes the
>>location) of the caller; a "cryptographic blob" identifying their phone
>>line would suffice.
>The proper analog is "Call Trace".  You dial a * code, and the 
>calling number gets recorded by the telco, but it can only be 
>retrieved via a LE process (I do not believe it requires a full 
>search warrant, but, joe-blow citizen certainly can't get it).  It 
>cannot be disabled (but presumably spoofable) by the caller.

The *-code you are referencing is *57 (1157 from a dial phone) and 
records the ANI (Call Setup and Routing) information not the 
spoof-capable CALLERID information. I think about am not sure that 
the information is accurate and can not be spoofed/faked. Note that 
the called party must use the code before another call comes in and 
the TelCo charges you when you use it.

Here is a Wikipedia article on the code/feature.