This would be a regulatory requirement for any telemarketer to register for a DNA-Marker ID. This ID would be required to be displayed on any Caller ID telephone system, and be audible (computer generated) at the end of any call similar to an SSN for telemarketers - even to answering machines. If a telemarketing call is submitted without their unique "DNA" and they are discovered - steep fines should be levied (suggestion $100 fine per illegal call). If a person is registered with the Do Not Call registry and they post a complaint with the "DNA" account number displayed then that caller would be investigated by inquiry into the Telecom Provider records. Using a crypto device deployed at the sending server that automatically stamps the DNA ID to the caller, which is licensed by the FTC it will assist in tracking down offenders. Technology can also be deployed to devices that receive an inaudible cue by phone receivers to record, and store those certifications (optional). This technology already exists on modern websites with SSL and website certificates. If a certification is not validated with a key provided by the FTC then the call would be automatically dropped & logged by local carriers preventing malicious or unlicensed callers, much like a modern SPAM filter works - but in this case at the LEC/CLEC level. This authentication method provides a steady stream of revenue to the FTC, and oversight into telecom marketer calls. Non-profit callers would be included with special keycodes that are also included in the issuance of any such program at no cost. This is a modern approach with a crypto-certification measure for marketing callers. The cost for implementation by callers would be minimal, and existing Caller ID systems already in place by consumers would be intact requiring no modification as the DNA ID would be displayed. The Crypto certification would limit phreaking, or illicit usage of DNA certificates as the Carrier would be required to produce the records of suspect calls to the FTC.
Log in or sign up for Devpost to join the conversation.