Security Threats and Requirements for Emergency Call Marking and Mapping
RFC 5069

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    ecrit mailing list <ecrit@ietf.org>, 
    ecrit chair <ecrit-chairs@tools.ietf.org>
Subject: Document Action: 'Security Threats and Requirements for 
         Emergency Call Marking and Mapping' to Informational RFC 

The IESG has approved the following document:

- 'Security Threats and Requirements for Emergency Call Marking and 
   Mapping '
   <draft-ietf-ecrit-security-threats-06.txt> as an Informational RFC

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

The IESG contact persons are Jon Peterson and Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-security-threats-06.txt

Technical Summary
 
This document describes the security requirements which must be fulfilled
to prevent or reduce the effectiveness of the attacks on the marking of an
emergency call and the location to PSAP URI mapping system.
 
Working Group Summary
 
The working group supports the advancement of this document.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson. Marc Linsner was
the PROTO shepherd. WG Reviewers are credited in the document.

Note to RFC Editor

Section 6

OLD:

   Requirement R9: the protocol or the system within which it is
   implemented MUST maintain confidentiality of the request and
   response.

NEW:

   Requirement R9: the protocol and the system within which it is
                                ^^^
   implemented MUST maintain confidentiality of the request and
   response.