A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain
RFC 4958
|
| Document |
Type |
|
RFC - Informational
(July 2007; Errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 4958 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Jon Peterson
|
|
Send notices to |
|
kimberly.s.king@saic.com
|
Network Working Group K. Carlberg
Request for Comments: 4958 G11
Category: Informational July 2007
A Framework for Supporting Emergency Telecommunications Services (ETS)
within a Single Administrative Domain
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 IETF Trust (2007).
Abstract
This document presents a framework discussing the role of various
protocols and mechanisms that could be considered candidates for
supporting Emergency Telecommunication Services (ETS) within a single
administrative domain. Comments about their potential usage as well
as their current deployment are provided to the reader. Specific
solutions are not presented.
Carlberg Informational [Page 1]
RFC 4958 ETS Single Domain Framework July 2007
Table of Contents
1. Introduction ....................................................3
1.1. Differences between Single and Inter-Domain ................3
2. Common Practice: Provisioning ...................................4
3. Objective .......................................................5
3.1. Scenarios ..................................................5
4. Topic Areas .....................................................6
4.1. MPLS .......................................................6
4.2. RSVP .......................................................7
4.2.1. Relation to ETS .....................................8
4.3. Policy .....................................................8
4.4. Subnetwork Technologies ....................................9
4.4.1. IEEE 802.1 VLANs ....................................9
4.4.2. IEEE 802.11e QoS ...................................10
4.4.3. Cable Networks .....................................10
4.5. Multicast .................................................11
4.5.1. IP Layer ...........................................12
4.5.2. IEEE 802.1d MAC Bridges ............................12
4.6. Discovery .................................................13
4.7. Differentiated Services (Diffserv) ........................14
5. Security Considerations ........................................14
6. Summary Comments ...............................................15
7. Acknowledgements ...............................................15
8. References .....................................................15
8.1. Normative Reference .......................................15
8.2. Informative References ....................................15
Carlberg Informational [Page 2]
RFC 4958 ETS Single Domain Framework July 2007
1. Introduction
This document presents a framework for supporting Emergency
Telecommunications Services (ETS) within the scope of a single
administrative domain. This narrow scope provides a reference point
for considering protocols that could be deployed to support ETS.
[rfc4375] is a complementary effort that articulates requirements for
a single administrative domain and defines it as "collection of
resources under the control of a single administrative authority".
We use this other effort as both a starting point and guide for this
document.
A different example of a framework document for ETS is [rfc4190],
which focused on support for ETS within IP telephony. In this case,
the focal point was a particular application whose flows could span
multiple autonomous domains. Even though this document uses a
somewhat more constrained perspective than [rfc4190], we can still
expect some measure of overlap in the areas that are discussed.
1.1. Differences between Single and Inter-Domain
The progression of our work in the following sections is helped by
stating some key differences between the single and inter-domain
cases. From a general perspective, one can start by observing the
following.
a) Congruent with physical topology of resources, each domain is
an authority zone, and there is currently no scalable way to
transfer authority between zones.
b) Each authority zone is under separate management.
c) Authority zones are run by competitors; this acts as further
deterrent to transferring authority.
Show full document text