Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain
RFC 4375

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: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    ieprep mailing list <ieprep@ietf.org>, 
    ieprep chair <ieprep-chairs@tools.ietf.org>
Subject: Document Action: 'Emergency Telecommunications Services 
         (ETS) Requirements for a Single Administrative Domain' to 
         Informational RFC 

The IESG has approved the following document:

- 'Emergency Telecommunications Services (ETS) Requirements for a Single 
   Administrative Domain '
   <draft-ietf-ieprep-domain-req-07.txt> as an Informational RFC

This document is the product of the Internet Emergency Preparedness 
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-ieprep-domain-req-07.txt

Ballot Text

Technical Summary

This document presents a list of requirements in support of Emergency
Telecommunications Service (ETS) within a single administrative domain.

Working Group Summary
 
The IEPREP Working Group supported the advancement of this document.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.

Note to RFC Editor
 
Please change the Abstract as follows:

OLD:

   This document presents a list of requirements in support of Emergency
   Telecommunications Service (ETS) within a single administrative
   domain. This document is an extension of the General Requirements of
   [rfc3689] and focuses on a more specific set of administrative
   constraints and scope.  Solutions to these requirements are not
   presented in this document.

NEW:

   This document presents a list of requirements in support of Emergency
   Telecommunications Service (ETS) within a single administrative
   domain. This document focuses on a specific set of administrative
   constraints and scope.  Solutions to these requirements are not
   presented in this document.

RFC Editor Note