Browse Prior Art Database

IP Telephony Requirements for Emergency Telecommunication Service (ETS) (RFC3690)

IP.com Disclosure Number: IPCOM000021745D
Original Publication Date: 2004-Feb-01
Included in the Prior Art Database: 2004-Feb-05
Document File: 8 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Carlberg: AUTHOR [+2]

Abstract

This document presents a list of requirements in support of Emergency Telecommunications Service (ETS) within the context of IP telephony. It is an extension to the general requirements presented in RFC 3689. Solutions to these requirements are not presented in this document.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Network Working Group K. Carlberg

Request for Comments: 3690 UCL

Category: Informational R. Atkinson

Extreme Networks

February 2004

IP Telephony Requirements for

Emergency Telecommunication Service (ETS)

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

This document presents a list of requirements in support of Emergency

Telecommunications Service (ETS) within the context of IP telephony.

It is an extension to the general requirements presented in RFC 3689.

Solutions to these requirements are not presented in this document.

1. Introduction

Effective telecommunications capabilities can be imperative to

facilitate immediate recovery operations for serious disaster events,

such as, hurricanes, floods, earthquakes, and terrorist attacks.

Disasters can happen unexpectedly, at any time or place. Quick

response for recovery operations requires immediate access to any

public telecommunications capabilities at hand. These capabilities

include: conventional telephone, cellular phones, and Internet

access via online terminals, IP telephones, and wireless Personal

Digital Assistants (PDAs). The commercial telecommunications

infrastructure is rapidly evolving to Internet-based technology.

Therefore, the Internet community needs to consider how it can best

support emergency management and recovery operations.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in [1].

Carlberg & Atkinson Informational [Page 1]

RFC 3690 ETS Telephony Requirements February 2004

1.1. Problem

Standards have been developed by other standards bodies concerning

emergency communications. As discussed in [3], some of these

standards, such as T1.631 [5], define specific indicators or labels

for emergency communications in Signaling System 7 (SS7) networks.

Certain requirements must be defined in order to achieve peering

across hybrid networks (networks that communicate between IP and

other types of networks, such as that realized by the Public Switched

Telephone Network) in order to achieve an interworking of services.

2. Scope

[3] has defined a set of general system requirements to support

Emergency Telecommunications Service (ETS). This document defines an

additional set of system requirements to achieve support for ETS

within the specific context of IP telephony (note that this document

views IP telephony within the context of an end-to-end application

layer service). Solutions to requirements are not defined. The

document does not specify protocol enhancements or specifications.

Note that [4], Requirements for Resource Priority Mechanisms for the

Session Initiation Protocol (SIP), is an RFC that shares some overlap

with this document. However...