Subject: [Ecrit] ECRIT Milestone update

From: Roger Marshall <[email-masked]>
Date: Tue, 23 Oct 2012 21:45:04 +0000

Per the IETF84 Vancouver’s meeting minutes, Marc & I have proposed updated milestone dates as below.

Please make a note of each revised milestone date, and let us know of any errors or reasons otherwise that would warrant a change from these proposed dates.

MILESTONE updates:

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

Change to:

Done - 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

Change to:

Mar 2013 - 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

Change to:

Mar 2013 - 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

Change to:

Apr 2013 - 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

Change to:

Dec 2013 - 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

Change to:

Jun 2013 - 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

Change to:

Mar 2013 - Submit 'Public Safety Answering Point (PSAP) Callbacks' to the IESG for consideration as an Informational RFC

Apr 2013 - Submit a draft 'Policy for defining new serviceÃ¢Â€Â“identifying labels' to the IESG for consideration as BCP

(no change)

Roger Marshall & Marc Linsner
ECRIT Chairs

CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.