IETF Logo Mail Archive

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

Tony Rutkowski <tony@yaanatech.co.uk> Fri, 03 February 2017 19:30 UTC

Return-Path: <tony@yaanatech.co.uk>
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 2940B129473; Fri, 3 Feb 2017 11:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 2bx_6V0gWgWp; Fri, 3 Feb 2017 11:30:25 -0800 (PST)
Received: from uk-www1.yaanatech.uk (uk-www1.yaanatech.uk [46.20.116.155]) (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 A95C2128B37; Fri, 3 Feb 2017 11:30:25 -0800 (PST)
Received: from [192.168.1.51] (pool-70-106-242-209.clppva.fios.verizon.net [70.106.242.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by uk-www1.yaanatech.uk (Postfix) with ESMTPSA id 9DAB5540231; Fri, 3 Feb 2017 19:30:23 +0000 (GMT)
References: <7F3DCD21-1085-4961-82D7-CE12DB308305@shockey.us> <a9417cde-33d4-3da2-ad2a-5b83bd81701f@yaanatech.co.uk> <74394dc8-5a61-cb8f-eb9d-98b499256326@dcrocker.net>
To: dcrocker@bbiw.net, "stir@ietf.org" <stir@ietf.org>, sipcore@ietf.org
From: Tony Rutkowski <tony@yaanatech.co.uk>
Organization: Yaana Ltd
Message-ID: <5fbc40d2-51f5-7073-f99a-488cd53f8fce@yaanatech.co.uk>
Date: Fri, 03 Feb 2017 14:30:22 -0500
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: <74394dc8-5a61-cb8f-eb9d-98b499256326@dcrocker.net>
Content-Type: multipart/alternative; boundary="------------E2A41BFB3B79C283149938B7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/G0bdmz883AwGMA4hOubnSFCFQEM>
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
Reply-To: tony@yaanatech.co.uk
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 19:30:27 -0000

So why not do that rather than use 30 year
old legacy technology that is unlikely to scale and
is onerous to implement?   I'm sure you could
do it.  Seems like a better road than doing PR
for FCC and CRTC regulatory mandates?  Indeed,
how likely is it anymore under the brave new
world of Trump?  The FCC will be lucky to hold
on to spectrum management.

-t


On 2017-02-03 2:23 PM, Dave Crocker wrote:
> Where is the standardized system specification that incorporates it 
> for use in SIP-based phone calls?

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