IETF Logo Mail Archive

Re: [stir] Questions about stir-certificates

Richard Shockey <richard@shockey.us> Mon, 23 October 2017 16:33 UTC

Return-Path: <richard@shockey.us>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B52A01380DB for <stir@ietfa.amsl.com>; Mon, 23 Oct 2017 09:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
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 HSZ7vF6czZAp for <stir@ietfa.amsl.com>; Mon, 23 Oct 2017 09:33:34 -0700 (PDT)
Received: from qproxy2.mail.unifiedlayer.com (qproxy2-pub.mail.unifiedlayer.com [69.89.16.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BC10137E0B for <stir@ietf.org>; Mon, 23 Oct 2017 09:33:34 -0700 (PDT)
Received: from cmgw3 (unknown [10.0.90.84]) by qproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 0160C357F3 for <stir@ietf.org>; Mon, 23 Oct 2017 10:33:33 -0600 (MDT)
Received: from box462.bluehost.com ([74.220.219.62]) by cmgw3 with id R4UV1w00A1MNPNq014UYnZ; Mon, 23 Oct 2017 10:28:33 -0600
X-Authority-Analysis: v=2.2 cv=H76r+6Qi c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=IkcTkHD0fZMA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=02M-m0pO-4AA:10 a=jqBRFv0mrdUA:10 a=ZZnuYtJkoWoA:10 a=RrXTNwEx0F7LVPkyUdMA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To :References:Message-ID:CC:To:From:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=FRAZKkWmt1IecEESQ4k9jd9gRC1O6vXvEKJ+k8jUPiE=; b=ofYQR2oz/eWh6rkeY+gM9sYY6h Ayr9yfSK8GvBVpmnv5aprYqGH9z1kD1Qgp7SJJufhjHQxXU6mtFV4pGKpi4uo8bHXloNLl8L5D2jj rnYn6U01y2McCfa0xuai2qLSX;
Received: from pool-100-36-44-145.washdc.fios.verizon.net ([100.36.44.145]:56524 helo=[192.168.1.152]) by box462.bluehost.com with esmtpa (Exim 4.87) (envelope-from <richard@shockey.us>) id 1e6faW-0046nn-UJ; Mon, 23 Oct 2017 10:28:29 -0600
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Mon, 23 Oct 2017 12:28:26 -0400
From: Richard Shockey <richard@shockey.us>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Chris Wendt <chris-ietf@chriswendt.net>
CC: "stir@ietf.org" <stir@ietf.org>, "Gorman, Pierce A [CTO]" <Pierce.Gorman@sprint.com>
Message-ID: <B198E322-83DB-4507-AAAD-ABA071FDBF29@shockey.us>
Thread-Topic: [stir] Questions about stir-certificates
References: <D60E0087.1EEE44%jon.peterson@neustar.biz> <CABkgnnV41djmwJ2A8WkLv1Qu_zxAKPb8EJnuoFS1Zeog3momyQ@mail.gmail.com> <6432f01322c74b1196075c4549f18a12@plswe13m04.ad.sprint.com> <4bbb6330-96e7-6317-cbae-07991075e776@alum.mit.edu> <171f91651e9e4a2eb7873fdbe1b9fcea@plswe13m04.ad.sprint.com> <4e1c72a3-4ae0-d424-8dfd-fff1c7049cdb@alum.mit.edu> <C0F0887C-F247-4B37-99DB-BF175943914C@chriswendt.net> <20d0f1d0-f4cc-2bed-b493-7cb4bfe746d1@alum.mit.edu>
In-Reply-To: <20d0f1d0-f4cc-2bed-b493-7cb4bfe746d1@alum.mit.edu>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box462.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 100.36.44.145
X-Exim-ID: 1e6faW-0046nn-UJ
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-36-44-145.washdc.fios.verizon.net ([192.168.1.152]) [100.36.44.145]:56524
X-Source-Auth: richard+shockey.us
X-Email-Count: 2
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NDYyLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/ASfKc0lmuk-VELBcekV3XFwwFAU>
Subject: Re: [stir] Questions about stir-certificates
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Oct 2017 16:33:36 -0000

For suitably smart devices (e.g. mobile phones) I would hope that 
    various apps and configuration options for those apps can provide the UI 
    to users. Then app providers can compete on who does it better and users 
    can choose. And these can evolve over time as the uptake on the signing 
    increases. Maybe this is what you mean by Call Analytics apps.
    
    It would be bad if all of this gets locked up in the FCC regulatory regime.

RS> Paul I don’t think this is going to get locked up in a FCC/FTC OFCOM CRTC like regime but the regulators do have legitimate concerns on consistency. The regulators have actually been quite helpful here. They are willing to eventually help with consumer education if the framework for display options is simple, and I also believe there are excellent opportunities for service providers to add value.   Sometimes choice is bad and confusing the consumer with different forms of UX could cause its own problems.  Its still early.

v2.23.0 | Report a Bug | By Email