RFC 8147 on Next-Generation Pan-European eCall
rfc-editor@rfc-editor.org Fri, 12 May 2017 15:42 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69767129B7A; Fri, 12 May 2017 08:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2lIUVOoNB-J; Fri, 12 May 2017 08:42:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 484C912EC28; Fri, 12 May 2017 08:37:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 50D2FB80E63; Fri, 12 May 2017 08:37:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8147 on Next-Generation Pan-European eCall
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ecrit@ietf.org
Message-Id: <20170512153720.50D2FB80E63@rfc-editor.org>
Date: Fri, 12 May 2017 08:37:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/cHSdIhrhiObU1HmqNpzJEfe96AI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 May 2017 15:42:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8147
Title: Next-Generation Pan-European eCall
Author: R. Gellens, H. Tschofenig
Status: Standards Track
Stream: IETF
Date: May 2017
Mailbox: rg+ietf@coretechnologyconsulting.com,
Hannes.Tschofenig@gmx.net
Pages: 43
Characters: 92777
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ecrit-ecall-27.txt
URL: https://www.rfc-editor.org/info/rfc8147
DOI: 10.17487/RFC8147
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.
This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC