Re: [cnit] CNIT Charter bashing..

Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> Fri, 12 June 2015 15:47 UTC

Return-Path: <Henning.Schulzrinne@fcc.gov>
X-Original-To: cnit@ietfa.amsl.com
Delivered-To: cnit@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3261A1A32 for <cnit@ietfa.amsl.com>; Fri, 12 Jun 2015 08:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 qvhCS-iltc-t for <cnit@ietfa.amsl.com>; Fri, 12 Jun 2015 08:47:17 -0700 (PDT)
Received: from DC-IP-2.fcc.gov (dc-ip-2.fcc.gov [192.104.54.91]) by ietfa.amsl.com (Postfix) with ESMTP id 80BB61A0338 for <cnit@ietf.org>; Fri, 12 Jun 2015 08:47:16 -0700 (PDT)
Message-ID: <E6A16181E5FD2F46B962315BB05962D07D3555A8@fcc.gov>
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Richard Shockey <richard@shockey.us>, "philippe.fouquart@orange.com" <philippe.fouquart@orange.com>, "cnit@ietf.org" <cnit@ietf.org>
Thread-Topic: [cnit] CNIT Charter bashing..
Thread-Index: AQHQpF27t1IjTQnD9Ee6If5FuC7/752nvtOAgAAcbYD//73Z54ABUaEAgAA9LQD//8LlU4AARHQA///U8M4=
Date: Fri, 12 Jun 2015 15:47:15 +0000
References: <D19F23AD.26CEA%richard@shockey.us> <E42CCDDA6722744CB241677169E8365603614617@MISOUT7MSGUSRDB.ITServices.sbc.com> <9588_1434045613_5579CCAD_9588_574_1_fki5dyxdmgyv92b6hugpfuoy.1434045608655@email.android.com> <E6A16181E5FD2F46B962315BB05962D07D354C94@fcc.gov> <9384_1434103912_557AB068_9384_7221_1_B5939C6860701C49AA39C5DA5189448B14C216E0@OPEXCLILM42.corporate.adroot.infra.ftgroup>, <D1A05A04.26E84%richard@shockey.us> <E6A16181E5FD2F46B962315BB05962D07D355543@fcc.gov>, <557AE9E4.5030205@cs.tcd.ie>
In-Reply-To: <557AE9E4.5030205@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/cnit/YIARNb2F2HIsDTmGQUw603Q_TK4>
Subject: Re: [cnit] CNIT Charter bashing..
X-BeenThere: cnit@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Calling Name Identity Trust discussion list <cnit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cnit>, <mailto:cnit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cnit/>
List-Post: <mailto:cnit@ietf.org>
List-Help: <mailto:cnit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cnit>, <mailto:cnit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2015 15:47:20 -0000

Good point, although I suspect that a business or individual that wants to disclose its name to the recipient and obviously already discloses its number to all carriers along the way seems unlikely to care that the carrier can also see its name. After all, today, all such carriers have access to CNAM information (along with others). At least in the US, the carriers are largely bound by strict privacy rules ("customer proprietary network information") that carriers tend to take very seriously. (I say "largely", because there may be entities such as CNAM providers and VoIP providers that are considering themselves not to be interconnected that are in the not-quite-carrier area.)

________________________________________
From: Stephen Farrell [stephen.farrell@cs.tcd.ie]
Sent: Friday, June 12, 2015 10:17 AM
To: Henning Schulzrinne; Richard Shockey; philippe.fouquart@orange.com; cnit@ietf.org
Subject: Re: [cnit] CNIT Charter bashing..

On 12/06/15 15:13, Henning Schulzrinne wrote:
> In almost all cases of interest, the calling party *wants* to
> disclose accurate information to the called party, so the privacy
> issues don't seem to arise. They would only arise if there was forced
> disclosure; I don't think anybody is proposing that.

Privacy issues could also arise if a middlebox could now see
sensitive information that it previously could not see. I think
that is independent of whether disclosure is desired by either
of the endpoints.

S.