SHAKEN & Know Your Customer Jim McEachern Principal Technologist ATIS October 2018

STI-GA/PA - Governance SHAKEN & Analytics SHAKEN Analytics STI-GA/PA - Governance “Root of Trust” Call Blocking STI-CA “Certificate Management” Display to user AS VS “Call Processing” Analytics / CVT Sign “good TNs” Provide traceability Ensure correct use of STI certificates Enabling technology Analyze robocall/spoofing data Detect fraudulent calls Block unwanted calls (at user’s request) Provide a consumer service WC Docket No.17-97 Call Authentication Trust Anchor CG Docket No. 17-59 Advanced Methods to Target and Eliminate Unlawful Robocalls

SHAKEN SHAKEN verifies that the entity originating a call is entitled to use the phone number displayed – nothing more! SHAKEN builds on the information the originating carrier has about the calling party. The originating service provider can only attest to “what it knows”. Enterprise Carrier 0 Carrier 2 SHAKEN

Call Origination Scenario Platform 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … Call Center Multiple Originating Carriers Enterprise Typical real-world call origination scenarios are far more complex.

Know Your Customer Platform 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … Call Center Ledger ? Enterprise Efforts are underway to verify all elements in call origination. No way to effectively link this information to the termination.

SHAKEN Plays Complementary Role Platform SHAKEN could extend the reach of “Know Your Customer” to include terminating network. 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … Call Center Ledger Enterprise Carrier 0 Carrier 2 SHAKEN

SHAKEN: Standards and Governance SHAKEN Governance Authority is an industry led initiative under the auspices of ATIS, with FCC oversight. Enterprise Standards: SHAKEN Standards developed by ATIS/SIP Forum IP-NNI TF Carrier 0 Carrier 2 SHAKEN

Know Your Customer: Standards and Governance Platform Governance must include: Enterprise Call centers Consumer advocates Carriers Others? 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … 1.555.555.0123 1.555.555.0124 1.555.555.0125 1.555.555.0126 1.555.555.0127 … Call Center Ledger Enterprise Standards Analysis underway in various forums, but no consolidated industry effort yet: PACE Consumer Protection Consortium USTelecom ATIS

SHAKEN No Trust Between Carriers and Enterprise TRUST CNAM may or may not have current data Legal Entity Not Verified No baseline of truth Analytics determine based on algorithm - Carrier 0 TRUST Carrier 2 Number not attested Cannot traceback to originating carrier\customer

SHAKEN ? Partial Trust Established Through SHAKEN ONLY TRUST Enterprise TRUST ? CNAM may or may not have current data Legal Entity Not Verified No baseline of truth Analytics determine based on algorithm - Carrier 0 TRUST Carrier 2 Number partially attested Traceback to originating carrier\customer

SHAKEN ? Trust Established Through SHAKEN ONLY TRUST Enterprise TRUST ? CNAM may or may not have current data Legal Entity Not Verified No baseline of truth Analytics determine based on algorithm - Carrier 0 TRUST Carrier 2 Know the number used by the owner Traceback to originating carrier\customer

SHAKEN Trust Established Through Know Your Customer & SHAKEN TRUST Enterprise TRUST Consumer informed of entity who is calling Legal Entity Verified Baseline of truth - Carrier 0 TRUST Carrier 2 Know the number used by the owner Traceback to originating carrier\customer

Summary Focus is different, but complementary: Know Your Customer: focused on the intent of the call SHAKEN: focused on verifying the source of the call The “Know Your Customer” initiative should remain distinct from SHAKEN. Trying to merge the two could compromise both. Coordination between the two initiatives would be valuable: Ensure necessary functionality is supported Understand limitations Coordinated messaging Watch this space…