ECRIT R. Gellens Internet-DraftQualcomm Technologies, Inc.Consultant Intended status: Standards Track H. Tschofenig Expires:August 22, 2016 (Individual) February 19,January 2, 2017 Individual July 1, 2016 Next-Generation Pan-European eCalldraft-ietf-ecrit-ecall-07.txtdraft-ietf-ecrit-ecall-08.txt 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 byvehicles. eCall deployment is required in the very near future in European Union member states,vehicles, providing real-time communications andeCall (and eCall- compatible systems) are also being deployed in other regions. eCall providesan integratedvoice path and a standardizedset ofvehicle, sensor (e.g., crash related), and locationrelated data.An eCall is recognized and handled as a specialized form of emergency call and is routed to a specialized eCall-capable Public Safety Answering Point (PSAP) capable of processing the vehicle data and trained in handling emergency calls from vehicles. Currently, eCall functions over circuit-switched cellular telephony; work on next-generation eCall (NG-eCall, sometimes called packet- switched eCall or PS-eCall) is now in process, and this document assists in that work by describing how to support eCall within the IP-based emergency services infrastructure.This document also registers a MIME Content Type and an Emergency Call Additional Data Block for the eCall vehicle data and metadata/ control data. 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 onAugust 22, 2016.January 2, 2017. Copyright Notice Copyright (c) 2016 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. Table of Contents 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . .45 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . .76 6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 77.6.1. Call Routing . . . . . . . . . . . . . . . . . . . . . .. . 9 8.8 7. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . .9 9.8 8. eCall-Specific Control/Metadata . . . . . . . . . . . . . . . 99.1.8.1. The eCall Control Block . . . . . . . . . . . . . . . . . 109.1.1.8.1.1. The <ack> element . . . . . . . . . . . . . . . . . .12 9.1.1.1.11 8.1.1.1. Attributes of the <ack> element . . . . . . . . .12 9.1.1.2.11 8.1.1.2. Child Elements of the <ack> element . . . . . . . 129.1.1.3.8.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . .13 9.1.2.12 8.1.2. The<capabilities><request> element . . . . . . . . . . . . .14 9.1.2.1. Child Elements. . . 12 8.1.2.1. Attributes of the<capabilities><request> element . .14 9.1.2.2. Capabilities. . . . . 12 8.1.2.2. Request Example . . . . . . . . . . . . . .15 9.1.3.. . . 13 9. The<request> elementemergencyCallData.eCall INFO package . . . . . . . . . . 13 9.1. INFO Package Requirements . . . . . .16 9.1.3.1. Attributes of the <request> element. . . . . . .16 9.1.3.2. Child Elements of the <request> element. . . 13 9.1.1. Overall Description . .18 9.1.3.3. Request Example. . . . . . . . . . . . . . . 14 9.1.2. Applicability . .19 9.2. The emergencyCallData.eCall. . . . . . . . . . . . . . . . . . 14 9.1.3. Info Package Name . . . . . . . . . . . . . . . . . . 15 9.1.4. Info Package Parameters . . . . . . . . . . . . . . . 15 9.1.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . 15 9.1.6. INFOpackageMessage Body Parts . . . . . . . . . . . . . . . 15 9.1.7. Info Package Usage Restrictions . . . . . . . . . . . 15 9.1.8. Rate of INFO Requests . . . . . . . .19. . . . . . . . 15 9.1.9. Info Package Security Considerations . . . . . . . . 15 9.1.10. Implementation Details . . . . . . . . . . . . . . . 16 9.1.11. Examples . . . . . . . . . . . . . . . . . . . . . . 16 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . .2016 11. Security Considerations . . . . . . . . . . . . . . . . . . .2418 12. Privacy Considerations . . . . . . . . . . . . . . . . . . .2620 13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . .2620 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . .2922 14.1. Service URN Registrations . . . . . . . . . . . . . . .2922 14.2. MIME Content-type Registration for'application/emergencyCallData.eCall.MSD+xml''application/emergencyCallData.eCall.MSD+per' . . . . .3023 14.3. MIME Content-type Registration for 'application/emergencyCallData.eCall.control+xml' . . .3124 14.4. Registration of the 'eCall.MSD' entry in the Emergency Call Additional Data Blocks registry . . . . . . . . . .3326 14.5. Registration of the 'eCall.control' entry in the Emergency Call Additional Data Blocks registry . . . . .3326 14.6. Registration of the emergencyCallData.eCall Info Package3326 14.7. URN Sub-Namespace Registration . . . . . . . . . . . . .3326 14.7.1. Registration for urn:ietf:params:xml:ns:eCall . . .3326 14.7.2. Registration for urn:ietf:params:xml:ns:eCall:control . . . . . . . .3427 14.8. Registry creation . . . . . . . . . . . . . . . . . . .3528 14.8.1. eCall Control Action Registry . . . . . . . . . . .3528 14.8.2. eCallStatic Message Registry . . . . . . . . . . . 36 14.8.3. eCall Reason Registry . . . . . . . . . . . . . . . 37 14.8.4. eCall Lamp IDControl Extension Registry . . . . . . . . . . 29 15. Contributors . . . . .38 14.8.5. eCall Camera ID Registry . . .. . . . . . . . . . .39 15. Contributors. . . . . . . . 29 16. Acknowledgements . . . . . . . . . . . . . . . .39 16. Acknowledgements .. . . . . . 30 17. Changes from Previous Versions . . . . . . . . . . . . . . .39 17.30 17.1. Changes fromPrevious Versions . . .draft-ietf-07 to draft-ietf-08 . . . . . . 30 17.2. Changes from draft-ietf-06 to draft-ietf-07 . . . . . .39 17.1.30 17.3. Changes from draft-ietf-05 to draft-ietf-06 . . . . . .40 17.2.30 17.4. Changes from draft-ietf-04 to draft-ietf-05 . . . . . .40 17.3.31 17.5. Changes from draft-ietf-03 to draft-ietf-04 . . . . . .40 17.4.31 17.6. Changes from draft-ietf-02 to draft-ietf-03 . . . . . .40 17.5.31 17.7. Changes from draft-ietf-01 to draft-ietf-02 . . . . . .40 17.6.31 17.8. Changes from draft-ietf-00 to draft-ietf-01 . . . . . .41 17.7.31 17.9. Changes from draft-gellens-03 to draft-ietf-00 . . . . .41 17.8.32 17.10. Changes from draft-gellens-02 to -03 . . . . . . . . . .41 17.9.32 17.11. Changes from draft-gellens-01 to -02 . . . . . . . . . .41 17.10.32 17.12. Changes from draft-gellens-00 to -01 . . . . . . . . . .4132 18. References . . . . . . . . . . . . . . . . . . . . . . . . .4132 18.1. Normative References . . . . . . . . . . . . . . . . . .4232 18.2. Informative references . . . . . . . . . . . . . . . . .4334 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .4435 1. Terminology 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]. This document re-uses terminology defined in Section 3 of [RFC5012]. Additionally, we use the following abbreviations: +--------+----------------------------------------+ | Term | Expansion | +--------+----------------------------------------+ | 3GPP | 3rd Generation Partnership Project | | | | | CEN | European Committee for Standardization | | | | | EENA | European Emergency Number Association | | | | | ESInet | Emergency Services IP network | | | | | IMS | IP Multimedia Subsystem | | | | | IVS | In-Vehicle System | | | | | MNO | Mobile Network Operator | | | | | MSD | Minimum Set of Data | | | | | PSAP | Public Safety Answering Point | +--------+----------------------------------------+ 2. Document Scope This document is limited to the signaling, data exchange, and protocol needs of next-generation eCall (NG-eCall, also referred to as packet-switched eCall (PS-eCall) and all-IP eCall) within the SIP framework for emergency calls, as described in [RFC6443] and [RFC6881]. eCall itself is specified by 3GPP and CEN and these specifications include far greater scope than is covered here. The eCall service operates over cellular wireless communication, but this document does not address cellular-specific details, nor client domain selection (e.g., circuit-switched versus packet-switched). All such aspects are the purview of their respective standards bodies. The scope of this document is limited to eCall operating within a SIP-based environment (e.g., 3GPP IMS Emergency Calling). The technical contents of this document can be suitable for use in other vehicle-initiated emergency call systems, but this is out of scope for this document. Vehicles designed for multiple regions might need to support eCall and other Advanced Automatic Crash Notification (AACN) systems, such as described in [I-D.ietf-ecrit-car-crash]. That system is compatible with eCall, differing primarily in the specific data set that is sent. 3. Introduction Emergency calls made from vehicles (e.g., in the event of a crash) assist in significantly reducing road deaths and injuries by allowing emergency services to be aware of the incident, the state of the vehicle, the location of the vehicle, and to have a voice channel with the vehicle occupants. This enables a quick and appropriate response. The European Commission initiative of eCall was conceived in the late 1990s, and has evolved to a European Parliament decision requiring the implementation of a compliant in-vehiclesystemssystem (IVS) in new vehicles and the deployment of eCall in the European Member States in the very near future.eCall (and eCall-compatible systems)Other regions arealso being adopted in other regions.developing eCall-compatible systems. The pan-European eCall system provides a standardized and mandated mechanism for emergency calls by vehicles. eCall establishes procedures for such calls to be placed by in-vehicle systems, recognized and processed by the mobile network, and routed to a specialized PSAP where the vehicle data is available to assist the call taker in assessing and responding to the situation. eCall provides a standard set of vehicle, sensor (e.g., crash related), and location data. An eCall can be either user-initiated or automatically triggered. Automatically triggered eCalls indicate a car crash or some other seriousincident and carry a greater presumption of risk of injury.incident. Manually triggered eCalls might be reports of witnessed crashes or serioushazards and are likely to require a different response than an automatically triggered eCall. Manually triggered eCalls are also more likely to be false (e.g., accidental) calls and sohazards. PSAPs mightbe subject to differentapply specific operational handlingby the PSAP. Currently,to manual and automatic eCalls. Legacy eCall is standardized (by 3GPP [SDO-3GPP] and CEN [CEN]) as a 3GPP circuit-switched call over GSM (2G) or UMTS (3G). Flags in the call setup mark the call as an eCall, and further indicate if the call was automatically or manually triggered. The call is routed to an eCall-capable PSAP, a voice channel is established between the vehicle and the PSAP, and an eCall in-band modem is used to carry a defined set of vehicle, sensor (e.g., crash related), and location data (the Minimum Set of Data or MSD) within the voice channel. The same in-band mechanism is used for the PSAP to acknowledge successful receipt of the MSD, and to request the vehicle to send a new MSD (e.g., to check if the state of or location of the vehicle or its occupants has changed).Work on next-generation eCall (NG-eCall, also referred to as packet-switched eCall or PS eCall) is now in process. As part of this work, the European Telecommunications Standards Institute (ETSI) [SDO-ETSI] has published a Technical Report titled "Mobile Standards Group (MSG); eCall for VoIP" [MSG_TR] that presents findings and recommendations regarding support for eCall in an all-IP environment.NG-eCall moves from circuit switched toall-IP,all- IP, and carries the vehicle data and other eCall-specific data as additional dataassociatedcarried with the call. This document describes how IETF mechanisms for IP-based emergency calls, including [RFC6443] and [I-D.ietf-ecrit-additional-data] are used to provide the signaling and data exchange of the next generation of pan-European eCall. The European Telecommunications Standards Institute (ETSI) [SDO-ETSI] has published a Technical Report titled "Mobile Standards Group (MSG); eCall for VoIP" [MSG_TR]recommendationthat presents findings and recommendations regarding support forNG-eCall is toeCall in an all-IP environment. The recommendations include the use of 3GPP IMS emergency calling with additional elements identifying the call as an eCall and as carrying eCall data and with mechanisms for carrying thedata.data and eCall-specific signaling. 3GPP IMS emergency services support multimedia, providing the ability to carry voice, text, and video. This capability is referred to within 3GPP as Multimedia Emergency Services (MMES). A transition period will exist during which time the various entities involved in initiating and handling an eCall might support next- generation eCall, legacy eCall, or both.This transition period might last several years or longer.Theissueissues ofmigration/co- existencemigration and co-existence during the transition period isvery important but isoutside the scope of this document.The ETSI TR "Mobile Standards Group (MSG); eCall for VoIP" [MSG_TR] discusses these issues in Clause 7.4. eCall RequirementsOveralleCall requirements are specified by CEN in [EN_16072] and by 3GPP in [TS22.101] clauses 10.7 and A.27. Requirements specific to vehicle data are contained in EN 15722 [msd].For convenience, the requirements most applicable to the limited scope of this document are summarized very briefly below. eCall requires: o The call be recognized as an eCall (which is inherently an emergency call) o The call setup indicates if the call was manually or automatically triggered o A voice channel between the vehicle and the PSAP o Carrying the MSD intrinsically with the call (the MSD needs to be available to the same call-taker as the voice) o The ability for the PSAP to acknowledge receipt of the MSD o The ability for the PSAP to request that the vehicle generate and transmit a new MSD o The ability of the PSAP to be able to re-contact the occupants of vehicle after the initial eCall is concluded o The ability to perform a test call (which can be routed to a PSAP but is not treated as an emergency call and not handled by a call taker) It is recognized that NG-eCall offers many potential enhancements, although these are not required by current EU regulations. For convenience, the enhancements most applicable to the limited scope of this document are summarized very briefly below. NG-eCall is expected to offer: o The ability to carry more data (e.g., an enhanced MSD or an MSD plus additional sets of data) o The ability to handle video o The ability to handle text o The ability for the PSAP to access vehicle components (e.g., an onboard camera (such as rear facing or blind-spot cameras) for a visual assessment of the crash site situation) o The ability for the PSAP to request the vehicle to take actions (e.g., sound the horn, disable the ignition, lock/unlock doors) o The ability to avoid audio muting of the voice channel (because the MSD is not transferred using an in-band modem)5. Vehicle Data Pan-European eCall provides a standardized and mandated set of vehicle related data, known as the Minimum Set of Data (MSD). The European Committee for Standardization (CEN) has specified this data in EN 15722 [msd], along with both ASN.1 and XML encodings for the MSD [msd].Circuit-switchedBoth circuit-switched eCalluses the ASN.1 encoding. The XML encoding is better suited for use in SIP messagesandis used inthisdocument. (Thedocument use the ASN.1encodingPER encoding, which is specified in Annex A of EN 15722[msd], while the[msd] (the XML encodingisspecified in AnnexC.)C is not used in this document). The "Additional Data related to an Emergency Call" document [I-D.ietf-ecrit-additional-data] establishes a general mechanism for attaching blocks of data to a SIP emergency call. This document makes use of that mechanism to carry the eCall MSD in a SIP emergency call. This document registers the 'application/emergencyCallData.eCall.MSD+xml'emergencyCallData.eCall.MSD+per' MIME Content-Type to enable the MSD to be carried in SIP. As an ASN.1 PER encoded object, the data is binary and transported using binary content transfer encoding within SIP messages. This document also adds the 'eCall.MSD' entry to the Emergency Call Additional Data Blocks registry (established by [I-D.ietf-ecrit-additional-data]) to enable the MSD to be recognized as such in a SIP-based eCall emergency call. Note that if additional data sets are defined and registered (e.g., in the future or in other regions) and transmitted using the same mechanisms, the size and frequency of transmission during asession needsdialog need to be evaluated to be sure it is appropriate to use the signaling channel. 6. Call Setup In circuit-switched eCall, the IVS places a special form of a 112 emergency call which carries an eCall flag (indicating that the call is an eCall and also if the call was manually or automatically triggered); the mobile network operator (MNO) recognizes the eCall flag and routes the call to an eCall-capable PSAP; vehicle data is transmitted to the PSAP via the eCall in-band modem (in the voice channel). ///----\\\ 112 voice call with eCall flag +------+ ||| IVS |||---------------------------------------->+ PSAP | \\\----/// vehicle data via eCall in-band modem +------+ Figure 1: circuit-switched eCall An In-Vehicle System (IVS)which supportsinitiating an NG-eCall transmits the MSD in accordance with [I-D.ietf-ecrit-additional-data] by encoding it as specified (perAppendix CAnnex A of EN 15722 [msd]) and attaching it to an INVITE as a MIME body part. The body part is identified by its MIME content-type('application/emergencyCallData.eCall.MSD+xml')('application/emergencyCallData.eCall.MSD+per') in the Content-Type header field of the body part. The body part is assigned a unique identifier which is listed in a Content-ID header field in the body part. The INVITE is marked as containing the MSD by adding (or appending to) a Call-Info header field at the top level of the INVITE. This Call-Info header field contains a CID URL referencing the body part's unique identifier, and a 'purpose' parameter identifying the data as the eCall MSD per the registry entry; the 'purpose' parameter's value is 'emergencyCallData.'andplus the root of the MIME type (not including the'emergencyCallData''emergencyCallData.' prefix and any suffix such as'+xml' (e.g., 'purpose=emergencyCallData.eCall.MSD').'+per', so in this case, 'purpose=emergencyCallData.eCall.MSD'. For NG-eCall, the IVS establishes an emergency call usingthe 3GPP IMS solution withaRequest-URIRequest- URI indicatingan eCall type of emergency call and with vehicle data attached;a manual or automatic eCall; the MNOor ESInet(or ESInet) recognizes the eCall URN and routes the call toaan NG-eCall capable PSAP; the PSAP interpets the vehicle data sent with the call and makes it available to the call taker. ///----\\\ IMS emergency call with eCall URN +------+ IVS ----------------------------------------->+ PSAP | \\\----/// vehicle data included in call setup +------+ Figure 2: NG-eCall This document registers new service URN children within the "sos" subservice. These URNs provide the mechanism by which an eCall is identified, and differentiate between manually and automatically triggered eCalls (whichcanmight be subject to different treatment, depending on policy). The two service URNs are: urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual7.6.1. Call Routing The routingrules for eCalls are likelyapplied to eCalls might differ from those of other emergencycalls becausecalls, as eCalls arespecial types of emergency calls (with implications for the types of response required) and needintended to be handled byspecially designated PSAPs.PSAPs that support eCall. Inan environmentregions without ESInets, typically the emergency services authorities and the originating network determine how such calls are routed. In a region that uses ESInets, the originating network passes all types of emergency calls to an ESInet(which(calls which have a request URI containing the "SOS" service URN). The ESInet is then responsible for routing such calls to the appropriate PSAP.In an environment without an ESInet, the emergency services authorities and the originating network jointly determine how such calls are routed. 8.7. Test Calls eCall requires the ability to place test calls. These are calls that are recognized and treated to some extent as eCalls but are not given emergency call treatment and are not handled by call takers. The specific handling of test eCalls is not itself standardized; typically, the test call facility allows the IVS or user to verify that an eCall can be successfully established with voice communication. The IVScanmight also be able to verify that the MSD was successfully received. A service URN starting with "test." indicates a test call. For eCall, "urn:service:test.sos.ecall" indicates such a test feature. This functionality is defined in [RFC6881]. This document registers "urn:service:test.sos.ecall" for eCall test calls.the current eCallThe CS-eCall test call facility is a non-emergency number so does not get treated as an emergency call.MNOsFor NG-eCall, MNOs, emergency authorities, and PSAPs can determine how to treat a vehicle callinrequesting the "test" service URNin a wayso thattests as muchthe desired functionalityas desired,is tested, but this is outside the scope of this document.PSAPs(One possibility is thathave the abilityMNOs route such calls as non-emergency calls toprocess NG-eCalls SHOULD accepta PSAP that supports NG-eCall; the PSAP accepts testcalls and sendcalls, sends anacknowledgment if theMSDwas successfully received, per this document. Such PSAPs MAY also playacknowledgment, and plays an audio clip (for example, saying that the call reachedaan eCall PSAP) in addition to supporting media loopback per[RFC6881]. 9.[RFC6881]). 8. eCall-Specific Control/Metadata eCall requires the ability for the PSAP to acknowledge successful receipt of an MSD sent by the IVS, and for the PSAP to request that the IVS send an MSD (e.g., the call taker can initiate a request for a new MSD to see if there have been changes in the vehicle'sstate or location has changed). Future enhancements are desired to enable the PSAP to send other requests to the vehicle, such as locking or unlocking doors, sounding the horn, flashing the lights, starting a video stream from on-board cameras (such as rear focus or blind-spot), etc.state, e.g., location, direction, number of fastened seatbelts). The mechanism established in [I-D.ietf-ecrit-additional-data], used in Section 5 of this document to carry the MSD from the IVS to the PSAP, is also used to carry a block ofcontrolmetadata/control data from the PSAP to the IVS. This eCall control block (sometimes referred to as eCall metadata) is an XML structure containing eCall-specific elements. When the PSAP needs to send an eCall control block that is in response tothe MSD or otherdata sent by the IVS in a SIPrequest,request (e.g., the MSD in the initial INVITE), the control block can be sent in the SIP response to that request (e.g., theINVITE).response to the INVITE request). When the PSAP needs to send an eCall control blockthat is not an immediate response to an MSD orin otherdata sent by the IVS,circumstances (e.g., mid-call), the control block can be transmitted from the PSAP to the IVS in a SIP INFOmessagerequest within the establishedsession.dialog. The IVScan then send anysends the requested data(such as a new(the MSD) inthe reply to thea new INFOmessage.request. This mechanism flexibly allows the PSAP to sendeCall-specificeCall- specific data to the IVS and the IVS to respond.If control data sent in a response message requests the IVS to send a new MSD or other data block, or to perform an action other than sending data, the IVS can send the requested data or an acknowledgment regarding the action in an INFO message within the session (it could also use re-INVITE but that is unnecessary when no aspect of the session or media is changing).This mechanism requires o An XML definition of the eCall control object o An extension mechanism by which newelementselements, attributes, and values can be added to the control object definition(e.g., permitting additional elements to be included by adding their namespace)o A MIME type registration for the control object (so it can be carried in SIP messages and responses) o An entry in the Emergency Call Additional Data Blocks sub-registry (established by [I-D.ietf-ecrit-additional-data]) so that the control block can be recognized as emergency call specific data withintheSIP messages o An Info-Package registration per [RFC6086] permitting data blocks registered in thecontrol blockEmergency Call Additional Data Blocks sub- registry (established by [I-D.ietf-ecrit-additional-data]) within Info messages9.1.When the IVS includes an unsolicited MSD in a SIP request (e.g., the initial INVITE), the PSAP sends a metadata/control block indicating successful/unsuccessful receipt of the MSD in the SIP response to the request. This also informs the IVS that an NG-eCall is in operation. If the IVS receives a SIP response without the metadata/control block, it indicates that the SIP dialog is not an NG-eCall. When the IVS sends a solicited MSD (e.g., in a SIP INFO request sent following receipt of a SIP INFO request containing a metadata/control block requesting an MSD), the PSAP does not send a metadata/control block indicating successful or unsuccessful receipt of the MSD. (Normal SIP retransmission handles non-receipt of requested data; if the IVS sends a requested MSD in an INFO request and does not receive a SIP status message for the INFO request, it resends it; if the PSAP requests an MSD and does not receive a SIP status message for the INFO request, it resends it.) This provides flexibility to handle various circumstances. For example, if a PSAP is unable to accept an eCall (e.g., due to overload or too many calls from the same location), it can reject the INVITE. Since a metadata/control object is also included in the SIP response that rejects the call, the IVS knows if the PSAP received the MSD, and can inform the occupants that the PSAP successfully received the vehicle location and information but can't talk to the occupants at that time. Especially for SIP response codes that indicate an inability to conduct a call (as opposed to a technical inability to process the request), the IVS can also determine that the call was successful on a technical level (e.g., not necessary to retry as a CS-eCall). The SIP response code 600 (Busy Everywhere) can be used to indicate this. Other SIP response codes that can be interpreted in this way include 480 (Temporarily Unavailable), 486 (Busy Here), and 603 (Decline). 8.1. The eCall Control Block The eCall control block is an XML data structure allowing foracknowledgments, requests,acknowledgments andcapabilities information.requests. It is carried in a SIP body part with a specific MIME content type.ThreeIt can be extended via an IANA registry to add additional elements, attributes, and values. Two top-level elements are defined for use within an eCall control block: ack Used in a control block sent byeither side. Thethe PSAPuses thisto acknowledge receipt of a data set sent by the IVS.The IVS uses this to acknowledge receipt of a request by the PSAP when that request would not otherwise be acknowledged (if the PSAP requests the vehicle to send data and the vehicle does so, the data serves as a success acknowledgement). capabilities: Used in a control block sent from the IVS to the PSAP (e.g., in the initial INVITE) to inform the PSAP of the vehicle capabilities. Child elements contain all actions and data types supported by the vehicle and all available lamps (lights) and cameras.request Used in a control block sent by the PSAP tothe IVS, torequest the vehicle to perform an action. The only action defined in this document is a request for the IVS to send an MSD. Mandatory Actions (the IVS and the PSAP MUST support): o Transmit data object Optional Actions (the IVS and the PSAP MAY support): oPlay and/or display static (pre-defined) message o Speak/display dynamic text (text supplied in action) o Flash or turn on or off a lamp (light) o Honk horn o Enable a cameraNone The <ack> element indicates the object being acknowledged(i.e., a data object or a <request> element),(e.g., the MSD), and reports success or failure. The<capabilities> element has child <request> elements to indicate the actions supported by the IVS. The<request> element contains attributes to indicate the request and to supplyany needed information, and MAY contain a <text> child element to contain the text for a dynamic message.related information. The 'action' attribute is mandatory and indicates the specific action. An IANA registry is created in Section 14.8.1 to contain the allowed values. Extensibility: New elements, child elements, attributes of new and existing elements, and values for new and existing attributes can bedefinedadded innew namespaces.the IANAregistriesregistry created in Section 14.8.2. The registry permits implementors to see what has been added, with a reference to the defining document. (Implementations areusednot expected tospecifydynamically check thepermitted values of several elementsregistry.) Implementations MUST ignore unsupported elements, attributes, andattributes. These mechanisms allow for extension. There is no 'request' action to play dynamic media (such as a pre- recorded audio message). The SIP re-INVITE mechanism can be used to establish a one-way media stream for this purpose. 9.1.1.values. 8.1.1. The <ack> element The <ack> element is transmitted by the PSAP to acknowledge receipt of an eCall data object. An <ack> element sent by a PSAP references the unique ID of the data object that was sent by the IVS, and further indicates if the PSAP considers the receipt successful or not. The <ack> elementis also transmitted by the IVS to the PSAP to acknowledge receipt of a <request> element that requested the IVS 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 transmit a data object would not result in a separate <ack> element being sent, since the data object itself serves as acknowledgment.) An <ack> element sent by an IVS references the unique ID of the request being acknowledged, indicates whether the request was successfully performed, and if not, optionally includes an explanation. The <ack> elementhas the followingattributes and child elements: 9.1.1.1.attributes: 8.1.1.1. Attributes of the <ack> element The <ack> element has the following attributes: Name: ref Usage: Mandatory Type: anyURI Description: References the Content-ID of the body part that contained the data objector control objectbeing acknowledged. Example: <ack received="yes" ref="1234567890@atlanta.example.com"/> Name: received Usage: Conditional: mandatory in an >ack< element sent by aPSAP; not applicable in an >ack< element sent by an IVSPSAP Type: Boolean Description: Indicates if the referenced object was successfully received or not Example: <ack received="yes" ref="1234567890@atlanta.example.com"/>9.1.1.2.8.1.1.2. Child Elements of the <ack> element The <ack> element hasthe followingno childelements: Name: actionResult Usage: Optional Description: An <actionResult> element indicates the result of an action (other than a 'send-data' action). When an <ack> element is in response to a control object with multiple <request>elements(that are not 'send-data' actions), the <ack> element contains an <actionResult> element for each. The <actionResult> element has the following attributes: Name: action Usage: Mandatory Type: token Description: Contains the value of the 'action' attribute of the <request> element Name: success Usage: Mandatory Type: Boolean Description: Indicates if the action was successfully accomplished Name: reason Usage: Conditional Type: token Description: Used when 'success' is "False", this attribute contains a reason code for a failure. A registry for reason codes is defined in Section 14.8.3. Name: details Usage: optional Type: string Description: Contains further explanation of the circumstances of a success or failure. The contents are implementation-specific and human-readable. Example: <actionResult action="msg-dynamic" success="true"/> Example: <actionResult action="lamp" success="false" reason="unable" details="The requested lamp is inoperable"/> 9.1.1.3.8.1.1.3. Ack Examples <?xml version="1.0" encoding="UTF-8"?><EmergencyCallData.eCallControl xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"<EmergencyCallData.eCall.Control xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: eCall-control">xsi:schemaLocation= "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> <ack received="true" ref="1234567890@atlanta.example.com"/></EmergencyCallData.eCallControl></EmergencyCallData.eCall.Control> Figure 3: Ack Example from PSAP to IVS<?xml version="1.0" encoding="UTF-8"?> <EmergencyCallData.eCallControl xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: eCall-control"> <ack ref="1234567890@atlanta.example.com"> <actionResult action="msg-dynamic" success="true"/> <actionResult action="lamp" success="false" reason="unable" details="The requested lamp is inoperable"/> </ack> </EmergencyCallData.eCallControl> Figure 4: Ack Example from IVS to PSAP 9.1.2.8.1.2. The<capabilities> element The <capabilities> element is transmitted by the IVS to indicate to the PSAP its capabilities. No attributes for this element are currently defined. The following child elements are defined: 9.1.2.1. Child Elements of the <capabilities> element The <capabilities> element has the following child elements: Name: request Usage: Mandatory Description: The <capabilities> element contains a <request> child element per action supported by the vehicle. Because support for a 'send-data' action is REQUIRED, a <request> child element with a "send-data" 'action' attribute is also REQUIRED. The 'supported-datatypes' attribute is REQUIRED in this<request> elementwithin a <capabilities> element, and MUST contain at a minimum the 'eCall.MSD' data block value; it SHOULD contain all data blocks supported by the IVS. All other actions are OPTIONAL. If the "msg-static" action is supported, aA <request>childelementwith a "msg-static" 'action' attribute is sent, with a 'msgid' attribute set to the highest supported static message supported by the vehicle. A registry is created in Section 14.8.2 to map 'msgid' values to static text messages. By sending the highest supported static message number in its <capabilities> element, the vehicle indicates its support for all static messages inallows theregistry upPSAP toand includingrequest thatvalue. Ifthe"lamp" action is supported, a <request> child element with a "lamp" 'action' is sent, with a 'supported-lamps' attribute set to all supported lamp IDs. If the "enable-camera" action is supported, a <request> child element withIVS send an"enable-camera" 'action' is sent, with a 'supported-cameras' attribute set to all supported camera IDs. Examples: <request action="send-data" supported-datatypes="eCall.MSD" /> <request action="send-data" supported-datatypes="eCall.MSD; VEDS; eCall.type2" /> <request action="msg-dynamic"/> <request action="msg.static" msgid="17" /> 9.1.2.2. Capabilities Example <?xml version="1.0" encoding="UTF-8"?> <EmergencyCallData.eCallControl xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: eCall-control"> <capabilities> <request action="send-data" supported-datatypes="eCall.MSD"/> <request action="lamp" supported-lamps="head;interior;fog-front;fog-rear;brake; position-front;position-rear;turn-left;turn-right;hazard"/> <request action="msg-static" msgid="3"/> <request action="msg-dynamic"/> <request action="honk"/> <request action="enable-camera" supported-cameras="backup; interior"/> </capabilities> </EmergencyCallData.eCallControl> Figure 5: Capabilities Example 9.1.3. The <request> element A <request> element appears one or more times on its own or as a child of a <capabilities> element.MSD. The following attributesand child elementsare defined:9.1.3.1.8.1.2.1. Attributes of the <request> element The <request> element has the following attributes: Name: action Usage: Mandatory Type: token Description: Identifies the action that the vehicle is requested to perform. An IANA registry is established in Section 14.8.1 to contain the allowed values. Example: action="send-data" Name:msgid Usage: Conditional Type: int Description: Mandatory with a "msg-static" action. Indicates the identifier of the static message to be displayed and/or spoken for the vehicle occupants. This document established an IANA registry for messages and their IDs, in Section 14.8.2 Example: msgid="3" Name: persistance Usage: Optional Type: duration Description: Specifies how long to carry on the specified action, for example, how long to continue honking or flashing. If absent, the default is indefinitely. Example: persistance="PT1H" Name:datatype Usage: Conditional Type: token Description: Mandatory with a "send-data" action. Specifies the data block that the IVS is requested to transmit, using the same identifier as in the 'purpose' attribute set in a Call-Info header field to point to the data block. Permitted values are contained in the 'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecrit-additional-data]. Example: datatype="eCall.MSD"Name: supported-datatypes Usage: Conditional Type: string Description: Used with a 'send-data' action in a <request> element that is a child of a <capability> element, this attribute lists all data blocks that the vehicle can transmit, using the same identifier as in the 'purpose' attribute in a Call-Info header field to point to the data block. Permitted values are contained in the 'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecrit-additional-data]. Multiple values are separated with a semicolon. Example: supported-datatypes="eCall.MSD; VEDS; eCall.foo" Name: lamp-action Usage: Conditional Type: token Description: Used with a 'lamp' action, indicates if the lamp is to be illuminated, turned off, or flashed. Permitted values are 'on', 'off', and 'flash'. Example: lamp-action="flash" Name: lamp-ID Usage: Conditional Type: token Description: Used with a 'lamp' action, indicates which lamp the action affects. Permitted values are contained in the registry of lamp-ID tokens created in Section 14.8.4 Example: lamp-ID="hazard" Name: supported-lamps Usage: Conditional Type: string Description: Used with a 'lamp' action in a <request> element that is a child of a <capability> element, this attribute lists all supported lamps, using values in the registry of lamp-ID tokens created in Section 14.8.4. Multiple values are separated with a semicolon. Example: supported-lamps="head; interior; fog-front; fog-rear; brake; position-front; position-rear; turn-left; turn-right; hazard" Name: camera-ID Usage: Conditional Type: token Description: Used with an 'enable-camera' action, indicates which camera to enable. Permitted values are contained in the registry of camera-ID tokens created in Section 14.8.5. When a vehicle camera is enabled, the IVS sends a re-INVITE to negotiate a one- way media stream for the camera. Example: camera-ID="backup" Name: supported-cameras Usage: Conditional Type: string Description: Used with an 'enable-camera' action in a <request> element that is a child of a <capability> element, this attribute lists all cameras that the vehicle supports (can add as a video feed in the current session), using the same identifiers as are used in the 'camera-ID' attribute (contained in the camera ID registry in Section 14.8.5). Multiple values are separated with a semicolon. Example: supported-cameras="backup; interior" 9.1.3.2. Child Elements of the <request> element The <request> element has the following child elements: Name: text Usage: Conditional Type: string Description: Used within a <request action="msg-dynamic"> element to contain the text to be displayed and/or spoken (via text-to- speech) for the vehicle occupants. Example: <text>Emergency authorities are aware of your incident and location. Due to a multi-vehicle incident in your area, no one is able to speak with you right now. Please remain calm. We will assist you soon.</text> 9.1.3.3.8.1.2.2. Request Example <?xml version="1.0" encoding="UTF-8"?><EmergencyCallData.eCallControl xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"<EmergencyCallData.eCall.Control xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: eCall-control">xsi:schemaLocation= "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> <request action="send-data" datatype="eCall.MSD"/><request action="lamp" lamp-id="hazard" lamp-action="flash" persistance="PT1H"/> <request action="msg-static" msgid="1"/> <request action="msg-dynamic"> <text>Remain calm. Help is on the way.</text> </request> </EmergencyCallData.eCallControl></EmergencyCallData.eCall.Control> Figure6:4: Request Example9.2.9. The emergencyCallData.eCall INFO package This document registers the 'emergencyCallData.eCall' INFO package. Both endpoints (the IVS and the PSAP equipment)set theinclude 'emergencyCallData.eCall' in a Recv-Info header fieldto 'emergencyCallData.eCall'per [RFC6086] to indicate ability to receive INFO messages carryingeCalldataor control blocks.as described here. Support for the 'emergencyCallData.eCall' INFO package indicates the ability to receiveeCallbody parts registered in the 'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecrit-additional-data]. An INFO request message carrying data related to an emergency call has an Info-Package header field set to 'emergencyCallData.eCall' per [RFC6086]. Per [I-D.ietf-ecrit-additional-data], the INFO request message contains one or more Call-Info header fields containing a CID URL referencing the unique identifier of a body part, andcontrol blocks, which area 'purpose' parameter identifying the data. Because the data is being carried inaan INFO request message, the body partwhose subtype starts with 'emergencyCallData.eCall.'. At present therealso carries a Content- Disposition header field set to "Info-Package". 9.1. INFO Package Requirements The requirements of Section 10 of [RFC6086] are addressed in the following sections. 9.1.1. Overall Description This section describes "what type of information isonly one defined eCall data block, which hascarried in INFO requests associated with the'application/emergencyCallData.eCall.MSD+xml' MIME type,Info Package, andone eCall control block, which hasfor what types of applications and functionalities UAs can use the'application/ emergencyCallData.eCall.control+xml' MIME type. The eCall control block includesInfo Package." INFO requests associated with theability foremergencyCallData.eCall INFO package carry data associated with emergency calls as registered in theIVS to indicate its capabilities, so'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecrit-additional-data]. The application is emergency calls established using SIP. The functionality is to carry data, metadata, and control information (requests) between vehicles and PSAPs. Refer to [TBD: THIS DOCUMENT] for more information. 9.1.2. Applicability This section describes "why theevent additional eCall blocks are defined,Info Package mechanism, rather than some other mechanism, has been chosen for theIVS can indicate which it supports.specific use-case...." The use of INFO is based on an analysis of the requirements against the intent and effects of INFO versus other approaches(such as(which included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, mediaplane, orplane transport, and non-SIP protocols). In particular, the transport ofeCallemergency call dataand controlblocksis done only during anoccurs within a SIP emergencysession established with SIP,dialog, using the mechanism established in [I-D.ietf-ecrit-additional-data], and is normally carried in the initial INVITE and its response; the use of INFO only occurs whenaemergency-call-related datablock or requestneeds to be sentsubsequently during the call.mid-call. While MESSAGE could be used, it is not tied to a SIPsessiondialog as isINFO. REINVITEINFO and thus might not be associated with the dialog. SIP OPTIONS or re-INVITE could also be used, but isnormally used to modify the session.seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into service, but the semantics are not aclean fit. Hence, INFOgood fit, e.g., the subscribe/notify mechanism provides one-way communication consisting of (often multiple) notifications from notifier to subscriber indicating that certain events in notifier have occurred, whereas what's needed here isappropriate. An INFO request message carrying an eCalltwo-way communication of dataor control block has an Info-Package header field setrelated to'emergencyCallData.eCall' per [RFC6086]. The INFO request messagethe emergency dialog. Use of the media plane mechanisms was discounted because the number of messages needing to be exchanged in a dialog ismarkednormally zero or very few, and the size of the data is likewise very small. The overhead caused by user plane setup (e.g., to use MSRP ascontainingtransport) would be disproportionately large, and further, a high-level application protocol identifying theeCallspecific dataor controlblock being sent within the media plane (as provided byathe Call-Info header fieldcontaining a CID URL referencing the unique identifier of theparameters and MIME body partcontainingcontent type within INFO) would need to be defined. Based on theeCall data or control, and a 'purpose' parameter identifyingtheblock. Becauseanalyses, theeCallSIP INFO method was chosen to provide for mid-call dataor control blocktransport. 9.1.3. Info Package Name The info package name isbeing carried in anemergencyCallData.eCall. 9.1.4. Info Package Parameters None. 9.1.5. SIP Option-Tags None. 9.1.6. INFOrequest message,Message Body Parts Only those body parts registered in the 'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecrit-additional-data] are associated with this INFO package. When more than one body partalso carriesis included, they are enclosed in aContent- Disposition header field set to "Info-Package". Per [I-D.ietf-ecrit-additional-data], emergency call related additional data MAY be includedmultipart body part (e.g., multipart/mixed). When a body part is digitally signed or encrypted, it is enclosed inany SIP requestan appropriate body part (e.g., multipart/signed orresponse message that can containmultipart/encrypted). The Content-Disposition value of abody. Hence, notwithstanding Section 4.3.2.message body part associated with the emergencyCallData.eCall info package is "info-package". 9.1.7. Info Package Usage Restrictions None. 9.1.8. Rate of[RFC6086],INFOresponse messages MAYRequests The rate of SIP INFO requests associated with the emergencyCallData.eCall info package is expected to be quite low (most dialogs are likely to containeCallzero INFO requests, while others can be expected to carry occasional requests). 9.1.9. Info Package Security Considerations The MIME content type registation for each dataor control blocks, provided they are included as describedblock registered inthis document (with a Call-Info header field containing a CID URL referencingtheunique identifier'Emergency Call Data Types' IANA registry established in [I-D.ietf-ecrit-additional-data] contains a discussion of thebody part,security and/or privacy considerations specific to that data block. The "Security Considerations" anda 'purpose' parameter identifying"Privacy Considerations" sections of [TBD: THIS DOCUMENT] discuss security and privacy considerations of theblock). When eCalldataor control blocks are includedcarried inan INFO response message, this is done per [I-D.ietf-ecrit-additional-data] and this document, and not under [RFC6086]; that is, they are included as emergency call additional data, not as an INFO package associated data.eCealls. 9.1.10. Implementation Details See [TBD: THIS DOCUMENT] for protocol details. 9.1.11. Examples See [TBD: THIS DOCUMENT] for protocol examples. 10. Examples Figure7 shows5 illustrates an eCall. The call uses the request URI 'urn:service:sos.ecall.automatic' service URN and is recognized as an eCall, and further as one that was invoked automatically by the IVS due to a crash or other serious incident. In this example, the originating network routes the call to an ESInet(as for any emergency call in an environment with an ESInet). The ESInetwhich routes the call to the appropriate NG-eCall capable PSAP. The emergency call is received by the ESInet's Emergency Services Routing Proxy (ESRP), as the entry point into the ESInet. The ESRP routes the call to a PSAP, where it is received by a call taker. In deployments where there is no ESInet, the originating network routes the call directly to the appropriate NG-eCall capablePSAP.PSAP, an illustration of which would be identical to the one below except without an ESInet or ESRP. +------------+ +---------------------------------------+ | | | +-------+ | | | | | PSAP2 | | | | | +-------+ | | | | | | | | +------+ +-------+ | Vehicle-->| |--+->| ESRP |---->| PSAP1 |--> Call-Taker | | | | +------+ +-------+ | | | | | | | | +-------+ | | | | | PSAP3 | | | Originating| | +-------+ | | Mobile | | | | Network | | ESInet | +------------+ +---------------------------------------+ Figure7:5: Example of NG-eCall Message Flow The example, shown in Figure8,6, illustrates a SIP eCall INVITE that contains anMSD and an eCall control block with vehicle capabilities.MSD. For simplicity, the example does not show all SIP headers, nor the SDP contents, nor does it showtheany additional data blocks added by the IVSandor the originating mobile network. Because the MSD is encoded in ASN.1 PER, which is a binary encoding, its contents cannot be included in a text document. INVITE urn:service:sos.ecall.automatic SIP/2.0 To: urn:service:sos.ecall.automatic From: <sip:+13145551111@example.com>;tag=9fxced76sl Call-ID: 3848276298220188511@atlanta.example.com Geolocation: <cid:target123@example.com> Geolocation-Routing: no Call-Info: cid:1234567890@atlanta.example.com; purpose=emergencyCallData.eCall.MSD; cid:2345678901@atlanta.example.com; purpose=emergencyCallData.eCall.control; Accept: application/sdp, application/pidf+xml,application/emergencyCallData.eCall.controlapplication/emergencyCallData.eCall.control+xml CSeq: 31862 INVITE Recv-Info: emergencyCallData.eCall Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, SUBSCRIBE, NOTIFY, UPDATE Content-Type: multipart/mixed; boundary=boundary1 Content-Length: ... --boundary1 Content-Type: application/sdp ...Session Description Protocol (SDP) goes here... --boundary1 Content-Type:application/emergencyCallData.eCall.MSD+xmlapplication/emergencyCallData.eCall.MSD+per Content-ID: 1234567890@atlanta.example.com Content-Disposition: by-reference;handling=optional<ECallMessage> <id>1</id> <msd> <msdStructure> <messageIdentifier>1</messageIdentifier> <control> <automaticActivation> <true/> </automaticActivation> <testCall> <false/> </testCall> <positionCanBeTrusted> <true/> </positionCanBeTrusted> <vehicleType> <passengerVehicleClassM1/> </vehicleType> </control> <vehicleIdentificationNumber> <isowmi>WMI</isowmi> <isovds>VDSVDS</isovds> <isovisModelyear>Y</isovisModelyear> <isovisSeqPlant>A123456</isovisSeqPlant> </vehicleIdentificationNumber> <vehiclePropulsionStorageType> <gasolineTankPresent> <true/> </gasolineTankPresent> <electricEnergyStorage> <true/> </electricEnergyStorage> </vehiclePropulsionStorageType> <timestamp>123456789</timestamp> <vehicleLocation> <positionLatitude>173881200</positionLatitude> <positionLongitude>41822520</positionLongitude> </vehicleLocation> <vehicleDirection>14</vehicleDirection> <recentVehicleLocationN1> <latitudeDelta>10</latitudeDelta> <longitudeDelta>-10</longitudeDelta> </recentVehicleLocationN1> <recentVehicleLocationN2> <latitudeDelta>10</latitudeDelta> <longitudeDelta>-20</longitudeDelta> </recentVehicleLocationN2> <numberOfPassengers>2</numberOfPassengers> </msdStructure> <optionalAdditionalData> <oid>1.2.125</oid> <data>30304646</data> </optionalAdditionalData> </msd> </ECallMessage> --boundary1 Content-Type: application/emergencyCallData.eCall.control+xml Content-ID: 2345678901@atlanta.example.com Content-Disposition: by-reference;handling=optional <?xml version="1.0" encoding="UTF-8"?> <EmergencyCallData.eCallControl xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: eCall-control"> <capabilities> <request action="send-data" supported-datatypes="eCall.MSD"/> <request action="lamp" supported-lamps="head;interior;fog-front;fog-rear; brake;position-front;position-rear;turn-left; turn-right;hazard"/> <request action="msg-static" msgid="3"/> <request action="msg-dynamic"/> <request action="honk"/> <request action="enable-camera" supported-cameras="backup; interior"/> </capabilities> </EmergencyCallData.eCallControl>Content-Transfer-Encoding: binary ...MSD in ASN.1 PER encoding goes here... --boundary1-- Figure8:6: SIP NG-eCall INVITE Continuing the example, Figure97 illustrates a SIP 200 OK response to the INVITE of Figure8,6, containing an eCall control block acknowledging successful receipt of the eCall MSD. (For simplicity, the example does not show all SIP headers.) SIP/2.0 200 OK To: <sip:+13145551111@example.com>;tag=9fxced76sl From: Exemplar PSAP <urn:service:sos.ecall.automatic> Call-ID: 3848276298220188511@atlanta.example.com Call-Info: cid:2345678901@atlanta.example.com; purpose=emergencyCallData.eCall.control; Accept: application/sdp, application/pidf+xml,application/emergencyCallData.eCall.control, application/emergencyCallData.eCall.MSDapplication/emergencyCallData.eCall.control+xml, application/emergencyCallData.eCall.MSD+per CSeq: 31862 INVITE Recv-Info: emergencyCallData.eCall Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, SUBSCRIBE, NOTIFY, UPDATE Content-Type: multipart/mixed; boundary=boundaryX Content-Length: ... --boundaryX Content-Type: application/sdp ...Session Description Protocol (SDP) goes here... --boundaryX Content-Type:application/EmergencyCallData:eCall-control+xmlapplication/EmergencyCallData.eCall.control+xml Content-ID: 2345678901@atlanta.example.com Content-Disposition: by-reference;handling=optional <?xml version="1.0" encoding="UTF-8"?><EmergencyCallData.eCallControl xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"<EmergencyCallData.eCall.Control xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: eCall-control">xsi:schemaLocation= "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> <ack received="true" ref="1234567890@atlanta.example.com"/></EmergencyCallData.eCallControl></EmergencyCallData.eCall.Control> --boundaryX-- Figure9:7: 200 OK response to INVITE 11. Security Considerations The security considerations described in [RFC5069] apply here. In addition to any network-provided locationthat is inherently permitted for IMS emergency calls(which might be determined solely by the network, or in cooperation with or possibly entirely by the originating device), an eCall carries an IVS-supplied location within the MSD. This is likely to be useful to the PSAP, especially when no network-provided location is included, or when the two locations are independently determined. Even in situations where the network-supplied location is limited to the cell site, this can be useful as a sanity check on the device-supplied location contained in the MSD. The document [RFC7378] discusses trust issues regarding location provided by or determined in cooperation with end devices. Security considerations specific to the mechanism by which the PSAP sends acknowledgments and requests to the vehicle are discussed in the "Security Considerations" block of Section 14.3.In addition to that discussion, it's important to note that vehicles MAY decline to carry out any requested action, e.g., if the vehicle is unable to verify the certificate used to sign the request. The vehicle MAY use any value in the reason registry in Section 14.8.3 to indicate why it did not take an action (e.g., the generic "unable" or the more specific "security-failure").Data received from external sources inherently carries implementationrisks includingrisks. For example, depending on the platform, bufferoverflows, which in many platformsoverflows can introduce remote code executionvulnerabilities;vulnerabilities, null characters can corrupt strings, numeric values used for internal calculations can result in underflow/overflowerrors;errors, malformed XML objects can expose parsing bugs, etc. Implementations need to be cognizant of the potential risks, observe best practices(e.g., good quality(which might include sufficiently capable static code analysis, fuzz testing, component isolation, avoiding use of unsafe coding techniques, third-party attack tests, signed software, over-the-air updates, etc.), and have multiple levels of protection. Implementors need to be aware that, potentially, the data objects described here and elsewhere might be malformed, might contain unexpected characters, excessively long attribute values, elements, etc.(This applies across the board, not just to the 'text' attribute of a <request> element.)Since this document depends on [I-D.ietf-ecrit-additional-data], the security considerations discussed there apply here (see especially the discussion of TLS, TLS versions, cypher suites, and PKI). When vehicle data or control/metadata is contained in a signed or encrypted body part, the enclosing multipart (e.g., multipart/signed or multipart/encrypted) has the same Content-ID as the enclosed data part. This allows an entity to identify and access the data blocks it is interested in without having to dive deeply into the message structure or decrypt parts it is not interested in. (The 'purpose' parameter in a Call-Info header field identifies thedata,data andthecontains a CID URLpointspointing to the data block in the body, which has a matching Content-ID body part header field). 12. Privacy Considerations Since this document builds on [I-D.ietf-ecrit-additional-data], the data structures specified there, and the corresponding privacy considerations discussed there, apply here as well. The MSD carries some additional identifying and personal information (mostly about the vehicle and less about the owner), as well as location information, and so needs to be protected against unauthorized disclosure. Local regulations may impose additional privacy protection requirements.The additional functionality enabled by this document, such as access to vehicle camera streams, carries a burden of protection and so implementations need to be careful that access is only provided within the context of an emergency call and to an emergency services provider, for example, by verifying that the request for camera access is signed by a certificate issued by an emergency services registrar.Privacy considerations specific to the data structure containing vehicle information are discussed in the "Security Considerations" block of Section 14.2. Privacy considerations specific to the mechanism by which the PSAP sends acknowledgments and requests to the vehicle are discussed in the "Security Considerations" block of Section 14.3. 13. XML Schema This section definesthean XML schemaoffor the eCall control block.(The schema forThe text description of theMSD can be foundeCall control block inEN 15722 [msd].)Section 8.1 is normative and supersedes any conflicting aspect of this schema. <?xml version="1.0"?> <xs:schematargetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"targetNamespace= "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns:xs="http://www.w3.org/2001/XMLSchema"xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns:xml="http://www.w3.org/XML/1998/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2009/01/xml.xsd"/> <xs:elementname="EmergencyCallData.eCallControl"name="EmergencyCallData.eCall.Control" type="pi:eCallControlType"/> <xs:simpleType name="iana-token"> <xs:annotation> <xs:documentation>Permitted values specified in IANA registries</xs:documentation> </xs:annotation> </xs:simpleType> <xs:complexType name="eCallControlType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:choice> <xs:elementname="capabilities" type="pi:capabilitiesType"/> <xs:elementname="request" type="pi:requestType"/> <xs:element name="ack" type="pi:ackType"/> <xs:element type="cx:iana-token"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:choice> <xs:anyAttribute/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:complexType name="ackType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:sequence minOccurs="1" maxOccurs="unbounded"><xs:element name="actionResult" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:attribute name="action" type="xs:token" use="required"/> <xs:attribute name="success" type="xs:boolean" use="required"/> <xs:attribute name="reason" type="xs:token"> <xs:annotation> <xs:documentation>conditionally mandatory when @success='false" to indicate reason code for a failure </xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="details" type="xs:string"/> <xs:anyAttribute processContents="skip"/> </xs:complexType> </xs:element><xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:attribute type="cx:iana-token"/> </xs:sequence> <xs:attribute name="ref" type="xs:anyURI" use="required"/> <xs:attribute name="received" type="xs:boolean"/> <xs:anyAttribute/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:complexTypename="capabilitiesType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:sequence minOccurs="1" maxOccurs="unbounded"> <xs:element name="request" type="pi:requestType" minOccurs="1" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:complexTypename="requestType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:choice minOccurs="1" maxOccurs="unbounded"> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:element type="cx:iana-token"/> </xs:choice> <xs:attribute name="action" type="xs:token" use="required"/> <xs:attributename="msgid" type="xs:unsignedInt"/> <xs:attribute name="persistence" type="xs:duration"/> <xs:attribute name="datatype" type="xs:token"/> <xs:attribute name="supported-datatypes" type="xs:string"/> <xs:attribute name="lamp-id" type="xs:token"/> <xs:attribute name="lamp-action"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value=""/> <xs:pattern value=""/> <xs:enumeration value="on"/> <xs:enumeration value="off"/> <xs:enumeration value="flash"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="supported-lamps" type="xs:string"/> <xs:attribute name="camera-id" type="xs:token"/> <xs:attribute name="supported-cameras" type="xs:string"/>type="cx:iana-token" minOccurs="0" maxOccurs="unbounded"/> <xs:anyAttribute/> </xs:restriction> </xs:complexContent> </xs:complexType> </xs:schema> Figure10:8: eCall Control Block Schema 14. IANA Considerations 14.1. Service URN Registrations IANA is requested to register the URN 'urn:service:sos.ecall' under the sub-services 'sos' registry defined in Section 4.2 of [RFC5031]. This serviceidentifies a type ofrequests resources associated with an emergency call(placedplaced bya specializedan in-vehiclesystem and asystem, carrying a standardized set of data related to the vehicle andcrash or incident, and is needed to direct the call to a specialized public safety answering point (PSAP) with technical and operational capabilities to handle such calls.incident. Two sub-services are registered aswell, namelywell: urn:service:sos.ecall.manualThis service URN indicates thatUsed with an eCallhad been triggered based on theinvoked due to manual interactionof the driver orby apassenger.vehicle occupant. urn:service:sos.ecall.automaticThis service URN indicates thatUsed with an eCallhad been triggeredinvoked automatically, for example, due to a crash or other seriousincident (e.g., fire).incident. IANA is also requested to register the URN 'urn:service:test.sos.ecall' under the sub-service 'test' registry defined in Setcion 17.2 of [RFC6881]. 14.2. MIME Content-type Registration for 'application/emergencyCallData.eCall.MSD+xml'emergencyCallData.eCall.MSD+per' IANA is requested to addapplication/emergencyCallData.eCall.MSD+xmlapplication/emergencyCallData.eCall.MSD+per as a MIME content type, with a reference to this document, in accordance to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name:emergencyCallData.eCall.MSD+xmlemergencyCallData.eCall.MSD+per Mandatory parameters: none Optional parameters:charset Indicates the character encoding of the XML content.none Encoding scheme: binary Encoding considerations: UsesXML,ASN.1 PER, whichcan employ 8-bit characters, depending on the characteris a binary encoding; when transported in SIP, binary content transfer encoding is used.See Section 3.2 of RFC 7303 [RFC7303].Security considerations: This content type is designed to carry vehicle and incident-related data during an emergency call. This data contains personal information including vehicle VIN, location, direction, etc. Appropriate precautions need to be taken to limit unauthorized access, inappropriate disclosure to third parties, and eavesdropping of this information. In general, it ispermissibleacceptable for the data to be unprotected while briefly in transit within the Mobile Network Operator (MNO); the MNO is trusted to not permit the data to be accessed by third parties. Sections 7 and Section 8 of [I-D.ietf-ecrit-additional-data] contain more discussion. Interoperability considerations: None Published specification: AnnexCA of EN 15722 [msd] Applications which use this media type: Pan-European eCall compliant systems Additional information: None Magic Number: None File Extension:.xmlNone Macintosh file type code:'TEXT''BINA' Person and email address for further information:Hannes Tschofenig, Hannes.Tschofenig@gmx.netRandall Gellens, rg+ietf@randy.pensive.org Intended usage: LIMITED USE Author:ThisThe MSD specification was produced by the European Committee For Standardization (CEN). For contact information, please see <http://www.cen.eu/cen/Pages/contactus.aspx>. Change controller: The European Committee For Standardization (CEN) 14.3. MIME Content-type Registration for 'application/ emergencyCallData.eCall.control+xml' IANA is requested to add application/ emergencyCallData.eCall.control+xml as a MIME content type, with a reference to this document, in accordance to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name: emergencyCallData.eCall.control+xml Mandatory parameters: none Optional parameters: charset Indicates the character encoding of the XML content. Encoding considerations: Uses XML, which can employ 8-bit characters, depending on the character encoding used. See Section 3.2 of RFC 7303 [RFC7303]. Security considerations: This content type carries metadata and control information and requests,primarilysuch as from a Public Safety Answering Point (PSAP) to an In-Vehicle System (IVS) during an emergencycall, and also capabilities from the IVS to the PSAP.call. Metadata (such as an acknowledgment that data sent by the IVS to the PSAP was successfully received) has limited privacy and security implications. Control information (such as requests from the PSAP that the vehicle perform an action) has some privacy andimportantsecurity implications. The privacy concern arises from the ability to request the vehicle to transmit a data set, which as described in Section 14.2, can contain personal information. The security concern is the ability to request the vehicle to perform an action.It is important that controlControl information needs to originate only from a PSAP or other emergency services provider, and not be modifieden- route.en-route. The level of integrity of the cellular network over which the emergency call is placed isimportant:a consideration: when the IVS initiates an eCall over a cellular network, in most cases it relies on the MNO to route the call to a PSAP. (Calls placed using other means, such as Wi-Fi or over-the-top services, generally incur somewhat higher levels of risk than calls placedover"natively" using cellular networks.) A call-back from a PSAPincursmerits additionalrisk,consideration, sincethecurrent mechanisms are not ideal for verifying that such a call is indeed a call-back from a PSAP in response to an emergency call placed by the IVS. See the discussion in Section 11 and the PSAP Callback document [RFC7090]. One potential safeguard, applicable regardless of which end initiated the call and the means of the call, is for the PSAP or emergency service provider to sign the body part using a certificate issued by a known emergency services certificate authority and for which the IVS can verify the rootcertificate.certificate; however, this depends on deployed key infrastructure including a recognized certificate authority, certificate revocation mechanisms, etc. Sections 7 and Section 8 of [I-D.ietf-ecrit-additional-data] contain more discussion. Interoperability considerations: None Published specification:Annex C of EN 15722 [msd]This document Applications which use this media type: Pan-European eCall compliant systems Additional information: None Magic Number: None File Extension: .xml Macintosh file type code: 'TEXT' Person and email address for further information: Randall Gellens,rg+ietf@qti.qualcomm.comrg+ietf@randy.pensive.org Intended usage: LIMITED USE Author: The IETF ECRIT WG. Change controller: The IETF ECRIT WG. 14.4. Registration of the 'eCall.MSD' entry in the Emergency Call Additional Data Blocks registry This specification requests IANA to add the 'eCall.MSD' entry to the Emergency Call Additional Data Blocks registry (established by [I-D.ietf-ecrit-additional-data]), with a reference to this document. 14.5. Registration of the 'eCall.control' entry in the Emergency Call Additional Data Blocks registry This specification requests IANA to add the 'eCall.control' entry to the Emergency Call Additional Data Blocks registry (established by [I-D.ietf-ecrit-additional-data]), with a reference to this document. 14.6. Registration of the emergencyCallData.eCall Info Package IANA is requested to add emergencyCallData.eCall to the Info Packages Registry under "Session Initiation Protocol (SIP) Parameters", with a reference to this document. 14.7. URN Sub-Namespace Registration 14.7.1. Registration for urn:ietf:params:xml:ns:eCall This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:eCall Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for eCall Data</title> </head> <body> <h1>Namespace for eCall Data</h1> <p>See [TBD: This document].</p> </body> </html> END 14.7.2. Registration for urn:ietf:params:xml:ns:eCall:control This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:eCall:control Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for eCall Data: Control Block</title> </head> <body> <h1>Namespace for eCall Data</h1> <h2>Control Block</h2> <p>See [TBD: This document].</p> </body> </html> END 14.8. Registry creation This document creates a new registry called 'eCall Control Data'. The following sub-registries are created for this registry. 14.8.1. eCall Control Action Registry This document creates a new sub-registry called "eCall Control Action Registry". As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the proposed action is within the purview of a vehicle, is sufficiently distinguishable from other actions, and theactionsaction is clearly and fully described. In most cases, a published and stable document is referenced for the description of the action. The content of this registry includes: Name: The identifier to be used in the 'action' attribute of an eCall control <request> element. Description: A description of the action. In most cases this will be a reference to a published and stable document. The description MUST specify if any attributes or child elements are optional or mandatory, and describe the action to be taken by the vehicle. The initial set of values is listed in Table 2.+---------------+------------------------------++-----------+------------------------------------------+ | Name | Description |+---------------+------------------------------++-----------+------------------------------------------+ | send-data | Sectionxxx of this document | | | | | msg-static |Sectionxxx8.1.2.1 of this document || | | | msg-dynamic | Section xxx of this document | | | | | honk | Section xxx of this document | | | | | lamp | Section xxx of this document | | | | | enable-camera | Section xxx of this document | +---------------+------------------------------++-----------+------------------------------------------+ Table 2: eCall Control Action Registry Initial Values 14.8.2. eCallStatic MessageControl Extension Registry This document creates a new sub-registry called "eCallStatic MessageControl Extension Registry".Because all compliant vehicles are expected to support all static messages translated into all languages supported by the vehicle, it is important to limit the number of such messages. As defined in [RFC5226], this registry operates under "Publication Required" rules, which require a stable, public document and imply expert review of the publication. The expert should determine that the document has been published by an appropriate emergency services organization (e.g., NENA, EENA, APCO) and that the proposed message is sufficiently distinguishable from other messages. The content of this registry includes: ID: An integer identifier to be used in the 'msgid' attribute of an eCall control <request> element. Message: The text of the message. Messages are listed in the registry in English; vehicles are expected to implement translations into languages supported by the vehicle. When new messages are added to the registry, the message text is determined by the registrant; IANA assigns the IDs. Each message is assigned a consecutive integer value as its ID.Thisallows an IVS to indicate by a single integer value that it supports all messages with that value or lower. The initial set of values is listed in Table 3. +----+--------------------------------------------------------------+ | ID | Message | +----+--------------------------------------------------------------+ | 1 | Emergency authorities are aware of your incident and | | | location, but are unable to speak with you right now. We | | | will help you as soon as possible. | +----+--------------------------------------------------------------+ Table 3: eCall Static Message Registry 14.8.3. eCall Reason Registry This document creates a new sub-registry called "eCall Reason Registry" whichregistry contains elements, attributes, and values for the'reason' attribute of the <actionResult> element.eCall metadata/control object. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the proposedreason is sufficiently distinguishable from other reasons and that the proposed description is understandable and correctly worded. The content of this registry includes: ID: A short string identifying the reason, for use in the 'reason' attribute of an <actionResult> element. Description: A description of the reason. The initial set of values is listed in Table 4. +------------------+------------------------------------------------+ | ID | Description | +------------------+------------------------------------------------+ | unsupported | The 'action' is not supported. | | | | | unable | The 'action' could not be accomplished. | | | | | data-unsupported | The data item referenced in a 'send-data' | | | request is not supported. | | | | | security-failure | The authenticity of the requestelements, attributes, and/ or values are within the| | | authoritypurview ofthe requestor could not be | | | verified. | +------------------+------------------------------------------------+ Table 4: eCall Reason Registry 14.8.4. eCall Lamp ID Registry This document createsanew sub-registry called "eCall Lamp ID Registry" to standardize the names of automotive lamps (lights). As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the proposed lamp name isvehicle, are sufficiently distinguishable, and clearlyunderstandableand fully described. In most cases, a published and stable document issufficiently distinguishable from other lamp names. The content of this registry includes: Name: The identifier to be used inreferenced for the'lamp-ID' attribute of an eCall control <request> element. Description: Adescription ofthe lamp (light). The initial set ofeach element, attribute, or value. New valuesis listedMUST indicate for which attributes or elements they are appropriate. New attributes MUST indicate inTable 5. +----------------+---------------------------------------------+ | Name | Description | +----------------+---------------------------------------------+ | head | The main lamps usedwhich elements they can appear and tolight the road ahead | | | | | interior | Interior lamp, oftenwhich values that can be set. New elements MUST indicate if they can appear as child elements within other elements, and if so which elements, and/ or if they can appear at the topcenter | | | | | fog-front | Front fog lamps | | | | | fog-rear | Rear fog lamps | | | | | brake | Brake indicator lamps | | | | | position-front | Front position/parking/standing lamps | | | | | position-rear | Rear position/parking/standing lamps | | | | | turn-left | Left turn/directional lamps | | | | | turn-right | Right turn/directional lamps | | | | | hazard | Hazard/four-way lamps | +----------------+---------------------------------------------+ Table 5: eCall Lamp ID Registry Initial Values 14.8.5.level of an eCallCamera ID Registry This document creates ametadata/control object. New elements MUST also describe which attributes and/or sub- elements they can contain and which are optional and which are mandatory. Note that this mechanism allows newsub-registry called "eCall Camera ID Registry"items tostandardize the names of automotive camera. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the proposed camera name is clearly understandable and is sufficiently distinguishable from other camera names.be added while maintaining compatibility with existing implementations, since unrecognized items are ignored. The content of this registry includes: Type: 'Element', 'Attribute', or 'Value'. Name: Theidentifier to be used in the 'camera-ID' attributename ofan eCall control <request> element.the new element or attribute. Not used for new values. Description: A description of thecamera. The initial set of values is listed in Table 6. +----------+--------------------------------------------------------+ | Name | Description | +----------+--------------------------------------------------------+ | backup | Shows what is behind the vehicle. Also known as | | | rearview, reverse, etc. | | | | | interior | Shows the interior (driver) | +----------+--------------------------------------------------------+ Table 6: eCall Camera ID Registry Initial Valueselement, attribute, or value. In most cases this will be a reference to a published and stable document. 15. Contributors Brian Rosen was a co-author of the original document upon which this document is based. 16. Acknowledgements We would like to thank Bob Williams and Ban Al-Bakri for their feedback andsuggestions, andsuggestion; Rex Buddenberg, Lena Chaponniere, Keith Drage,James Winterbottom,Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, andRex BuddenbergJames Winterbottom for their review andcomments.comments; Robert Sparks and Paul Kyzivat for their help with the SIP mechanisms. We would like to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and Ulrich Dietz for their help with the original document upon which this document is based. 17. Changes from Previous Versions 17.1. Changes from draft-ietf-07 to draft-ietf-08 o eCall MSD now encoded as ASN.1 PER, using binary content transfer encoding o Added text to point out aspects of call handling and metadata/ control usage, such as use in rejected calls, call-backs, and solicited MSDs 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 response to the requesting INFO o Added material to INFO package registation to comply with Section 10 of [RFC6086] o Moved material not required by 3GPP into [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ control elements, attributes, and values o Revised test call wording to clarify that specific handling is out of scope o Revised wording throughout the document to simplify o Moved new Section Section 6.1 to be a subsection of Section 6 o Moved new Section Section 9 to be a main section instead of a subsection of Section 8 o Revised SIP INFO usage and package registration per advice from Robert Sparks and Paul Kyzivat 17.2. Changes from draft-ietf-06 to draft-ietf-07 o Fixed typo in Acknowledgements 17.3. Changes from draft-ietf-05 to draft-ietf-06 o Added additional security and privacy clarifications regarding signed and encrypted data o Additional security and privacy text o Deleted informative section on ESINets as unnecessary.17.2.17.4. Changes from draft-ietf-04 to draft-ietf-05 o Reworked the security and privacy considerations material in the document as a whole and in the MIME registation sections of the MSD and control objects o Clarified that the <actionResult> element can appear multiple times within an <ack> element o Fixed IMS definition o Added clarifying text for the 'msgid' attribute17.3.17.5. Changes from draft-ietf-03 to draft-ietf-04 o Added Privacy Considerations section o Reworded most uses of non-normative "may", "should", "must", and "recommended." o Fixed nits in examples17.4.17.6. Changes from draft-ietf-02 to draft-ietf-03 o Added request to enable cameras o Improved examples and XML schema o Clarifications and wording improvements17.5.17.7. Changes from draft-ietf-01 to draft-ietf-02 o Added clarifying text reinforcing that the data exchange is for small blocks of data infrequently transmitted o Clarified that dynamic media is conveyed using SIP re-INVITE to establish a one-way media stream o Clarified that the scope is the needs of eCall within the SIP emergency call environment o Added informative statement that the document may be suitable for reuse by other ACN systems o Clarified that normative language for the control block applies to both IVS and PSAP o Removed 'ref', 'supported-mime', and <media> elements o Minor wording improvements and clarifications17.6.17.8. Changes from draft-ietf-00 to draft-ietf-01 o Added further discussion of test calls o Added further clarification to the document scope o Mentioned that multi-region vehicles may need to support other crash notification specifications in addition to eCall o Added details of the eCall metadata and control functionality o Added IANA registration for the MIME content type for the eCall control object o Added IANA registries for protocol elements and tokens used in the eCall control object o Minor wording improvements and clarifications17.7.17.9. Changes from draft-gellens-03 to draft-ietf-00 o Renamed from draft-gellens- to draft-ietf-. o Added mention of and reference to ETSI TR "Mobile Standards Group (MSG); eCall for VoIP" o Added text to Introduction regarding migration/co-existence being out of scope o Added mention in Security Considerations that even if the network- supplied location is just the cell site, this can be useful as a sanity check on the IVS-supplied location o Minor wording improvements and clarifications17.8.17.10. Changes from draft-gellens-02 to -03 o Clarifications and editorial improvements.17.9.17.11. Changes from draft-gellens-01 to -02 o Minor wording improvements o Removed ".automatic" and ".manual" from "urn:service:test.sos.ecall" registration and discussion text.17.10.17.12. Changes from draft-gellens-00 to -01 o Now using 'EmergencyCallData' for purpose parameter values and MIME subtypes, in accordance with changes to [I-D.ietf-ecrit-additional-data] o Added reference to RFC 6443 o Fixed bug that caused Figure captions to not appear 18. References 18.1. Normative References [EN_16072] CEN, , "Intelligent transport systems - eSafety - Pan- European eCall operatingrequirements", December 2011.requirements, EN 16072", April 2015. [I-D.ietf-ecrit-additional-data] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and J. Winterbottom, "Additional Data Related to an Emergency Call",draft-ietf-ecrit-additional-data-37draft-ietf-ecrit-additional-data-38 (work in progress),OctoberApril 2016. [msd] CEN, , "Intelligent transport systems -- eSafety -- eCall minimum set of data (MSD), EN 15722", April 2015. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI10.17487/ RFC2119,10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <http://www.rfc-editor.org/info/rfc3688>. [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services", RFC 5031, DOI 10.17487/RFC5031, January 2008, <http://www.rfc-editor.org/info/rfc5031>. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>. [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, "Framework for Emergency Calling Using Internet Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 2011, <http://www.rfc-editor.org/info/rfc6443>. [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, January 2013, <http://www.rfc-editor.org/info/rfc6838>. [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in Support of Emergency Calling", BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, <http://www.rfc-editor.org/info/rfc6881>. [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, DOI 10.17487/RFC7303, July 2014, <http://www.rfc-editor.org/info/rfc7303>. [TS22.101] 3GPP, ,"Technical"3GPP TS 22.101: Technical Specification Group Services and System Aspects; Service aspects; Serviceprinciples", . [msd] CEN, , "Intelligent transport systems -- eSafety -- eCall minimum set of data (MSD), EN 15722", June 2011.principles". 18.2. Informative references [CEN] "European Committee for Standardization", <http://www.cen.eu>. [I-D.ietf-ecrit-car-crash] Gellens, R., Rosen, B., and H. Tschofenig, "Next- Generation Vehicle-Initiated Emergency Calls", draft-ietf-ecrit-car-crash-03ecrit-car-crash-07 (work in progress),July 2015.February 2016. [MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04), April 2014. [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for Emergency Context Resolution with Internet Technologies", RFC 5012, DOI 10.17487/RFC5012, January 2008, <http://www.rfc-editor.org/info/rfc5012>. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. Shanmugam, "Security Threats and Requirements for Emergency Call Marking and Mapping", RFC 5069, DOI 10.17487/RFC5069, January 2008, <http://www.rfc-editor.org/info/rfc5069>. [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session Initiation Protocol (SIP) INFO Method and Package Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, <http://www.rfc-editor.org/info/rfc6086>. [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. Patel, "Public Safety Answering Point (PSAP) Callback", RFC 7090, DOI 10.17487/RFC7090, April 2014, <http://www.rfc-editor.org/info/rfc7090>. [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, December 2014, <http://www.rfc-editor.org/info/rfc7378>. [SDO-3GPP] "3d Generation Partnership Project", <http://www.3gpp.org/>. [SDO-ETSI] "European Telecommunications Standards Institute (ETSI)", <http://www.etsi.org>. Authors' Addresses Randall GellensQualcomm Technologies, Inc. 5775 Morehouse DriveConsultant 6755 Mira Mesa Blvd 123-151 San Diego9265192121 US Email: rg+ietf@randy.pensive.org Hannes Tschofenig(Individual)Individual Email: Hannes.Tschofenig@gmx.net URI: http://www.tschofenig.priv.at