Re: [cnit] CNIT Charter bashing..

Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> Sun, 14 June 2015 13:50 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 971FB1A8753 for <cnit@ietfa.amsl.com>; Sun, 14 Jun 2015 06:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ir8T1F8cZfBV for <cnit@ietfa.amsl.com>; Sun, 14 Jun 2015 06:50:14 -0700 (PDT)
Received: from DC-IP-1.fcc.gov (dc-ip-1.fcc.gov [192.104.54.97]) by ietfa.amsl.com (Postfix) with ESMTP id A49441A8758 for <cnit@ietf.org>; Sun, 14 Jun 2015 06:50:12 -0700 (PDT)
Message-ID: <E6A16181E5FD2F46B962315BB05962D07D35B1E0@fcc.gov>
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: "Dwight, Timothy M (Tim)" <timothy.dwight@verizon.com>, "cnit@ietf.org" <cnit@ietf.org>
Thread-Topic: [cnit] CNIT Charter bashing..
Thread-Index: AQHQpF27t1IjTQnD9Ee6If5FuC7/752nvtOAgAAcbYD//73Z54ABUaEAgAA9LQD//8LlU4AARHQAgAAZ6QCAABA5AIAAH5PPgAGUY3CAAPphQA==
Date: Sun, 14 Jun 2015 13:50:11 +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> <D1A0761F.26EE1%richard@shockey.us>, <2B0F677F0B95454297753F58D4A07FA30279326B59@FHDP1LUMXC7V31.us.one.verizon.com> <E6A16181E5FD2F46B962315BB05962D07D355940@fcc.gov>, <2B0F677F0B95454297753F58D4A07FA30279326E8E@FHDP1LUMXC7V31.us.one.verizon.com>
In-Reply-To: <2B0F677F0B95454297753F58D4A07FA30279326E8E@FHDP1LUMXC7V31.us.one.verizon.com>
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/lVXXDKqe_UXTdxWoXwNX15iOflw>
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: Sun, 14 Jun 2015 13:50:16 -0000

With in-band delivery, controlling delivery of information should, in theory, be easier, since we no longer rely on third-party services.

My guess is that many PBX and SIP trunking systems rely on companies like OpenCNAM or the other service providers listed at http://www.voip-info.org/wiki/view/CNAM . They currently can't provide call-by-call privacy, only a global "always on"/"always off" setting.

Thus, I think we all agree that callers should have control, either permanently or maybe call-by-call, on whether to disclose caller name information, and callers should be aware that this information may be visible to carriers in the call path. (In many cases, that's likely to be just the caller's carrier and the destination carrier, but things obviously sometimes get more complicated in rural call scenarios or if there's a separate LD carrier.)

Henning
________________________________________
From: Dwight, Timothy M (Tim) [timothy.dwight@verizon.com]
Sent: Saturday, June 13, 2015 7:09 PM
To: Henning Schulzrinne; cnit@ietf.org
Subject: RE: [cnit] CNIT Charter bashing..

Henning,

As you may know, there are controls over disclosure of calling name data that mirror those which govern disclosure of calling number.  In the conventional CNAM model these are attributes in the LIDB.  These need either to be explicitly changed (e.g., if consumers no longer need these protections) or replicated into whatever alternative model this group develops.  Since it's not up to the IETF to determine public policy, I guess we're best off trying to replicate the existing functionality.

Intuitively I agree that an entity with a "public" or "semi-public" telephone number would probably not object to their name being displayed to people they call.  But that is not necessarily the case.  All I can say for sure is that today consumers have control over this (you can mark your name "public" or "private" in the LIDB;  and you can ask that name presentation be "tied" to number presentation - i.e., if you can ask that presentation of your name be blocked if presentation of your number is blocked, either permanently or call-by-call).

Similarly I can't say for sure whether anyone would object to their name being visible to networks or network elements to which it is not visible today.  I think if we propose to increase its visibility the onus is on us to be sure.

Tim