Next-Generation Pan-European eCall
RFC 8147
|
| Document |
Type |
|
RFC - Proposed Standard
(May 2017; No errata)
|
|
Last updated |
|
2018-12-20
|
|
Replaces |
|
draft-gellens-ecrit-ecall
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Allison Mankin
|
|
Shepherd write-up |
|
Show
(last changed 2016-11-13)
|
| IESG |
IESG state |
|
RFC 8147 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alissa Cooper
|
|
Send notices to |
|
"Allison Mankin" <allison.mankin@gmail.com>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) R. Gellens
Request for Comments: 8147 Core Technology Consulting
Category: Standards Track H. Tschofenig
ISSN: 2070-1721 Individual
May 2017
Next-Generation Pan-European eCall
Abstract
This document describes how to use IP-based emergency services
mechanisms to support the next generation of the Pan-European in-
vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an
integrated set of related data.
This document also registers MIME media types and an Emergency Call
Data Type for the eCall vehicle data and metadata/control data, and
an INFO package to enable carrying this data in SIP INFO requests.
Although this specification is designed to meet the requirements of
next-generation Pan-European eCall (NG-eCall), it is specified
generically such that the technology can be reused or extended to
suit requirements across jurisdictions.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8147.
Gellens & Tschofenig Standards Track [Page 1]
RFC 8147 Next-Generation eCall May 2017
Copyright Notice
Copyright (c) 2017 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.
Gellens & Tschofenig Standards Track [Page 2]
RFC 8147 Next-Generation eCall May 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 6
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 7
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 11
9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 13
9.1.1. The <ack> Element . . . . . . . . . . . . . . . . . . 14
9.1.1.1. Attributes of the <ack> Element . . . . . . . . . 14
9.1.1.2. Child Element of the <ack> Element . . . . . . . 15
9.1.1.3. Example of the <ack> Element . . . . . . . . . . 16
9.1.2. The <capabilities> Element . . . . . . . . . . . . . 16
9.1.2.1. Child Element of the <capabilities> Element . . . 16
9.1.2.2. Example of the <capabilities> Element . . . . . . 17
9.1.3. The <request> Element . . . . . . . . . . . . . . . . 17
9.1.3.1. Attributes of the <request> Element . . . . . . . 17
9.1.3.2. Child Element of the <request> Element . . . . . 19
9.1.3.3. Request Example . . . . . . . . . . . . . . . . . 19
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 20
11. Security Considerations . . . . . . . . . . . . . . . . . . . 25
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 27
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
14.1. The EmergencyCallData Media Subtree . . . . . . . . . . 30
14.2. Service URN Registrations . . . . . . . . . . . . . . . 31
Show full document text