Re: [stir] [sipcore] The Canadian Regulator has issued a Notice of Consultation on robocalls spoofing STIR/SHAKEN

Richard Shockey <richard@shockey.us> Fri, 03 February 2017 23:27 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 EB169129587 for <stir@ietfa.amsl.com>; Fri, 3 Feb 2017 15:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level:
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 w-pjuTByS_GU for <stir@ietfa.amsl.com>; Fri, 3 Feb 2017 15:27:11 -0800 (PST)
Received: from qproxy5-pub.mail.unifiedlayer.com (qproxy5-pub.mail.unifiedlayer.com [69.89.21.30]) by ietfa.amsl.com (Postfix) with SMTP id 3837212957D for <stir@ietf.org>; Fri, 3 Feb 2017 15:27:10 -0800 (PST)
Received: (qmail 30946 invoked by uid 0); 3 Feb 2017 23:27:10 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by qproxy5.mail.unifiedlayer.com with SMTP; 3 Feb 2017 23:27:10 -0000
Received: from box462.bluehost.com ([74.220.219.62]) by CMOut01 with id gPMw1u02Q1MNPNq01PMzQs; Fri, 03 Feb 2017 16:22:00 -0700
X-Authority-Analysis: v=2.1 cv=NJxGpSKg c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=1oJP67jkp3AA:10 a=n2v9WMKugxEA:10 a=ZZnuYtJkoWoA:10 a=PeFO9FbFhS32YxYntvkA:9 a=48vgC7mUAAAA:8 a=7spupVCzAAAA:8 a=k7Ga1wGzAAAA:8 a=I0MiS0zW0TjwPNBc-LsA:9 a=4nMBXvXinvZLF1FJ:21 a=fC0f2rJhZ069jljm:21 a=QEXdDO2ut3YA:10 a=jvqvEWPmYTEA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=z_ZDNOd-t759Mkd8KWIA:9 a=ggIf8jvmlZ8Qm0I1:21 a=Q0opR868Ej6atB7n:21 a=w16YP-8g7pw-WpGR:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=6c0Kp0hCwIag1lhdXwqI:22 a=ijMaxGghyylP-n2pFjDB:22 a=BKKCjISod1eDJeS0ORpz:22 a=zjWhRoSqWz9hl55Hdlzg:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-type:Mime-version:In-Reply-To:References:Message-ID:To: From:Subject:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=gN9qQOrOdyTva0LLp25C2t6ROvi9jFxjDCDZoFC2ylg=; b=QMdAXZHDhHVTMLj789+Y7uKv3U lyDTkfNiztGm4JDF33ZDEgaM1kSdil1X47mIRlZDAlWWrAbe8srmZd8vaawlNwQkEyxfWKeZcNTjy Y9dh7W5NfLMMVlDR9X1q8NLAu;
Received: from pool-100-36-44-71.washdc.fios.verizon.net ([100.36.44.71]:63311 helo=[192.168.1.152]) by box462.bluehost.com with esmtpa (Exim 4.87) (envelope-from <richard@shockey.us>) id 1cZnAy-0003SM-Is; Fri, 03 Feb 2017 16:21:56 -0700
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Fri, 03 Feb 2017 18:21:55 -0500
From: Richard Shockey <richard@shockey.us>
To: <tony@yaanatech.co.uk>, <dcrocker@bbiw.net>, "stir@ietf.org" <stir@ietf.org>, <sipcore@ietf.org>
Message-ID: <9BB472BA-06BF-4F5F-9EAB-07AA841605E4@shockey.us>
Thread-Topic: [sipcore] [stir] The Canadian Regulator has issued a Notice of Consultation on robocalls spoofing STIR/SHAKEN
References: <7F3DCD21-1085-4961-82D7-CE12DB308305@shockey.us> <a9417cde-33d4-3da2-ad2a-5b83bd81701f@yaanatech.co.uk> <74394dc8-5a61-cb8f-eb9d-98b499256326@dcrocker.net> <5fbc40d2-51f5-7073-f99a-488cd53f8fce@yaanatech.co.uk> <974c2333-aef5-1c93-744c-58dbaaa20ca9@dcrocker.net> <286e60eb-baa3-c4ec-6c32-43e217713310@yaanatech.co.uk>
In-Reply-To: <286e60eb-baa3-c4ec-6c32-43e217713310@yaanatech.co.uk>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3568990916_381444252"
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.71
X-Exim-ID: 1cZnAy-0003SM-Is
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-36-44-71.washdc.fios.verizon.net ([192.168.1.152]) [100.36.44.71]:63311
X-Source-Auth: richard+shockey.us
X-Email-Count: 3
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NDYyLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/VNI8VRAiAp9X1y5WETG_p_IMdn8>
Subject: Re: [stir] [sipcore] The Canadian Regulator has issued a Notice of Consultation on robocalls spoofing STIR/SHAKEN
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 03 Feb 2017 23:27:14 -0000

 

Wow Tony … that’s some Kool-Aid you are sipping or smoking … share the Joy.  

 

 

 

 

From: sipcore <sipcore-bounces@ietf.org> on behalf of Tony Rutkowski <tony@yaanatech.co.uk>
Organization: Yaana Ltd
Reply-To: <tony@yaanatech.co.uk>
Date: Friday, February 3, 2017 at 3:00 PM
To: <dcrocker@bbiw.net>et>, "stir@ietf.org" <stir@ietf.org>rg>, <sipcore@ietf.org>
Subject: Re: [sipcore] [stir] The Canadian Regulator has issued a Notice of Consultation on robocalls spoofing STIR/SHAKEN

 

It may be well understood at some level,
albeit not widely used.  Scaling its use globally
has a chance of between zero and none. 
Mr. Google can point you to all the other 
solutions proffered out there by other bodies
and national administrations.

So prior to 7 Nov 2016, it had some marginal chance
of having US uptake with a FCC forcing function.  
Or at least it sounded good for FCC PR purposes.
Today, in the brave new world in Washington,
it seems just a matter of time it gets formally
flushed along with NetNeutrality, Title II jurisdiction,
etc.  It just doesn't fit the new political paradigm.

Blockchain solutions for dealing with authentication 
requirements such as call spoofing are fast ascending 
and in the long term far more attractive.  So since
there is now more time to play with, why not shift
to an alternative mechanism that's more contemporary
and with better technical, operational, and political
attributes.   As Bobby Dylan reminded us, you don't
need a weatherman here.

tony

 

On 2017-02-03 2:39 PM, Dave Crocker wrote:

Given how many years STIR/Shaken have taken -- and that's for well-understood technology with lots of field experience -- you are suggesting the process start over? 

What are the incremental benefits that will accrue from waiting another 5-8 years to deploy this alternative mechanism? 

d/ 


_______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore