hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 5.3 Calculation | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 5.3.1 General | The data to be hashed shall be the concatenation of the following in the order specified: 1) String encoding of Android package name provided in AndroidManifest.xml [i.2]. 2) Big endian 8-byte integer representing the version code provided in AndroidManifest.xml [i.3]. 3) The string "startManifestMain". 4) For each att... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 5.3.2 Shared UIDs | In Android APKs are allowed to share UIDs. Each APK shall be treated as an application as a whole and if two or more APK use the same shared UID, each of them will be considered an application in its own right. Each of those APKs shall be certified independently and each of them will have a unique application ID. ETSI ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 5.3.3 ROM applications | Application identifiers of apps built-into the device firmware (aka ROM) may be extracted by the MirrorLink Server from the self-signed certificate instead of being dynamically generated at runtime. This may be necessary due to firmware optimizations, which change the structure of an APK thus making it difficult to mai... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 5.4 APK Validation | An APK which contains files outside of the 'META-INF' directory with no MANIFEST.MF entries will be rejected by the Android platform. If a file is present in the MANIFEST.MF but does not a have a *-Digest entry then this will also be rejected by the Android platform. This is because both of these are requirements for a... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6 Application Information | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.1 General | As described in clause 6.1 of the Handling of Application Certificates specification [1], an application should come with a MirrorLink developer self-signed certificate Application Certificate for the purposes of providing the information needed by the MirrorLink Server to list the application in the A_ARG_TYPE_AppList... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.2 Self-Signed Application Certificates | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.2.1 General | The MirrorLink servers running on an Android platform shall allow for Self-Signed Application Certificates as described in clause 6.1 of [1]. ETSI ETSI TS 103 544-22 V1.3.1 (2019-10) 12 |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.2.2 Application Certificate Self-Signing Process | To create a MirrorLink aware application a Self-Signed X.509 Certificate shall be created. The certificate shall include the MirrorLink Extension Headers as described in clause 5.2.1 of [1]. The key used shall be a 2048-RSA key and the hashing shall be done using SHA-256 or SHA-512 signature algorithms. The self-signed... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.2.3 Self-Signed Application Certificate Installation | The Self-Signed Certificate shall be placed in a file called "self-signed.ccc.crt". The certificate file shall be placed in the assets folder of the APK containing the application. The MirrorLink server shall use the "self-signed.ccc.crt" file as the self-signed Application Certificate as described in clause 6.1 of [1]... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.3 Particulars of Android Application Certificates | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.3.1 General | The following clauses 6.3.2 and 6.3.3 describe any items which are in the Application Certificates that need to be adapted to the Android OS. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.3.2 Platform version | The platform version in the certificates shall match the constants defined in Build.VERSION_CODES. So for example if an application is available for Ice Cream Sandwich devices, the constant value of Build.VERSION_CODES.ICE_CREAM_SANDWICH should be used, which is the integer 14. The string representation shall be decima... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.3.3 Icon URLs | The Icon URL field shall be left empty; therefore, the iconList element shall be omitted from the Application Certificate. The MirrorLink Server shall use the icon provided with the Activity which accepts the LAUNCH and TERMINATE MirrorLink-specific Intents (see clause 8.2.2) or the icon provided through the Actions mo... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 6.4 Localized strings for the entries in the application certificate | The application certificate provides various strings without any localization information. In order to support localized versions of the strings, the application will provide them as string resources as follows. Table 1 Certificate element Resource name Name "com.mirrorlink.app.certificate.name" providerName "com.mirro... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 7 Development Certificates | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 7.1 General | Android MirrorLink Server devices will support the development of MirrorLink Applications. Clause 7 of the present document covers those aspects of the MirrorLink specification that address development of applications as described in the Handling of Application Development Certificates specification [3]. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 7.2 Device ID | Device IDs are the IMEI/IMEISV number or version 5 UUID derived from an equivalent unique identifier of the MirrorLink Server devices on which development applications can be used. All Android MirrorLink Servers should use the IMEI (or MEID/ESB for CDMA devices) as provided by the TelephonyManager's getDeviceId method ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 7.3 Application Development Certificates | The Android platform uses Application Development Certificates as described in clauses 5.1 and 7 of the Handling of Application Developer Certificates Document [3]. These certificates differ from the Self-Signed Application Certificate by the inclusion of an additional extension containing the Developer ID, which can b... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 7.4 Developer ID Entry | The Android MirrorLink server may provide a mechanism for the user of the device to enter one or more developer IDs into the server, as part of functionality available as part of the "developer mode" menu. (In Android 4.2, this can be reached by tapping on the Build Number entry 7 times in the About Phone screen.) The ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 7.5 Manual Developer ID Certificate Revocation Checks | The Android MirrorLink server shall allow for the user of the phone to immediately request the Developer ID Certificate associated with the Developer ID. This capability should be provided as part of the "developer mode" menu as described above. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8 MirrorLink API Implementation | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.1 General | All MirrorLink Servers using the Android platform shall implement the MirrorLink API as described below. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.2 API Overview | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.2.1 General | Before defining the actual API an overview of the mechanisms used in it should be considered: • The API is based on the "Android Interface Definition Language" (AIDL) and on the concept of content provider Contract classes. This should provide the necessary flexibility and extensibility of the API. Also, it means that ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.2.2 Android MirrorLink Server Requirements | • MirrorLink Servers shall allow access to the MirrorLink Service for all applications that bind using the "com.mirrorlink.android.service.BIND" family of Intents, and that have the "com.mirrorlink.android.service.ACCESS_PERMISSION" permission. This permission should be user- grantable on the MirrorLink Server. If more... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.2.3 Application Requirements | For an application to be MirrorLink aware there need to be some requirements that shall be met: • The application shall listen to the "com.mirrorlink.android.app.LAUNCH" and "com.mirrorlink.android.app.TERMINATE" Intents. It shall use the "android.intent.category.DEFAULT" category to filter on these intents. There shal... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3 MirrorLink API Library Definition | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.1 Data Type Definitions | For the data types defined please refer to the API javadoc files [i.4]. The data types refer back to the relevant section in the MirrorLink API Template [2]. The MirrorLink API template defines quite a few data types (for example all the variants of integers). To keep it simpler for the Java platform the types used wil... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.2 Data Structure Definitions | For the data structures defined please refer to the API javadoc files [i.4]. The data types refer back to the relevant section in the MirrorLink API Template [2]. ETSI ETSI TS 103 544-22 V1.3.1 (2019-10) 18 |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.3 MirrorLink API Elements accessible from the Service | To access the MirrorLink API Android MirrorLink Service an application shall use the "com.mirrorlink.android.service.BIND" family of Intents. Once the "service bind" callback is received, the application will get a reference to an ICommonAPIService (Api Level 1) or IMirrorLinkService_2 (Api Level 2) object. From this t... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.4 MirrorLink API Elements accessible from the Content Provider | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.4.1 General | The modules available through the Android MirrorLink Content Provider (together with the requirements for the Server and Application supporting them) are: Table 3 Module Content Path Mime Type Obligation CommonAPI /apilevel/ vnd.com.mirrorlink.android.provider.a pilevel Shall Connection Information /connection/ vnd.com... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.4.2 0xF0xx ' MirrorLink API Information mapping | Table 4 Resolver MirrorLink API Selection Query 0xF001 ' MirrorLink API Version None Query 0xF003 ' Server Device Identifier None Insert Not supported n/a Update Not supported n/a Delete Not supported n/a Notify Not supported n/a getType 0xF002 ' MirrorLink API Module Available n/a |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.4.3 0x02xx ' Certification Information mapping | Table 5 Resolver MirrorLink API Selection Query 0x0206 ' Get Any Application Certification Status appId Query 0x0207 ' Get Any Application Certifying Entities appId query 0x0208 ' Get Any Application Certification Information appId, entity Insert Not supported n/a ETSI ETSI TS 103 544-22 V1.3.1 (2019-10) 20 Resolver Mi... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.4.4 0x03xx ' Connection Information mapping | Table 6 Resolver MirrorLink API Cursor Query 0x0301 ' Established MirrorLink Connection None Insert Not supported n/a Update Not supported n/a Delete Not supported n/a Notify 0x0302 ' Established MirrorLink Connection Callback n/a |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.4.5 0x0Cxx ' Actions mapping | Table 7 Resolver Common API Selection Insert 0x0C01 ' Create Application Actions None Update 0x0C02 ' Update Application Actions actionId Query 0x0C03 ' Retrieve Application Actions appId actionType Delete 0x0C04 ' Delete Application Action actionId Notify 0x0C07 ' Application Actions Changed Callback None |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5 Modules dependencies | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.1 General | This clause describes the dependencies that exist between each module and other part of the MirrorLink protocol, like the application certificate for example. Whenever possible, the documentation pertaining to each specific module will be provided in javadoc format together with the Android MirrorLink Service AIDL and ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.2 General Android MirrorLink Service access | The Android MirrorLink Service is guarded by the "com.mirrorlink.android.service.ACCESS_PERMISSION". Additionally, a server may restrict access to the Android MirrorLink Service to applications sporting a valid certificate. ETSI ETSI TS 103 544-22 V1.3.1 (2019-10) 21 |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.3 General Android Content Provider Service access | The Android MirrorLink Content Provider is guarded by the "com.mirrorlink.android.provider. MIRRORLINK_PROVIDER_ACCESS_PERMISSION". Additionally, a server may restrict access to the Android MirrorLink Service to applications sporting a valid certificate. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.4 Actions Module write access | Only applications having the "com.mirrorlink.android.provider" pseudo service identifier listed in their certificate <serviceList> entry are allowed to publish actions to other MirrorLink aware applications. Only applications having the "com.mirrorlink.android.app.variant" pseudo service identifier listed in their cert... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.5 DataService Module Source Service Access | Only applications having the "{service-name}.source" pseudo service identifier listed in their certificate <serviceList> entry are allowed to contribute data to MirrorLink Data Services implemented as source by the MirrorLink server and consumed through a Sink by the MirrorLink client, for those services that it also l... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.6 Launch of Actions | On Android, and with the exception of variants, Actions shall be mapped to an Intent where the Intent action is the action type, the Intent package is the publishing application's package name and the Intent category is set to "com.mirrorlink.category.MIRRORLINK". Any Action Parameters shall be passed using the Intent ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.5.7 MirrorLink Actions | Whenever possible MirrorLink actions defined in the MirrorLink API specification shall be matched to their natural Android counterpart. As Intents shall be used by MirrorLink Servers and Applications to invoke a MirrorLink Action and query the result of an Action invocation each MirrorLink Action Type shall be matched ... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.6 Context Information Lifetime | The context information provided by a MirrorLink aware application shall be persisted and used by the MirrorLink server for the lifetime of the application's connection to the Android MirrorLink Service, independent of the underlying status of the MirrorLink connection to a MirrorLink client. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 8.3.7 Return values outside of a MirrorLink session | A MirrorLink Server may return undefined implementation specific values outside of a MirrorLink session. ETSI ETSI TS 103 544-22 V1.3.1 (2019-10) 23 |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 9 MirrorLink Events | |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 9.1 General | As the MirrorLink Server shall use the Android OS standard mechanisms for key events and virtual keyboards, these modules are not exposed using the MirrorLink API Service or Content Provider. Instead, standard Android Event injections mechanism are used to translate between MirrorLink events and native Android events. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 9.2 Touch Events Injections | The touch events shall be injected into the Android system by the MirrorLink server and the application should receive them as appropriate. This allows for the system to decide which activity gets to handle the events. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 9.3 Key Events Injections | The key events shall be injected into the Android system by the MirrorLink server and the application should receive them as appropriate. This allows for the system to decide which activity gets to handle the events. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 9.4 Key Event Mapping | MirrorLink Key Events, injected into the MirrorLink Server Device are mapped in Table 9 to the following Android Specific Key Events. The MirrorLink Server shall re-map all the Key Events marked with YES to standard Android Key Events and no other ones outside this set (none of the entries in the rows marked with NO ma... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 9.5 Virtual Keyboard | The virtual keyboard will be supported by the MirrorLink Server through the standard Android OS. Therefore, the application will not need any specific means to retrieve information about the virtual keyboard support. ETSI ETSI TS 103 544-22 V1.3.1 (2019-10) 25 |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 10 Platform Limitations | 10.1 CCC-TS-010-VNC Based Display and Control (ETSI TS 103 544-2) |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 10.1.1 Server Event Configuration Message | As the Android Operation System does not support ITU key bindings, MirrorLink Servers on Android shall not advertise ITU key support in their Server Event Configuration message, in accordance to the mapping table defined in clause 7. |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 10.1.2 Handling of Overlays | Overlays on Android can be classified in 4 broad classes: 1) Toast messages. 2) Overlay views. 3) System dialogs. 4) Application dialogs. Android does not support native detection and dismissal of class 1 or 2 overlays, and offer limited support to an application (i.e. not to a system services) to detect class 3 or 4 o... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 10.1.3 Handling of Applications Seeking Foreground Status | Android does not support actively preventing an application to be brought in the foreground so MirrorLink Servers on Android cannot be expected to prevent any application to be brought in the foreground by the operation system. MirrorLink Servers however, shall detect application coming into the foreground and alter th... |
af0c7044d8200bbd2e4acf7b4498a3d5 | 103 544-22 | 10.1.4 Removal of audio from non-certified applications | Besides Audio Focus Management, the Android operating system does not offer any APIs allowing to either detect applications actively contributing to the audio stream or prevent applications from contributing to the audio stream. Thus, MirrorLink Servers on Android cannot be expected to be able to remove effectively aud... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 1 Scope | The present document specifies a protocol implementation profile to enable secure communication between IPsec-protected network endpoints while enabling network operations. The Enterprise Network Security profile depends on two protocols in the IPsec family of protocols. First, Internet Key Exchange Protocol Version 2 ... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 2 References | |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 3 Definition of terms, symbols and abbreviations | |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 3.1 Terms | For the purposes of the present document, the following terms apply: Child SA: SA established by IKEv2 for use with the Encapsulating Security Payload (ESP) protocol or Authentication Header (AH) protocol Diffie-Hellman (DH) elements: longer-lived Diffie-Hellman public/private key pair contained in the Asymmetric Key P... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 3.2 Symbols | Void. |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN Abstract Syntax Notation CERT Certificate CMS Cryptographic Message Syntax DDOS Distributed Denial Of Service DER Distinguished Encoding Rules DH Diffie-Hellman EAP Extensible Authentication Protocol ENS Enterprise Network Security ESP Enc... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.1 Profile characteristics | In the ENS profile defined in the present document, one endpoint uses a longer-lived Diffie-Hellman key and so that endpoint unilaterally enables traffic visibility. The ENS profile defined in the present document also grants access to the entire data stream associated with the Security Associations (SAs) that are esta... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.2 Deployment of Enterprise Network Security (informative) | |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.2.1 Introduction | IPsec offers two modes of use: transport mode and tunnel mode as defined in IETF RFC 4301 [i.3]. In transport mode, ESP provides protection primarily for next layer protocols, and a transport mode SA is typically employed between a pair of hosts to provide end-to-end security services. In tunnel mode, ESP is applied to... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.2.2 Transport Mode Security Associations | Figure 4.1 depicts the deployment of ENS in a configuration where all IPsec SAs use transport mode. As a result, one set of end-to-end SAs are established between Protected Endpoint 1 and Protected Endpoint 2. The SAs are established under the longer-lived Diffie-Hellman public/private key pair, and this enables the mi... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.2.3 Tunnel Mode Security Associations | Figure 4.2 depicts the deployment of ENS with two tunnel endpoints (enterprise security gateways) protecting communications between two subnets using IKEv2 in tunnel mode. In this deployment environment, all IPsec SAs use tunnel mode. As in the case of Transport Mode, the middlebox receives a passive copy of the packet... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3 Enterprise Network Security | |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.1 IKEv2 Diffie-Hellman Key Exchange (informative) | IKEv2 [1] is a component of the IPsec family of protocols that performs mutual authentication and establishes Security Associations (SAs). IKEv2 establishes an IKE SA that includes shared secret information that can be used to efficiently establish SAs for the Encapsulating Security Payload (ESP) [i.2]. All IKEv2 commu... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.2 Diffie-Hellman key exchange with visibility | The ENS profile shall use exactly the same messages and procedures as defined in IETF RFC 7296 [1] to establish the initial IKE SA, to rekey the IKE SA, to establish ESP SAs, and to rekey ESP SAs. However, the party located in the enterprise network or data centre (whether initiator or responder), shall do all of the f... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.3 Visibility information | The ENS profile shall support authentication based on a certificate, as defined in Recommendation ITU-T X.509 [3]. The certificate shall include an extension that contains visibility information to indicate that the ENS profile is being used, unless such notice is provided by some other means as described in Annex A. 1... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4 Longer-lived Diffie-Hellman public/private key pair management | |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4.1 General | The present document does not mandate how the longer-lived Diffie-Hellman public/private key pairs defined in clause 4.3.2 are shared between IPsec peers, middleboxes, and other key consumers. However, an ENS implementation may use the mechanisms specified in clauses 4.3.4.2 to 4.3.4.3.4. The security of the ENS IPsec ... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4.2 Individually managed keys | This clause describes one of the simplest means of management. When the individually managed keys mechanism is used, the longer-lived Diffie-Hellman public/private key pair shall be manually or automatically installed in both the IPsec peer and permitted middleboxes. |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4.3 Centrally managed keys | 4.3.4.3.1 Introduction Figure 4.7 shows the architecture for using a central key manager to deploy the Enterprise Network Security profile longer-lived Diffie-Hellman keys to a key consumer, which include the IPsec peer and passive decryption middleboxes. When this centrally managed keys mechanism is used, the key mana... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4.3.2 Asymmetric key package | When Enterprise Network Security profile longer-lived Diffie-Hellman public/private key pairs are sent from the key manager to a key consumer using this centrally managed keys mechanism, they shall be packaged using the Asymmetric Key Package defined in IETF RFC 5958 [4]. Each Asymmetric Key Package shall contain one o... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4.3.3 Protecting the key package | When the centrally managed keys mechanism described in clause 4.3.4.3 is used, Enterprise Network Security Asymmetric Key Packages shall be transferred between the key manager and key consumer using HTTP Over TLS [9], commonly called HTTPS. In addition, the Cryptographic Message Syntax (CMS) defined in IETF RFC 5652 [i... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 4.3.4.3.4 Transferring keys | 4.3.4.3.4.1 Protocol overview The HTTP messages containing key packages shall comprise an HTTP header followed by the Asymmetric Key Package, encoded using Distinguished Encoding Rules (DER). The HTTP Content-Type header shall be set to application/pkcs8 as defined in IETF RFC 5958 [4] for plaintext packages and set to... |
6aaaf5f2a85e64c6204a36e4ec6eedd3 | 103 523-5 | 5 Security | The Enterprise Network Security profile does not provide all the security guarantees provided by IKEv2 [1] and ESP [i.2]. The ENS profile does not provide the same forward secrecy for IPsec Security Associations (SAs). Knowledge of a given longer-lived Diffie-Hellman private key can be used to decrypt all of the SAs wi... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 1 Scope | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, whi... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 2 References | |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 3 Definition of terms, symbols and abbreviations | |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 3.1 Terms | Void. |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 3.2 Symbols | Void. ETSI ETSI TS 103 544-5 V1.3.1 (2019-10) 6 |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface CCC Car Connectivity Consortium CDB Common Data Bus DAP Device Attestation Protocol IP Internet Protocol TCP Transmission Control Protocol UPnP Universal Plug-and-Play URL Universal Resource Locator VNC Vi... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4 Common Data Bus Architecture | |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.1 General Architecture | The Common Data Bus (CDB) is a simple, low-bandwidth shared bus, which allows exchanging data between two CDB endpoints, residing in the MirrorLink Server and Client. The Common Data Bus is fully symmetrical, i.e. services can be provided on both endpoints independently from each other. A CDB endpoint can host a CDB Si... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.2 Bindings | |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.2.1 TCP Binding | |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.2.1.1 Launching the Common Data Bus | The MirrorLink Server, providing Common Data Bus functionality, shall include the Common Data Bus into its application listing as specified in [1]. The MirrorLink Client shall identify the Common Data Bus from the application listing as specified in [1]. ETSI ETSI TS 103 544-5 V1.3.1 (2019-10) 7 The Common Data Bus sha... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.2.1.2 Intentionally Terminating the Common Data Bus | The MirrorLink Client and Server can terminate the Server's Common Data Bus endpoint anytime, using the CDB ByeBye message and the UPnP TmApplicationServer:1 services, as defined in [1]. The CDB endpoint in the MirrorLink Client shall use the following sequence to terminate the CDB operation: 1) Client CDB endpoint sha... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.2.1.3 Unintentionally Terminating the CDB Session | Unintentional termination of the CDB session may happen any time in case of error conditions. In this case the respective CDB Server or Client endpoint will disconnect the TCP connection. The respective counterpart should disconnect as well. If the MirrorLink Client decides to re-establish the CDB session, it shall fol... |
ac2dfb52e0e09c68fcf1de18a28eae22 | 103 544-5 | 4.2.2 Other Bindings | Besides TCP/IP, it will be also possible to run MirrorLink Common Data Bus on top of other protocol like Bluetooth RFCOMM, but how to discover and establish connection for such configuration is outside the scope of the present document. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.