Postal Services - Hybrid Mail - Functional Specification for postal registered electronic mail

This Technical Specification constitutes the functional specification of a secure electronic postal service, referred to as the postal registered electronic mail or PReM service. PReM provides a trusted and certified electronic mail exchange between mailer, postal operators and addressee/mailee. In addition, evidence of corresponding events and operations within the scope of PReM will be generated and archived for future attestation.
The PReM service is defined by reference to the concepts, schemas and operations defined in CEN/TS 15121-1:2011. It utilises six SePS operational verbs (CheckIntegrity, LogEvent, Postmark, RetrieveResults, Sign and Verify) and the five additional server-side operational verbs (SendMessagetoDestination, Subscribe Notification, UnscbscribeNotification, RejectMessage and ReceiveNotification) to fulfil the operational requirements of a PReM System.
Return of Investment (ROI), market potential, revenues model, business plan and pricing policy are outside the scope of this functional specification. Postal operators are advised to make the necessary marketing study and research prior to considering leasing, procuring or developing such a PReM system in accordance with this functional specification.

Postalische Dienstleistungen - Hybride Sendungen - Funktionale Spezifikation für elektronische Posteinschreibsendungen

Diese Technische Spezifikation legt die funktionale Spezifikation eines gesicherten elektronischen Postdienstes fest, der als elektronische Posteinschreibsendung oder PReM-Dienst bezeichnet wird. PReM bietet einen vertrauenswürdigen und zertifizierten Austausch von elektronischen Sendungen zwischen Absender, Postbetreibern und Empfänger/Adressat. Des Weiteren werden Nachweise der entsprechenden Ereignisse und Prozesse innerhalb des Anwendungsbereiches von PReM generiert und für eine spätere Bescheinigung archiviert.
Der PReM-Dienst wird unter Bezug auf die in CEN/TS 15121-1:2011 festgelegten Konzepte, Schemata und Prozesse definiert. Es werden sechs SePS-Prozessverben („CheckIntegrity“, „LogEvent“, „Postmark“, „RetrieveResults“, „Sign“ und „Verify“) und fünf zusätzliche serverseitige Prozessverben („SendMessagetoDestination“, „SubscribeNotification“, „UnscbscribeNotification“, „RejectMessage“ und „ReceiveNotification“) verwendet, um die Prozessanforderungen eines PReM-Systems zu erfüllen.
Rentabilität (ROI), Marktpotential, Umsatzmodelle, Businessplan und Preispolitik liegen außerhalb des Anwendungsbereiches dieser funktionalen Spezifikation. Postbetreibern wird empfohlen, die erforderliche Marktanalyse und -forschung vor dem Anmieten, der Bereitstellung oder Entwicklung eines derartigen PReM-Systems nach dieser funktionalen Spezifikation durchzuführen.

Services postaux - Courrier hybride - Spécifications fonctionnelles pour le courrier recommandé électronique

Poštne storitve - Hibridna pošta - Funkcionalne specifikacije za elektronske poštne pošiljke

Ta tehnična specifikacija sestavlja funkcijsko specifikacijo varovane elektronske poštne storitve, imenovane elektronske poštne pošiljke ali storitev PReM. Storitev PReM zagotavlja zaupanja vredno in certificirano izmenjavo elektronske pošte med pošiljateljem, poštnimi operaterji in naslovnikom. Poleg tega se zapisi o ustreznih dogodkih in postopkih v okviru cilja PReM ustvarjajo in shranjujejo za njihovo morebitno uporabo v prihodnosti. Storitev PReM določa povezava s koncepti, shemami in postopki, opredeljenimi v standardu CEN/TS 15121-1:2011. Uporabljenih je šest operativnih glagolov SePS (CheckIntegrity, LogEvent, Postmark, RetrieveResults, Sign in Verify) in pet dodatnih strežniških operativnih glagolov (SendMessagetoDestination, SubscribeNotification, UnsubscribeNotification, RejectMessage in ReceiveNotification), da so izpolnjene operativne zahteve sistema PReM. Donosnost naložb (ROI), tržni potencial, prihodkovni model, poslovni načrt in cenovna politika so zunaj obsega te funkcijske specifikacije. Poštnim operaterjem se svetuje, naj, preden pomislijo na zakup, nabavo ali razvitje takšnega sistema PReM v skladu s to funkcionalno specifikacijo, izvedejo potrebno tržno študijo in raziskavo.

