Vorlage 3a

Technical requirements for the handover interfaces for the execution of telecommunications surveillance

4.2.3.9.8 Ad hoc HI-1 interface XML of an UpdateResponse payload (real-time simple LI deactivation)

ETSI TS 103 120 V1.2.1 Clause 6.4

Update response LITask Element or attribute Description Example UPDATEResponse

Identifier Object Identifier UUID d8c14821-a4d5-4481-9076-

according to IETF RFC 4122 7e3b649c9f66

canonical form

HI-1 Object

ObjectIdentifier UUID according to d8c14821-a4d5-4481-9076-

IETF RFC 4122 canonical 7e3b649c9f66

form

LITask

Reference LIID (see ETSI TS 103 280 2016092187654321

V1.2.1)

Table 4-24: Ad hoc HI-1 interface XML of a simple UpdateResponse payload (Sent by PTSS)

4.2.3.10 Applicable XML schema version for real-time interception orders on the ad hoc HI1 interface

The XML schema versions are identical to the ones stated in section 4.2.2.9.

4.2.4 HI-A XML over HTTP administrative interface for ordering retained data (HI-A ETSI TS 102 657 V1.17.1)

Based on ETSI TS 102 657 V1.17.1 clause 4.5, HI-A can use the encoding and delivery format XML over HTTP. The requirements and options for this handover interface are detailed in the section 7.5.

Retained data orders encompass the historical data (aka retroactive interception) (see section 7) and the information requests (see section 8).

4.2.4.1 Transport security

Implementations shall support HTTPS as defined in IETF RFC 2818, including the support for mutual authentication through bidirectional certificate usage.

The exchange of the certificates and security requirements (such as key management, key length and the choice of cryptographic algorithm) is an implementation issue and shall be agreed bilaterally between the PTSS and the CSP.

4.2.4.2 Message flow for XML over HTTP order processing for retained data