Vorlage 3a

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

delivery may pass through a number of intermediate succeeded

message servers. This field does not indicate the end- failed

to-end delivery status. It indicates the status of the "next retried

hop".

protocol [MsgTransmission] Tables C.3,C.4

Description and requirements ELEMENTS

Message transmission protocol used. smtp

x400

protocol [MsgStoreOperation] Tables C.3,C.4

Description and requirements ELEMENTS

Message store manipulation protocol. pop

imap

webmail

clientID Tables C.3,C.4

Description and requirements Examples

IP address of the source of the message transmission. 203.0.113.28

The IP address can be either IPv4 or IPv6. 2001:db8:85a3::8a2e:370:7334 Preferably in text format using the element

"iPTextAddress".

serverID Tables C.3,C.4

Description and requirements Examples

IP address of the destination of the message 198.51.100.65

transmission. The IP address can be either IPv4 or 2001:db88:5a35:4a1::ab4c:882a IPv6.

Preferably in text format using the element

"iPTextAddress".

messageID Tables C.3,C.4

Description and requirements Examples

Unique identifier for the message - for example IETF [email protected] RFC 5322 message-id header. [email protected]

sourceServerName Table C.3

Description and requirements Example

Name for the server sending the message. mailout12.atlanta.com

destinationServerName Tables C.3

Description and requirements Example

Name for the server receiving the message. omr.mx.biloxi.com

operation Tables C.4