General Information

Status
Published
Publication Date
08-Jan-2013
Technical Committee
Current Stage
9060 - Closure of 2 Year Review Enquiry - Review Enquiry
Due Date
02-Sep-2021
Completion Date
02-Sep-2021

Buy Standard

Technical specification
-TS CEN/TS 16326:2013
English language
55 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 16326:2013
01-maj-2013

Poštne storitve - Hibridna pošta - Funkcionalne specifikacije za elektronske poštne

pošiljke

Postal Services - Hybrid Mail - Functional Specification for postal registered electronic

mail
Postalische Dienstleistungen - Hybride Sendungen - Funktionale Spezifikation für
elektronische Posteinschreibsendungen

Services postaux - Courrier hybride - Spécifications fonctionnelles pour le courrier

recommandé électronique
Ta slovenski standard je istoveten z: CEN/TS 16326:2013
ICS:
03.240 Poštne storitve Postal services
SIST-TS CEN/TS 16326:2013 en,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 16326:2013
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 16326:2013
TECHNICAL SPECIFICATION
CEN/TS 16326
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
January 2013
ICS 03.240
English Version
Postal Services - Hybrid Mail - Functional Specification for postal
registered electronic mail

Services postaux - Courrier hybride - Spécifications Postalische Dienstleistungen - Hybride Sendungen -

fonctionnelles pour le courrier recommandé électronique Funktionale Spezifikation für elektronische

Posteinschreibsendungen

This Technical Specification (CEN/TS) was approved by CEN on 7 February 2012 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their

comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available

promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)

until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,

Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United

Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: Avenue Marnix 17, B-1000 Brussels

© 2013 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16326:2013: E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
Contents Page

Foreword ..............................................................................................................................................................4

Introduction .........................................................................................................................................................5

1 Scope ......................................................................................................................................................6

2 Normative references ............................................................................................................................6

3 Terms and definitions ...........................................................................................................................7

4 Symbols and abbreviations ..................................................................................................................8

5 Coordinate system.................................................................................................................................8

5.1 Conceptual models ................................................................................................................................8

5.2 Operation scenarios ........................................................................................................................... 11

5.2.1 Mailer and addressee/mailee both using an Email Client Interface and subscribing to

PReM Service provided by different postal operators .................................................................... 11

5.2.2 System workflow of mailer and addressee/mailee using an Email Client Interface and

subscribing to PReM Service provided by different postal operators .......................................... 13

5.2.3 Mailer and addressee/mailee both using Web-based Interface and subscribing to PReM

Service provided by different postal operators ............................................................................... 15

5.2.4 System Workflow of mailer and addressee/mailee using Web-based Interfaces and

subscribing to PReM Service provided by different postal operators. ......................................... 17

5.2.5 PReM implementation ........................................................................................................................ 19

5.2.6 Interoperation between PReM System and non-PReM System ..................................................... 19

6 Roles in PReM ..................................................................................................................................... 20

7 Functional specification ..................................................................................................................... 21

7.1 Introduction ......................................................................................................................................... 21

7.2 Functional description ....................................................................................................................... 21

7.2.1 CheckIntegrity ..................................................................................................................................... 21

7.2.2 LogEvent .............................................................................................................................................. 21

7.2.3 PostMark .............................................................................................................................................. 21

7.2.4 RetrieveResults ................................................................................................................................... 21

7.2.5 Sign ...................................................................................................................................................... 21

7.2.6 Verify .................................................................................................................................................... 21

7.2.7 SendMessageToDestination .............................................................................................................. 21

7.2.8 RejectMessage .................................................................................................................................... 24

7.2.9 SubscribeNotification ......................................................................................................................... 24

7.2.10 UnsubscribeNotification .................................................................................................................... 26

7.2.11 ReceiveNotification............................................................................................................................. 26

8 DATA STRUCTURES AND FORMATS............................................................................................... 27

