One document matched: draft-jesske-ecrit-ecall-urn-extension-00.txt
Network Working Group R. Jesske
Internet-Draft Deutsche Telekom
Intended status: Standards Track June 25, 2013
Expires: December 27, 2013
Uniform Resource Name (URN) extension for automatic and manual Emergency
Services
draft-jesske-ecrit-ecall-urn-extension-00
Abstract
This document describes a mechanism for extending sos URN's to
fulfill the emergency call requirements of carriers.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 27, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Jesske Expires December 27, 2013 [Page 1]
Internet-Draft June 2013
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Overall Applicability . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. IANA Consideration . . . . . . . . . . . . . . . . . . . . . 4
4.1. New Service-Identifying Labels . . . . . . . . . . . . . 4
4.2. sublabel for sos service and the relarted subservices . . 4
4.3. IANA Registration . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Contributors and Acknowledgements . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Overall Applicability
Uniform Resource Name (URN) for emergency and other Well-Known
Services are well defined within IETF RFC 5031. There are also
existing proposals for automatic and manual ecall IN-Vehicles which
defines their own URN's and additional procedures for vehicle
specific eCalls. Due to the existing telecommunication world and
their implementations a combination of both is needed. Due to the
fact that only one URN can be used within the request line of a SIP
Message a new approach is needed. Therefore this document proposes
to extend the existing URN's with an extension to reflect this.
2. Conventions
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 [RFC2119].
3. Overview
RFC5031[RFC5031] defines URN values for emergency calls. The values
for the SOS subtree are sos.ambulance, sos.animal-control, sos.fire,
Jesske Expires December 27, 2013 [Page 2]
Internet-Draft June 2013
sos.gas, sos.marine, sos.mountain , sos.physician, sos.poison and
sos.police and draft-rosen-ecrit-
ecall-08.txt[draft-rosen-ecrit-ecall-08.txt] proposes two additional
URN for ecall. automatic and ecall.manual the sub-services 'sos' as
specified in Section 4.2 of RFC5031 [RFC5031].
Within the existing implementation in GSM networks for emergency call
as specified in 3GPP TS 22.101 [TS22101] the following requirements
and code points are described:
---------------------------------------------------------------------
---
It shall be possible to initiate emergency calls to different
emergency call centres, depending on the type of emergency. The
following types of emergency calls shall be possible:
o Police
o Ambulance
o Fire Brigade
o Marine Guard
o Mountain Rescue
o Manually Initiated eCall
o Automatically Initiated eCall
....
It shall be possible to tie any emergency call number to any single
emergency call type or to any combination of emergency call types.
--------------------------------------------------------------------
This means in practise that a emergency Call Center from police must
differentiate between automatic and manual eCalls. Same belongs to
the other types like fire brigade Marine Guard ect.
Requirement:
Req-1: It shall be possible to tie a manually initiated eCall with
different type of emergency type i.e. Police, Ambulance, Fire
Brigade, Marine Guard and Mountain Rescue.
Jesske Expires December 27, 2013 [Page 3]
Internet-Draft June 2013
Req-2:It shall be possible to tie a automatically initiated eCall
with different type of emergency type i.e. Police, Ambulance, Fire
Brigade, Marine Guard and Mountain Rescue.
4. IANA Consideration
Within RFC 5031 [RFC5031] the service URN is completely describes.
The syntax is expendable therefore. This document extends the sub-
service URN for SOS described within Section 4.2 in RFC5031 [RFC5031]
with an additional sub-label as described within section 4.1
4.1. New Service-Identifying Labels
Services and sub-services are identified by labels managed by IANA.
RFC5031 [RFC5031] defines and registers the following formats:
Service Reference Description
--------------------------------------------------------------------
foo RFCxyz Brief description of the 'foo' top-level service
foo.bar RFCabc Description of the 'foo.bar' service
This document registers an additional sub-label for the sos service
URN.
Entries in the registration table have the following format:
Service Reference Description
----------------------------------------------------------------------------
foo.bar RFCabc Description of the 'foo.bar' service
foo.bar.sub RFCabc Description of the 'foo.bar.sub' extended service
4.2. sublabel for sos service and the relarted subservices
An additional sublabels for 5 values are defined.
.automatic
This sublevel indicates that an eCall had been triggered
automatically. This could be a sensor-controlled measuring of heat
or pressure in case of car accidents or fire situations.
Jesske Expires December 27, 2013 [Page 4]
Internet-Draft June 2013
.manual
This sublevel indicates that an eCall had been triggered based on the
manual interaction of a person.
4.3. IANA Registration
Service Reference Description
-----------------------------------------------------------------------------------
sos.automatic RFC 5031 Emergency services, automatic eCall
sos.manual RFC 5031 Emergency services, manual eCall
sos.police.automatic RFC 5031 Police, law enforcement, automatic eCall
sos.police.manual RFC 5031 Police, law enforcement, manual eCall
sos.ambulance.automatic RFC 5031 Ambulance service, automatic eCall
sos.ambulance.manual RFC 5031 Ambulance service, manual eCall
sos.fire.automatic RFC 5031 Fire service, automatic eCall
sos.fire.manual RFC 5031 Fire service, manual eCall
sos.marine.automatic RFC 5031 Maritime search and rescue, automatic eCall
sos.marine.manual RFC 5031 Maritime search and rescue, manual eCall
sos.mountain.automatic RFC 5031 Mountain rescue, automatic eCall
sos.mountain.manual RFC 5031 Mountain rescue, manual eCall
5. Security Considerations
This document does not raise security considerations beyond those
described in RFC5031 [RFC5031].
6. Contributors and Acknowledgements
The author would like to thank Dieter Jacobsohn, Maik Kirsch and
Thoms Dennert for clarifying the requirements on automatic and manual
eCall in the existing GSM world.
7. Normative References
[RFC2119] , .
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031,
January 2008.
[TS22101] 3GPP, "3rd Generation Partnership Project; Technical
Specification Group Services and System Aspects; Service
aspects; Service principles (Release 11)", 3GPP TS 22.101
11.7.0, September 2012.
Jesske Expires December 27, 2013 [Page 5]
Internet-Draft June 2013
[draft-rosen-ecrit-ecall-08.txt]
Rosen, B., Tschofenig, H., and R. Gellens, "Internet
Protocol-based In-Vehicle Emergency Call", January 2013.
Author's Address
Roland Jesske
Deutsche Telekom
Heinrich-Herz-Strasse 3-7
64295 Darmstadt
Germany
Email: r (DOT) jesske (AT) telekom (DOT) de
Jesske Expires December 27, 2013 [Page 6]
| PAFTECH AB 2003-2026 | 2026-04-24 02:00:14 |