1 / 8

H. Schulzrinne , S. McCann, G. Bajko , H . Tschofenig, D. Kroeselberg

Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices. H. Schulzrinne , S. McCann, G. Bajko , H . Tschofenig, D. Kroeselberg. Status.

chelsi
Download Presentation

H. Schulzrinne , S. McCann, G. Bajko , H . Tschofenig, D. Kroeselberg

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extensions to the Emergency Services Architecture for dealing withUnauthenticated and Unauthorized Devices H. Schulzrinne, S. McCann, G. Bajko,H. Tschofenig, D. Kroeselberg

  2. Status • draft-ietf-ecrit-unauthenticated-access-03.txt addressed editorial commentsfrom Bernard Aboba, Martin Thomson, and Marc Linsner. • Presentation solicits feedback from WG on version -04 draft. • Scope of the draft: • No Access Authentication (NAA) • No ASP (NASP) • Zero-balance ASP (ZBP)

  3. Issue #1: Current No Access Authentication (NAA) Architecture: Fraud Problem Start Credentialsfornetworkaccessavailable? yes no Waiting for ES callinitiation Lower-layerattach ASP configured? no Emergency NW attachpossible? yes no yes Tell userthat ES callisnot allowed in jusristiction PhoneBCP NASP NAA Authorized? no yes ZBP PhoneBCP

  4. Issue #1: Revised No Access Authentication (NAA) Architecture Start Credentialsfornetworkaccessavailable? yes no Waiting for ES callinitiation Lower-layerattach ASP configured? no Emergency NW attachpossible? yes no yes Tell userthat ES callisnot allowed in jusristiction PhoneBCP NASP NAA Authorized? no yes ZBP PhoneBCP NASP PROPOSAL

  5. Issue #2: Deployment Reality • Today’s networks suffer from many limitations. • Traffic inception (e.g., HTTP redirect) • Lots of user-interaction for network access • Described solution cannot be deployed with today’s network. • PROPOSAL: Add a section to warn about challenges.

  6. Issue #3: Lack of network access authorization • The NAA case only focuses on the lack of credentials but does not consider the case where credentials are available but network access authorization fails nevertheless. • Lack of authorization at the application layer is covered. • QUESTION: Should authorization failure for network access authentication also be described?

  7. Issue #4: Document Writing Style • Draft states the steps that are necessary for performing the emergency call. • Alternative: • Cite selected parts from Phone BCP and say what is not applicable. • Summarize what is different. • PROPOSAL: Leave as is.

  8. New Table of Contents • Introduction • Limitations • Terminology • Architecture • Zero-balance ASP (ZBP) Procedures • No ASP (NASP)Procedures • No Access Authentication (NAA)Procedures • Security Considerations

More Related