Subject: [Ecrit] Correcting Milestone descriptions - RFC type for 3 IDs

From: Roger Marshall <[email-masked]>
Date: Thu, 4 Aug 2016 15:37:56 +0000

As was mentioned in Berlin at IETF96 during the Chairs discussion, there is a need to align Milestone descriptions with what is in 3 Internet Drafts (links below).  The reason for these changes is to correct errors made during the original milestone submission process.  These IDs have been labeled appropriately as Stds Track RFCs from their inception at -00, we just need to properly list them in the Milestone list as the same.

Changed from:
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

To:
Nov 2016 	Submit 'A LoST extension to return complete and similar location info' to the IESG for consideration as a Standards Track RFC
draft-ietf-ecrit-similar-location
Nov 2016 	Submit 'Next-Generation Pan-European eCall' to the IESG for consideration as a Standards Track RFC
draft-ietf-ecrit-ecall
Nov 2016 	Submit 'Internet Protocol-based In-Vehicle Emergency Calls' to the IESG for consideration as a Standards Track RFC
draft-ietf-ecrit-car-crash

Reference links:
https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/
https://datatracker.ietf.org/doc/draft-ietf-ecrit-car-crash/
https://datatracker.ietf.org/doc/draft-ietf-ecrit-similar-location/

Does anyone object to aligning these milestone descriptions with the document descriptions?

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.