My ETSI TS 103 120 Notes - Revision history

Paul: /* 6.4.3 Action Responses */

2022-11-17T19:36:52Z

6.4.3 Action Responses

@@ Line 113: / Line 113: @@
 | DELIVER RESPONSE || Successful receipt of an HI-1 Object. || See clause 6.4.10
 |}
 == 8.3 LDTaskObject ==

Paul: /* 6.2.2. Structure */

2022-11-17T19:28:16Z

6.2.2. Structure

@@ Line 61: / Line 61: @@
 |-
 | Version || Version (see clause 6.2.3 for details) || Version of the present document and relevant national profile used for interpreting the message.
 |}

Paul: /* Message Structure */

2022-11-17T18:12:04Z

Message Structure

@@ Line 13: / Line 13: @@
 See specification for full details.
-== Message Structure ==
+== 6. Message Structure ==
 See 6.1 overview for details.
@@ Line 42: / Line 42: @@
 In the response, there should be an Action Response for each Action Request (in the absence of errors)
 == 8.3 LDTaskObject ==

Paul: /* Message Structure */

2022-11-17T18:04:56Z

Message Structure

← Older revision		Revision as of 13:04, 17 November 2022
Line 16:		Line 16:

	See 6.1 overview for details.		See 6.1 overview for details.

			Each message consists of two parts:
			* Message Header
			* Message Payload (Request \| Response)

			Request format:

	Message > Header > Request Payload > Action Request (one to many) > (GET \| CREATE \| UPDATE \| LIST) > (Object Identifier, Object)		Message > Header > Request Payload > Action Request (one to many) > (GET \| CREATE \| UPDATE \| LIST) > (Object Identifier, Object)

			Response format:

			Message > Header > Response Payload > Action Response (one to many) > (GET \| CREATE \| UPDATE \| LIST) Response > (Object Identifier, Object)

	Top level container for all HI-1 message		Top level container for all HI-1 message

Paul: /* 103 120 Scope */

2022-11-17T18:02:51Z

103 120 Scope

← Older revision		Revision as of 13:02, 17 November 2022
Line 12:		Line 12:

	See specification for full details.		See specification for full details.

			== Message Structure ==

			See 6.1 overview for details.

			Message > Header > Request Payload > Action Request (one to many) > (GET \| CREATE \| UPDATE \| LIST) > (Object Identifier, Object)

			Top level container for all HI-1 message

			Header contains routing and timestamp information - see clause6.2

			Payloads contain multiple Actions (either Requests or Responses) - see clause 6.3

			Each Action has a Verb such as GET or CREATE – either a request or a response, depending on the message. See clauses 6.4.5 through 6.4.8.

			This generally contains an Object Identifier, which identifies the Object being acted on (see clause 7 and clause 8). Depending on the verb. It may also contain an Object.

			There may be many Action Requests in a Request message. Each will generally act on a separate message.

			In the response, there should be an Action Response for each Action Request (in the absence of errors)

	== 8.3 LDTaskObject ==		== 8.3 LDTaskObject ==

Paul: /* 8.3.3 Status */

2022-11-16T18:22:55Z

8.3.3 Status

Show changes

Paul: /* 8.3.1 Overview */

2022-11-16T16:52:10Z

8.3.1 Overview

@@ Line 22: / Line 22: @@
 {| class="wikitable sortable"
-|+ Caption text
+|+ LDTaskObject
 |-
 ! Field !! Format !! Description !! Reference
@@ Line 48: / Line 48: @@
 | NationalLDTaskingParameters || See annex G. ||See annex G. || Annex G
 |}
 <center>[[My 33.128 Notes|To My 33.128 Notes]]</center>

Paul: /* 103 120 Scope */

2022-11-16T16:32:59Z

103 120 Scope

