I'd like your help. Perhaps together we can get an infrastructure in place
to stop illegal robocalling.
You may remember that in 2012-2013 the FTC (NOT FCC) held a contest
for a way to stop illegal robocalling.
I entered the contest, but did not win. My proposal is technical - I
don't think trying to change bad behavior will work.
The summary of my original proposal can be seen at
I could not get the entry itself made visible because the contest is closed.
Because I think the affair needs FCC (not FTC) action, I tried to get
people at the FCC to look at my proposal and tell me what's wrong with
it. I've been unsuccessful in getting feedback.
So, other pool of expertise is you. What I'd like is for those of you
so inclined to look at my entry and critique it. If it turns out it
has fatal flaws, so be it, I'll go away quietly. But if there's
consensus that it will work, the next step is to gather suggestions as
to how to get it implemented. At this moment I would guess that means
proposing and advocating new FCC rules, nontrivial as that may be.
Our Moderator, Bill Horne, has kindly posted my entry document on the
telecom web site, even while warning me of the difficulty of this
task. Be aware before you jump in that it's 15 pages (the FTC contest
limit) of fairly small print and technical. Some of you will remember
a thread in this newsgroup about this topic; I exploited information
in that thread and referenced it in the proposal.
You can access the proposal here:
The main thrust of the proposal is to detect Caller ID spoofing. For
your information, the IETF has resurrected its efforts to detect
Caller ID spoofing.
Check it out:
Also available at:
To summarize, what's needed is
1) critiques of my robocall/caller-ID document
2) advice on how to proceed next if we can agree that it will work.
8 years ago