8.1 Introduction ......................................................................................................................................... 27

8.2 Message format ................................................................................................................................... 27

8.3 Evidence types .................................................................................................................................... 27

8.4 Evidence format .................................................................................................................................. 30

8.5 Signature format ................................................................................................................................. 30

9 Policy considerations ......................................................................................................................... 30

9.1 Introduction ......................................................................................................................................... 30

9.2 Identity management and authentication models ........................................................................... 31

Annex A (normative) PReM XML Schema V1.00 ........................................................................................... 32

Annex B (normative) PReM Web Services Description Language (WSDL) V1.0 ....................................... 47

---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)

Annex C (informative) Relevant intellectual property rights (IPR) ............................................................... 54

C.1 Introduction .......................................................................................................................................... 54

C.2 IPR advised .......................................................................................................................................... 54

Bibliography ...................................................................................................................................................... 55

---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
Foreword

This document (CEN/TS 16326:2013) has been prepared by Technical Committee CEN/TC 331 “Postal

services”, the secretariat of which is held by NEN.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent

rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.

Keeping pace with the changing communications market, postal operators are increasingly using new

communication and information technologies to move beyond what is traditionally regarded as their core

postal business. They are meeting higher customer expectations with an expanded range of products and

value-added services.

Standards are important prerequisites for effective postal operations and for interconnecting the global

network. The European Committee for Standardization, their Technical Committee 331 "Postal Services"

develops and maintains a growing number of standards to improve the exchange of postal-related information

between postal operators, postal handling organisations, customers, suppliers and other partners, including

various international organisations.

This functional specification has been developed in close relationship with the following technical standards:

 CEN/TS 15121-1:2011;
 ETSI TS 102 640-1.

The use of this Technical Specification as a basis for any implementation is at the risk of the user. Any party

intending such use is strongly advised to seek close contact with the appropriate working group, so that it can

be kept informed of ongoing work.

The CEN/TS 16326 was originally published as a UPU standard S52-1and was adopted by CEN under the

current Memorandum of Understanding between UPU and CEN.

According to the CEN/CENELEC Internal Regulations, the national standards organisations of the following

countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus,

Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany,

Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,

Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.

---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
Introduction

This document describes the functional specification for a postal operator to build or implement the postal

registered electronic mail (abbreviated hereinafter to PReM) system which can be offered to the customers of

the postal operator as part of the Secure electronic Postal Services (SePS).

PReM is an electronic version of the traditional postal registered mail service. It uses state-of-the-art

cryptographic technologies to provide strong role authentication, protection of message confidentiality and

integrity and to add non-repudiation attributes to evidence of events and operations. Therefore, the goal of a

PReM is to enhance the traditional e-mail service so as to provide an end-to-end trusted electronic

communication service, encompassing both evidence of submission and delivery between authenticated

parties.

The service is embodied in the secured and trusted exchange of electronic mail, as every step of the process

is logged for future evidence tracing and any entity involved is authenticated. The PReM service comprises

the following features:

— secured message forwarding and delivery: ensures the PReM Message confidentiality (encryption)

and integrity (no modification); and authenticity and non-repudiation of users (mailer and addressee)

and postal operators (origin and destination). In addition, PReM messages will be securely

transported from mailer to addressee/mailee;

— evidence generation: all significant events within a complete operation cycle are traceable. Types of

evidence and evidence formats are described in 7.2;

— event notification: notification that a particular event/operation has occurred will be generated and

sent to corresponding parties;
— archival of evidence: storage of generated evidence for future attestation.

The implementation of part or all of this functional specification might involve the use of intellectual property

which is the subject of patent and/or trademark rights. Since the specification was developed in close

relationship with ETSI TS 102 640, these might include rights held by ETSI. It is the responsibility of users of

the standard to conduct any necessary searches and to ensure that any pertinent rights are in the public

domain, are licensed, or are avoided. CEN/TC 331 cannot accept any responsibility in case of infringement,

on the part of users of this document, of any third party intellectual property rights. Nevertheless, document

users and owners of such rights are encouraged to advise the Secretariat of the UPU Standards Board or the

