Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
-- ============================
-- Description of the Email PDU
-- ============================
EmailPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) email(2) version18(18)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
-- from ETSI TS 102 232-1 [3]
IPAddress
FROM LI-PS-PDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version26(26)}
-- from ETSI TS 102 232-5 [38]
IPMMCC
FROM IPMultimediaPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version8(8)};
-- ============================
-- Object Identifier Definition
-- ============================
emailPDUObjId RELATIVE-OID ::= {li-ps(5) email(2) version18(18)}
emailIRIObjId RELATIVE-OID ::= {emailPDUObjId iRI(1)}
emailCCObjId RELATIVE-OID ::= {emailPDUObjId cC(2)}
messagingIRIObjId RELATIVE-OID ::= {emailPDUObjId messagingIRI(3)}
messagingCCObjId RELATIVE-OID ::= {emailPDUObjId messagingCC(4)}
messagingMMCCObjId RELATIVE-OID ::= {emailPDUObjId messagingMMCC(5)}
-- definitions are relative to
-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2)}
-- =============================
-- Email Communications Contents
-- =============================
EmailCC ::= SEQUENCE
-- EmailCC is the PDU sent for each "piece" of E-mail captured content
{
emailCCObjId [0] RELATIVE-OID,
email-Format [1] Email-Format,
content [2] OCTET STRING
-- Network byte order
}
Email-Format ::= ENUMERATED
{
ip-packet(1),
-- When this is the email format, the content will contain the bytes of the IP packet from
-- the IP header through to the end of the IP packet
-- Meets requirement E.2.7
application(2)
-- Only the IP stack Layer 4 payload, (i.e. no IP or TCP headers)
-- Meets requirement E.2.8
}
-- =======================================
-- Intercept-related information for Email
-- =======================================
EmailIRI ::= SEQUENCE
-- EmailIRI is the PDU sent for each "piece" of E-mail IRI
{
emailIRIObjId [0] RELATIVE-OID,
eventType [1] E-mail-Event,
client-Address [2] IPAddress OPTIONAL,
-- Provided if available
server-Address [3] IPAddress OPTIONAL,
-- Provided if available
client-Port [4] INTEGER OPTIONAL,
-- Provided if available
server-Port [5] INTEGER OPTIONAL,
-- Provided if available
server-Octets-Sent [6] INTEGER,
client-Octets-Sent [7] INTEGER,
protocol-ID [8] E-mail-Protocol,
e-mail-Sender [9] UTF8String (SIZE (0..255)) OPTIONAL,
-- Not available in some cases; if a value is available, it shall be provided.
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
e-mail-Recipients [10] E-mail-Address-List OPTIONAL,
-- Not available in some cases; if a value is available, it shall be provided
-- Note that as of version 3.13.1, this field may contain RFC 6530-compliant addresses.
status [11] E-mail-Status,
total-Recipient-Count [12] INTEGER (0..4294967295) OPTIONAL,
message-ID [13] OCTET STRING OPTIONAL,
-- Network byte order
nationalParameter [14] OCTET STRING OPTIONAL,
-- Completely defined on a national basis, including byte ordering
...,
national-EM-ASN1parameters [15] National-EM-ASN1parameters OPTIONAL,
-- Completely defined on a national basis
aAAInformation [16] AAAInformation OPTIONAL,
e-mail-Sender-Validity [17] ENUMERATED
{
Loading
Loading full blame…