RE: SHAKEN/STIR Robocall Summit - July 11 2019 at FCC

[Peter Beckman <beckman () angryox com>]

On Thu, 11 Jul 2019, Keith Medcalf wrote:

> On Thursday, 11 July, 2019 12:38, Ross Tajvar <ross () tajvar io> wrote:
>
> > What if you use different carriers for termination and origination?
> > How does your termination carrier validate that your origination
> > carrier has allocated certain numbers to you and that you're
> > therefore allowed to make outbound calls with a caller ID set to
> > those numbers? That doesn't sound to me like something that can be
> > solved as quickly and easily as you imply.
>
> It does not really matter.  What matters is that they bear responsibility
> for an act in furtherance of a conspiracy to commit fraud.

 Fraud means you'll need to know the content of the call to determine if
 the spoofing of the CallerID value meets the bar of breaking the law.

 Truth in CallerID Act is only violated if there is intent to defraud when
 the CallerID is spoofed. If you spoof CallerID and do not know the content
 of the call, you cannot know if the Act was violated.

 And we don't want to get into the business of monitoring the content of
 phone calls. That opens legal floodgates.

 If someone complains, at least you have some recourse. But you have that
 today. And by the time someone complains and you trace the call back to a
 source in the US (if you can, a woman from AT&T said a "traceback" now
 takes days instead of months, still too slow to take any real action), you
 find out it originated outside the US and you have a dead end.

 Traceroute for Calls would be nice... each hop adds its own header, kind
 of like the "Received:" header that exists multiple times in an email.

Beckman
---------------------------------------------------------------------------
Peter Beckman                                                  Internet Guy
beckman () angryox com                                 http://www.angryox.com/
---------------------------------------------------------------------------