< draft-ietf-ecrit-car-crash-12.txt   draft-ietf-ecrit-car-crash-13.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: March 29, 2017 NeuStar, Inc. Expires: April 6, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
September 25, 2016 October 3, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-12.txt draft-ietf-ecrit-car-crash-13.txt
Abstract Abstract
This document describes how to use IP-based emergency services This document describes how to use IP-based emergency services
mechanisms to support the next generation of emergency calls placed mechanisms to support the next generation of emergency calls placed
by vehicles (automatically in the event of a crash or serious by vehicles (automatically in the event of a crash or serious
incident, or manually invoked by a vehicle occupant) and conveying incident, or manually invoked by a vehicle occupant) and conveying
vehicle, sensor, and location data related to the crash or incident. vehicle, sensor, and location data related to the crash or incident.
Such calls are often referred to as "Automatic Crash Notification" Such calls are often referred to as "Automatic Crash Notification"
(ACN), or "Advanced Automatic Crash Notification" (AACN), even in the (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the
skipping to change at page 2, line 20 skipping to change at page 2, line 20
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 29, 2017. This Internet-Draft will expire on April 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 30 skipping to change at page 3, line 30
15.1. MIME Content-type Registration for 15.1. MIME Content-type Registration for
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32
15.2. Registration of the 'VEDS' entry in the Emergency Call 15.2. Registration of the 'VEDS' entry in the Emergency Call
Additional Data registry . . . . . . . . . . . . . . . . 34 Additional Data registry . . . . . . . . . . . . . . . . 34
15.3. New Action Values . . . . . . . . . . . . . . . . . . . 34 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 34
15.4. Static Message Registry . . . . . . . . . . . . . . . . 34 15.4. Static Message Registry . . . . . . . . . . . . . . . . 34
15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35 15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35
15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36 15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
17. Changes from Previous Versions . . . . . . . . . . . . . . . 37 17. Changes from Previous Versions . . . . . . . . . . . . . . . 37
17.1. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 37 17.1. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 37
17.2. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 17.2. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38
17.3. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 17.3. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38
17.4. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 17.4. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38
17.5. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38 17.5. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38
17.6. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38 17.6. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38
17.7. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 38 17.7. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38
17.8. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39 17.8. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39
17.9. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 17.9. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39
17.10. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 17.10. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
17.11. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39 17.11. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39
17.12. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39 17.12. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39
17.13. Changes from draft-gellens-01 to -02 . . . . . . . . . . 39 17.13. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39
17.14. Changes from draft-gellens-00 to -01 . . . . . . . . . . 39 17.14. Changes from draft-gellens-01 to -02 . . . . . . . . . . 39
17.15. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
18.1. Normative References . . . . . . . . . . . . . . . . . . 40 18.1. Normative References . . . . . . . . . . . . . . . . . . 40
18.2. Informative references . . . . . . . . . . . . . . . . . 41 18.2. Informative references . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 13, line 49 skipping to change at page 13, line 49
data to a SIP emergency call. This mechanism permits certain data to a SIP emergency call. This mechanism permits certain
emergency call MIME types to be attached to SIP messages. This emergency call MIME types to be attached to SIP messages. This
document makes use of that mechanism. This document also registers document makes use of that mechanism. This document also registers
an INFO package (in Section 11) to enable NG-ACN related data blocks an INFO package (in Section 11) to enable NG-ACN related data blocks
to be carried in SIP INFO requests (per [RFC6086], new INFO usages to be carried in SIP INFO requests (per [RFC6086], new INFO usages
require the definition of an INFO package). require the definition of an INFO package).
An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS])
by attaching it to a SIP message as a MIME body part per [RFC7852]. by attaching it to a SIP message as a MIME body part per [RFC7852].
The body part is identified by its MIME content-type ('application/ The body part is identified by its MIME content-type ('application/
emergencyCallData.eCall.VEDS+xml') in the Content-Type header field emergencyCallData.VEDS+xml') in the Content-Type header field of the
of the body part. The body part is assigned a unique identifier body part. The body part is assigned a unique identifier which is
which is listed in a Content-ID header field in the body part. The listed in a Content-ID header field in the body part. The SIP
SIP message is marked as containing the VEDS data by adding (or message is marked as containing the VEDS data by adding (or appending
appending to) a Call-Info header field at the top level of the SIP to) a Call-Info header field at the top level of the SIP message.
message. This Call-Info header field contains a CID URL referencing This Call-Info header field contains a CID URL referencing the body
the body part's unique identifier, and a 'purpose' parameter part's unique identifier, and a 'purpose' parameter identifying the
identifying the data as a VEDS data block per the Emergency Call data as a VEDS data block per the Emergency Call Additional Data
Additional Data Blocks registry entry; the 'purpose' parameter's Blocks registry entry; the 'purpose' parameter's value is
value is 'emergencyCallData.VEDS'. A VEDS data block is carried in a 'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO
SIP INFO request by using the INFO package defined in Section 11. request by using the INFO package defined in Section 11.
A PSAP or IVS transmits a metadata/control object (see A PSAP or IVS transmits a metadata/control object (see
[I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME [I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME
body part per [RFC7852]. The body part is identified by its MIME body part per [RFC7852]. The body part is identified by its MIME
content-type ('application/emergencyCallData.control+xml') in the content-type ('application/emergencyCallData.control+xml') in the
Content-Type header field of the body part. The body part is Content-Type header field of the body part. The body part is
assigned a unique identifier which is listed in a Content-ID header assigned a unique identifier which is listed in a Content-ID header
field in the body part. The SIP message is marked as containing the field in the body part. The SIP message is marked as containing the
metadata/control block by adding (or appending to) a Call-Info header metadata/control block by adding (or appending to) a Call-Info header
field at the top level of the SIP message. This Call-Info header field at the top level of the SIP message. This Call-Info header
skipping to change at page 20, line 5 skipping to change at page 20, line 5
enable-camera adds a one-way media stream (established via SIP re- enable-camera adds a one-way media stream (established via SIP re-
INVITE sent by the vehicle) to enable the PSAP call taker to view INVITE sent by the vehicle) to enable the PSAP call taker to view
a feed from a camera. a feed from a camera.
Note that there is no 'request' action to play dynamic media (such as Note that there is no 'request' action to play dynamic media (such as
an audio message). The PSAP can send a SIP re-INVITE to establish a an audio message). The PSAP can send a SIP re-INVITE to establish a
one-way media stream for this purpose. one-way media stream for this purpose.
9.2. Request Example 9.2. Request Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<request action="send-data" datatype="VEDS"/> <request action="send-data" datatype="VEDS"/>
<request action="lamp" lamp-id="hazard" <request action="lamp" lamp-id="hazard"
lamp-action="flash" persistance="PT1H"/> lamp-action="flash" persistance="PT1H"/>
<request action="msg-static" msgid="1"/> <request action="msg-static" msgid="1"/>
<request action="msg-dynamic"> <request action="msg-dynamic">
<text>Remain calm. Help is on the way.</text> <text>Remain calm. Help is on the way.</text>
</request> </request>
</EmergencyCallData.eCallControl> </EmergencyCallData.control>
Figure 7: Request Example Figure 7: Request Example
9.3. The <ack> element 9.3. The <ack> element
In [I-D.ietf-ecrit-ecall], the <ack> element is transmitted by the In [I-D.ietf-ecrit-ecall], the <ack> element is transmitted by the
PSAP to acknowledge the MSD. Here, the <ack> element is also PSAP to acknowledge the MSD. Here, the <ack> element is also
transmitted by the PSAP to acknowledge the VEDS data and by the IVS transmitted by the PSAP to acknowledge the VEDS data and by the IVS
to acknowledge receipt of a <request> element that requested the IVS to acknowledge receipt of a <request> element that requested the IVS
to perform an action other than transmitting a data object (e.g., a to perform an action other than transmitting a data object (e.g., a
request to display a message would be acknowledged, but a request to request to display a message would be acknowledged, but a request to
transmit VEDS data would not result in a separate <ack> element being transmit VEDS data would not result in a separate <ack> element being
sent, since the data object itself serves as acknowledgment.) An sent, since the data object itself serves as acknowledgment.) An
<ack> element sent by an IVS references the unique ID of the <ack> element sent by an IVS references the unique ID of the
metadata/control object containing the request(s) and indicates metadata/control object containing the request(s) and indicates
whether the request was successfully performed, and if not, whether the request was successfully performed, and if not,
optionally includes an explanation. optionally includes an explanation.
9.3.1. Ack Examples 9.3.1. Ack Examples
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<ack ref="1234567890@atlanta.example.com"> <ack ref="1234567890@atlanta.example.com">
<actionResult action="msg-dynamic" success="true"/> <actionResult action="msg-dynamic" success="true"/>
<actionResult action="lamp" success="false" reason="unable" <actionResult action="lamp" success="false" reason="unable"
details="The requested lamp is inoperable"/> details="The requested lamp is inoperable"/>
</ack> </ack>
</EmergencyCallData.eCallControl> </EmergencyCallData.control>
Figure 8: Ack Example from IVS to PSAP Figure 8: Ack Example from IVS to PSAP
9.4. The <capabilities> element 9.4. The <capabilities> element
The <capabilities> element ([I-D.ietf-ecrit-ecall]) is transmitted by The <capabilities> element ([I-D.ietf-ecrit-ecall]) is transmitted by
the IVS to indicate its capabilities to the PSAP. the IVS to indicate its capabilities to the PSAP.
The <capabilities> element contains a <request> child element per The <capabilities> element contains a <request> child element per
action supported by the vehicle. The vehicle MUST support sending action supported by the vehicle. The vehicle MUST support sending
skipping to change at page 22, line 8 skipping to change at page 22, line 8
created in Section 15.5 to contain lamp ID values. created in Section 15.5 to contain lamp ID values.
If the "enable-camera" action is supported, a <request> child element If the "enable-camera" action is supported, a <request> child element
with the 'action' attribute set to "enable-camera" is included, with with the 'action' attribute set to "enable-camera" is included, with
the 'supported-values' attribute set to all supported camera IDs. A the 'supported-values' attribute set to all supported camera IDs. A
registry is created in Section 15.6 to contain camera ID values. registry is created in Section 15.6 to contain camera ID values.
9.4.1. Capabilities Example 9.4.1. Capabilities Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<capabilities> <capabilities>
<request action="send-data" supported-values="VEDS"/> <request action="send-data" supported-values="VEDS"/>
<request action="lamp" <request action="lamp"
supported-values="head;interior;fog-front;fog-rear;brake; supported-values="head;interior;fog-front;fog-rear;brake;
position-front;position-rear;turn-left;turn-right;hazard"/> position-front;position-rear;turn-left;turn-right;hazard"/>
<request action="msg-static" msgid="3"/> <request action="msg-static" msgid="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" supported-values="backup; interior"/> <request action="enable-camera" supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.eCallControl> </EmergencyCallData.control>
Figure 9: Capabilities Example Figure 9: Capabilities Example
10. Test Calls 10. Test Calls
An NG-ACN test call is a call that is recognized and treated to some An NG-ACN test call is a call that is recognized and treated to some
extent as an NG-ACN call but not given emergency call treatment and extent as an NG-ACN call but not given emergency call treatment and
not handled by a call taker. The specific handling of test NG-ACN not handled by a call taker. The specific handling of test NG-ACN
calls is not itself standardized; the test call facility is intended calls is not itself standardized; the test call facility is intended
to allow the IVS, user, or TSP to verify that an NG-ACN call can be to allow the IVS, user, or TSP to verify that an NG-ACN call can be
skipping to change at page 30, line 51 skipping to change at page 30, line 51
<VehicleFireIndicator>false</VehicleFireIndicator> <VehicleFireIndicator>false</VehicleFireIndicator>
</Crash> </Crash>
</AutomatedCrashNotification> </AutomatedCrashNotification>
--boundary1 --boundary1
Content-Type: application/emergencyCallData.control+xml Content-Type: application/emergencyCallData.control+xml
Content-ID: <1234567892@atlanta.example.com> Content-ID: <1234567892@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<capabilities> <capabilities>
<request action="send-data" supported-datatypes="VEDS"/> <request action="send-data" supported-datatypes="VEDS"/>
<request action="lamp" <request action="lamp"
supported-values="head;interior;fog-front;fog-rear; supported-values="head;interior;fog-front;fog-rear;
brake;position-front;position-rear;turn-left; brake;position-front;position-rear;turn-left;
turn-right;hazard"/> turn-right;hazard"/>
<request action="msg-static" msgid="3"/> <request action="msg-static" msgid="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" <request action="enable-camera"
supported-values="backup; interior"/> supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.eCallControl> </EmergencyCallData.control>
--boundary1-- --boundary1--
Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call
13. Security Considerations 13. Security Considerations
Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852],
the security considerations described there and in [RFC5069] apply the security considerations described there and in [RFC5069] apply
here. Implementors are cautioned to read and understand the here. Implementors are cautioned to read and understand the
skipping to change at page 37, line 47 skipping to change at page 37, line 47
We would like to thank Lena Chaponniere, Stephen Edge, and Christer We would like to thank Lena Chaponniere, Stephen Edge, and Christer
Holmberg for their review and suggestions; Robert Sparks and Paul Holmberg for their review and suggestions; Robert Sparks and Paul
Kyzivat for their help with the SIP mechanisms; Michael Montag, Kyzivat for their help with the SIP mechanisms; Michael Montag,
Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex
Buddenberg for their feedback; and Ulrich Dietz for his help with Buddenberg for their feedback; and Ulrich Dietz for his help with
earlier versions of the original version of this document. earlier versions of the original version of this document.
17. Changes from Previous Versions 17. Changes from Previous Versions
17.1. Changes from draft-ietf-10 to draft-ietf-11 17.1. Changes from draft-ietf-11 to draft-ietf-13
o Fixed typos
17.2. Changes from draft-ietf-10 to draft-ietf-11
o Clarifications suggested by Christer o Clarifications suggested by Christer
o Corrections to Content-Disposition text and examples as suggested o Corrections to Content-Disposition text and examples as suggested
by Paul Kyzivat by Paul Kyzivat
o Clarifications to Content-Disposition text and examples to clarify o Clarifications to Content-Disposition text and examples to clarify
that handling=optional is only used in the initial INVITE that handling=optional is only used in the initial INVITE
17.2. Changes from draft-ietf-09 to draft-ietf-10 17.3. Changes from draft-ietf-09 to draft-ietf-10
o Fixed errors in examples found by Dale in eCall draft o Fixed errors in examples found by Dale in eCall draft
o Removed enclosing sub-section of INFO package registration section o Removed enclosing sub-section of INFO package registration section
o Added text per Christer and Dale's suggestions that the MSD and o Added text per Christer and Dale's suggestions that the MSD and
metadata/control blocks are sent in INFO with a Call-Info header metadata/control blocks are sent in INFO with a Call-Info header
field referencing them field referencing them
o Other text changes per comments received from Christer and Ivo o Other text changes per comments received from Christer and Ivo
against eCall draft. against eCall draft.
17.3. Changes from draft-ietf-08 to draft-ietf-09 17.4. Changes from draft-ietf-08 to draft-ietf-09
o Added INFO package registration for eCall.VEDS o Added INFO package registration for eCall.VEDS
o Moved <capabilities> element and other extension points back to o Moved <capabilities> element and other extension points back to
eCall document so that extension points are in base spec (and also eCall document so that extension points are in base spec (and also
to get XML schema to compile) to get XML schema to compile)
o Text changes for clarification. o Text changes for clarification.
17.4. Changes from draft-ietf-07 to draft-ietf-08 17.5. Changes from draft-ietf-07 to draft-ietf-08
o Moved much of the metadata/control object from o Moved much of the metadata/control object from
[I-D.ietf-ecrit-ecall] to this document as extensions [I-D.ietf-ecrit-ecall] to this document as extensions
o Editorial clarifications and simplifications o Editorial clarifications and simplifications
o Moved "Call Routing" to be a subsection of "Call Setup" o Moved "Call Routing" to be a subsection of "Call Setup"
o Deleted "Profile" section and moved some of its text into o Deleted "Profile" section and moved some of its text into
"Introduction" "Introduction"
17.5. Changes from draft-ietf-06 to draft-ietf-07 17.6. Changes from draft-ietf-06 to draft-ietf-07
o Minor editorial changes o Minor editorial changes
17.6. Changes from draft-ietf-05 to draft-ietf-06 17.7. Changes from draft-ietf-05 to draft-ietf-06
o Added clarifying text regarding signed and encrypted data o Added clarifying text regarding signed and encrypted data
o Additional informative text in "Migration to Next-Generation" o Additional informative text in "Migration to Next-Generation"
section section
o Additional clarifying text regarding security and privacy. o Additional clarifying text regarding security and privacy.
17.7. Changes from draft-ietf-04 to draft-ietf-05 17.8. Changes from draft-ietf-04 to draft-ietf-05
o Reworded security text in main document and in MIME registration o Reworded security text in main document and in MIME registration
for the VEDS object for the VEDS object
17.8. Changes from draft-ietf-03 to draft-ietf-04 17.9. Changes from draft-ietf-03 to draft-ietf-04
o Added example VEDS object o Added example VEDS object
o Additional clarifications and corrections o Additional clarifications and corrections
o Removed references from Abstract o Removed references from Abstract
o Moved Document Scope section to follow Introduction o Moved Document Scope section to follow Introduction
17.9. Changes from draft-ietf-02 to draft-ietf-03 17.10. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections o Additional clarifications and corrections
17.10. Changes from draft-ietf-01 to draft-ietf-02 17.11. Changes from draft-ietf-01 to draft-ietf-02
o This document now refers to [I-D.ietf-ecrit-ecall] for technical o This document now refers to [I-D.ietf-ecrit-ecall] for technical
aspects including the service URN; this document no longer aspects including the service URN; this document no longer
proposes a unique service URN for non-eCall NG-ACN calls; the same proposes a unique service URN for non-eCall NG-ACN calls; the same
service URN is now used for all NG-ACN calls including NG-eCall service URN is now used for all NG-ACN calls including NG-eCall
and non-eCall and non-eCall
o Added discussion of an NG-ACN call placed to a PSAP that doesn't o Added discussion of an NG-ACN call placed to a PSAP that doesn't
support it support it
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
17.11. Changes from draft-ietf-00 to draft-ietf-01 17.12. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications such as eCall crash notification specifications such as eCall
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
17.12. Changes from draft-gellens-02 to draft-ietf-00 17.13. Changes from draft-gellens-02 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf- o Renamed from draft-gellens- to draft-ietf-
o Added text to Introduction to clarify that during a CS ACN, the o Added text to Introduction to clarify that during a CS ACN, the
PSAP call taker usually needs to listen to the data and transcribe PSAP call taker usually needs to listen to the data and transcribe
it it
17.13. Changes from draft-gellens-01 to -02 17.14. Changes from draft-gellens-01 to -02
o Fixed case of 'EmergencyCallData', in accordance with changes to o Fixed case of 'EmergencyCallData', in accordance with changes to
[RFC7852] [RFC7852]
17.14. Changes from draft-gellens-00 to -01 17.15. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852] MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
18. References 18. References
18.1. Normative References 18.1. Normative References
[I-D.ietf-ecrit-ecall] [I-D.ietf-ecrit-ecall]
Gellens, R. and H. Tschofenig, "Next-Generation Pan- Gellens, R. and H. Tschofenig, "Next-Generation Pan-
European eCall", draft-ietf-ecrit-ecall-11 (work in European eCall", draft-ietf-ecrit-ecall-13 (work in
progress), August 2016. progress), September 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, Types", RFC 3023, DOI 10.17487/RFC3023, January 2001,
<http://www.rfc-editor.org/info/rfc3023>. <http://www.rfc-editor.org/info/rfc3023>.
 End of changes. 30 change blocks. 
54 lines changed or deleted 58 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/