Telechat Review of draft-ietf-ecrit-data-only-ea-22
review-ietf-ecrit-data-only-ea-22-secdir-telechat-kaufman-2020-03-25-00

Request Review of draft-ietf-ecrit-data-only-ea
Requested revision No specific revision (document currently at 22)
Type Telechat Review
Team Security Area Directorate (secdir)
Deadline 2020-03-03
Requested 2020-02-14
Authors Brian Rosen , Henning Schulzrinne , Hannes Tschofenig , Randall Gellens
I-D last updated 2020-03-25
Completed reviews Opsdir Last Call review of -18 by Jürgen Schönwälder (diff)
Secdir Last Call review of -18 by Charlie Kaufman (diff)
Genart Last Call review of -18 by Mohit Sethi (diff)
Opsdir Telechat review of -21 by Jürgen Schönwälder (diff)
Iotdir Telechat review of -21 by Gonzalo Salgueiro (diff)
Secdir Telechat review of -22 by Charlie Kaufman
Genart Telechat review of -21 by Mohit Sethi (diff)
Assignment Reviewer Charlie Kaufman
State Completed
Request Telechat review on draft-ietf-ecrit-data-only-ea by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/rTnx1JEshxXRid-0MjXY4mAavXQ/
Reviewed revision 22
Result Ready
Completed 2020-03-09
review-ietf-ecrit-data-only-ea-22-secdir-telechat-kaufman-2020-03-25-00
I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
 Document editors and WG chairs should treat these comments just like any other
last call comments.

This document defines a new MIME type: 'application/EmergencyCallData.cap+xml'
for use primarily by sensors to send alert messages to emergency services
providers. It also defines a new Emergency Call Data Type: 'cap' in order to
embed this data efficiently in a SIP transaction. I saw no new security issues
beyond those already noted for the protocols carrying these messages.

I reviewed version 18 of this document last August, and found no security
issues then either. I made several editorial suggestions and they have been
incorporated in subsequent drafts.

 --Charlie

Sent from Outlook<http://aka.ms/weboutlook>