Re: [art] New Version Notification for draft-httpemaildevphone-00.txt

Ben Campbell <ben@nostrum.com> Tue, 18 December 2018 16:56 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7B913111F for <art@ietfa.amsl.com>; Tue, 18 Dec 2018 08:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.068
X-Spam-Level:
X-Spam-Status: No, score=-0.068 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 ooFL9ExqINRd for <art@ietfa.amsl.com>; Tue, 18 Dec 2018 08:56:12 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 709041311F7 for <art@ietf.org>; Tue, 18 Dec 2018 08:56:09 -0800 (PST)
Received: from [10.0.1.45] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wBIGu3gL093317 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 18 Dec 2018 10:56:04 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1545152164; bh=LkCYHmvblFNUAg6ZFli+iYP2ExKZjw5RBT00f9Vds3M=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=addRpYwNQpSWtLVoYKjwIoOM9KVWYY2urB8PijsFtOOF2nKxYCaNHtylGfGdtxULt aZykCEWkMr4sC+NlO3dBiN6w0CXlgmeLAPflc7buvzbwM86WSbK+1dIno9v3b2CttO JUvt8pxPZpk657ZUPx8lHaiuzlcNCgPqKulUQP9I=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.45]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <1734CBC3-B54C-4AD5-A829-DE45B3002B70@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4B4D3044-193C-421D-ACCE-93AA053A2D1C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 18 Dec 2018 10:56:02 -0600
In-Reply-To: <TY2PR03MB44800BC0BE2BFFB2F81C1062B7BD0@TY2PR03MB4480.apcprd03.prod.outlook.com>
Cc: "art@ietf.org" <art@ietf.org>
To: pradeep xplorer <pradeepan88@hotmail.com>
References: <154467689893.21229.8392151070943582246.idtracker@ietfa.amsl.com> <TY2PR03MB44804EABD3628C5FDF4A5D07B7A00@TY2PR03MB4480.apcprd03.prod.outlook.com> <TY2PR03MB44800BC0BE2BFFB2F81C1062B7BD0@TY2PR03MB4480.apcprd03.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/tmfkQ6AsvQlZWKqJhFxGsZV8ZT8>
Subject: Re: [art] New Version Notification for draft-httpemaildevphone-00.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2018 16:56:15 -0000

(Speaking as an individual)

I’ve read the draft, and I do not agree with the requirement. In the past some mobile provides (and perhaps others) have offered something similar to what you describe, but that is their decision to make. I don’t think it’s appropriate for the IETF to recommend it one way or another.

More importantly, a well-known connection between a person’s email address and phone number is a privacy issue. People may legitimately be willing to share one but not the other. Linking them also creates more correlation opportunities.

To summarize, I think that the requirement expressed in the draft is out of scope for the IETF, and would in fact be harmful if the IETF were to publish it.

Thanks,

Ben.




> On Dec 18, 2018, at 2:07 AM, pradeep xplorer <pradeepan88@hotmail.com> wrote:
> 
> The ability for me to sit in this internet center and type in device mac address or phone number in To of email and get it delivered to a device would help many. I have no idea why there are no comments. Older people and such  dont use smartphones and would be just comfortable if emails can be read or send with no other functionality without too much knowledge of emailer programmes and email addresses.
> 
> I have no idea why there are no comments, it looks related to the
> cybercrime i am victimised
> 
> From: pradeep xplorer <pradeepan88@hotmail.com <mailto:pradeepan88@hotmail.com>>
> Sent: Thursday, December 13, 2018 1:07 PM
> To: art@ietf.org <mailto:art@ietf.org>
> Subject: Fwd: New Version Notification for draft-httpemaildevphone-00.txt
> 
> Any comments
> 
> Sent from MailDroid <https://goo.gl/ODgwBb>
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
> To: Pradeep Kumar Xplorer <pradeepan88@hotmail.com <mailto:pradeepan88@hotmail.com>>, pradeep xplorer <pradeepan88@hotmail.com <mailto:pradeepan88@hotmail.com>>
> Sent: Thu, 13 Dec 2018 10:25 AM
> Subject: New Version Notification for draft-httpemaildevphone-00.txt
> 
> 
> A new version of I-D, draft-httpemaildevphone-00.txt
> has been successfully submitted by Pradeep Kumar Xplorer and posted to the
> IETF repository.
> 
> Name: draft-httpemaildevphone
> Revision: 00
> Title: Need for associating email address to device address and phone numbers
> Document date: 2018-12-13 <tel:20181213>
> Group: Individual Submission
> Pages: 3
> URL:            https://www.ietf.org/internet-drafts/draft-httpemaildevphone-00.txt <https://www.ietf.org/internet-drafts/draft-httpemaildevphone-00.txt>
> Status:         https://datatracker.ietf.org/doc/draft-httpemaildevphone <https://datatracker.ietf.org/doc/draft-httpemaildevphone>/
> Htmlized:       https://tools.ietf.org/html/draft-httpemaildevphone-00 <https://tools.ietf..org/html/draft-httpemaildevphone-00>
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-httpemaildevphone <https://datatracker.ietf.org/doc/html/draft-httpemaildevphone>
> 
> 
> Abstract:
>     This document describes the need for associating email address to device
> address     and phone numbers
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
> 
> The IETF Secretariat
> 
> _______________________________________________
> art mailing list
> art@ietf.org <mailto:art@ietf.org>
> https://www.ietf.org/mailman/listinfo/art <https://www.ietf.org/mailman/listinfo/art>