TECH TRANSITION UPDATE

Transcription

1 ATIS Denver May TECH TRANSITION UPDATE Henning Schulzrinne ATIS May Denver

2 ATIS Denver May Overview Tech transition Service trials Rural broadband Numbering: numbering testbed workshop Data gathering: where are we? what motivates consumer choices? Managerial framework: address hard policy issues Challenges ahead Public safety Robocalls Moving beyond 1980s services

3 ATIS Denver May Technology Transitions application transport network TDM voice TDM circuits & analog VoIP (incl. VoLTE) IP packets physical layer copper twisted-pair fiber coax wireless copper twisted-pair (and combinations) satellite

4 ATIS Denver May What are some of the keeper attributes? Universality reachability global numbering & interconnection media HD audio, video, text availability universal service regardless of geography income disability affordability service competition + affordable standalone broadband Public safety citizen-to-authority: emergency services (911) authority-to-citizen: alerting law enforcement survivable (facilities redundancy, power outages) Quality media (voice + ) quality assured identity: telephone numbers assured privacy (CPNI) accountable reliability initial list not exhaustive

5 ATIS Denver May Service-based trials Currently, only AT&T for wirecenter-style trials West Delray Beach, Florida and Carbon Hill, Alabama others have hinted combination of wireline & wireless & TBD stages: opt-in, no new customers, conversion No 214 (discontinuance) requests yet What parameters should be measured QoS and reliability? Customer satisfaction? Economic impact?

6 ATIS Denver May Other Jan. 30, 2014 Commission item Targeted experiments rural America: invite bids for serving with robust broadband, including by non-traditional carriers (e.g., rural electric utilities) ~1000 declarations of interest: rural electric cooperatives, communities, rural phone companies, WISPs people with disabilities: $3M research fund for relay services numbering: workshop and test bed for all-ip numbering Data improvement consumer complaint system intergovernmental cooperation NG911 data other data sources

7 ATIS Denver May Getting out of the death spiral AOL model (generate cash from captive customers)? Not in the public interest: same 3.5 khz audio, lower voice quality (if 3G), higher prices, less dependable during power outages, less reliable 911, more robocalls, can t reach some customers ( retrans standoffs for phone service ), fewer consumer protections, How can we make faster progress? HD audio Video & text integration Third-party features ( apps ) Better caller identification beyond # & 16 characters NG911 for all networks Simpler networks let IP networks ignore TDM legacy constraints

8 ATIS Denver May Sample issues Power backup can we get to 24 hour battery backup for basic broadband + voice access? standard consumer-replaceable batteries Nuisance calls can we reduce nuisance (robo) calls? Reliable 911 can we provide precise business & in-home location?

9 NUMBERS ATIS Denver May

10 ATIS Denver May Communication identifiers Property Example E.164 Servicespecific Protocolindependent URL owned e URL provider alice@gmail.com sip:alice@ilec.co m m/alice.example no no yes yes Multimedia yes yes maybe (VRS) maybe Portable yes no somewhat no Groups yes yes bridge number Trademark issues Privacy not generally yes unlikely unlikely possible Depends on name chosen (pseudonym) Depends on naming scheme mostly Depends on provider real name policy

11 ATIS Denver May Numbering philosophy Avoid incrementalism clean slate start with requirements Assume all-voip environment and (probably) after any current numbering-related contract Leave old system for backward compatibility until last TDM switch dies fed by same authoritative data bases Separate policy and mechanism e.g., mechanism supports anybody can get any number anywhere and can port numbers in any way they like start with flexible mechanism and policy knobs, not built-to-policy policy may restrict number availability (e.g., geographic or by entity type) and porting Built-in security: spoofing, data privacy Additional services: e.g., property assertions ( gov t agency )

12 ATIS Denver May Reconsider assumptions NANPA, LNP, LERG, RespOrg, separation numerous separate databases with often unclear data flows and business models that encourage rent-seeking (or outright criminality see CNAM fraud) Golden root databases can the technology support a federated, competitive model similar to the white space databases? roughly 10 operators that exchange data to ensure consistency

13 ATIS Denver May The role of rate centers/latas Unclear that anybody knows any more what local or intra-lata calls are if needed, maybe an automated 800# that provides information? Bill & keep impact Intersects with LNP restrictions are confusing to consumers and prevent full intermodal porting Can we do this for VoIP only?

14 ATIS Denver May Geographic numbering Increasingly confusing to consumers e.g., wireline wireless wireline Still relevant, but probably decreasing like SSN: indicates state of birth/youth? What do ivoip providers (SIP trunking, cable) do? Could states restrict numbers by initial geographic nexus? Germany requires address verification By usage type (human vs. machine)? existing wireline geo restrictions affinity restrictions usage restrictions national pool

15 registrar ATIS Denver May Architecture 1: tree registry # assignee

16 ATIS Denver May Architecture 2: mesh + tree global time registry assumed to be cooperative example: TV whitespace DB, LoST (NG911) registry registry registrar registry # assignee

17 registrar ATIS Denver May Protocol interactions # assignee EPP? DRINKS? registry public or private DNS HTTP + JSON create delete transfer update renew info number NAPTR DN S number + credentials properties

18 ATIS Denver May Number meta-data Data element E.164 number key OCN Expiration date Public key whois record Log entries (who, what, when)? Comments several for different media & geographic scope? if records expire for STIR similar to domain name? need to be visible?

19 ATIS Denver May Test bed for exploring numbering issues MOADB, JIT, ENUM, STIR, move from reports to prototypes and testing neutral, non-production, collaborative, non-legacy IETF mailing REST + JSON? protocol ( API ) client (emulate providers) DB implement API (server side) emulate NANPA-NG multiple instances legacy DBs ENUM

