1 / 4

Enhancements to RFC 5222: Extending LoST Service Response for Improved Location Accuracy

This document outlines proposed extensions to RFC 5222, focusing on the LoST (Location-to-Service Translation) service. Two key extensions are described: how to handle incomplete civic locations while providing additional context, and how to suggest alternative locations if the provided civic address is marked as invalid. The revisions enhance clarity, security, and alignment with existing RFC standards, facilitating better use within emergency services and location records. This update serves as a valuable tool for the deployment of NG9-1-1 systems and improves client awareness of location-related information.

juan
Télécharger la présentation

Enhancements to RFC 5222: Extending LoST Service Response for Improved Location Accuracy

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. :: ecrit-similar-location RogerMarshall, Jeff Martin - TeleCommunication Systems Brian Rosen - Neustar

  2. :: Extends RFC 5222 LoSTfindServiceResponse message :: Two extensions described -- If returned civic location is valid, yet is incomplete, and LoST server knows more :: Provides additional caType elements -- If returned civic location has any civic address elements marked as <invalid> :: Suggests alternative locations :: Overview

  3. :: Revised to -04 based on a couple of reviews -- Better describe how this extension can be useful -- Align with RFC2119 -- Discuss if/how clients can be made aware of this extension’s added information -- Add security considerations around more info than input for both valid and invalid addresses -- Acknowledged the need for extension point RelaxNG/detailed xml and examples -- Reworked terminology to better align with text -- General editorial cleanup [thank you Barbara Stark & Scott Bradner] :: Update

  4. :: Not too different from addressing interfaces that inquire, “Did you mean?” :: Emergency Services dependencies do exist (NENA/EENA) -- LIS provision of location records -- Valuable tool in deployment of NG9-1-1 :: WG Adopt? :: Next Steps

More Related