1 / 8

Geopriv Location Error Registry

This draft aims to bring together granular location-based error codes to enhance the original sending device's understanding of what went wrong with the sent message. It also promotes interoperability between protocols.

smcdaniels
Download Presentation

Geopriv Location Error Registry

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. Geopriv Location Error Registry draft-polk-geopriv-location-based-error-registry-00 James Polk

  2. What is it? • An attempt to bring together granular location based error codes so the original sending devices knows what was wrong with the sent message, and to promote interoperability between protocols

  3. An example of use Alice Bob | | | Request w/ Location | |--------------------------------->| | | ********************** | | * There is something * | | * wrong with the * | | * supplied Location * | | ********************** | 424 (Bad Location Information) | | with Location Error indication | |<---------------------------------| | |

  4. An example of use Alice Proxy | | | Request w/ Location | |--------------------------------->| | | ********************** | | * There is something * | | * wrong with the * | | * supplied Location * | | ********************** | 424 (Bad Location Information) | | with Location Error indication | |<---------------------------------| | |

  5. Error Codes to Register Cause-Code Optional-Default-Text ---------- --------------------- Cause=1 Location Format Not Supported Cause=2 Geo-location Format Desired Cause=3 Civic-location Format Desired Cause=4 Unsupported Schema Cause=5 Cannot Parse Location Supplied Cause=6 Cannot Find Location Cause=7 Cannot Dereference Cause=8 Conflicting Locations Supplied Cause=9 Incomplete Location Supplied Cause=10 Dereference Timeout Cause=11 Cannot Process Dereference Cause=400 Bad Request Cause=403 Forbidden Cause=404 Not Found Cause=414 Location Error Cause=500 Server Internal Error Cause=501 Service Not Implemented Cause=504 Server Time-Out Based on Lost -01, this is the list of Error codes to Register

  6. A Suggestion Made... #1 - There has been a suggestion made, for Cause=4; Unsupported Schema To include a list of those schemas that the original recipient wants in the subsequent message Solution Proposed: Cause=4; Unsupported Schema; sip-uri Means the sent schema is not acceptable, send a sip-uri instead • This can typically have multiple answers, for example: Cause=4; Unsupported Schema; sip-uri; sips-uri, pres-uri • Or individual ones (grouped numbering now): Cause=20; Unsupported Schema; sip-uri; Cause=21; Unsupported Schema; sips-uri; Cause=22; Unsupported Schema; pres-uri;

  7. Other Suggestions Made... #2 - This should be done in each Using Protocol doc #3 - This doc is turned into a INFO doc, that’s generalized to not list error code numbers, but list error types that should be supported – or explained why not.

  8. What to do... • I don’t really care (believing something should be done here), but we have to do it asap • ...for the Conveyance ID • I need to input the error codes into Conveyance and IANA Register them if This WEEK if Geopriv doesn’t want this effort (and I’m presenting in SIP on Friday morning)

More Related