20 NUISANCE CALLS ATIS Denver May

21 ATIS Denver May Impact of illegal robocalls Consumer fraud Nuisance impact on landline higher than cell phone increase abandonment of landlines? Loss of phone numbers (personal & small business) Impact on legitimate mass-calling services (e.g., alerts) Cost to carriers: Customer service calls with no good resolution ICC fraud

22 ATIS Denver May Three parts of phone number identity Phone number (CNG) nuisance call backs vishing Textual caller ID impersonation ( IRS ) Citibank & Citybank Properties registered charity political candidate gov t agency bank

23 ATIS Denver May Stop spoofing stop robocalls If numbers can be trusted, filters work: industry-wide fraudulent number list (e.g., DoNotCall violators) crowd-sourcing bad numbers by other consumers and services Filter options: opt-in service by terminating carrier (e.g., using consumer-chosen source of numbers) app on Android smartphones corporate PBX and hosted VoIP services Enable consumer choice Note: initially, only some calls will be validated Type of call Validated? Sample action Personal friend (in address book) Maybe answer Good robocaller (e.g., alert service, airline) Yes answer Lazy robocaller (legal) No voic Bad robocaller No voic

24 ATIS Denver May Caller validation requirements Multiple legitimate users of number multiple private-public key pairs Carrier, (large) customer, agent of customer (call center) Avoid interruptions if (say) agent changes Incremental deployment with at least proportional value protect high-value targets first Work with existing number management systems may have separate interfaces but not too strongly tied may evolve slowly Avoid single high-value key store targets don t want to revoke all +1 numbers Avoid religious arguments about DNS vs. HTTP numbering authority carrier with OCN reseller telecom customer agent

25 ATIS Denver May Basic caller-id validation architecture cert or public key validate validate validate LD carrier local carrier signs number after normalization SS7 may tunnel as UUI rendezvous mechanism

26 ATIS Denver May Validation: assignment with delegation Reseller Carrier private key {1544, PuK 1, gov} web service {1544, PuK 1, gov} web service {1544, PuK 1, gov} public key PuK 1 Customer generates key pair, doesn t share private key with anyone similar for certificate CSR Reseller authenticates Customer using normal auth (cert, HTTP Basic, API key, ) same for carrier registry Number PuK Prop PuK 1.gov PuK 2.edu

27 ATIS Denver May Short term (partial) robocall solutions International gateways mark or drop calls that have unassigned numbers invalid blocks numbers not yet assigned within block numbers assigned to TDM companies numbers explicitly blocked by customer (e.g., banks, police, IRS) Automatic reporting of robocalls Working on updated consumer complaint system with API Allow third parties to build filtering tools Implement API or simultaneous ringing e.g., make block list programmable

28 PUBLIC SAFETY ATIS Denver May

29 ATIS Denver May Some public safety challenges Telephony denial-of-service attacks Transition in user behaviors and home capabilities Emergency alerting good for seek shelter now not so great for multi-day informational outreach Sandy: where can I find gas? which roads are passable? Redundancy that isn t small number of selective routers or SIP proxies One 911 app per PSAP innovate around slow 911 tech evolution but fragmentation Indoor location determination

30 CAMA trunks ATIS Denver May

31 1980s home model ATIS Denver May

32 ATIS Denver May Typical Millenials apartment

33 ATIS Denver May Indirect 911 screen PSAP

34 ATIS Denver May TDOS Payday loan & false tax debt extortion Pay or swamp phone lines Hospitals, PSAPs, schools,

35 ATIS Denver 35 May 2014 Indoor Location Accuracy -- 3rd Further Notice of Proposed Rulemaking Indoor Parameter Deadline Accuracy Percent of Calls Horizontal (x-y) Within 2 years of Effective Date of Rule Within 5 years of Effective Date of Rule 50 meters 67% 50 meters 80% Feb Vertical (z-axis) Within 3 years of Effective Date of Rule Within 5 years of Effective Date of Rule 3 meters 67% 3 meters 80%

36 ATIS Denver May Public safety long term vision Everybody should be able to reach 911 reliably resilient: attack, volume independent of the technology used for general purpose communication services with appropriate media real-time text, photos, maybe video with precise location GNSS-precise outdoors apartment, office, hotel room or suite indoors direct or via mediated services Efficient overall system separate human interface from telecom service provision not every PSAP needs to be its own telecom kingdom do we really need 6,000 PSAPs? we re for all IP, except when we re selling CAMA trunks

37 ATIS Denver May Indoor location 70% (est.) of wireless calls indoors GPS generally only works in woodframe single-family homes or near windows Does not provide floor or apartment/cubicle Can deliver cronut coupons to within 10, but not EMTs to the right store Integrate multiple location technologies rough for routing, backup and spoofing prevention fine-grained for dispatch not all technologies all the time consider building infrastructure

38 ATIS Denver May Improving monitoring & statistics Old model: largely local facilities & monitoring limited on-going location accuracy testing limited analysis Opportunity: state-wide or regional network operations center remote recovery statistics response time components nature of calls location accuracy

39 ATIS Denver May Integration of emergency handling into day-to-day operations Larger roles for fire marshals location accuracy testing 911 dialability in hotels & other semi-public buildings Integration of commercial technologies and emergency handling e.g., use ad networks for delivering emergency Using delivery vehicles for location accuracy testing Is there a clear boundary between 311, 911 and information dissemination? public safety as information hub

40 ATIS Denver May Conclusion Pieces falling into place core underlying protocol standards operational experience business models Commission willing to move expeditiously Maintain consumer value proposition Time for timelines? Go do it!