Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-27

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: allison.mankin@gmail.com, "Allison Mankin" <allison.mankin@gmail.com>, alissa@cooperw.in, ecrit-chairs@ietf.org, "The IESG" <iesg@ietf.org>, draft-ietf-ecrit-ecall@ietf.org, rfc-editor@rfc-editor.org, ecrit@ietf.org
Subject: Protocol Action: 'Next-Generation Pan-European eCall' to Proposed Standard (draft-ietf-ecrit-ecall-27.txt)

The IESG has approved the following document:
- 'Next-Generation Pan-European eCall'
  (draft-ietf-ecrit-ecall-27.txt) as Proposed Standard

This document is the product of the Emergency Context Resolution with
Internet Technologies Working Group.

The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa
Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/

Ballot Text

Technical Summary
draft-ietf-ecrit-ecall specifies IETF mechanisms to support next-generation pan-European eCall (European vehicle-initiated emergency calls).  It also provides the basis for next-generation vehicle-initiated emergency calls in other regions.  The document also registers MIME media types and an INFO package.  Multiple SDOs (including 3GPP, 3GPP2, CEN, NENA, and others) have references to this document and are waiting for an RFC number.

Working Group Summary

The document was reviewed by a large number of people during its development.  Towards the end it received a large number of comments from a small number of people, and their comments were carefully considered, and resolved with good (mostly not rough) consensus.  Multiple WG participants also participate in the SDOs intending to use this document and have made sure the document meets the needs of those SDOs.

Document Quality

There are not presently implementations of the protocol, but the SDOs charged with overall next-generation pan-European emergency call have many vendors interested in implementation on a quick timetable. 

Media types registered by this document received expert review on the mediatypes mailing list.  The expertise of Ned Freed, in particular, was extremely helpful in solving an issue that arose, in a way that was compatible with a predecessor document, RFC 7852.
The media type discussion can be found in the thread that begins with:

https://www.ietf.org/mail-archive/web/media-types/current/msg00835.html

Other types of formal expert review were not required.  
 
Personnel

  Allison Mankin is the Document Shepherd. Alissa Cooper is the Responsible Area Director

RFC Editor Note