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 |
Done | | Submit |
Oct 2010 | | Submit 'Synchronizing Location-to-Service Translation (LoST)
Protocol based Service Boundaries and Mapping Elements' to the
IESG for consideration as an Experimental RFC |
Nov 2010 | | Submit 'Using Imprecise Location for Emergency Call Routing' to
the IESG for consideration as an Informational RFC |
Mar 2011 | | Submit 'Additional Data related to a Call for Emergency Call
Purposes' to the IESG for consideration as a Standards Track
RFC |
Apr 2011 | | Submit 'Common Alerting Protocol (CAP) based Data-Only
Emergency Alerts using the Session Initiation Protocol (SIP)'
to the IESG for consideration as an Experimental RFC |
Dec 2011 | | Submit 'Extensions to the Emergency Services Architecture for
dealing with Unauthenticated and Unauthorized Devices' to the
IESG for consideration as a Standards Track RFC |
Jan 2012 | | Submit 'Trustworthy Location Information' to the IESG for
consideration as an Informational RFC |
Mar 2012 | | Submit 'Public Safety Answering Point (PSAP) Callbacks' to the
IESG for consideration as an Informational RFC |