IETF Logo Mail Archive

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

Dave Crocker <dcrocker@bbiw.net> Sat, 04 February 2017 01:03 UTC

Return-Path: <dcrocker@bbiw.net>
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 0AC2712953F; Fri, 3 Feb 2017 17:03:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bbiw.net
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 AoTHZwSx3Cxs; Fri, 3 Feb 2017 17:03:27 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 672AA1294C9; Fri, 3 Feb 2017 17:03:27 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v14153tN015059 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 3 Feb 2017 17:05:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1486170304; bh=Jt/pZ3B/aqdHNNrXEHIKo/DWhu13GDzgZ9mgmP6AgTU=; h=Subject:To:References:From:Date:In-Reply-To:From; b=HBBKOpWNxSVOEeQpU3aBdGlz4TZPXr4v9Xlhyi4Hu36gFV4bPE9f/0fNzf+Sty3Ik oKJfJJFmled+OHmMkaPDIWzhtXxFT57avjYCIJMgoYkOKNnxdBJBURZqYLtk0ebMwU RsdL6Xa8YmklB2aB1CCHaElMjXtcZBB9gimEW+sg=
To: tony@yaanatech.co.uk, Richard Shockey <richard@shockey.us>, "stir@ietf.org" <stir@ietf.org>, sipcore@ietf.org
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> <9BB472BA-06BF-4F5F-9EAB-07AA841605E4@shockey.us> <535b8880-8ae8-28d5-e478-aae5b9bb38da@yaanatech.co.uk>
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
Message-ID: <67565cb1-6f0c-ebb0-a45c-a306aa602efb@bbiw.net>
Date: Fri, 3 Feb 2017 17:03:12 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <535b8880-8ae8-28d5-e478-aae5b9bb38da@yaanatech.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/s_h28trHeQK-DnwgB9iLVz7jXdM>
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: Sat, 04 Feb 2017 01:03:28 -0000

On 2/3/2017 3:51 PM, Tony Rutkowski wrote:
> On the technology and business side of the
> equation, click on the following:


Sorry I wasn't clear.  I meant /specifications/.  Theory is always a 
nice starting point, but it's a terrible ending point.  Remember that 
5-8 years I mentioned before?


> Then ask yourself why any telecommunication
> provider would go to their national regulator
> and say "regulate me and force me to provide
> SHAKEN-STIR services against the interests of
> many of my business customers."

Your premise seems to be that SITR/Shaken can't be used without 
regulatory mandate.  I don't understand that.

And to the extent is has validity, what makes a blockchain-based 
approach any more-easily adopted?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.9.2 | Report a Bug | By Email