Re: Thoughts from IETF-92

[Phillip Hallam-Baker <[e-mail]>]

A meet up on general policy related stuff or the robocall scams?

I think it is absolutely clear that we can apply many of the
techniques used to control email spam to block robocalls in principle.
But the problem is that the telephone system architecture only gives
us stupid boxes with no APIs or ability to customize their function.

I suspect a large part of the problem is that most of the folk who
could work on this problem are cord cutters who use mobiles. Robocalls
are an increasing problem there as well but it is much smaller. I get
maybe one mobile robocall a month while there are six a day on the
home phone.

By telephone service, I mean the voice communication service I can
access from any of the 12 handsets in the house and allows me to call
anyone with a telephone number.

Now this is not where I want to be. I want to add more handsets for a
start and I would like the handsets to have effective encryption
between the handset and the base station.

Some things that I think would help (in no particular order).

1) State laws that require products with defective security (e.g. car
door keys, garage door openers, DECT6.0 phones) to be sold with large
stickers saying 'Defective Security'.

2) Someone producing a clear, easy to understand guide specifying the
hardware and service requirements for setting up an Internet telephony
system that provides an API allowing intelligent control

3) Hardware vendors who provide VOIP access points could provide API hooks.

4) A Web service protocol specification allowing the API to be
activated remotely.


For example, I would like to be able to program my telephone system to
add the following features:

* Direct voicemail to my own systems that NEVER EVER delete a message
or make me w-a-i-t w-h-i-l-e a v-e-r-y s-l-o-o-o-o-o-w s-p-e-a-k-e-r
t-e-l-l-s me stuff I already know.

* While in a call, I dial a code on the handset to white list that caller
* While in a call, I dial a code to black list that caller

* Control which incoming calls can cause the ringer to sound and at
which times of the day.

* Route calls to certain numbers end to end without going through the
PSTN at all.

* Place calls on Skype etc. directly.

Yes, I know, Asterix. But the ability to hack someone else's code is
not the same as being able to make one device talk to another over a
defined interface.


Apple, Cisco, Google and Microsoft are all players in this game right
now but none will deliver what the market needs. And they all could
with just a little willingness to make the system open.

The problem is that the telco people do not understand open systems
and don't think of opening up the system as a possible solution. It
simply isn't in their mid set.