draft-ietf-ieprep-domain-req-02.txt   draft-ietf-ieprep-domain-req-03.txt 
Internet Engineering Task Force Ken Carlberg Internet Engineering Task Force Ken Carlberg
Sept 21, 2004 Oct 19, 2004
Emergency Telecommunications Services (ETS) Requirements Emergency Telecommunications Services (ETS) Requirements
for a Single Administrative Domain for a Single Administrative Domain
<draft-ietf-ieprep-domain-req-02.txt> <draft-ietf-ieprep-domain-req-03.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of [rfc3668]. all provisions of Section 10 of [rfc3668].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 32 skipping to change at page 1, line 31
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft
Shadow Directories can be accessed at Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
For potential updates to the above required-text see: For potential updates to the above required-text see:
http://www.ietf.org/ietf/1id-guidelines.txt http://www.ietf.org/ietf/1id-guidelines.txt
IPR Disclosure Acknowledgement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Abstract Abstract
This document presents a list of requirements in support of Emergency This document presents a list of requirements in support of Emergency
Telecommunications Service (ETS) within a single administrative Telecommunications Service (ETS) within a single administrative
domain. This document is an extension of the General Requirements of domain. This document is an extension of the General Requirements of
[rfc3689] and focuses on a more specific set of administrative [rfc3689] and focuses on a more specific set of administrative
constraints and scope. Solutions to these requirements are not constraints and scope. Solutions to these requirements are not
presented in this document. presented in this document.
1. Introduction 1. Introduction
skipping to change at page 5, line 47 skipping to change at page 6, line 9
The form of the service provided to ETS users and articulated in the The form of the service provided to ETS users and articulated in the
form of policies may be realized in one of several forms. Better form of policies may be realized in one of several forms. Better
than best effort is probably the service that most ETS users would than best effort is probably the service that most ETS users would
expect when the communication system is stressed and overall quality expect when the communication system is stressed and overall quality
has degraded. However, the concept of best available service should has degraded. However, the concept of best available service should
also be considered under such stressed conditions. Further, a also be considered under such stressed conditions. Further, a
measure of degraded service may also be desirable to ensure a measure measure of degraded service may also be desirable to ensure a measure
of communication versus none. These services may be made available of communication versus none. These services may be made available
at the network or application layer. at the network or application layer.
4.2 "Emergency" 4.2 Redundancy
The ITU has migrated away from the term "emergency" and ETS because
of legal ramifications within the U.K. Apparantly, there is a legal
expectation when the term "emergency" is used as a service. Hence,
the ITU is currently using the term Telecommunications for Disaster
Relief (TDR). Legal issues such as this are outside the scope of
this document and the IETF. However, to provide a bridge of
understanding, the reader can assume that ETS within the IETF is
synonymous with TDR in the ITU -- each involving authorized use of a
service that attempts to compensate for stressed conditions of
resources.
4.3 Redundancy
The issue of making network fault tolerant is important and yet not The issue of making network fault tolerant is important and yet not
one that can be easily articulated in terms of requirements. one that can be easily articulated in terms of requirements.
Redundancy in connectivity and nodes (be it routers or servers) is Redundancy in connectivity and nodes (be it routers or servers) is
probably the most common approach taken by network adminstrators, and probably the most common approach taken by network adminstrators, and
it can be assumed that administrative domains apply this approach in it can be assumed that administrative domains apply this approach in
various degrees to there own resources. various degrees to there own resources.
5. Security Considerations 5. Security Considerations
skipping to change at page 7, line 18 skipping to change at page 7, line 15
Emergency Telecommunications Service", RFC3689 Emergency Telecommunications Service", RFC3689
Feb 2004 Feb 2004
[rfc2119] Bradner, S., "Key words for use in RFCs to Indicate [rfc2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[frame] Carlberg, K., "A Framework for Supporting ETS in Stub [frame] Carlberg, K., "A Framework for Supporting ETS in Stub
Domains", Internet Draft, Work in Progress, Domains", Internet Draft, Work in Progress,
draft-ieprep-domain-frame-02.txt, June 2003. draft-ieprep-domain-frame-02.txt, June 2003.
8. IPR Disclosure Acknowledgement 8. Author's Addresses
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
9. Author's Addresses
Ken Carlberg Ken Carlberg
G11 G11
123a Versailles Circle 123a Versailles Circle
Baltimore, MD Baltimore, MD
USA USA
carlberg@g11.org.uk carlberg@g11.org.uk
Full Copyright Statement Full Copyright Statement
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/