< draft-ietf-ecrit-ecall-16.txt   draft-ietf-ecrit-ecall-17.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: April 15, 2017 Individual Expires: April 19, 2017 Individual
October 12, 2016 October 16, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-16.txt draft-ietf-ecrit-ecall-17.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 the pan European in- mechanisms to support the next generation of the pan European in-
vehicle emergency call service defined under the eSafety initiative vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an calls placed by vehicles, providing real-time communications and an
integrated set of related data. integrated set of related data.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 April 15, 2017. This Internet-Draft will expire on April 19, 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 2, line 47 skipping to change at page 2, line 47
10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18 10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18
10.1. Overall Description . . . . . . . . . . . . . . . . . . 18 10.1. Overall Description . . . . . . . . . . . . . . . . . . 18
10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19 10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19
10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19 10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19
10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19 10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19
10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19 10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19
10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 20 10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 20
10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20 10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20
10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20 10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20
10.9. Info Package Security Considerations . . . . . . . . . . 20 10.9. Info Package Security Considerations . . . . . . . . . . 20
10.10. Implementation Details . . . . . . . . . . . . . . . . . 20 10.10. Implementation Details . . . . . . . . . . . . . . . . . 21
10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21 10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21 11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21
12. Security Considerations . . . . . . . . . . . . . . . . . . . 26 12. Security Considerations . . . . . . . . . . . . . . . . . . . 26
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28 14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
15.1. Service URN Registrations . . . . . . . . . . . . . . . 30 15.1. Service URN Registrations . . . . . . . . . . . . . . . 30
15.2. MIME Content-type Registration for 15.2. MIME Content-type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 31 'application/emergencyCallData.eCall.MSD+per' . . . . . 31
15.3. MIME Content-type Registration for 15.3. MIME Content-type Registration for
skipping to change at page 3, line 24 skipping to change at page 3, line 24
15.6. Registration of the emergencyCallData.eCall Info Package 34 15.6. Registration of the emergencyCallData.eCall Info Package 34
15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34 15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34
15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34 15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34
15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35 15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35
15.8. Registry creation . . . . . . . . . . . . . . . . . . . 36 15.8. Registry creation . . . . . . . . . . . . . . . . . . . 36
15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 36 15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 36
15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 37 15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 37
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38 16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38
18. Changes from Previous Versions . . . . . . . . . . . . . . . 38 18. Changes from Previous Versions . . . . . . . . . . . . . . . 38
18.1. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38 18.1. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38
18.2. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38 18.2. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38
18.3. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38 18.3. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38
18.4. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38 18.4. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38
18.5. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39 18.5. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38
18.6. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39 18.6. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39
18.7. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 18.7. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39
18.8. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39 18.8. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39
18.9. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40 18.9. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39
18.10. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40 18.10. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40
18.11. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40 18.11. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40
18.12. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40 18.12. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40
18.13. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 40 18.13. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40
18.14. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41 18.14. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41
18.15. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41 18.15. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41
18.16. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41 18.16. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41
18.17. Changes from draft-gellens-02 to -03 . . . . . . . . . . 41 18.17. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41
18.18. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42 18.18. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42
18.19. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42 18.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42
18.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
19.1. Normative References . . . . . . . . . . . . . . . . . . 42 19.1. Normative References . . . . . . . . . . . . . . . . . . 42
19.2. Informative references . . . . . . . . . . . . . . . . . 43 19.2. Informative references . . . . . . . . . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
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 20, line 23 skipping to change at page 20, line 23
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in SIP messages other than INFO with how these body parts are sent in SIP messages other than INFO
requests, each associated body part is referenced by a Call-Info requests, each associated body part is referenced by a Call-Info
header field at the top level of the SIP message. The body part has header field at the top level of the SIP message. The body part has
a Content-Disposition header field set to "By-Reference". a Content-Disposition header field set to "By-Reference".
An MSD or metadata/control block is always enclosed in a multipart An MSD or metadata/control block is always enclosed in a multipart
body part (even if it would otherwise be the only body part in the body part (even if it would otherwise be the only body part in the
SIP message), since as of the date of this document, the use of SIP message), since as of the date of this document, the use of
Content-ID as a SIP header field is not defined (while it is defined Content-ID as a SIP header field is not defined (while it is defined
for use as a MIME header field). for use as a MIME header field). The innermost multipart that
contains only body parts associated with the INFO package has a
Content-Disposition value of Info-Package.
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
10.7. Info Package Usage Restrictions 10.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
10.8. Rate of INFO Requests 10.8. Rate of INFO Requests
skipping to change at page 25, line 18 skipping to change at page 25, line 18
Call-Info: <cid:3456789012@atlanta.example.com>; Call-Info: <cid:3456789012@atlanta.example.com>;
purpose=emergencyCallData.control purpose=emergencyCallData.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.control+xml, application/emergencyCallData.control+xml,
application/emergencyCallData.eCall.MSD+per application/emergencyCallData.eCall.MSD+per
CSeq: 41862 INFO CSeq: 41862 INFO
Info-Package: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundaryZZZ Content-Type: multipart/mixed; boundary=boundaryZZZ
Content-Dispositio: Info-Package
Content-Length: ... Content-Length: ...
--boundaryZZZ --boundaryZZZ
Content-Disposition: by-reference Content-Disposition: by-reference
Content-Type: application/emergencyCallData.control+xml Content-Type: application/emergencyCallData.control+xml
Content-ID: <3456789012@atlanta.example.com> Content-ID: <3456789012@atlanta.example.com>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<emergencyCallData.control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
skipping to change at page 26, line 18 skipping to change at page 26, line 18
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <cid:4567890123@atlanta.example.com>; Call-Info: <cid:4567890123@atlanta.example.com>;
purpose=emergencyCallData.eCall.MSD purpose=emergencyCallData.eCall.MSD
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.control+xml application/emergencyCallData.control+xml
CSeq: 51862 INFO CSeq: 51862 INFO
Info-Package: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundaryLine Content-Type: multipart/mixed; boundary=boundaryLine
Content-Disposition: Info-Package
Content-Length: ... Content-Length: ...
--boundaryLine --boundaryLine
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: <4567890123@atlanta.example.com> Content-ID: <4567890123@atlanta.example.com>
Content-Disposition: by-reference Content-Disposition: by-reference
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundaryLine-- --boundaryLine--
skipping to change at page 38, line 25 skipping to change at page 38, line 25
for their review and comments; Robert Sparks and Paul Kyzivat for for their review and comments; Robert Sparks and Paul Kyzivat for
their help with the SIP mechanisms; Mark Baker and Ned Freed for their help with the SIP mechanisms; Mark Baker and Ned Freed for
their help with the media subtype registration issue. We would like their help with the media subtype registration issue. We would like
to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and
Ulrich Dietz for their help with the original document upon which Ulrich Dietz for their help with the original document upon which
this document is based. Christer Holmberg deserves special mention this document is based. Christer Holmberg deserves special mention
for his many detailed reviews. for his many detailed reviews.
18. Changes from Previous Versions 18. Changes from Previous Versions
18.1. Changes from draft-ietf-15 to draft-ietf-16 18.1. Changes from draft-ietf-16 to draft-ietf-17
o Clarify Content-Disposition value in INFO requests
18.2. Changes from draft-ietf-15 to draft-ietf-16
o Various clarifications and simplifications o Various clarifications and simplifications
o Added reference to 3GPP 23.167 o Added reference to 3GPP 23.167
18.2. Changes from draft-ietf-14 to draft-ietf-15 18.3. Changes from draft-ietf-14 to draft-ietf-15
o eCall body parts now always sent enclosed in multipart (even if o eCall body parts now always sent enclosed in multipart (even if
only body part in SIP message) and hence always have a Content- only body part in SIP message) and hence always have a Content-
Disposition of By-Reference Disposition of By-Reference
o Fixed errors in attribute directionality text o Fixed errors in attribute directionality text
o Fixed typos. o Fixed typos.
18.3. Changes from draft-ietf-13 to draft-ietf-14 18.4. Changes from draft-ietf-13 to draft-ietf-14
o Added text to the IANA Considerations to formalize the o Added text to the IANA Considerations to formalize the
EmergencyCallData media subtree EmergencyCallData media subtree
o Fixed some typos o Fixed some typos
18.4. Changes from draft-ietf-12 to draft-ietf-13 18.5. Changes from draft-ietf-12 to draft-ietf-13
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
18.5. Changes from draft-ietf-11 to draft-ietf-12 18.6. Changes from draft-ietf-11 to draft-ietf-12
o Fixed errors in examples found by Dale o Fixed errors in examples found by Dale
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 Deleted Call Routing section (7.1) in favor of a statement that o Deleted Call Routing section (7.1) in favor of a statement that
call routing is outside the scope of the document call routing is outside the scope of the document
o Other text changes per comments received from Christer and Ivo. o Other text changes per comments received from Christer and Ivo.
18.6. Changes from draft-ietf-09 to draft-ietf-11 18.7. Changes from draft-ietf-09 to draft-ietf-11
o Renamed INFO package to emergencyCallData.eCall.MSD o Renamed INFO package to emergencyCallData.eCall.MSD
o Changed INFO package to only permit MSD and metadata/control MIME o Changed INFO package to only permit MSD and metadata/control MIME
types types
o Moved <capabilities> element back from car-crash but made it o Moved <capabilities> element back from car-crash but made it
OPTIONAL OPTIONAL
o Moved other extension points back from car-crash so that extension o Moved other extension points back from car-crash so that extension
points are in base spec (and also to get XML schema to compile) points are in base spec (and also to get XML schema to compile)
o Text changes for clarification. o Text changes for clarification.
18.7. Changes from draft-ietf-08 to draft-ietf-09 18.8. Changes from draft-ietf-08 to draft-ietf-09
o Created a new "Data Transport" section that describes how the MSD o Created a new "Data Transport" section that describes how the MSD
and metadata/control blocks are attached, and then referred to and metadata/control blocks are attached, and then referred to
that section rather than repeat the information about the CID and that section rather than repeat the information about the CID and
Call-Info and so forth, which means most references to the Call-Info and so forth, which means most references to the
additional-data draft have now been deleted additional-data draft have now been deleted
o Mentioned edge cases where a PSAP response to INVITE isn't o Mentioned edge cases where a PSAP response to INVITE isn't
received by the IVS received by the IVS
o Reworded description of which status codes are used when a PSAP o Reworded description of which status codes are used when a PSAP
wishes to reject a call but inform the vehicle occupants that it wishes to reject a call but inform the vehicle occupants that it
is aware of the situation to be more definite is aware of the situation to be more definite
o Added examples showing INFO o Added examples showing INFO
o Added references for eCall test call requirement o Added references for eCall test call requirement
o Described meaning of eCall URNs in Section 8 as well as in IANA o Described meaning of eCall URNs in Section 8 as well as in IANA
registration registration
18.8. Changes from draft-ietf-07 to draft-ietf-08 18.9. Changes from draft-ietf-07 to draft-ietf-08
o eCall MSD now encoded as ASN.1 PER, using binary content transfer o eCall MSD now encoded as ASN.1 PER, using binary content transfer
encoding encoding
o Added text to point out aspects of call handling and metadata/ o Added text to point out aspects of call handling and metadata/
control usage, such as use in rejected calls, and solicited MSDs control usage, such as use in rejected calls, and solicited MSDs
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
o Moved material not required by 3GPP into o Moved material not required by 3GPP into
[I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/
control elements, attributes, and values control elements, attributes, and values
o Revised test call wording to clarify that specific handling is out o Revised test call wording to clarify that specific handling is out
of scope of scope
o Revised wording throughout the document to simplify o Revised wording throughout the document to simplify
o Moved new Section 7.1 to be a subsection of 7 o Moved new Section 7.1 to be a subsection of 7
o Moved new Section Section 10 to be a main section instead of a o Moved new Section Section 10 to be a main section instead of a
subsection of Section 9 subsection of Section 9
o Revised SIP INFO usage and package registration per advice from o Revised SIP INFO usage and package registration per advice from
Robert Sparks and Paul Kyzivat Robert Sparks and Paul Kyzivat
18.9. Changes from draft-ietf-06 to draft-ietf-07 18.10. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.10. Changes from draft-ietf-05 to draft-ietf-06 18.11. Changes from draft-ietf-05 to draft-ietf-06
o Added additional security and privacy clarifications regarding o Added additional security and privacy clarifications regarding
signed and encrypted data signed and encrypted data
o Additional security and privacy text o Additional security and privacy text
o Deleted informative section on ESINets as unnecessary. o Deleted informative section on ESINets as unnecessary.
18.11. Changes from draft-ietf-04 to draft-ietf-05 18.12. Changes from draft-ietf-04 to draft-ietf-05
o Reworked the security and privacy considerations material in the o Reworked the security and privacy considerations material in the
document as a whole and in the MIME registation sections of the document as a whole and in the MIME registation sections of the
MSD and control objects MSD and control objects
o Clarified that the <actionResult> element can appear multiple o Clarified that the <actionResult> element can appear multiple
times within an <ack> element times within an <ack> element
o Fixed IMS definition o Fixed IMS definition
o Added clarifying text for the 'msgid' attribute o Added clarifying text for the 'msgid' attribute
18.12. Changes from draft-ietf-03 to draft-ietf-04 18.13. Changes from draft-ietf-03 to draft-ietf-04
o Added Privacy Considerations section o Added Privacy Considerations section
o Reworded most uses of non-normative "may", "should", "must", and o Reworded most uses of non-normative "may", "should", "must", and
"recommended." "recommended."
o Fixed nits in examples o Fixed nits in examples
18.13. Changes from draft-ietf-02 to draft-ietf-03 18.14. Changes from draft-ietf-02 to draft-ietf-03
o Added request to enable cameras o Added request to enable cameras
o Improved examples and XML schema o Improved examples and XML schema
o Clarifications and wording improvements o Clarifications and wording improvements
18.14. Changes from draft-ietf-01 to draft-ietf-02 18.15. Changes from draft-ietf-01 to draft-ietf-02
o Added clarifying text reinforcing that the data exchange is for o Added clarifying text reinforcing that the data exchange is for
small blocks of data infrequently transmitted small blocks of data infrequently transmitted
o Clarified that dynamic media is conveyed using SIP re-INVITE to o Clarified that dynamic media is conveyed using SIP re-INVITE to
establish a one-way media stream establish a one-way media stream
o Clarified that the scope is the needs of eCall within the SIP o Clarified that the scope is the needs of eCall within the SIP
emergency call environment emergency call environment
o Added informative statement that the document may be suitable for o Added informative statement that the document may be suitable for
reuse by other ACN systems reuse by other ACN systems
o Clarified that normative language for the control block applies to o Clarified that normative language for the control block applies to
both IVS and PSAP both IVS and PSAP
o Removed 'ref', 'supported-mime', and <media> elements o Removed 'ref', 'supported-mime', and <media> elements
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.15. Changes from draft-ietf-00 to draft-ietf-01 18.16. 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 in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME content type for the control o Added IANA registration for the MIME content type for the control
object object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
control object control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.16. Changes from draft-gellens-03 to draft-ietf-00 18.17. Changes from draft-gellens-03 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf-. o Renamed from draft-gellens- to draft-ietf-.
o Added mention of and reference to ETSI TR "Mobile Standards Group o Added mention of and reference to ETSI TR "Mobile Standards Group
(MSG); eCall for VoIP" (MSG); eCall for VoIP"
o Added text to Introduction regarding migration/co-existence being o Added text to Introduction regarding migration/co-existence being
out of scope out of scope
o Added mention in Security Considerations that even if the network- o Added mention in Security Considerations that even if the network-
supplied location is just the cell site, this can be useful as a supplied location is just the cell site, this can be useful as a
sanity check on the IVS-supplied location sanity check on the IVS-supplied location
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.17. Changes from draft-gellens-02 to -03 18.18. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.18. Changes from draft-gellens-01 to -02 18.19. Changes from draft-gellens-01 to -02
o Minor wording improvements o Minor wording improvements
o Removed ".automatic" and ".manual" from o Removed ".automatic" and ".manual" from
"urn:service:test.sos.ecall" registration and discussion text. "urn:service:test.sos.ecall" registration and discussion text.
18.19. Changes from draft-gellens-00 to -01 18.20. 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
19. References 19. References
19.1. Normative References 19.1. Normative References
 End of changes. 30 change blocks. 
45 lines changed or deleted 55 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/