[Ieprep] RFC 4190 on Framework for Supporting Emergency Telecommunications Service (ETS) in IP Telephony

rfc-editor@rfc-editor.org Wed, 16 November 2005 01:49 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcCQa-0000kL-IC; Tue, 15 Nov 2005 20:49:36 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcCQY-0000k4-9F; Tue, 15 Nov 2005 20:49:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18093; Tue, 15 Nov 2005 20:49:01 -0500 (EST)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EcCht-0005MO-Gd; Tue, 15 Nov 2005 21:07:29 -0500
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jAG1mwE18258; Tue, 15 Nov 2005 17:48:58 -0800 (PST)
Message-Id: <200511160148.jAG1mwE18258@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: Tue, 15 Nov 2005 17:48:58 -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: 9a2be21919e71dc6faef12b370c4ecf5
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: ieprep@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ieprep] RFC 4190 on Framework for Supporting Emergency Telecommunications Service (ETS) in IP Telephony
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 4190

        Title:      Framework for Supporting Emergency
                    Telecommunications Service (ETS) in IP Telephony
        Author(s):  K. Carlberg, I. Brown, C. Beard
        Status:     Informational
        Date:       November 2005
        Mailbox:    k.carlberg@cs.ucl.ac.uk, I.Brown@cs.ucl.ac.uk,
        Pages:      28
        Characters: 69447
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ieprep-framework-10.txt

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

This document presents a framework for supporting authorized,
emergency-related communication within the context of IP telephony.
We present a series of objectives that reflect a general view of how
authorized emergency service, in line with the Emergency
Telecommunications Service (ETS), should be realized within today's
IP architecture and service models.  From these objectives, we
present a corresponding set of protocols and capabilities, which
provide a more specific set of recommendations regarding existing
IETF protocols.  Finally, we present two scenarios that act as
guiding models for the objectives and functions listed in this
document.  These models, coupled with an example of an existing
service in the Public Switched Telephone Network (PSTN), contribute to
a constrained solution space.

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

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