← Older revision		Revision as of 11:32, 16 November 2022
Line 12:		Line 12:

	See specification for full details.		See specification for full details.

			== 8.3 LDTaskObject ==

			=== 8.3.1 Overview ===

			An Lawful Disclosure Task Object (LDTaskObject) represents the state of an LD Task - that is, the act of disclosing information. This corresponds to the WarrantTargetID and WarrantTechSpec elements defined in ETSI TR 103 690. In general, multiple tasks may be authorised by a single warrant.

			The LDTaskObject consists of the following fields.

			{\| class="wikitable sortable"
			\|+ Caption text
			\|-
			! Field !! Format !! Description !! Reference
			\|-
			\| Reference\|\|LDID (see ETSI TS 103 280) \|\|LDID assigned to the product of task. \|\| Clause 8.3.2
			\|-
			\| Status\|\| LDTaskStatus Dictionary Entry.\|\| The current status of the task as determined by the Receiver.\|\| Clause 8.3.3
			\|-
			\| StatusReason \|\| ActionUnsuccessful structure (see clause 6.4.9).\|\| Optional information for the Receiver to indicate why the Object is in a certain state (such as Invalid or Rejected). Usage for national agreement.\|\| Clause 6.4.9
			\|-
			\| DesiredStatus\|\| LDTaskDesiredStatus Dictionary Entry.\|\| The current status of the task as specified by the Sender.\|\| Clause 8.3.4
			\|-
			\|RequestDetails \|\|LDRequestDetails (see clause 8.3.5). \|\| Details regarding the content of the disclosure request, such as identifiers and dates.\|\| Clause 8.3.5
			\|-
			\| DeliveryDetails \|\| List of LDDeliveryDestination structures (see clause 8.3.6).\|\|Destination(s) for the disclosure product. \|\| Clause 8.3.6
			\|-
			\| ApprovalDetails\|\| ApprovalDetails (see annex E).\|\| Details regarding the approval for this Task, including dates and signatures where appropriate.\|\| Clause 8.2.9
			\|-
			\|CSPID \|\|EndpointID (see clause 6.2.4). \|\| Describes the CSP required to implement the Task.\|\| Clause 8.2.10
			\|-
			\| HandlingProfile\|\|LDHandlingProfile (see clause 8.2.11). \|\| A dictionary entry which gives the name of a handling profile that represents a set of configuration information associated with this task.\|\|Clause 8.2.11
			\|-
			\|Flags \|\|LDTaskFlags (see clause 8.3.7). \|\|A set of flags associated with the Task Object. \|\| Clause 8.3.7
			\|-
			\| NationalLDTaskingParameters \|\| See annex G. \|\|See annex G. \|\| Annex G
			\|}


	<center>[[My 33.128 Notes\|To My 33.128 Notes]]</center>		<center>[[My 33.128 Notes\|To My 33.128 Notes]]</center>

Paul at 21:08, 4 October 2022

2022-10-04T21:08:25Z

← Older revision		Revision as of 16:08, 4 October 2022
Line 1:		Line 1:
			Find and download [https://www.etsi.org/ ETSI] standards [https://www.etsi.org/standards here]

	My notes on ETSI TS 103 120 document titled '''Lawful Interception (LI); Interface for warrant information'''.		My notes on ETSI TS 103 120 document titled '''Lawful Interception (LI); Interface for warrant information'''.

	~~Find~~ and ~~download [https~~:~~//www~~.~~etsi~~.~~org/ ETSI] standards [https://www~~.~~etsi~~.~~org/standards here]~~		== 103 120 Scope ==

			ETSI TS 103 120 document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception. Typically this interface
			would be used between: on one side, a Communications Service Provider; and, on the other side, a Government or Law Enforcement Agency who is entitled to request a lawful action.

			The ETSI reference model for LI (ETSI TS 102 232-1) defines three interfaces between law enforcement and CSPs, called HI-1, HI-2 and HI-3. The protocol defined in 103 120 document is designed to provide a large part of the functionality for HI-1. It is not designed to be used for HI-2 (delivery of intercept related information) or HI-3 (delivery of communications content). The protocol designed in 103 120 document may also be used for interfaces which require structured exchange of information relating to the establishment and management of Lawful Interception. The general view is that the HI-1 concept can also be used for other legal actions than LI. For that reason the present
			document could, besides LI, also be applied for retained data requests, seized data requests, data preservation orders and other similar legal requests

			See specification for full details.


	<center>[[My 33.128 Notes\|To My 33.128 Notes]]</center>		<center>[[My 33.128 Notes\|To My 33.128 Notes]]</center>

Paul: initial page creation

2022-10-04T15:53:41Z

initial page creation

New page

My notes on ETSI TS 103 120 document titled '''Lawful Interception (LI); Interface for warrant information'''.

Find and download [https://www.etsi.org/ ETSI] standards [https://www.etsi.org/standards here]

<center>[[My 33.128 Notes|To My 33.128 Notes]]</center>