IETF Logo Mail Archive

Re: [cnit] CNIT Charter bashing..

Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> Mon, 15 June 2015 22:11 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 891801B2C5E for <cnit@ietfa.amsl.com>; Mon, 15 Jun 2015 15:11:30 -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_40=-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 V-qzpZmBCHp1 for <cnit@ietfa.amsl.com>; Mon, 15 Jun 2015 15:11:29 -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 DA2231B2C5D for <cnit@ietf.org>; Mon, 15 Jun 2015 15:11:28 -0700 (PDT)
Message-ID: <E6A16181E5FD2F46B962315BB05962D07D35E829@fcc.gov>
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: "Dwight, Timothy M (Tim)" <timothy.dwight@verizon.com>
Thread-Topic: [cnit] CNIT Charter bashing..
Thread-Index: AQHQpF27t1IjTQnD9Ee6If5FuC7/752nvtOAgAAcbYD//73Z54ABUaEAgAA9LQD//8LlU4AARHQAgAAZ6QCAAArCAIAAB9cAgAAPTgCAABkwgP//7x3tADGHMBAAITkHRAAICivQADuTr0w=
Date: Mon, 15 Jun 2015 22:11:26 +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> <15E9AA29-E9F1-4DA6-ADA4-E201F8F07B7A@brianrosen.net> <2B0F677F0B95454297753F58D4A07FA30279326B72@FHDP1LUMXC7V31.us.one.verizon.com> <53A932AB-5E5D-41C0-895F-21EC1D4B17D5@brianrosen.net>, <2B0F677F0B95454297753F58D4A07FA30279326CB7@FHDP1LUMXC7V31.us.one.verizon.com> <E6A16181E5FD2F46B962315BB05962D07D3558A5@fcc.gov>, <2B0F677F0B95454297753F58D4A07FA30279326E8D@FHDP1LUMXC7V31.us.one.verizon.com> <E6A16181E5FD2F46B962315BB05962D07D35C213@fcc.gov>, <2B0F677F0B95454297753F58D4A07FA30279326EC8@FHDP1LUMXC7V31.us.one.verizon.com>
In-Reply-To: <2B0F677F0B95454297753F58D4A07FA30279326EC8@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/LmakbTeZHze_wsyqPzbvga1nAcI>
Cc: "cnit@ietf.org" <cnit@ietf.org>
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: Mon, 15 Jun 2015 22:11:30 -0000

Agreed that the terminating carrier can provide added value, e.g., by linking to other information. You could imagine mapping numbers to BBB information, or databases or registered charities, or Yelp... I am somewhat surprised that this isn't happening already more broadly.

________________________________________
From: Dwight, Timothy M (Tim) [timothy.dwight@verizon.com]
Sent: Sunday, June 14, 2015 1:58 PM
To: Henning Schulzrinne
Cc: cnit@ietf.org
Subject: RE: [cnit] CNIT Charter bashing..

Henning,

I'm not sure 'carrier B' would in the "in-band case" have no incentive to use a 3rd party service.  It might be that the 3rd party service provides additional information and/or is considered more trustworthy than whoever provided the in-band information.  We can (and I hope will) change the incentives.  I think it would be a reasonable objective to carry whatever content is deemed "necessary" to serve the public, in-band.  If people want to operate databases full of calling party's cat pictures, and Carrier B wants to provide this to their customer (or allow their customer to obtain it themselves, e.g., provide them a link to it) that's all OK with me.

I agree with you about the importance of being able to know unambiguously, who inserted the information.

Tim

v2.23.0 | Report a Bug | By Email