IETF Logo Mail Archive

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

Alex Bobotek <alex@bobotek.net> Sat, 04 February 2017 03:03 UTC

Return-Path: <alex@bobotek.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 1D0371294C3 for <stir@ietfa.amsl.com>; Fri, 3 Feb 2017 19:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 sPMnRp8daLI0 for <stir@ietfa.amsl.com>; Fri, 3 Feb 2017 19:03:27 -0800 (PST)
Received: from resqmta-po-11v.sys.comcast.net (resqmta-po-11v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:170]) (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 5DCA21294BF for <stir@ietf.org>; Fri, 3 Feb 2017 19:03:27 -0800 (PST)
Received: from resomta-po-17v.sys.comcast.net ([96.114.154.241]) by resqmta-po-11v.sys.comcast.net with SMTP id ZqcccOB3V5l5NZqdKconqw; Sat, 04 Feb 2017 03:03:26 +0000
Received: from BOBO1A.bobotek.net ([76.104.190.59]) by resomta-po-17v.sys.comcast.net with SMTP id ZqdGcVz9de3QFZqdIcPARg; Sat, 04 Feb 2017 03:03:25 +0000
Received: from BOBO1A.bobotek.net ([fe80::4851:b4bb:416a:e1ad]) by BOBO1A.bobotek.net ([fe80::4851:b4bb:416a:e1ad%10]) with mapi; Fri, 3 Feb 2017 18:38:10 -0800
From: Alex Bobotek <alex@bobotek.net>
To: Dave Crocker <dcrocker@bbiw.net>, "tony@yaanatech.co.uk" <tony@yaanatech.co.uk>, "stir@ietf.org" <stir@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Fri, 03 Feb 2017 18:38:09 -0800
Thread-Topic: [stir] The Canadian Regulator has issued a Notice of Consultation on robocalls spoofing STIR/SHAKEN
Thread-Index: AdJ+dfJOM0rtjVH0SUC9nCwfqgtbUgAGnvag
Message-ID: <4B1956260CD29F4A9622F00322FE0531012CFB5151B1@BOBO1A.bobotek.net>
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> <3d4c18f8-f08c-8ce9-6e37-5498069ae5df@bbiw.net>
In-Reply-To: <3d4c18f8-f08c-8ce9-6e37-5498069ae5df@bbiw.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CMAE-Envelope: MS4wfGo7pd4wWyiOov63QFz70p4EGJ+emjUPWJAmdjLD9cK5RawsEw6DR8YgW0YYGWrbuAMFGGPmnaXZukP6/Z+pLyaXuouLd4xWhG4K2f9MgOBN1GdDBNG1 nvxRysmM2DruVqs+rOprGI1m6BRHabO/Re6O38WxL75D0oLYp2X/qE7brRWvYh105F8tdX/sgZT8E+oKMg9ijUm8SnNrmArDAXVBMMqi0kkjSFuPTQGQKM4R KK/bky58C0BUDdjfvcaJxg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/xtqpex1ziaLWo1AOR3XclTYsOHI>
Subject: Re: [stir] 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 03:03:29 -0000

To the extent that the overhead of authorizing legitimate delegation of authority might impede wider use of STIR/SHAKEN, blockchain-based  technology _might_ be utilized as an alternative authority delegation mechanism in a way that reduces overhead.  

I'm not certain if that's what Tony is referring to, and the "_might_" is not me taking any position at this time wrt the relative pros and cons of blockchain vs STIR's delegation technologies.  

Tony, I'm apparently not the only one who doesn't understand how you believe blockchain might help, but am always ready to listen to an explanation.  

On the original point of CRTC's ask for information that got this thread going, a number of CRTC personnel will be attending and/or speaking on panels at M3AAWG VTASIG on the 23rd in San Francisco.  I'm not sure what CRTC's rules are on informal discussion of issues that are part of their formal regulatory process, but at the very least I expect them to present it and have open ears.  

Regards,

Alex 

> -----Original Message-----
> From: stir [mailto:stir-bounces@ietf.org] On Behalf Of Dave Crocker
> Sent: Friday, February 3, 2017 3:59 PM
> To: tony@yaanatech.co.uk; stir@ietf.org; sipcore@ietf.org
> Subject: Re: [stir] The Canadian Regulator has issued a Notice of Consultation
> on robocalls spoofing STIR/SHAKEN
> 
> On 2/3/2017 12:00 PM, Tony Rutkowski wrote:
> > Mr. Google can point you to all the other solutions proffered out
> > there by other bodies and national administrations.
> 
> Citations to standardized (ie, multilaterally-supported) detailed specifications
> of an integrated service, please.  You are making the claim, so you can do the
> google and proffer the satisfying results.
> 
> 
> > Blockchain solutions for dealing with authentication requirements such
> > as call spoofing are fast ascending and in the long term far more
> > attractive.
> 
> If there is a problem with the uptake of STIR/Shaken, what will make the
> uptake of a blockchain-based service -- whatever that might be -- any
> better?
> 
> d/
> --
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> 
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir

v2.29.0 | Report a Bug | By Email | System Status