Secretariat of CEN/TC 331 or CEN/TC 331 WG2 of any explicit claim that any technique or solution described

herein is protected by such right in any UPU member country. Any such claims will, without prejudice, be

documented in the next update of this standard or otherwise at the discretion of the Standards Board or

Secretariat of the CEN/TC 331 WG2.

Annex C of this document lists the intellectual property rights brought to the attention of the UPU Standards

Board or CEN/TC 331 WG2 prior to approval of the publication of this version of the standard.

---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
1 Scope

This Technical Specification constitutes the functional specification of a secure electronic postal service,

referred to as the postal registered electronic mail or PReM service. PReM provides a trusted and certified

electronic mail exchange between mailer, postal operators and addressee/mailee. In addition, evidence of

corresponding events and operations within the scope of PReM will be generated and archived for future

attestation.

The PReM service is defined by reference to the concepts, schemas and operations defined in

CEN/TS 15121-1:2011. It utilises six SePS operational verbs (CheckIntegrity, LogEvent, Postmark,

RetrieveResults, Sign and Verify) and the five additional server-side operational verbs

(SendMessagetoDestination, Subscribe Notification, UnscbscribeNotification, RejectMessage and

ReceiveNotification) to fulfil the operational requirements of a PReM System.

Return of Investment (ROI), market potential, revenues model, business plan and pricing policy are outside

the scope of this functional specification. Postal operators are advised to make the necessary marketing study

and research prior to considering leasing, procuring or developing such a PReM system in accordance with

this functional specification.
2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are

indispensable for its application. For dated references, only the edition cited applies. For undated references,

the latest edition of the referenced document (including any amendments) applies.

a) European Telecommunications Standards Institute (ETSI) Standards
NOTE ETSI standards are available at www.etsi.org.

ETSI TS 102 640-1, Electronic Signatures and Infrastructures (ESI);Registered Electronic Mail (REM);

Part 1: Architecture
ETSI TS 101 862 V1.3.3 (2006-01), Qualified Certificate Profile
b) European Committee for Standardization (CEN)

NOTE CEN standards can be obtained from national standardization institutes of CEN National Members (see

http://www.cen.eu)

CEN/TS 15121-1:2011, Postal Services — Hybrid Mail — Part 1: Secured electronic postal services

(SePS) interface specification — Concepts, schemas and operations
CWA 14169, Secure Signature-Creation Devices "EAL 4+"

c) Internet Engineering Task Force Public Key Infrastructure X.509 working group (IETF PKIX)

RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL)

Profile, May 2008, D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R.Housley, W.Polk, available from:

http://www.rfc-editor.org/rfc/pdfrfc/rfc5280.txt.pdf
---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
d) Universal Postal Union (UPU) Standards

NOTE UPU standards are available on subscription from the UPU International Bureau: Weltpoststrasse 4, Case

postale, 3000 Berne 15, SWITZERLAND; Tel: +41 31 350 3111; Fax: +41 31 350 3110; http://www.upu.int

UPU Technical Standard S43a, Secured electronic postal services (SePS) interface specification —

Part A: Concepts, schemas and operations
3 Terms and definitions

For the purposes of this document, the terms and definitions given in the UPU Standards glossary, in the

documents referred to in Clause 2 and in Bibliography, and the following apply. The definition of other

frequently used or particularly important terms as well as other terms introduced in this document is given

below.
3.1
Advanced Electronic Signature

signature, uniquely linked to and capable of identifying the signatory, which was created by a signature

creation device in the sole control of the signatory and which is linked to data in such a way that subsequent

change to such data is detectable
3.2
postal operator

entity officially designated by a UPU member country to operate postal services and to fulfil some or all of the

related obligations arising out of the Acts of the UPU in its territory
3.3
postal operator Trust List

list of registered and authenticated postal operators which is maintained by the UPU International Bureau

3.4
Email Client Software

software which supports the creation, sending, reception and storage of messages intended to be or actually

transmitted over electronic communication systems in accordance with the Simple Mail Transfer Protocol

3.5
notification

message that informs the involved parties that a PReM operation has been performed or a PReM event has

