Avamprogetto 2a
Consultazione 2017/22: Progetto di legislazione esecutiva relativa alla revisione totale della legge federale sulla sorveglianza della corrispondenza postale e del traffico delle telecomunicazioni · 194 pagine
Fedlex · Progetto · Pagina 102Fedlex · Progetto
Technical requirements for the handover interfaces for the execution of telecommunications surveillance
6.5.4 ETSI TS 102 232-2 V3.9.1 Service-specific details for messaging services
Clause Available options for Swiss Additional requirements or
ETSI TS applications specifications
102 232-2
V3.9.1
6.2.3 Email send IRI
IRI data according to table 1 for the
event “Email send” must always be
transferred.
6.3.3 Email receive IRI
IRI data according to table 2 for the
event “Email receive” must always be
transferred.
6.4.3 Email download IRI
IRI data according to table 3 for the
event ”Email download” must always
be transferred.
7.10 AAAInformation
This information is critical as email AAAInformation is accepted in either the addresses themselves are not e-mail-login event, or in the transfer authenticated and it is easy for a user event (e-mail-send / receive / download to spoof an email “from” address so it / partial-download / upload), or in both. is important to be able to see which However the AAAInformation must not mailbox is being used to send emails. be missing from both the login and the transfer event.
Annex A SMTP
The quick reference table in section Annex B POP3 6.5.4.2 provides a detailed
representation of the ASN.1 parameters Annex C IMAP to be delivered for the different protocols
and events.
Annex D Messaging ASN.1 Table 6-13: ETSI TS 102 232-2 V3.9.1 Service-specific details for messaging services
The supported ASN.1 Object identifiers and versions are stated in section 6.6
6.5.4.1 Splitting of large email
ETSI TS 102 232-2 V3.9.1 does not specify a method for dealing with large volumes of content emails. PTSS set the following requirements: Large emails over 2MB must be split into multiple PDUs with a payload content of no more than 2MB each. The multiple PDUs will all be identical apart from the payload content itself and the sequenceNumber which must be incremented by one for each PDU delivered. Fragmented emails must be delivered in the correct order with the correct sequence numbers so that they can be re-assembled at the LEMF.