160 likes | 283 Vues
This workshop focused on collaborative policy development to combat caller ID spoofing, an emerging challenge in telecommunications. Key stakeholders, including M3AAWG and LAP, discussed strategies to reduce complaints regarding VoIP abuse, robocalls, and illegal telemarketing. With a phased approach—short, mid, and long-term—participants explored techniques such as call detail record (CDR) sharing, user-initiated blocking, and the implementation of advanced frameworks like STIR and RFC 3325. The initiative emphasizes international cooperation and industry best practices for effective regulation.
E N D
ITU Workshop on “Caller ID Spoofing” (Geneva, Switzerland, 2 June 2014) Collaborative policy development at M3AAWG VTASIG and LAP DNC Hein Dries-Ziekenheiner VIGILO (itu@vigilo.nl)
Introduction • VIGILO • www.vigilo.nl • M3AAWG (Mobile Messaging Malware Anti Abuse Workgroup) • www.m3aawg.org • LAP (London Action Plan) • www.londonactionplan.org
VTASIG • Formed out of M3AAWG membership • Larger (North American, European carriers, ISPs, Senders) • In co-operation with LAP (especially DNC group) • Text book definition: public private partnership
VTASIG • Goal: bring down complaints on Voip abuse • Robocalls • Illegal telemarketing • Fraud • Policy development for three phases: • Short term • Mid term • Long term
Short term • *50 -> CDRs to regulator • Next hop • Find Originator of abuse (enforcement) • Charge back? • Agency determines applicability • Consumer Carrier “Charges Back” upstream carriers • VoIP, Cable-Co, Telco and OTT must adhere to abuse reporting standard • Honeypots • Trace back (P-ANI)
Charge-Back Model *50 M3AAWG 30th General Meeting | San Francisco, February 2014 Agencies Regulators CDR Sharing $5/call Bad CDR’s In or Out of Band Abuse Reporting / Billing Charge Back Charge Back $12/call $10/call $15 / Call Initiates *50
(P)Honey Pots • Goal: gather intelligence using honey pots • Currently: large data set gathered from TNs that were abandoned for abuse CDRs of incoming calls(+1) • CRTC Working on receiving regular numbers from telco’s (more +1) • Georgia Tech: currently working on data to gather information and actionable intelligence
Mid term • Do Not Call list • Abuse from outside SS7 network • Intended mostly for VOIP->SS7 gateways • Compares CgPN to list of “Do not Spoof” (SS7 based consumer) numbers
Mid Term • User initiated blocking? • Taking away legal/regulatory barriers
Mid Term • RFC 3325 P-Asserted-Identity • PAI Header for carriers to assert identiy (CID) of user • Also for privacy options • Creates a Trusted domain • Subject to common spec(T) • Could even work in hybrid networks (SS7/VOIP with SS7/ISUP trust bits)
Mid Term • User initiated blocking? • Taking away legal/regulatory barriers
Long term • STIR • Others will present on this • M3AAWG/LAP follow development • Consider implications
Conclusions and recommendations No silver bullet International co-operation (PPP) required National level: keep eye out for complaint levels ..And respond with Best Practices defined internationally For regulators: join LAP Industry: join M3AAWG Together:VTASIG Brussels, Montreal, Boston, SF Further info: itu@vigilo.nl www.vigilo.nl