taken place
3.6
PReM Dispatch

PReM Message together with all previously collected evidence related thereto the PReM Message

3.7
PReM Object
electronic message or file(s) that mailer intends to send to addressee/mailee
3.8
PReM Policy Domain

collection of PReM enabled postal operators which belong to a group that it is managed according to agreed

rules and regulations agreed by the group
3.9
PReM Message
S/MIME object consisting of one or more PReM Objects
---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
3.10
PReM End User
mailer or addressee/mailee of a PReM System
3.11
Qualified Electronic Signature

Advanced Electronic Signature (AES) which is based on a Qualified Certificate (QC) and which is created by a

Secure Signature Creation Device (SSCD)
3.12
web browser

software which enables a user to display and interact with text, images, videos, music and other information

typically located on a Web page at a web site on the World Wide Web or a local area network

4 Symbols and abbreviations

For the purposes of this document, the symbols, abbreviations and acronyms given in the UPU Standards

glossary, and CEN/TS 15121-1:2011 and the following apply:
HTTPS Hypertext Transfer Protocol over Secure Socket Layer
PReM Postal Registered electronic Mail
S/MIME Secure/Multipurpose Internet Mail Extensions
SMTP Simple Mail Transfer Protocol
POP3 Post Office Protocol version 3
IMAP4 Internet Message Access Protocol
SOAP Simple Object Access Protocol
SOA Service-Oriented Architecture
EDI Electronic Data Interchange
REM Registered Electronic Mail
ETSI European Telecommunications Standards Institute
QES Qualified Electronic Signature
QC Qualified Certificate
SSCD Secure Signature Creation Device
5 Coordinate system
5.1 Conceptual models

The conceptual model of a PReM System comprises of the mailer, addressee/mailee, authorised party, postal

operator of origin, postal operator of destination and postal operator trust list distribution point.

---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)

Records of mailers and/or addressees/mailees held by postal operators should be stored in a directory server

so that registered PReM users can search for other PReM users using criteria such as their email address or

common name. Lightweight Directory Access Protocol (LDAP) is recommended as the directory service

protocol for building such a repository.

Furthermore, in order to identify a legitimate postal operator of destination, a postal operator Trust List should

be maintained and published by the UPU acting as the postal operator Trust List Distribution Point under the

rules and regulations of the PReM Policy Domain.

Conditions and policies for postal operators to join the PReM Policy Domain are outside the scope of this

technical functional specification.

The mailer and addressee/mailee may subscribe to the PReM services offered by the same or different postal

operators. Figure 1 represents the case in which the mailer and addressee/mailee subscribe to the service of

the same postal operator, while Figure 2 represents the case in which the mailer and addressee/mailee

subscribe to the services of different postal operators.
Figure 1 — Mailer and addressee/mailee subscribing to the same postal operator
---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)
Figure 2 — Mailer and addressee/mailee subscribing to different postal operators
---------------------- Page: 12 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)

When sending or receiving a PReM Message, mailer and addressee/mailee may use an email client interface

or a Web-based Interface to interact with a PReM service provided by a postal operator.

The following table shows all possible interface combinations used by the mailer and addressee/mailee.

Table 1 — possible interface combinations used by the mailer and addressee/mailee mailer

Mailer Addressee/mailee
Email Client Interface Email Client Interface
Email Client Interface Web-based Interface
Web-based Interface Web-based Interface
Web-based Interface Email Client Interface

System workflows described in 5.2 only apply when mailer and addressee/mailee subscribe to PReM services

of different postal operators. However, if mailer and addressee/mailee subscribe to the PReM service

provided by the same postal operator, similar procedures should be applicable with appropriate modifications.

Among all possible interface combinations mentioned in the above table, only the first and third cases are

explicitly described in 5.2. However, if the mailer uses Email Client Interface and the addressee/mailee uses

Webbased Interface or the mailer uses Web-based Interface and the addressee/mailee uses Email Client

Interface, appropriate modifications should be done to the workflow to accommodate these scenarios

accordingly.

Although the mailer, addressee/mailee and postal operators are automatically notified with relevant evidence

during the transmission process they are entitled to access it at a later date if necessary.

