hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.4.2 BothDirections | The presence of the BothDirections field indicates that frames matching in both directions match the criteria. If the BothDirections field is present, the frame is considered a match if either: • all of the SourceMACAddress, DestinationMACAddress or VLANCriteria that are present match their respective frame headers per... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.5 RCSPolicyCriteria | RCSPolicyCriteria defines a criterion based on the communication service identifier of an Rich Communication Suite (RCS) service flow. Table 7.24d: RCSPolicyCriteria Field Format Description Reference M/C/O CommunicationServiceID ShortString Match service flows of a specific RCS communication service identified by Comm... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.3 Action | Action to be applied to the policy. Given as an Action DictionaryEntry. The TrafficAction Dictionary is defined below (see annex F for more details on Dictionaries). ETSI ETSI TS 103 120 V1.22.1 (2026-03) 47 Table 7.25: TrafficAction Dictionary Dictionary Owner Dictionary Name ETSI TrafficAction. Defined DictionaryEntr... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.4 Parameters | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.4.1 Overview | Parameters that are applicable to an action. Given as an action-specific choice of parameters. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.4.2 Truncate Action Parameters | TruncateActionParameters defines the parameters that are applicable to the Truncate action. Table 7.26: TruncateActionParameters Field Format Description Reference M/C/O NumberOfOctets Non-negative Integer Request to deliver only the specified number of the first octets of all the intercepted IP or ethernet datagrams p... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.7 IRIPolicyObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.7.1 Overview | The IRIPolicyObject represents a policy from an LEA which is to be applied to the intercepted materials as part of an LITaskObject. An LEA may associate multiple IRIPolicyObjects to an LITaskObject, using the LITaskObject's ListOfIRIPolicyObjects field (see clause 8.2.13.2). A change to an IRI policy should be reflecte... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.7.2 Order | IRIRuleReferences are considered in ascending order according to the Order field. If all of the criteria listed in the IRIRuleObject referenced by the ObjectIdentifier field are matched (see clause 7.8.2), then the action described in the referenced IRIRuleObject's Action field is taken (see clause 7.8.3) and no furthe... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8 IRIRuleObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.1 Overview | 7. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.1 Overview | Table 7.29: IRIRuleObject Field Format Description Reference M/C/O Criteria List of IRICriteria List of rule criteria all of which shall match for this rule to apply. Clause 7.8.2 M Action IRIAction Dictionary Entry The action to take with records matching criteria. Clause 7.8.3 M Parameters ActionParameters Parameters... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2 IRICriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.1 Overview | 7. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.1 Overview | The IRICriteria structure defines whether an IRIRule applies to a particular set of reportable events or not. If multiple IRICriteria are given in the same IRIRuleObject, they are logically ANDed together - that is, the intercepted event shall match all of them in order for the IRIRule to be considered matching. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.2 NFTypeCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.2.1 Overview | The NFTypeCriteria is one type of IRICriteria. The NFTypeCriteria structure consists of a list of NFs from which an event is intercepted. If the record comes from a POI within any of the NFs listed, the IRICriteria shall be considered matching. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 49 Table 7.30: NFTypeCriteria Field ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.2.2 NFType Dictionary | Contains a list of NF Types where the reported event takes place. Table 7.31 includes ETSI defined NF Types (see annex F for more details on Dictionaries). Table 7.31: NFType Dictionary Dictionary Owner Dictionary Name ETSI NFType Defined DictionaryEntries Value Meaning The present document does not define any dictiona... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.3 IRIEventCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.3.1 Overview | IRIEventCriteria defines a criteria based on a list of IRIEvents names. Table 7.32: IRIEventCriteria Field Format Description Reference M/C/O IRIEvents IRIEvents Dictionary Entry Match records with the listed IRIEvents. Shall be present if certain IRI Event names should be used as a criteria. Clause 7.8.2.3.2 C |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.3.2 IRIEvents Event Dictionary | Table 7.33 includes IRIEvents defined by the present document (see annex F for more details on Dictionaries). Table 7.33: IRIEvents Dictionary Dictionary Owner Dictionary Name ETSI IRIEvents Defined DictionaryEntries Value Meaning All All IRI Events. Additional service specific dictionaries for the IRIEvents event crit... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.4 HandoverFormatCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.4.1 Overview | HandoverFormatCriteria defines a criteria based on a list of Handover formats. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 50 Table 7.34: HandoverFormatCriteria Field Format Description Reference M/C/O HandoverFormats HandoverFormat Dictionary Entry Specifies the handover format of the IRI records to be matched. Shall be pr... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.8.2.4.2 HandoverFormat Dictionary | The present document defines the HandoverFormat Dictionary in clause 8.2.8.4 table 8.13 (see annex F for more details on Dictionaries). 7.8.3 Action Action to be applied to the policy. Given as an Action DictionaryEntry. The IRIAction Dictionary is defined below (see annex F for more details on Dictionaries). Table 7.3... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.1 Overview | Parameters that are applicable to an action. Given as an action-specific choice of parameters. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.9 EncryptionObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.9.1 Overview | 7. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.1 Overview | The EncryptionObject represents information about the encryption of the data for data disclosure request. Depending on the context where it is used, it may either: • Convey an LEA request to CSP to encrypt information. In this case, an LEA may reference an Encryption Object with an LDTaskObject. • Allow the CSP to prov... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.9.2 EncryptionScheme | The encryption scheme associated with this request, given as an EncryptionScheme DictionaryEntry. The EncryptionScheme Dictionary is defined below (see annex F for more details on Dictionaries). The DictionaryEntries may be specified in national profiles. An encryption scheme defines the encryption algorithm used/to us... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.9.3 X509EncryptionDetails | The X509EncryptionDetails type consists of the fields shown in table 7.38. Table 7.38: X509EncryptionDetails Field Format Description Reference M/C/O X509Certificates List of X509Certificate List of X509Certificate objects. M Table 7.39: X509Certificate Field Format Description Reference M/C/O X509CertificateDER Base64... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8 Task Objects | 8.1 Overview This clause defines a set of HI1Object definitions that can be used to describe "Tasks". These Objects are intended to describe the technical details of a request or instruction, and will typically by associated with an AuthorisationObject which represents the legal basis for the technical request. The pre... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2 LITaskObject | 8.2.1 Overview An LITaskObject represents the state of an LITask. This corresponds to the WarrantTargetID and WarrantTechSpec elements defined in ETSI TR 103 690 [i.1]. In general, multiple tasks may be authorised by a single warrant. The LITaskObject consists of the following fields. Further details are given in claus... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.2 Reference | The Reference field gives a reference identifier for the Task, for correlation with other processes. This shall be set to the LIID that will be assigned to the product of the task. Format will be as per ETSI TS 103 280 [7], clause 6.1. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.3 Status | The Status field gives the status of the LITaskObject as determined by the Receiver. A Sender shall not attempt to set the Status as part of a CREATE or UPDATE Request, and a Receiver shall return an Action Unsuccessful Information response if the Sender attempts to do so. The Status field provides a key mechanism for ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.4 DesiredStatus | The DesiredStatus field gives the status of the LITaskObject as determined by the Sender. Given as a TaskDesiredStatus Dictionary Entry. The TaskDesiredStatus Dictionary is defined in table 8.3 (see annex F for more details on Dictionaries). ETSI ETSI TS 103 120 V1.22.1 (2026-03) 54 Table 8.3: TaskDesiredStatus Diction... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.5 TimeSpan | The period for which the interception is active. May not be identical to the AuthorisationTimespan (although it is likely that national laws will require it to be within the AuthorisationTimespan). Given as a TaskTimeSpan structure as defined in table 8.4. Table 8.4: TaskTimeSpan Field Format Description StartTime Qual... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.6 TargetIdentifier | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.6.1 Overview | The TargetIdentifier specifies the communications address or technical identifier used to identify the target of the Task in conjunction with TargetIdentifierSubtype. It consists of the following fields. Table 8.5: TargetIdentifier Field Format Description TargetIdentifierValues List of TargetIdentifierValue structures... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.6.2 TargetIdentifierValues Field | The TargetIdentifierValues field contains a list of TargetIdentifierValue structures, which are combined (with ordering and Boolean ANDed together) to identify the targeted information (e.g. the target's traffic). Each TargetIdentifierValue structure contains the following fields. ETSI ETSI TS 103 120 V1.22.1 (2026-03)... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.6.3 FormatType | A TargetIdentifier FormatType uniquely identifies a particular TargetIdentifier Format. It can be used to retrieve the correct Target Identifier Format definition for a given Target Identifier. It consists of the following fields. Table 8.7: TargetIdentifier FormatType Field Format Description FormatOwner ShortString (... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.6.4 Task Service Type | Type of service or services that are subject to the LITask using the specified TargetIdentifiers. Given as a list of TaskServiceType DictionaryEntries. The usage and meaning of the Service Type is likely to be closely coupled to national legislation, as will the permissible combinations of TargetIdentifier Types and Se... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.7 DeliveryType | Delivery type of the Task. Given as a TaskDeliveryType DictionaryEntry. The TaskDeliveryType Dictionary is defined below (see annex F for more details on Dictionaries). Table 8.10: TaskDeliveryType Dictionary Dictionary Owner Dictionary Name ETSI TaskDeliveryType. Defined DictionaryEntries Value Meaning IRIOnly Only IR... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.8 TaskDeliveryDetails | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.8.1 Overview | The TaskDeliveryDetails field indicates where the information should be delivered. The TaskDeliveryDetails field consists of a list of DeliveryDestination structures. Each entry in the list represents a desired destination for traffic related to the Task. Limits on the type, number or combinations of DeliveryDestinatio... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.8.2 DeliveryDestination | The DeliveryDestination structure contains the following fields. Table 8.11: DeliveryDestination Field Format Description DeliveryAddress DeliveryAddress (see clause 8.2.8.3) The address to which the traffic for this Task should be delivered. EncryptionDetails NationalEncryptionDetails Details regarding the encryption ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.8.3 DeliveryAddress | The DeliveryAddress is specified in one of the following formats. Table 8.12: DeliveryAddress Field Format Description IPv4Address IPv4Address (see ETSI TS 103 280 [7], clause 6.11) IPv4 destination. IPv6Address IPv6Address (see ETSI TS 103 280 [7], clause 6.12) IPv6 destination. IPAddressPort IPAddressPort (see ETSI T... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.8.4 HandoverFormat | The HandoverFormat dictionary is defined in table 8.13 (see annex F for more details on Dictionaries). Table 8.13: HandoverFormat Dictionary Dictionary Owner Dictionary Name ETSI HandoverFormat. Defined DictionaryEntries Value Meaning TS102232-2 Handed over in ETSI TS 102 232-2 [15] format. TS102232-3 Handed over in ET... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.9 ApprovalDetails | The ApprovalDetails field gives details regarding the approval for the Task. The information is specified in using the ApprovalDetails structure given in annex E. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.10 CSPID | The CSPID field gives a globally unique CSP Identifier that identifies the CSP required to implement the Task. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 58 |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.11 HandlingProfile | The HandlingProfile field gives a dictionary entry which gives the name of a handling profile that represents a set of configuration information associated with this task. The use of this field is for national agreement. If used, the dictionary of permissible values shall be defined by the relevant national profile. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.12 Flags | The Flags field allows a set of multiple flags to be associated with the LITaskObject. Each flag is given as a TaskFlag Dictionary Entry. If a flag is present in the Flags field, then the meaning given as part of that flag's definition shall be taken to apply. The TaskFlag Dictionary is defined in table 8.14 (see annex... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.13 ListOfTrafficPolicyReferences | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.13.1 Overview | The ListOfTrafficPolicyReferences field gives an ordered list of TrafficPolicyReferences that shall be applied to the information produced by the Task (see clause 7.5). If no ListOfTrafficPolicyReferences is associated with the LITaskObject, then the traffic shall be delivered as-is. Each TrafficPolicyReference consist... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.13.2 Order | TrafficPolicyReferences are considered in ascending order according to the Order field. Once a rule in the TrafficPolicyObject referenced by the ObjectIdentifier field is matched and the action in the referenced TrafficPolicyObject is taken (see clause 7.6.3), then no further TrafficPolicyReferences are evaluated. If n... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.14 ListOfIRIPolicyReferences | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.14.1 Overview | The ListOfIRIPolicyReferences fields gives an ordered list of IRIPolicyReferences that shall be applied to the intercepted traffic (see clause 7.7). The IRIPolicyReference fields contain elements defined in table 8.14b. Table 8.14b: IRIPolicyReference Field Format Description Reference M/C/O Order Positive Integer Dete... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.2.14.2 Order | IRIPolicyReferences are considered in ascending order according to the Order field. Once a rule in the IRIPolicyObject referenced by the ObjectIdentifier field is matched and the action in the referenced IRIPolicyObject is taken (see clause 7.8.3), then no further IRIPolicyReferences are evaluated. If no rules are matc... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3 LDTaskObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.1 Overview | An 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 [i.1]. In general, multiple tasks may be authorised by a single warrant. The LDTaskObject consists of the following fields. Tab... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.3 Status | Reason 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 Se... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.2 Reference | The Reference field gives a reference identifier for the Task, for correlation with other processes. For LD, this shall be set to the LDID that will be assigned to the product of the disclosure. Format will be as per ETSI TS 103 280 [7], clause 6.48. 8.3.3 Status The Status field gives the status of the LDTaskObject as... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.4 DesiredStatus | The DesiredStatus field gives the status of the LDTaskObject as determined by the Sender. Given as a LDTaskDesiredStatus Dictionary Entry. The LDTaskDesiredStatus Dictionary is defined in table 8.17 (see annex F for more details on Dictionaries). ETSI ETSI TS 103 120 V1.22.1 (2026-03) 61 Table 8.17: LDTaskDesiredStatus... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5 RequestDetails | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5.1 Overview | The RequestDetails structure specifies the content of the disclosure request. It consists of the following fields. Table 8.18: LDRequestDetails Field Format Description Type RequestType (see clause 8.3.5.2) Specifies the products to be disclosed. StartTime QualifiedDateTime (see ETSI TS 103 280 [7], clause 6.4) If a da... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5.2 RequestType | Type of disclosure or disclosures to produce using the specified RequestDetails. Given as a list of RequestType DictionaryEntries. The usage and meaning of the Request Type is likely to be closely coupled to national legislation, as will the permissible combinations of Request Values and Request Types. It is therefore ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5.3 RequestValues | The RequestValues field contains a list of RequestValue structures, which are combined (with ordering and Boolean ANDed together) to identify the requested disclosure. Each RequestValue structure contains the following fields. Table 8.20: RequestValue Field Format Description FormatType As defined below Specifies a Req... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5.4 FormatType | A RequestValue FormatType uniquely identifies a particular Request Value Format. It can be used to retrieve the correct RequestValue Format definition for a RequestValues structure. It consists of the following fields. Table 8.21: RequestValue FormatType Field Format Description FormatOwner ShortString (see ETSI TS 103... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5.5 Subtype | Subtype of CSP product or products to disclose information about. This field is for use in cases where this cannot be sufficiently well-determined from the Type field (see clause 8.3.5.2). This field is optional. Given as a list of LDRequestSubtype DictionaryEntries. More than one entry may be chosen. The usage and mea... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.5.6 TargetIdentifierSubtype | The kind of CSP entity to disclose information about. For use in cases where multiple kinds of CSP entities exist that possibly share a RequestValue, and the Requestor knows what kind of CSP entity they are targeting for the disclosure request. This additional granularity is used to accurately identify specific targets... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.6 DeliveryDetails | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.6.1 Overview | The LDTaskDeliveryDetails field indicates where disclosed product should be delivered. The LDTaskDeliveryDetails field consists of a list of LDDeliveryDestination structures. Each entry in the list represents a desired destination for product related to the Task. Limits on the type, number or combinations of LDDelivery... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.6.2 LDDeliveryDestination | The LDDeliveryDestination structure contains the following fields. Table 8.23a: LDDeliveryDestination Field Format Description DeliveryAddress DeliveryAddress (see clause 8.2.8.3) The address to which the product for this Task should be delivered. EncryptionDetails NationalEncryptionDetails Details regarding the encryp... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.6.3 HandoverFormat | The LDHandoverFormat dictionary is defined in table 8.24 (see annex F for more details on Dictionaries). Table 8.24: LDHandoverFormat Dictionary Dictionary Owner Dictionary Name ETSI LDHandoverFormat. Defined DictionaryEntries Value Meaning TS102657 Handed over in ETSI TS 102 657 [22] format, using HI-B as described in... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.7 Flags | The Flags field allows a set of multiple flags to be associated with the LDTaskObject. Each flag is given as a LDTaskFlag Dictionary Entry. If a flag is present in the Flags field, then the meaning given as part of that flag's definition shall be taken to apply. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 65 The LDTaskFlag ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.8 AlternativePreservationReferences | In situations where an LDTask Object is related to one or more prior preservations request exchanged via a mechanism outside of those described in the present document (i.e. an out-of-band process), this field shall be used to provide references to those prior preservation requests. The field is given as a list of Alte... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.9 Deadlines | The Deadlines field gives details of the procedural or other deadlines associated with the Task. When given, it shall be supplied as a list of LDDeadline structures, as defined in table 8.26a below. Any legal significance of these deadlines is out of scope of the present document. Table 8.26a: LDDeadline Field Format D... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.3.10 ManualInformation | The ManualInformation field provides any additional human-readable information regarding the LDTask. This field shall only be used if required information cannot be contained in any other field. CSPs and LEAs need to be aware that the information carried in this field cannot be guaranteed to be machine-processable and ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4 LPTaskObject | 8.4.1 Overview An LPTaskObject represents the state of an LPTask - that is, the act of preserving information. In general, multiple tasks may be associated with a single Authorisation. The LPTask is intended to be used only for preserving historical data, not for ordering the preservation of data generated in the futur... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.2 Status | Reason 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 LPTaskDesiredStatus Dictionary Entry The current status of the task as specified by the Se... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.3 DesiredStatus | The DesiredStatus field gives the status of the LPTaskObject as determined by the Sender. Given as an LPTaskDesiredStatus Dictionary Entry. The LPTaskDesiredStatus Dictionary is defined in table 8.29 (see annex F for more details on Dictionaries). Table 8.29: LPTaskDesiredStatus Dictionary Dictionary Owner Dictionary N... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.4 RequestDetails | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.4.1 General | The RequestDetails structure specifies the content of the disclosure request. It consists of the following fields. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 68 Table 8.30: LPRequestDetails Field Format Description Type RequestType (see clause 8.3.5.2) Specifies the products to be preserved. StartTime QualifiedDateTime (se... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.4.2 Subtype | Subtype of CSP product or products to preserve information about. This field is for use in cases where this cannot be sufficiently well-determined from the Type field (see clause 8.3.5.2). This field is optional. Given as a list of LPRequestSubtype DictionaryEntries. More than one entry may be chosen. The usage and mea... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.5 DesiredPreservationExpiration | The DesiredPreservationExpiration field indicates the time at which the LEA desires the data retained in response to the preservation request to expire. This field is set by the LEA. When requesting an extension of a preservation, the LEA shall update this field to indicate the new desired expiration time of the retain... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.4.6 PreservationExpiration | The PreservationExpiration field indicates the time at which the data retained in response to the preservation request will expire. This field is set by the CSP. When extending a preservation, the CSP shall update this field to indicate the new expiration time of the retained data. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5 TDTaskObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.1 Overview | A TDTaskObject represents the state of a TDTask - that is, the act of requesting that an account, content or service is taken down. The TDTaskObject consists of the following fields. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 69 Table 8.32: TDTaskObject Field Format Description Reference RequesterReference LongString (see ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.4 Status | Reason 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 TDTaskDesiredStatus Dictionary Entry (see clause 8.5.5, table 8.34) The current status of ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.2 RequesterReference | The Reference field allows the requesting system to provide a reference identifier for the Task, for correlation with other out-of-band processes. If present, the value shall be chosen by the requesting system. Format will be a LongString as defined in ETSI TS 103 280 [7], clause 6.30. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.3 CSPReference | The Reference field allows the CSP to provide a reference identifier for the Task, for correlation with out-of-band processes. If present, the value shall be specified by the CSP. A Sender shall not attempt to set the CSPReference as part of a CREATE or UPDATE Request, and a Receiver shall return an Action Unsuccessful... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.5 DesiredStatus | The DesiredStatus field gives the status of the TDTaskObject as determined by the Sender. Given as a TDTaskDesiredStatus Dictionary Entry. The TDTaskDesiredStatus Dictionary is defined in table 8.34 (see annex F for more details on Dictionaries). Table 8.34: TDTaskDesiredStatus Dictionary Dictionary Owner Dictionary Na... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.6 RequestDetails | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.6.1 Overview | The RequestDetails structure specifies the content of the takedown request. It consists of the following fields. Table 8.35: TakedownRequestDetails Field Format Description Reference RequestValues List of RequestValue structures (see clause 8.5.6.2) Specifies the value(s) used to identify the subject of the takedown re... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.6.2 RequestValues | The RequestValues field contains a list of RequestValue structures, which are combined (with ordering and Boolean ANDed together) to identify the data that is requested to be taken down. Each RequestValue follows the structure given in clause 8.3.5.3. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 71 |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.6.3 RequestValueRefinement | The RequestValueRefinement field contains any free-text information required, in conjunction with the RequestValues field, to fully specify and identify the data that is requested to be taken down. This is used to reduce the scope of the search i.e. it shall not be used to add material beyond that specified in the Requ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.7 Flags | The Flags field allows a set of multiple flags to be associated with the TDTaskObject. Each flag is given as a TDTaskFlag Dictionary Entry. If a flag is present in the Flags field, then the meaning given as part of that flag's definition shall be taken to apply. The TDTaskFlag Dictionary is defined in table 8.36 (see a... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.8 Deadlines | The Deadlines field gives details of the procedural or other deadlines associated with the Task. When given, it shall be supplied as a list of TakedownDeadline structures, as defined in table 8.37 below. Any legal or contractual significance of these deadlines is out of scope of the present document. Table 8.37: Takedo... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.9 AlternativeDisclosureReferences | In situations where some or all of the data subject to takedown is also the subject of a disclosure request exchanged via a mechanism outside of those described in the present document (i.e. an out-of-band process), this field shall be used to provide references to those disclosure requests. The field is given as a lis... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 8.5.10 ManualInformation | The ManualInformation field provides any additional human-readable information regarding the TDTask. This field shall only be used if required information cannot be contained in any other field. CSPs and LEAs need to be aware that the information carried in this field cannot be guaranteed to be machine-processable and ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9 Transport and Encoding | 9.1 Overview This clause describes the transport and encoding mechanisms used in exchanging WI messages. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.