Last Modified: 2009-09-30
Done | Informational RFC containing terminology definitions and the requirements | |
Done | An Informational document describing the threats and security considerations | |
Done | A Standards Track RFC describing how to identify a session set-up request is to an emergency response center | |
Done | A Standards Track RFC describing how to route an emergency call based on location information | |
Done | An Informational document describing the Mapping Protocol Architecture | |
Done | Submit 'Location Hiding: Problem Statement and Requirements' to the IESG for consideration as an Informational RFC. | |
Done | Submit 'Framework for Emergency Calling using Internet Multimedia' to the IESG for consideration as an Informational RFC. | |
Done | Submit 'Best Current Practice for Communications Services in support of Emergency Calling' to the IESG for consideration as a BCP document | |
Oct 2009 | Submit 'Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements' to the IESG for consideration as an Experimental RFC | |
Dec 2009 | Submit "LoST Extension for returning Boundary Information for Services" to the IESG for consideration as an Experimental RFC | |
Mar 2010 | Submit "Using Imprecise Location for Emergency Call Routing" to the IESG for consideration as an Informational RFC |
RFC | Status | Title |
---|---|---|
RFC5012 | I | Requirements for Emergency Context Resolution with Internet Technologies |
RFC5031 | PS | A Uniform Resource Name (URN) for Emergency and Other Well-Known Services |
RFC5069 | I | Security Threats and Requirements for Emergency Call Marking and Mapping |
RFC5222 | PS | LoST: A Location-to-Service Translation Protocol |
RFC5223 | PS | Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP) |
RFC5582 | I | Location-to-URL Mapping Architecture and Framework |
None received.