scope:

The basic purpose of a Registered E-Mail service is to provide users, in addition to the usual services supplied by the ordinary e-mail service providers, with a set of evidence suitable to uphold assertions of acceptance (i.e. of "shipment"), of delivery/non delivery, of receipt, etc. of e-mails sent/delivered through such service.

The present document provides:

a) Rules for building a REM-MD Envelope and, consequently, a REM Dispatch or a REM-MD Message.

b) Syntax and semantics of REM-MD Evidence to be produced by a REM Management Domain.

c) Rules on the signature to be used within REM-MD Envelopes.

REM-MD Evidence formats are deemed to comply with legal, regulatory or contractual requirements to provide legal validity and enforceability under domestic or international law.

The structure of the present document is as follows:

• Clause 2 contains the list of normative and informative references.

• Clause 3 includes definitions of the relevant concepts to the present document and abbreviations.

• Clause 4 contains the generic REM-MD Envelope structure.

• Clause 5 contains the definition of REM-MD Evidence produced by REM-MDs, in terms of content and semantics. Specific syntaxes are addressed by annexes.

• Clause 6 deals with digital signatures to be applied by REM-MD for building REM-MD Envelopes.

• Clause 7 deals with the implementation of aTSL based mechanism for allowing mutual trust of REM-MDs.

• Annex A provides ASN.1 syntax for REM-MD Evidence.

• Annex B provides xml syntax for REM-MD Evidence.

• Annex C provides PDF syntax for REM-MD Evidence.

• Annex D specifies identifiers and codes for reporting events reasons in REM-MD Evidence.

• Annex E provides the ASN.1 definition for REM-MD Evidence encoded in ASN.1.

• Annex F provides the XML schema for REM-MD Evidence encoded in XML.