Subject: [Ecrit] ECRIT Milestone updates & corrections

From: Roger Marshall <[email-masked]>
Date: Thu, 21 Jul 2016 18:24:27 +0000

We're in the process of updating the Milestones for ECRIT.  There are 2 changes being proposed.

1. Date change.  The chairs have updated the Milestone dates for the following 4 Internet Drafts (changed from Mar 2016 to Nov 2016):

Nov 2016 Submit 'A LoST extension to return complete and similar location info' to the IESG for consideration as an Informational RFC
draft-ietf-ecrit-similar-location

Nov 2016 Submit 'Next-Generation Pan-European eCall' to the IESG for consideration as an Informational RFC
draft-ietf-ecrit-ecall

Nov 2016 Submit 'Internet Protocol-based In-Vehicle Emergency Calls' to the IESG for consideration as an Informational RFC
draft-ietf-ecrit-car-crash

Nov 2016 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

2. During the update process, an error was discovered in the type of RFC listed withing 3 of the Milestones - each indicating "Informational RFC", instead of "Proposed Standard" as we believe should have been specified from the start.  Each of these 3 drafts are currently, and have been, listed as "std" from its -00 version, as listed in the xml source.

<rfc category="std" ipr="trust200902" docName="draft-ietf-ecrit-car-crash-08.txt"> (currently listed as an Informational RFC)
<rfc category="std" ipr="trust200902" docName="draft-ietf-ecrit-ecall-08.txt"> (currently listed as an Informational RFC)
<rfc category="std" >> ipr="trust200902" docName="draft-ietf-ecrit-similar-location-03"> (currently listed as an Informational RFC)

We Propose these additional changes to each of these 3 Milestones to the status of "Proposed Standard".

Please respond to the list by 7/30, if you object to making the above changes.

Roger & Marc
ECRIT Chairs

NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and/or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media.