1 / 7

draft- ietf-ecrit-location-hiding-req Location Hiding: Problem Statement and Requirements

draft- ietf-ecrit-location-hiding-req Location Hiding: Problem Statement and Requirements. Henning Schulzrinne , Laura Liess , Hannes Tschofenig , Barbara Stark, A. Kuett. Overview. Makes no recommendation right now probably needs overall service requirement.

austin
Download Presentation

draft- ietf-ecrit-location-hiding-req Location Hiding: Problem Statement and Requirements

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. draft-ietf-ecrit-location-hiding-reqLocation Hiding: Problem Statement and Requirements Henning Schulzrinne, Laura Liess, HannesTschofenig, Barbara Stark, A. Kuett ECRIT - IETF 72 (Dublin)

  2. Overview • Makes no recommendation right now • probably needs overall service requirement. • Assumes exiting ECRIT architecture • e.g., LoST may be operated by VSP • not, say, ISP-based HELD, LoST and call routing • LbyR with PSAP access control out of scope • may not suffice for LoST ECRIT - IETF 72 (Dublin)

  3. High-level Requirements • A: ISP SHOULD be able to withhold LI. • B: End point and VSP MUST be able to route calls. • C: VSP MUST be able to validate URL as emergency URL. • D: PSAP MUST be able to get precise location information. ECRIT - IETF 72 (Dublin)

  4. Detailed requirements • 1: no business relationship ISP & VSP • 2: VSP outside PSAP jurisdiction • 3: no manual configuration • 4: same end point steps (SHOULD) • 5: works for non-SIP • 6: must work with PSAP holes • 7: must not assume higher-level ESRPs ECRIT - IETF 72 (Dublin)

  5. Detailed requirements • 8: different service boundaries for different services • 9: no trial-and-error (otherwise trial-and-judgment ) • 10: must work prior to call • 11: discover dial string prior to call • 12: minimal UA impact • 13: must allow LoST usage for non-emergency services • 15: calls may reach PSTN gateway ECRIT - IETF 72 (Dublin)

  6. Desirable • No cost shifting to non-hiding ISPs, UAs, VSPs • Minimal impact on LoST, SIP conveyance, DHCP • Don’t rely on DHCP to configure LoST server ECRIT - IETF 72 (Dublin)

  7. To do • Req: no impact on automated call testing • SHOULD allow PSAP to provide location information for validation • “You have reached the Dublin PSAP. You are located in Citywest Hotel, Saggart County, Ireland.” • Security requirements: must have no impact on LoST or call integrity • e.g., munging signed responses no-no • Add sentence on user location validation • inherent impact • Otherwise done. ECRIT - IETF 72 (Dublin)

More Related