If a mailer so wishes, a PReM Message could be addressed to multiple addressees/mailees, possibly

subscribing to a PReM service provided by the same postal operator.
5.2 Operation scenarios

5.2.1 Mailer and addressee/mailee both using an Email Client Interface and subscribing to PReM

Service provided by different postal operators

PReM Email Client Interfaces can, but are not required to be, based on a commercially available product such

as Microsoft Outlook, Microsoft Outlook Express, Mozilla ThunderBird, Lotus Notes and Qualcomm Eudora.

Such products will generally require the user to install Email Client Plug-in software to add PReM functionality.

---------------------- Page: 13 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)

Figure 3 — System workflow of mailer and addressee/mailee subscribing to different postal operators

using both Email Client Interface
---------------------- Page: 14 ----------------------
SIST-TS CEN/TS 16326:2013
CEN/TS 16326:2013 (E)

5.2.2 System workflow of mailer and addressee/mailee using an Email Client Interface and

subscribing to PReM Service provided by different postal operators
Actor Workflow Process
Mailer 1.1 Prepare Message using Email Client Software.

(Assisted by 1.2 Use PReM Email Client Software Plug-in to send the PReM Message.

PReM Email 1.3 PReM Email Client Software Plug-in converts Message to PReM object(s).

Client Software 1.4 PReM Email Client Software Plug-in signs PReM object(s) with mailer’s signature

Plug-in) private key/password for Proof-of-Ownership and Content Integrity.

1.5 Decide if the PReM object(s) should be encrypted or not with encryption public key

of addressee/mailee, which can be searched and retrieved from a public repository

located in the postal operator of destination using the Plug-in directory searching

feature.
1.6 PReM Email Client Software Plug-in applies encryption to PReM object(s) if
necessary.
1.7 PReM Email Client Software Plug-in converts PReM object(s) to PReM Message.
1.8 PReM Email Client Software Plug-in invokes postal operator of origin’s
SendMessageToDestination to send PReM Message to postal operator of origin.

1.9 PReM Email Client Software Plug-in authenticates to a postal operator of origin with

a pre-configured credential.
Postal 2.1 Receive/Not Receive PReM Message from mailer using
operator of origin SendMessageToDestination if authentication of mailer has been
Successful/Unsuccessful.
2.2 Assign a unique Identifier to PReM Message.
2.3 Postmark PReM Message using Postmark for Proof of Receipt Time from mailer.
2.4 Log “Evidence of Postmark- PReM Message Received – DOO (#26)” into Evidence
Store using LogEvent.

2.5 Check if postal operator of destination is in the postal operator Trust List.

2.6 Accept/Reject PReM Message from mailer if previous checking has been
Successful/Unsuccessful.
2.7 Notify mailer with “Evidence of Sent – PReM Message Acceptance/Rejection –
DOO (#01)”.

2.8 Log “Evidence of Successful Notification – PReM Message Acceptance/Rejection –

DOO (#07)” into Evidence Store using LogEvent if notification has been
successful.
2.9 Log “Evidence of Failed Notification – PReM Message Acceptance/Rejection –
DOO (#08)” into Evidence Store using LogEvent if notification has not been
successful.

2.10 Prepare PReM Dispatch for postal operator of destination with PReM Message plus

all previously collected Evidence.

Mailer 3.1 Receive “Evidence of Sent – PReM Message Acceptance/Rejection – DOO (#01)”

from postal operator of origin using Email Client Software.

Postal 4.1 Postmark PReM Dispatch using Postmark for Proof of Receipt Time by postal

operator of origin operator of origin.

4.2 Sign PReM Dispatch using Sign for Proof of Origin to be verified by postal operator

of destination.
4.3 Authenticate to postal operator of destination.
4.4 Invoke postal operator of destination’s SendMessageToDestination to forward

mailer’s PReM Dispatch to postal operator of destination if authentication has been

successful.
4.5 Log “Evidence of Forward – DOO (#03)” using LogEvent.

4.6 Log “Evidence of Failed Forward due to Authentication Error – DOO (#05)” using

LogEvent if authentication has not been successful.
4.7 Log
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.