[Ieprep] RFC 4375 on Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain

rfc-editor@rfc-editor.org Thu, 26 January 2006 01:57 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1wNr-0007ba-3C; Wed, 25 Jan 2006 20:57:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1wNp-0007bM-Hh; Wed, 25 Jan 2006 20:57:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24084; Wed, 25 Jan 2006 20:55:37 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1wXe-0006A6-2s; Wed, 25 Jan 2006 21:07:21 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k0Q1su626217; Wed, 25 Jan 2006 17:54:56 -0800 (PST)
Message-Id: <200601260154.k0Q1su626217@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 25 Jan 2006 17:54:55 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: ieprep@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ieprep] RFC 4375 on Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.


        RFC 4375

        Title:      Emergency Telecommunications Services (ETS)
                    Requirements for a Single Administrative Domain
        Author(s):  K. Carlberg
        Status:     Informational
        Date:       January 2006
        Mailbox:    carlberg@g11.org.uk
        Pages:      8
        Characters: 17037
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ieprep-domain-req-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4375.txt


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.

This document is a product of the Internet Emergency Preparedness
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep