Debian Codegraph @

rfc6109.html

raw
1 <pre>Internet Engineering Task Force (IETF) C. Petrucci
2 Request for Comments: 6109 DigitPA
3 Category: Informational F. Gennai
4 ISSN: 2070-1721 A. Shahin
5 ISTI-CNR
6 A. Vinciarelli
7 April 2011
8
9
10 <span class="h1">La Posta Elettronica Certificata - Italian Certified Electronic Mail</span>
11
12 Abstract
13
14 Since 1997, the Italian laws have recognized electronic delivery
15 systems as legally usable. In 2005, after two years of technical
16 tests, the characteristics of an official electronic delivery
17 service, named certified electronic mail (in Italian "Posta
18 Elettronica Certificata") were defined, giving the system legal
19 standing.
20
21 The design of the entire system was carried out by the National
22 Center for Informatics in the Public Administration of Italy
23 (DigitPA), followed by efforts for the implementation and testing of
24 the service. The DigitPA has given the Italian National Research
25 Council (CNR), and in particular the Institute of Information Science
26 and Technologies at the CNR (ISTI), the task of running tests on
27 providers of the service to guarantee the correct implementation and
28 interoperability. This document describes the certified email system
29 adopted in Italy. It represents the system as it is at the moment of
30 writing, following the technical regulations that were written based
31 upon the Italian Law DPR. November 2, 2005.
32
33 Status of This Memo
34
35 This document is not an Internet Standards Track specification; it is
36 published for informational purposes.
37
38 This document is a product of the Internet Engineering Task Force
39 (IETF). It has been approved for publication by the Internet
40 Engineering Steering Group (IESG). Not all documents approved by the
41 IESG are a candidate for any level of Internet Standard; see <a href="./rfc5741#section-2">Section</a>
42 <a href="./rfc5741#section-2">2 of RFC 5741</a>.
43
44 Information about the current status of this document, any errata,
45 and how to provide feedback on it may be obtained at
46 <a href="http://www.rfc-editor.org/info/rfc6109">http://www.rfc-editor.org/info/rfc6109</a>.
47
48
49
50
51
52 <span class="grey">Petrucci, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2010 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
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 <span class="grey">Petrucci, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
111
112
113 Table of Contents
114
115 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-5">5</a>
116 <a href="#section-1.1">1.1</a>. Scope ......................................................<a href="#page-5">5</a>
117 <a href="#section-1.2">1.2</a>. Notational Conventions .....................................<a href="#page-6">6</a>
118 <a href="#section-1.2.1">1.2.1</a>. Requirement Conventions .............................<a href="#page-6">6</a>
119 <a href="#section-1.2.2">1.2.2</a>. Acronyms ............................................<a href="#page-6">6</a>
120 <a href="#section-1.2.3">1.2.3</a>. Terminology and Definitions .........................<a href="#page-7">7</a>
121 <a href="#section-2">2</a>. PEC Model .......................................................<a href="#page-8">8</a>
122 <a href="#section-2.1">2.1</a>. System-Generated Messages ..................................<a href="#page-8">8</a>
123 <a href="#section-2.1.1">2.1.1</a>. Message Types ......................................<a href="#page-10">10</a>
124 <a href="#section-2.2">2.2</a>. Basic Structure ...........................................<a href="#page-12">12</a>
125 <a href="#section-2.2.1">2.2.1</a>. Access Point .......................................<a href="#page-12">12</a>
126 <a href="#section-2.2.2">2.2.2</a>. Incoming Point .....................................<a href="#page-14">14</a>
127 <a href="#section-2.2.3">2.2.3</a>. Delivery Point .....................................<a href="#page-16">16</a>
128 <a href="#section-2.2.4">2.2.4</a>. Storage ............................................<a href="#page-17">17</a>
129 <a href="#section-2.2.5">2.2.5</a>. Provider Service Mailbox ...........................<a href="#page-17">17</a>
130 <a href="#section-2.2.6">2.2.6</a>. Provider Service Email Address .....................<a href="#page-17">17</a>
131 <a href="#section-2.3">2.3</a>. Log .......................................................<a href="#page-17">17</a>
132 <a href="#section-3">3</a>. Message Processing .............................................<a href="#page-18">18</a>
133 <a href="#section-3.1">3.1</a>. Access Point ..............................................<a href="#page-18">18</a>
134 <a href="#section-3.1.1">3.1.1</a>. Formal Checks on Messages ..........................<a href="#page-18">18</a>
135 3.1.2. Non-Acceptance PEC Notification Due to
136 Formal Exceptions ..................................<a href="#page-19">19</a>
137 3.1.3. Non-Acceptance PEC Notification Due to
138 Virus Detection ....................................<a href="#page-20">20</a>
139 <a href="#section-3.1.4">3.1.4</a>. Server-User Acceptance PEC Notification ............<a href="#page-20">20</a>
140 <a href="#section-3.1.5">3.1.5</a>. PEC Transport Envelope .............................<a href="#page-21">21</a>
141 <a href="#section-3.1.6">3.1.6</a>. Timeout Delivery Error PEC Notification ............<a href="#page-23">23</a>
142 <a href="#section-3.2">3.2</a>. Incoming Point ............................................<a href="#page-24">24</a>
143 <a href="#section-3.2.1">3.2.1</a>. Server-Server Acceptance PEC Notification ..........<a href="#page-24">24</a>
144 <a href="#section-3.2.2">3.2.2</a>. PEC Anomaly Envelope ...............................<a href="#page-25">25</a>
145 <a href="#section-3.2.3">3.2.3</a>. Virus Detection PEC Notification ...................<a href="#page-27">27</a>
146 <a href="#section-3.2.4">3.2.4</a>. Virus-Induced Delivery Error PEC notification ......<a href="#page-28">28</a>
147 <a href="#section-3.3">3.3</a>. Delivery Point ............................................<a href="#page-29">29</a>
148 <a href="#section-3.3.1">3.3.1</a>. Checks on Incoming Messages ........................<a href="#page-29">29</a>
149 <a href="#section-3.3.2">3.3.2</a>. Delivery PEC Notification ..........................<a href="#page-29">29</a>
150 <a href="#section-3.3.3">3.3.3</a>. Non-Delivery PEC Notification ......................<a href="#page-34">34</a>
151 <a href="#section-3.4">3.4</a>. Sender and Receiver Belonging to the Same Domain ..........<a href="#page-34">34</a>
152 <a href="#section-3.5">3.5</a>. Example: Complete Transaction between Two PEC Domains .....<a href="#page-34">34</a>
153 <a href="#section-4">4</a>. Formats ........................................................<a href="#page-35">35</a>
154 <a href="#section-4.1">4.1</a>. Temporal Reference ........................................<a href="#page-35">35</a>
155 <a href="#section-4.2">4.2</a>. User Date/Time ............................................<a href="#page-36">36</a>
156 <a href="#section-4.3">4.3</a>. Format of a PEC Message Body ..............................<a href="#page-36">36</a>
157 <a href="#section-4.3.1">4.3.1</a>. User Readable Text .................................<a href="#page-37">37</a>
158 <a href="#section-4.3.2">4.3.2</a>. Original Message ...................................<a href="#page-37">37</a>
159 <a href="#section-4.3.3">4.3.3</a>. Certification Data .................................<a href="#page-37">37</a>
160 <a href="#section-4.4">4.4</a>. Certification Data Scheme .................................<a href="#page-37">37</a>
161
162
163
164 <span class="grey">Petrucci, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
167
168
169 <a href="#section-4.5">4.5</a>. PEC Providers Directory Scheme ............................<a href="#page-39">39</a>
170 <a href="#section-4.5.1">4.5.1</a>. providerCertificateHash Attribute ..................<a href="#page-41">41</a>
171 <a href="#section-4.5.2">4.5.2</a>. providerCertificate Attribute ......................<a href="#page-41">41</a>
172 <a href="#section-4.5.3">4.5.3</a>. providerName Attribute .............................<a href="#page-41">41</a>
173 <a href="#section-4.5.4">4.5.4</a>. mailReceipt Attribute ..............................<a href="#page-42">42</a>
174 <a href="#section-4.5.5">4.5.5</a>. managedDomains Attribute ...........................<a href="#page-42">42</a>
175 <a href="#section-4.5.6">4.5.6</a>. LDIFLocationURL Attribute ..........................<a href="#page-43">43</a>
176 <a href="#section-4.5.7">4.5.7</a>. providerUnit Attribute .............................<a href="#page-43">43</a>
177 <a href="#section-4.5.8">4.5.8</a>. LDIFLocationURLObject Object Class .................<a href="#page-44">44</a>
178 <a href="#section-4.5.9">4.5.9</a>. Provider Object Class ..............................<a href="#page-44">44</a>
179 <a href="#section-4.5.10">4.5.10</a>. LDIF File Example .................................<a href="#page-44">44</a>
180 <a href="#section-5">5</a>. Security-Related Aspects .......................................<a href="#page-48">48</a>
181 <a href="#section-5.1">5.1</a>. Digital Signature .........................................<a href="#page-48">48</a>
182 <a href="#section-5.2">5.2</a>. Authentication ............................................<a href="#page-48">48</a>
183 <a href="#section-5.3">5.3</a>. Secure Interaction ........................................<a href="#page-49">49</a>
184 <a href="#section-5.4">5.4</a>. Virus .....................................................<a href="#page-49">49</a>
185 <a href="#section-5.5">5.5</a>. S/MIME Certificate ........................................<a href="#page-49">49</a>
186 <a href="#section-5.5.1">5.5.1</a>. Provider-Related Information (Subject) .............<a href="#page-50">50</a>
187 <a href="#section-5.5.2">5.5.2</a>. Certificate Extensions .............................<a href="#page-50">50</a>
188 <a href="#section-5.5.3">5.5.3</a>. Example ............................................<a href="#page-51">51</a>
189 <a href="#section-5.6">5.6</a>. PEC Providers Directory ...................................<a href="#page-55">55</a>
190 <a href="#section-6">6</a>. PEC System Client Technical and Functional Prerequisites .......<a href="#page-55">55</a>
191 <a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-55">55</a>
192 <a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-56">56</a>
193 <a href="#section-8.1">8.1</a>. Registration of PEC Message Header Fields .................<a href="#page-56">56</a>
194 <a href="#section-8.1.1">8.1.1</a>. Header Field: X-Riferimento-Message-ID: ............<a href="#page-56">56</a>
195 <a href="#section-8.1.2">8.1.2</a>. Header Field: X-Ricevuta: ..........................<a href="#page-56">56</a>
196 <a href="#section-8.1.3">8.1.3</a>. Header Field: X-VerificaSicurezza: .................<a href="#page-57">57</a>
197 <a href="#section-8.1.4">8.1.4</a>. Header Field: X-Trasporto: .........................<a href="#page-57">57</a>
198 <a href="#section-8.1.5">8.1.5</a>. Header Field: X-TipoRicevuta: ......................<a href="#page-57">57</a>
199 <a href="#section-8.1.6">8.1.6</a>. Header Field: X-Mittente: ..........................<a href="#page-58">58</a>
200 <a href="#section-8.2">8.2</a>. Registration of LDAP Object Identifier Descriptors ........<a href="#page-58">58</a>
201 8.2.1. Registration of Object Classes and
202 Attribute Types ....................................<a href="#page-58">58</a>
203 <a href="#section-9">9</a>. References .....................................................<a href="#page-59">59</a>
204 <a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-59">59</a>
205 <a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-61">61</a>
206 <a href="#section-10">10</a>. Acknowledgments ...............................................<a href="#page-62">62</a>
207 <a href="#appendix-A">Appendix A</a>. Italian Fields and Values in English ..................<a href="#page-63">63</a>
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Petrucci, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
223
224
225 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
226
227 Since 1997, the Italian laws have recognized electronic delivery
228 systems as legally usable. In 2005, after two years of technical
229 tests, the characteristics of an official electronic delivery
230 service, named certified electronic mail (in Italian Posta
231 Elettronica Certificata, from now on "PEC") were defined, giving the
232 system legal standing.
233
234 This document represents the English version of the Italian
235 specifications
236 (<a href="http://www.digitpa.gov.it/sites/default/files/normativa/Pec_regole_tecniche_DM_2-nov-2005.pdf">http://www.digitpa.gov.it/sites/default/files/normativa/</a>
237 <a href="http://www.digitpa.gov.it/sites/default/files/normativa/Pec_regole_tecniche_DM_2-nov-2005.pdf">Pec_regole_tecniche_DM_2-nov-2005.pdf</a>); the Italian version is the
238 normative PEC reference.
239
240 IETF review did not result in community consensus. Since this
241 specification describes existing deployment and implementation, the
242 issues identified by the IETF community have not been addressed in
243 this document. However, these issues would need to be addressed
244 before a successor to this document could be published. At a
245 minimum, the successor document would need to include:
246
247 * A clear statement of the requirements/goals that need to be
248 satisfied by the protocol;
249
250 * A comprehensive diagram and description of the overall message flow
251 and delivery sequence required to achieve the requirements;
252
253 * Alignment with traditional terminology for IETF email and security
254
255 * A review of prior art; and
256
257 * A replacement of the unregistered LDAP DN name space used in this
258 specification, which may lead to conflict with other registered or
259 unregistered names, with a registered name space.
260
261 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Scope</span>
262
263 To ensure secure transactions over the Internet, cryptography can be
264 associated with electronic messages in order to provide some
265 guarantee on sender identity, message integrity, confidentiality, and
266 non-repudiation of origin. Many end-to-end techniques exist to
267 accomplish such goals, and some offer a high level of security. The
268 downside of end-to-end cryptography is the need for an extensive
269 penetration of technology in society, because it is essential for
270 every user to have asymmetric keys and certificates signed by a
271 Certification Authority. Along with that, users would need to have
272 an adequate amount of knowledge regarding the use of such technology.
273
274
275
276 <span class="grey">Petrucci, et al. Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
279
280
281 PEC, on the other hand, uses applications running on servers to
282 digitally sign messages, thus avoiding the complexity end-to-end
283 systems bring about. By doing so, the user need only have an
284 ordinary mail client with which to interact. The downside is that
285 the level of security drops, since the protection does not cover the
286 entire transaction. Nonetheless, application is simpler and does not
287 require specific user skills, making it easily more widespread among
288 users.
289
290 This document describes PEC's technical aspects and features. It
291 presents the details of the protocol and the messages that are sent
292 between service providers, introducing the system adopted by the
293 Italian government for the exchange of certified emails.
294
295 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Notational Conventions</span>
296
297 <span class="h4"><a class="selflink" id="section-1.2.1" href="#section-1.2.1">1.2.1</a>. Requirement Conventions</span>
298
299 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
300 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
301 document are to be interpreted as described in [<a href="#ref-REQ" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">REQ</a>].
302
303 <span class="h4"><a class="selflink" id="section-1.2.2" href="#section-1.2.2">1.2.2</a>. Acronyms</span>
304
305 CMS: Cryptographic Message Syntax
306 CNIPA: Italian National Agency for Digital Administration
307 (Centro Nazionale per l'Informatica nella Pubblica
308 Amministrazione)
309 CNR: Italian National Research Council (Consiglio Nazionale
310 delle Ricerche)
311 CRL: Certificate Revocation List
312 CRL DP: Certificate Revocation List Distribution Point
313 DNS: Domain Name Service
314 DTD: Document Type Definition
315 FQDN: Fully Qualified Domain Name
316 ISTI: The Institute of Information Science and Technologies
317 at the CNR (Istituto di Scienza e Tecnologie
318 dell'Informazione "A.Faedo")
319 LDAP: Lightweight Directory Access Protocol
320 LDIF: LDAP Data Interchange Format
321 MIME: Multipurpose Internet Mail Extensions
322 PEC: Certified Electronic Mail (Posta Elettronica
323 Certificata)
324 S/MIME: Secure/MIME
325 SMTP: Simple Mail Transfer Protocol
326 TLS: Transport Layer Security
327 XML: eXtensible Markup Language
328
329
330
331
332 <span class="grey">Petrucci, et al. Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
335
336
337 <span class="h4"><a class="selflink" id="section-1.2.3" href="#section-1.2.3">1.2.3</a>. Terminology and Definitions</span>
338
339 Certification data: A set of data certified by the sender's PEC
340 provider that describes the original message. It includes the date
341 and time of dispatch, sender email address, recipient(s) email
342 address(es), subject, and message identifier.
343
344 Certified electronic mail: A service based on electronic mail, as
345 defined by the [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] and [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>] standards and extensions, which
346 permits the transmission of documents produced with informatics
347 tools.
348
349 DigitPA: Ex-CNIPA.
350
351 Holder: The person or organization to whom a PEC mailbox is assigned.
352
353 Message sent: A PEC message is considered sent when the sender's PEC
354 provider, after several checks, accepts the email and returns a
355 server-user acceptance PEC notification to the sender.
356
357 Message received: A PEC message is considered received when it is
358 stored in the receiver's mailbox, after which the receiver PEC
359 provider returns a delivery PEC notification to the sender.
360
361 Msgid: Is the message identifier generated by the email client, as
362 defined in [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>], before the message is submitted to the PEC
363 system.
364
365 Ordinary mail: Non-PEC email messages.
366
367 Original message: Is the user-generated message before its arrival to
368 the sender Access Point. The original message is delivered to the
369 recipient inside a PEC transport envelope.
370
371 PEC domain: Corresponds to a DNS domain dedicated to the holders'
372 mailboxes.
373
374 PEC mailbox: An electronic mailbox for which delivery PEC
375 notifications are issued upon reception of PEC messages. Such a
376 mailbox can be defined exclusively within a PEC domain.
377
378 PEC msgid: Is a unique identifier generated by the PEC system, which
379 will substitute the msgid.
380
381
382
383
384
385
386
387
388 <span class="grey">Petrucci, et al. Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
391
392
393 PEC provider: The entity that handles one or more PEC domains with
394 their relative points of Access, Reception, and Delivery. It is the
395 holder of the key that is used for signing PEC notifications and
396 envelopes, and it interacts with other PEC providers for
397 interoperability with other holders.
398
399 PEC provider's key: Is a key released by DigitPA to every PEC
400 provider. It is used to sign PEC notifications and envelopes and to
401 authorize access to the PEC providers directory.
402
403 PEC providers directory: Is an LDAP server positioned in an area
404 reachable by all PEC service providers. It constitutes the technical
405 structure related to the public list of PEC service providers and
406 contains the list of PEC domains and service providers with relevant
407 certificates.
408
409 Service mailbox: A mailbox for the sole use of the provider,
410 dedicated for the reception of server-server acceptance and virus
411 detection PEC notifications.
412
413 Time stamp: Digital evidence with which a temporal reference, that
414 can't be repudiated, is attributed to one or more documents.
415
416 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. PEC Model</span>
417
418 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. System-Generated Messages</span>
419
420 The PEC system generates messages in MIME format composed of a
421 descriptive textual part and other [<a href="#ref-MIME1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">MIME1</a>] parts, the number and
422 content of which varies according to the type of message generated.
423
424 A system-generated message falls into one of the following
425 categories:
426
427 o Notifications;
428
429 o Envelopes.
430
431 The message is inserted in an S/MIME v3 structure in CMS format and
432 signed with the PEC provider's private key. The X.509v3 certificate
433 associated with the key MUST be included in the aforementioned
434 structure. The S/MIME format used to sign system-generated messages
435 is the "multipart/signed" format (.p7s), as described in <a href="#section-3.4.3">section</a>
436 <a href="#section-3.4.3">3.4.3</a> of [<a href="#ref-SMIMEV3" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification&quot;">SMIMEV3</a>].
437
438 To guarantee the verifiability of signatures on as many mail clients
439 as possible, X.509v3 certificates used by certified email systems
440 MUST abide by the profile found in <a href="#section-6.5">section 6.5</a>.
441
442
443
444 <span class="grey">Petrucci, et al. Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
447
448
449 In order for the receiving mail client to verify the signature, the
450 sender address MUST coincide with the one indicated within the
451 X.509v3 certificate. For this mechanism, PEC transport envelopes
452 MUST indicate in the "From:" field a single author's address which is
453 different from the one contained in the original message. To allow
454 for better message usability by the receiving user, the author's mail
455 address in the original message is inserted as a "display name". For
456 example, a "From:" field such as:
457
458 From: "John Smith" &lt;[email protected]&gt;
459
460 would result in the following "From:" value in the respective PEC
461 transport envelope:
462
463 From: "On behalf of: [email protected]"
464 &lt;[email protected]&gt;
465
466 Both "From:" and "Sender:" fields MUST contain the same value. In
467 order for replies to be correctly sent back to the proper
468 destination, the "Reply-To:" field in the PEC transport envelope MUST
469 contain the same unaltered value of the original message's
470 "Reply-To:" field. When it is not explicitly specified in the
471 original message, the system that generates the PEC transport
472 envelope creates it by extracting the information from the "From:"
473 field in the original message.
474
475 When PEC notifications are sent, the system MUST use the original
476 message sender's address as the destination address, as is specified
477 in the reverse path data of the SMTP protocol. PEC notifications
478 MUST be sent to the sender's PEC mailbox without taking into account
479 the "Reply-To:" field, which might be present in the original
480 message's header.
481
482 All system-generated PEC messages are identifiable for having a
483 specific header defined in PEC according to the type of message
484 generated.
485
486 To determine the certification data, the elements used for the actual
487 routing of the message are employed. In SMTP dialog phases, the
488 reverse path and forward path data ("MAIL FROM" and "RCPT TO"
489 commands) are thus considered certification data of both the sender
490 and the recipients, respectively. Addressing data present in the
491 message body ("To:" and "Cc:" fields) are used solely in order to
492 discriminate between primary and carbon copy recipients when
493 necessary; addressing data present in the "Bcc:" field MUST be
494 considered invalid by the system.
495
496
497
498
499
500 <span class="grey">Petrucci, et al. Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
503
504
505 <span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Message Types</span>
506
507 All system-generated messages inherit their header fields and values
508 from the original message, with extra fields added according to the
509 type of message generated.
510
511 <span class="h5"><a class="selflink" id="section-2.1.1.1" href="#section-2.1.1.1">2.1.1.1</a>. PEC Notifications</span>
512
513 They have the purpose of informing the sending user and interacting
514 providers of the progress the message is making within the PEC
515 network.
516
517 <span class="h6"><a class="selflink" id="section-2.1.1.1.1" href="#section-2.1.1.1.1">2.1.1.1.1</a>. Success PEC Notifications</span>
518
519 These notifications indicate an acknowledgment on the provider's side
520 for the reception or handling of a PEC message. More specifically,
521 it can indicate one of three situations: server-user acceptance,
522 server-server acceptance, or delivery.
523
524 Added header fields are:
525
526 o X-Ricevuta:
527
528 o X-Riferimento-Message-ID:
529
530 The field "X-Ricevuta:" indicates the type of PEC notification
531 contained in the message, whereas "X-Riferimento-Message-ID:"
532 contains the message identifier generated by the mail client (msgid).
533
534 Body contents differ according to notification type. This is
535 described more thoroughly in <a href="#section-3">section 3</a>.
536
537 o A server-user acceptance PEC notification informs the user that
538 his provider has accepted the message and will be taking care of
539 passing it on to the provider(s) of the addressee(s).
540
541 o A server-server acceptance PEC notification is an inter-provider
542 communication only, it MUST NOT be sent to the users. With this
543 notification, the receiving provider simply informs the sending
544 one that it has received a PEC message, and will take the
545 responsibility of forwarding it to the addressee(s). From then
546 on, the sender provider is no longer held responsible as to the
547 whereabouts of the message, but is limited to notifying its user
548 of the success or failure of delivery.
549
550 o Delivery PEC notifications take place as the final communication
551 of a transaction, indicating overall success in handing the
552 message over to the addressee(s).
553
554
555
556 <span class="grey">Petrucci, et al. Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
559
560
561 <span class="h6"><a class="selflink" id="section-2.1.1.1.2" href="#section-2.1.1.1.2">2.1.1.1.2</a>. Delay PEC Notifications</span>
562
563 Delay PEC notifications are sent out 12 hours after a message has
564 been dispatched from the sending provider, and no server-server
565 acceptance or delivery PEC notification has been received. These
566 have the sole purpose of notifying the user of the delay.
567
568 If another 12 hours go by without any sign of a server-server
569 acceptance or delivery PEC notification (amounting to a 24-hour
570 delay), another delay PEC notification is dispatched to the user
571 informing him of the possible delivery failure. The provider will
572 not keep track of the delay any further.
573
574 <span class="h6"><a class="selflink" id="section-2.1.1.1.3" href="#section-2.1.1.1.3">2.1.1.1.3</a>. Failure PEC Notifications</span>
575
576 They are sent when there is some error in transmission or reception.
577 More specifically, a failure PEC notification can indicate either a
578 formal-exception error or a virus detection.
579
580 Added header fields are:
581
582 o X-Ricevuta:
583
584 o X-Riferimento-Message-ID:
585
586 o X-VerificaSicurezza: [optional]
587
588 "X-Ricevuta:" and "X-Riferimento-Message-ID:" have the same role as
589 indicated in <a href="#section-2.1.1.1.1">section 2.1.1.1.1</a> (Success Notifications).
590 "X-VerificaSicurezza:" (security verification) is an optional header
591 field, used for virus-related PEC notifications.
592
593 Body contents differ according to notification type. This is
594 described more thoroughly in <a href="#section-3">section 3</a>.
595
596 <span class="h5"><a class="selflink" id="section-2.1.1.2" href="#section-2.1.1.2">2.1.1.2</a>. PEC Envelopes</span>
597
598 Messages entering the PEC network are inserted within specific PEC
599 messages, called envelopes, before they are allowed to circulate
600 further within the network. These envelopes MUST inherit the
601 following header fields, along with their unmodified values, from the
602 message itself:
603
604 o Received:
605
606 o To:
607
608 o Cc:
609
610
611
612 <span class="grey">Petrucci, et al. Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
615
616
617 o Return-Path:
618
619 o Reply-To: (if present)
620
621 Depending on the type of message requesting admission into the PEC
622 network, it will be inserted in either a PEC transport envelope or a
623 PEC anomaly envelope. Distinction will be possible through the
624 addition of the "X-Trasporto:" header field.
625
626 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Basic Structure</span>
627
628 +-------------+ +------------+
629 | +--+ | | |
630 | |AP| | PEC | |
631 +----+ | +--+ | messages &amp; | +---+ +--+ | +----+
632 |user|&lt;--&gt;| |&lt;-------------&gt;| |InP| |DP| |&lt;--&gt;|user|
633 +----+ | +--+ +---+ | notifications | +---+ +--+ | +----+
634 | |DP| |InP| | | |
635 | +--+ +---+ | | |
636 +-------------+ +------------+
637 PEC PEC
638 sender receiver
639 provider provider
640
641 where:
642
643 AP = Access Point
644 DP = Delivery Point
645 InP = Incoming Point
646
647 <span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Access Point</span>
648
649 This is what the user client at the sender side interacts with,
650 giving the user access to PEC services set up by the provider.
651
652 Such access MUST be preceded by user authentication on the system
653 (see <a href="#section-5.2">section 5.2</a>). The Access Point receives the original messages
654 its user wishes to send, runs some formal checks, and acts according
655 to the outcome:
656
657 o if the message passes all checks, the Access Point generates a
658 server-user acceptance PEC notification and inserts the original
659 message inside a PEC transport envelope;
660
661 o if a formal exception is detected, the Access Point refuses the
662 message and emits the relevant non-acceptance PEC notification
663 (see <a href="#section-3.1.1">section 3.1.1</a>);
664
665
666
667
668 <span class="grey">Petrucci, et al. Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
671
672
673 o if a virus is detected, the Access Point generates a non-
674 acceptance PEC notification and inserts the original message as is
675 in the provider's special store.
676
677 Generation of the server-user acceptance notification indicates to
678 the user that the message was accepted by the system, certifying also
679 the date and time of the event. The notification MUST contain user-
680 readable text, and an XML part containing the certification data.
681 The notification MAY also contain other attachments for extra
682 features offered by the provider.
683
684 Using the data available in the PEC providers directory (see <a href="#section-4.5">section</a>
685 <a href="#section-4.5">4.5</a>), the Access Point runs checks on every recipient in the "To:"
686 and "Cc:" fields present in the original message to verify whether
687 they belong to the PEC infrastructure or to non-PEC domains. Such
688 checks are done by verifying the existence, through a case-
689 insensitive search, of the recipients' domains in the
690 "managedDomains" attribute found within the PEC providers directory.
691 Therefore, the server-user acceptance PEC notification (and relevant
692 certification data) relates to, for each address, the typology of its
693 domain; PEC or non-PEC.
694
695 The message identifier (PEC msgid) of accepted original messages
696 within the PEC infrastructure MUST be unambiguous in order to consent
697 correct tracking of messages and relative PEC notifications. The
698 format of such an identifier is:
699
700 [alphanumeric string]@[provider mail domain]
701
702 or:
703
704 [alphanumeric string]@[FQDN mail server]
705
706 Therefore, both the original message and the corresponding PEC
707 transport envelope MUST contain the following header field:
708
709 Message-ID: &lt;[unique identifier]&gt;
710
711 When an email client that is interacting with the Access Point has
712 already inserted a message identifier (msgid) in the original
713 message, that msgid SHALL be substituted by a PEC msgid. In order to
714 allow the sender to link the message sent with the relative PEC
715 notifications, the msgid MUST be inserted in the original message as
716 well as the relative PEC notifications and transport envelope. If
717 present, the msgid is REQUIRED in the original message's header by
718 adding the following header field:
719
720 X-Riferimento-Message-ID: &lt;[msgid]&gt;
721
722
723
724 <span class="grey">Petrucci, et al. Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
727
728
729 which will also be inserted in the PEC transport envelope and
730 notifications, and related in the certification data (see <a href="#section-4.4">section</a>
731 <a href="#section-4.4">4.4</a>).
732
733 <span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. Incoming Point</span>
734
735 This point permits the exchange of PEC messages and notifications
736 between PEC providers. It is also the point through which ordinary
737 mail messages can be inserted within the system of certified mail.
738
739 The exchange of messages between providers takes place through SMTP-
740 based transactions, as defined in [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>]. If SMTP communication
741 errors occur, they MAY be handled using the standard error
742 notification mechanisms, as provided by SMTP in [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>] and
743 [<a href="#ref-SMTP-DSN" title="&quot;Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)&quot;">SMTP-DSN</a>]. The same mechanism is also adopted for handling
744 transitory errors, that result in long idling periods, during an SMTP
745 transmission phase. In order to guarantee that an error is returned
746 to the user, as defined in <a href="#section-3.3.3">section 3.3.3</a>, the system that handles PEC
747 traffic MUST adopt a time limit for message idleness equal to 24
748 hours.
749
750 Once a message arrives, the Incoming Point runs the following list of
751 checks and operations:
752
753 o verifies correctness and type of the incoming message;
754
755 o if the incoming message is a correct and undamaged PEC transport
756 envelope:
757
758 - emits a server-server acceptance PEC notification towards the
759 sender provider (<a href="#section-3.2.1">section 3.2.1</a>);
760
761 - forwards the PEC transport envelope to the Delivery Point
762 (<a href="#section-3.3">section 3.3</a>).
763
764 o if the incoming message is a correct and undamaged PEC
765 notification, forwards the notification to the Delivery Point.
766
767 o if the incoming message does not conform to the prerequisites of a
768 correct and undamaged PEC transport envelope or notification, but
769 comes from a PEC provider, i.e., passes the verifications
770 regarding existence, origin, and validity of the signature, then
771 the message MUST be propagated towards the recipient.
772
773 Therefore, the Incoming Point:
774
775 - inserts the incoming message in a PEC anomaly envelope (<a href="#section-3.2.2">section</a>
776 <a href="#section-3.2.2">3.2.2</a>);
777
778
779
780 <span class="grey">Petrucci, et al. Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
783
784
785 - forwards the PEC anomaly envelope to the Delivery Point.
786
787 o if the incoming message does not originate from a PEC system,
788 i.e., fails verifications regarding existence, origin, and
789 validity of the signature, then the message will be treated as
790 ordinary email, and, if propagated to the recipient:
791
792 - is inserted in a PEC anomaly envelope (<a href="#section-3.2.2">section 3.2.2</a>);
793
794 - the PEC anomaly envelope is forwarded to the Delivery Point.
795
796 The server-server acceptance PEC notification is generated by the
797 receiving provider and sent to the sending provider. Its purpose
798 is to keep track of the message in its transition from one
799 provider to another, and is therefore strictly intra-provider
800 communication; the end user knows nothing about it.
801
802 To check the correctness and integrity of a PEC transport envelope
803 or notification, the Incoming Point runs the following tests:
804
805 o Signature existence - the system verifies the presence of an
806 S/MIME signature structure within the incoming message;
807
808 o Signature origin - the system verifies whether or not the
809 signature belongs to a PEC provider by extracting the certificate
810 used for signing and verifying its presence in the PEC providers
811 directory. To ease the check, it is possible to calculate the
812 certificate's [<a href="#ref-SHA1" title="&quot;US Secure Hash Algorithm 1 (SHA1)&quot;">SHA1</a>] hash value and perform a case-insensitive
813 search of its hexadecimal representation within the
814 "providerCertificateHash" attribute found in the PEC providers
815 directory. This operation allows one to easily identify the
816 sender provider for subsequent and necessary matching checks
817 between the extracted certificate and the one present in the
818 provider's record;
819
820 o Signature validity - S/MIME signature correctness is verified by
821 recalculating the signature value, checking the entire
822 certification path, and verifying the [<a href="#ref-CRL" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">CRL</a>] and temporal validity
823 of the certificate. In case some caching mechanism is used for
824 CRL contents, an update interval MUST be adopted so that the most
825 up-to-date data is guaranteed, thus minimizing the possible delay
826 between a publication revocation by the Certification Authority
827 and the variation acknowledgment by the provider;
828
829 o Formal correctness - the provider performs sufficient and
830 necessary checks to guarantee that the incoming message is
831 compliant with the formats specified in this document (PEC
832 transport envelope and notifications).
833
834
835
836 <span class="grey">Petrucci, et al. Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
839
840
841 If a virus-infected PEC transport envelope passes the checks just
842 mentioned, it is still considered correct and undamaged. The
843 presence of the virus will be detected in a second phase, during
844 which the contents of the PEC transport envelope are verified.
845 Thus, the Incoming Point will refrain from forwarding the message
846 to the recipient, instead sending the appropriate PEC notification
847 of non-delivery and storing the virus-infected message in the
848 provider's special storage.
849
850 In case ordinary mail messages are received, the PEC provider
851 SHALL perform virus checks in order to prevent the infiltration of
852 potentially dangerous mail messages within the PEC system. If a
853 virus is detected in an ordinary mail message, the latter can be
854 discarded at the Incoming Point before it enters the PEC system.
855 In other words, no special treatment is reserved for the error; it
856 is handled in a manner that is conformant to the procedures
857 usually followed for messages going through the Internet.
858
859 When the receiving provider detects a virus inside a PEC transport
860 envelope during the reception phase, it emits a virus detection
861 PEC notification to the sending provider, which then realizes its
862 checks failed to detect that virus. When this happens, the
863 sending provider MUST:
864
865 o check what virus typologies were not detected by its own antivirus
866 to verify the possibility of interventions
867
868 o send a virus-induced non-delivery PEC notification to the sender's
869 mailbox.
870
871 <span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a>. Delivery Point</span>
872
873 This point is the point that receives messages from the Incoming
874 Point and forwards them to the final recipient.
875
876 It MUST run a series of tests on received messages before forwarding
877 them to the user (see <a href="#section-3.3.1">section 3.3.1</a>). It first verifies the typology
878 of the message and decides whether or not a PEC notification should
879 be issued to the sender. The delivery PEC notification (<a href="#section-3.3.2">section</a>
880 <a href="#section-3.3.2">3.3.2</a>) is emitted after the message was delivered to the recipient's
881 PEC mailbox and only at reception of a valid PEC transport envelope
882 (sections <a href="#section-2.2.2">2.2.2</a> and <a href="#section-3.1.5">3.1.5</a>).
883
884 In all other cases, such as PEC anomaly envelopes and PEC
885 notifications, the delivery PEC notification is not emitted.
886 Regardless, the message received from the Delivery Point MUST be
887 delivered unmodified to the recipient's mailbox.
888
889
890
891
892 <span class="grey">Petrucci, et al. Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
895
896
897 The delivery PEC notification indicates to the sender that the
898 message sent was in fact conveyed to the specified recipient's
899 mailbox and certifies the date and time of delivery through use of
900 user-readable text and an XML part containing certification data,
901 along with other possible attachments added for extra features
902 offered by the provider.
903
904 If a PEC transport envelope received at the Delivery Point can't be
905 delivered to the destination mailbox, the Delivery Point emits a non-
906 delivery PEC notification (<a href="#section-3.3.3">section 3.3.3</a>). If, on the other hand,
907 the delivery error concerns a message that arrives from Internet
908 (i.e., a non-PEC message), no such notification is emitted.
909
910 <span class="h4"><a class="selflink" id="section-2.2.4" href="#section-2.2.4">2.2.4</a>. Storage</span>
911
912 Each provider MUST dedicate a special storage for the deposition of
913 any virus-infected messages encountered. Whether the virus be
914 detected by the sender's Access Point or the receiver's Incoming
915 Point, the provider that detects it MUST store the mail message in
916 its own storage, and keep it for 30 months.
917
918 <span class="h4"><a class="selflink" id="section-2.2.5" href="#section-2.2.5">2.2.5</a>. Provider Service Mailbox</span>
919
920 For exclusive use of the provider, dedicated to the reception of PEC
921 notifications in two cases only:
922
923 o server-server acceptance notification; and
924
925 o virus detection notification.
926
927 <span class="h4"><a class="selflink" id="section-2.2.6" href="#section-2.2.6">2.2.6</a>. Provider Service Email Address</span>
928
929 Each provider MUST register a special purpose email address for use
930 when sending PEC transport envelopes and notifications, as delineated
931 in <a href="#section-3">section 3</a>. This address MAY coincide with that of the service
932 mailbox described in <a href="#section-2.2.5">section 2.2.5</a>.
933
934 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Log</span>
935
936 The server administrator MUST keep track of any and all operations
937 carried out in a specific message log file. The information kept in
938 the log for each operation is the following:
939
940 o message identifier (msgid)
941
942 o date and time of event
943
944 o sender of original message
945
946
947
948 <span class="grey">Petrucci, et al. Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
951
952
953 o recipient(s) of original message
954
955 o subject of original message
956
957 o event type (reception, delivery, PEC notification emission, etc.)
958
959 o message identifiers of related generated messages
960
961 o sending provider
962
963 The service provider MUST store this data and preserve it unmodified.
964 Italian laws have specified that the service provider retain the data
965 for 30 months.
966
967 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Message Processing</span>
968
969 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Access Point</span>
970
971 The Access Point acts as a submission service as defined in
972 [<a href="#ref-SUBMISSION" title="&quot;Message Submission for Mail&quot;">SUBMISSION</a>].
973
974 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Formal Checks on Messages</span>
975
976 When the Access Point receives a message the user wishes to send, it
977 MUST guarantee said message's formal conformity as defined in
978 [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>], and verify that the:
979
980 o [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] header section contains a "From:" header field holding an
981 [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] compliant email address;
982
983 o [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] header section contains a "To:" header field holding one
984 or more [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] compliant email addresses;
985
986 o sender's address, specified in the SMTP reverse path, coincides
987 with the one in the message's "From:" header field;
988
989 o recipients' addresses specified in the SMTP forward path coincide
990 with the ones present in the "To:" or "Cc:" header fields of the
991 message;
992
993 o "Bcc:" header field does not contain any value;
994
995 o total message size falls within the limits accepted by the
996 provider. Such limits apply depending on the number of recipients
997 as well; by multiplying it to the message size, the outcome MUST
998 fall within the limits accepted by the provider. Italian laws
999 have specified this limit as being 30 MB.
1000
1001
1002
1003
1004 <span class="grey">Petrucci, et al. Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1007
1008
1009 If the message does not pass the tests, the Access Point MUST NOT
1010 accept the message within the PEC system, thus emitting the relative
1011 PEC notification of non-acceptance.
1012
1013 <span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Non-Acceptance PEC Notification Due to Formal Exceptions</span>
1014
1015 When the Access Point cannot forward the message received due to
1016 failure in passing formal checks, the sender is notified of such an
1017 outcome. If the error is caused by the message failing size checks,
1018 a non-acceptance PEC notification is sent as long as the size remains
1019 bound by a certain limit. If the size exceeds said limit, error
1020 handling is left to SMTP.
1021
1022 The notification header will contain the following fields:
1023
1024 X-Ricevuta: non-accettazione
1025 Date: [date of notification emission]
1026 Subject: AVVISO DI NON ACCETTAZIONE: [original subject]
1027 From: posta-certificata@[mail domain]
1028 To: [original sender]
1029 X-Riferimento-Message-ID: [msgid]
1030
1031 The notification body will contain a text part that constitutes the
1032 actual notification in readable format according to a model that
1033 relates the following information:
1034
1035 Error in message acceptance
1036 On [date] at [time] ([time zone]), in the message "[subject]"
1037 originating from "[original sender]" and addressed to:
1038 [recipient_1]
1039 [recipient_2]
1040 [recipient_n]
1041 a problem was detected that prevents its acceptance due to
1042 [error description].
1043 The message was not accepted.
1044 Message identifier: [PEC msgid of corresponding
1045 PEC transport envelope]
1046
1047 The same certification information is inserted in an XML file to be
1048 added to the notification body, thus allowing automatic checks on the
1049 message (<a href="#section-4.4">section 4.4</a>). Parsing MUST be done on the XML part only.
1050 Additional parts MAY be included by the provider for provider-
1051 specific services. Regardless, the original message MUST NOT be
1052 included. The message MUST follow the format described in <a href="#section-4.3">section</a>
1053 <a href="#section-4.3">4.3</a>.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Petrucci, et al. Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1063
1064
1065 <span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>. Non-Acceptance PEC Notification Due to Virus Detection</span>
1066
1067 The Access Point MUST run some tests on the content of messages it
1068 receives from its users and reject them if a virus is detected. In
1069 which case, a virus-detection-induced non-acceptance PEC notification
1070 MUST be emitted to clearly inform the user of the reason the message
1071 was refused.
1072
1073 The notification header contains the following fields:
1074
1075 X-Ricevuta: non-accettazione
1076 X-VerificaSicurezza: errore
1077 Date: [notification emission date]
1078 Subject: AVVISO DI NON ACCETTAZIONE PER VIRUS: [original
1079 subject]
1080 From: posta-certificata@[mail domain]
1081 To: [original sender]
1082 X-Riferimento-Message-ID: [msgid]
1083
1084 The body contains a readable text part according to the following
1085 model:
1086
1087 Error in message acceptance due to virus presence
1088 On [date] at [time] ([time zone]), in the message "[subject]"
1089 originating from "[original sender]" and addressed to:
1090 [recipient_1]
1091 [recipient_2]
1092 [recipient_n]
1093 a security problem was detected [ID of detected content type].
1094 The message was not accepted.
1095 Message identifier: [PEC msgid of corresponding
1096 PEC transport envelope]
1097
1098 The same certification data is inserted in an XML file added to the
1099 notification to allow for automatic checks (<a href="#section-4.4">section 4.4</a>). Parsing
1100 MUST be done on the XML part only. Additional parts MAY be included
1101 by the provider for provider-specific services. Regardless, the
1102 original message MUST NOT be included. The message MUST follow the
1103 format described in <a href="#section-4.3">section 4.3</a>.
1104
1105 <span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a>. Server-User Acceptance PEC Notification</span>
1106
1107 The server-user acceptance PEC notification is a message sent to the
1108 sender by his server, containing date and time of message acceptance
1109 into the system, sender and recipient data, and subject.
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Petrucci, et al. Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1119
1120
1121 The header contains the following fields:
1122
1123 X-Ricevuta: accettazione
1124 Date: [actual date of server-user acceptance]
1125 Subject: ACCETTAZIONE: [original subject]
1126 From: posta-certificata@[mail domain]
1127 To: [original sender]
1128 X-Riferimento-Message-ID: [msgid]
1129
1130 The message body contains a text part that constitutes the
1131 notification in readable format, according to a model that relates
1132 the following information:
1133
1134 Server-User Acceptance PEC notification
1135 On [date] at [time] ([time zone]), the message "[subject]"
1136 originating from "[original sender]" and addressed to:
1137 [recipient_1] (["certified mail" | "ordinary mail"])
1138 [recipient_2] (["certified mail" | "ordinary mail"])
1139 [recipient_n] (["certified mail" | "ordinary mail"])
1140 was accepted by the system and forwarded to the recipient(s).
1141 Message identifier: [PEC msgid of corresponding
1142 PEC transport envelope]
1143
1144 The same certification data is inserted in an XML file added to the
1145 notification message, allowing automatic checks on it (<a href="#section-4.4">section 4.4</a>).
1146 Parsing MUST be done on the XML part only. Additional parts MAY be
1147 included by the provider for provider-specific services. The message
1148 MUST follow the format described in <a href="#section-4.3">section 4.3</a>.
1149
1150 <span class="h4"><a class="selflink" id="section-3.1.5" href="#section-3.1.5">3.1.5</a>. PEC Transport Envelope</span>
1151
1152 A PEC transport envelope is a message generated by the Access Point
1153 that contains the original message as well as certification data.
1154
1155 As mentioned in <a href="#section-2.1.1.2">section 2.1.1.2</a>, the PEC transport envelope inherits
1156 from the original message the values of the following header fields,
1157 which MUST be related unmodified:
1158
1159 o Received:
1160
1161 o To:
1162
1163 o Cc:
1164
1165 o Return-Path:
1166
1167 o Reply-To: (if present)
1168
1169
1170
1171
1172 <span class="grey">Petrucci, et al. Informational [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1175
1176
1177 On the other hand, the following fields MUST be modified, or inserted
1178 if necessary:
1179
1180 X-Trasporto: posta-certificata
1181 Date: [actual date of server-user acceptance]
1182 Subject: POSTA CERTIFICATA: [original subject]
1183 From: "On behalf of: [original sender]"
1184 &lt;certified-mail@[mail_domain]&gt;
1185 Reply-To: [original sender] (inserted only if not present)
1186 Message-ID: [PEC msgid generated as in <a href="#section-2.2.1">section 2.2.1</a>]
1187 X-Riferimento-Message-ID: [msgid]
1188 X-TipoRicevuta: [completa/breve/sintetica]
1189
1190 The "X-TipoRicevuta:" field indicates the type of delivery PEC
1191 notification the sender wishes to receive -- complete, brief, or
1192 concise.
1193
1194 The body of the PEC transport envelope contains a text part that
1195 constitutes the readable format of the message according to a model
1196 that relates the following certification data:
1197
1198 Certified mail message
1199 On [date] at [time] ([time zone]), the message "[subject]" was
1200 sent by "[original sender]" and addressed to:
1201 [recipient_1]
1202 [recipient_2]
1203 [recipient_n]
1204 The original message is included in attachment.
1205 Message identifier: [PEC msgid of corresponding
1206 PEC transport envelope]
1207
1208 Within the PEC transport envelope, the entire, non-modified original
1209 message is inserted in a format compliant with [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] (except for
1210 what has been said regarding the message identifier), as well as an
1211 XML part, which contains the certification data that was already
1212 related in text format, and information on the type of message and
1213 PEC notification requested (<a href="#section-4.4">section 4.4</a>). Parsing MUST be done on
1214 the XML part only. Additional parts MAY be included by the provider
1215 for provider-specific services. The message MUST follow the format
1216 described in <a href="#section-4.3">section 4.3</a>.
1217
1218 Note that the routing data of the PEC transport envelope (forward and
1219 reverse paths) remain unaltered.
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Petrucci, et al. Informational [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1231
1232
1233 <span class="h4"><a class="selflink" id="section-3.1.6" href="#section-3.1.6">3.1.6</a>. Timeout Delivery Error PEC Notification</span>
1234
1235 If the sending provider doesn't receive a server-server acceptance or
1236 delivery PEC notification from the receiving provider within 12 hours
1237 of the message dispatch, it informs the user that the recipient's
1238 provider might not be able to deliver the message. In case the
1239 sending provider doesn't receive a delivery PEC notification within
1240 24 hours after message dispatch, it emits another non-delivery PEC
1241 notification to the user by the 24-hour timeout, but not before 22
1242 hours have passed.
1243
1244 Such a communication takes place through a PEC notification of non-
1245 delivery due to timeout, the header of which contains the following
1246 fields:
1247
1248 X-Ricevuta: preavviso-errore-consegna
1249 Date: [date of notification emission]
1250 Subject: AVVISO DI MANCATA CONSEGNA PER SUP. TEMPO MASSIMO:
1251 [original subject]
1252 From: posta-certificata@[mail domain]
1253 To: [original recipient]
1254 X-Riferimento-Message-ID: [msgid]
1255
1256 The body of the first non-delivery PEC notification (12-hour timeout)
1257 contains a text part that represents the readable format of the
1258 notification which will relate the following data:
1259
1260 Non-delivery PEC notification
1261 On [date] at [time] ([time zone]), the message
1262 "[subject]" originating from "[original sender]"
1263 and addressed to "[recipient]"
1264 has not been delivered within the first 12 hours following
1265 its dispatch. Not excluding that the message might eventually
1266 be delivered, it is deemed useful to consider that dispatch
1267 might not have a positive outcome. The system will see to
1268 sending another non-delivery PEC notification if in the
1269 following twelve hours no confirmation is received from the
1270 recipient.
1271 Message identifier: [PEC msgid of corresponding
1272 PEC transport envelope]
1273
1274 On the other hand, 24-hour-timeout induced PEC notifications, which
1275 have the same header as described above, will have the following text
1276 in their body:
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Petrucci, et al. Informational [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1287
1288
1289 Non-delivery PEC notification
1290 On [date] at [time] ([time zone]), the message
1291 "[subject]" originating from "[original sender]"
1292 and addressed to "[recipient]"
1293 has not been delivered within 24 hours of its dispatch.
1294
1295 The transaction is deemed to be considered terminated with a
1296 negative outcome.
1297 Message identifier: [PEC msgid of corresponding
1298 PEC transport envelope]
1299
1300 The same certification data is inserted in an XML file added to both
1301 PEC notification types to allow automatic checks (<a href="#section-4.4">section 4.4</a>).
1302
1303 Parsing MUST be done on the XML part only. Additional parts MAY be
1304 added for services supplied by the PEC provider. Regardless, the
1305 original message MUST NOT be included. The message MUST follow the
1306 format described in <a href="#section-4.3">section 4.3</a>.
1307
1308 A timeout PEC notification is generated if one of the following
1309 scenarios occurs:
1310
1311 o the sending provider receives a server-server acceptance PEC
1312 notification during the first 12 hours following message dispatch,
1313 but does not receive a delivery PEC notification at all. In this
1314 case, it would be a 24-hour timeout PEC notification.
1315
1316 o the sending provider does not receive a server-server acceptance
1317 PEC notification, but receives a delivery PEC notification after
1318 12 hours and before the 24-hour timeout. In this case it would be
1319 a 12-hour timeout PEC notification.
1320
1321 o the sending provider doesn't receive either a server-server
1322 acceptance or a delivery PEC notification. In this case, two
1323 timeout PEC notifications are generated; a 12-hour and a 24-hour
1324 timeout PEC notification.
1325
1326 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Incoming Point</span>
1327
1328 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Server-Server Acceptance PEC Notification</span>
1329
1330 When correct PEC transport envelopes (as defined in <a href="#section-2.2.2">section 2.2.2</a>.)
1331 are exchanged between PEC providers, the receiver MUST send a server-
1332 server acceptance PEC notification to the sender. The single
1333 dispatched notification concerns all recipients who belong to the
1334 same provider, and to whom the incoming message was addressed, as
1335 stated in the routing data (forward and reverse paths) of the SMTP
1336 transaction. Within the certification data of a single server-server
1337
1338
1339
1340 <span class="grey">Petrucci, et al. Informational [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1343
1344
1345 acceptance PEC notification, all recipients of the message to which
1346 it refers are listed. In general, when receiving a PEC transport
1347 envelope, each provider MUST emit one or more server-server
1348 acceptance PEC notifications to cover, in absence of SMTP transport
1349 errors, all the recipients in its jurisdiction.
1350
1351 The header of a server-server acceptance PEC notification contains
1352 the following fields:
1353
1354 X-Ricevuta: presa-in-carico
1355 Date: [date of server-server acceptance]
1356 Subject: PRESA IN CARICO: [original subject]
1357 From: posta-certificata@[mail domain]
1358 To: [sender provider service mailbox]
1359 X-Riferimento-Message-ID: [msgid]
1360
1361 The provider's service email address is obtained from the PEC
1362 providers directory during the necessary queries made in the
1363 signature verification stage.
1364
1365 The body contains a text part that follows the underlying model:
1366
1367 Server-server acceptance PEC notification
1368 On [date] at [time] ([time zone]), the message "[subject]"
1369 originating from "[original sender]" and addressed to:
1370 [recipient_1]
1371 [recipient_2]
1372 [recipient_n]
1373 was accepted by the system.
1374 Message identifier: [PEC msgid of corresponding
1375 PEC transport envelope]
1376
1377 The same certification data is inserted in an XML file which is added
1378 to the notification message to allow for automatic checks (<a href="#section-4.4">section</a>
1379 <a href="#section-4.4">4.4</a>). Parsing MUST be done on the XML part only. Additional parts
1380 MAY be added by the provider for provider-specific services. The
1381 message MUST follow the format described in <a href="#section-4.3">section 4.3</a>.
1382
1383 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. PEC Anomaly Envelope</span>
1384
1385 If the tests on an incoming message detect an error, or the message
1386 is identified as being ordinary mail and the provider is set to
1387 forward it to the recipient, the system MUST insert such a message in
1388 a PEC anomaly envelope. Before delivery, the entire message received
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Petrucci, et al. Informational [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1399
1400
1401 at the Incoming Point is inserted in a format compliant with [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
1402 as a [<a href="#ref-MIME1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">MIME1</a>] part inside a new message that MUST inherit the
1403 unmodified values for the following header fields from the received
1404 message:
1405
1406 o Received:
1407
1408 o To:
1409
1410 o Cc:
1411
1412 o Return-Path:
1413
1414 o Message-ID:
1415
1416 Whereas, the following header fields MUST be modified or inserted:
1417
1418 X-Trasplorto: errore
1419 Date: [mlessage arrival date]
1420 Subject: ANOMALIA MESSAGGIO: [original subject]
1421 From: "On behalf of: [original sender]"
1422 &lt;posta-certificata@[mail_domain]&gt;
1423 Reply-To: [original sender (inserted only if not already
1424 present)]
1425
1426 The body contains a user-readable text part according to a model that
1427 relates the following data:
1428
1429 Message anomaly
1430 On [date] at [time] ([time zone]), the message "[subject]"
1431 originating from "[original sender]" and addressed to:
1432 [recipient_1]
1433 [recipient_2]
1434 [recipient_n]
1435 was received.
1436 The data has not been certified due to the following error:
1437 [concise description of error]
1438 The original message is attached.
1439
1440 Due to uncertainty regarding origin and/or conformity of the message
1441 received, the PEC anomaly envelope MUST NOT contain [<a href="#ref-MIME1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">MIME1</a>] parts
1442 other than the entire message that arrived at the Incoming Point.
1443
1444 Note that the routing data of such an envelope (forward and reverse
1445 paths) remain unaltered. Doing so guarantees both message forwarding
1446 to the recipients, and reception of SMTP error notifications, if any
1447 occur, by the sender (as specified in [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>] and [<a href="#ref-SMTP-DSN" title="&quot;Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)&quot;">SMTP-DSN</a>]).
1448
1449
1450
1451
1452 <span class="grey">Petrucci, et al. Informational [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1455
1456
1457 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Virus Detection PEC Notification</span>
1458
1459 If the Incoming Point receives virus-infected PEC messages, it MUST
1460 NOT forward them. Rather it MUST inform the sending provider, which
1461 will in turn inform the sending user, of the failed transmission. A
1462 separate PEC notification of virus detection MUST be sent on behalf
1463 of every recipient within the provider's domain.
1464
1465 In case a virus is detected during the reception phase of a message
1466 whose origin was asserted through sender signature verification, the
1467 system generates a virus-detected PEC notification indicating the
1468 error found, and sends it to the sending provider's service mailbox.
1469
1470 The header of this PEC notification contains the following fields:
1471
1472 X-Ricevuta: rilevazione-virus
1473 X-Mittente: [original sender]
1474 Date: [date of notification emission]
1475 Subject: PROBLEMA DI SICUREZZA: [original subject]
1476 From: posta-certificata@[mail domain]
1477 To: [sender provider notifications]
1478 X-Riferimento-Message-ID: [msgid]
1479
1480 The body contains a readable text part according to a model that
1481 relates the following data:
1482
1483 Virus detection PEC notification
1484 On [date] at [time] ([time zone]), in the message "[subject]"
1485 originating from "[original sender]" and addressed to
1486 "[recipient]"
1487 a security problem was detected [ID of content type detected].
1488 Message identifier: [PEC msgid of corresponding
1489 PEC transport envelope]
1490
1491 The same certification data is inserted in an XML file and added to
1492 the notification to allow for automatic checks (<a href="#section-4.4">section 4.4</a>).
1493 Parsing MUST be done on the XML part only. Additional parts MAY be
1494 included by the provider for provider-specific services. Regardless,
1495 the original message MUST NOT be included. The message MUST follow
1496 the format described in <a href="#section-4.3">section 4.3</a>.
1497
1498 The message body MUST contain the reason for which the transmission
1499 could not be completed.
1500
1501
1502
1503
1504
1505
1506
1507
1508 <span class="grey">Petrucci, et al. Informational [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1511
1512
1513 <span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Virus-Induced Delivery Error PEC notification</span>
1514
1515 At the reception of a virus detection PEC notification from the
1516 receiving provider, the sender provider emits a non-delivery PEC
1517 notification to the sending user.
1518
1519 The header for this notification contains the following fields:
1520
1521 X-Ricevuta: errore-consegna
1522 X-VerificaSicurezza: errore
1523 Date: [date of notification emission]
1524 Subject: AVVISO DI MANCATA CONSEGNA PER VIRUS: [original
1525 subject]
1526 From: posta-certificata@[mail domain]
1527 To: [original sender]
1528 X-Riferimento-Message-ID: [msgid]
1529
1530 The body contains a readable text part according to a model that
1531 relates the following data:
1532
1533 Delivery error PEC notification due to virus
1534 On [date] at [time] ([time zone]), in the message "[subject]"
1535 addressed to "[recipient]"
1536 a security problem was detected [ID of content type detected
1537 by the anti-virus].
1538 The message was not delivered.
1539 Message identifier: [PEC msgid of corresponding
1540 PEC transport envelope]
1541
1542 All the information necessary for the construction of such a PEC
1543 notification can be obtained from the correlated virus-detected PEC
1544 notification.
1545
1546 The same certification data is inserted in an XML file and added to
1547 the notification message to allow for automatic checks (<a href="#section-4.4">section 4.4</a>).
1548 Parsing MUST be done on the XML part only. Additional parts MAY be
1549 included by the provider for provider-specific services. The reason
1550 the transaction was not completed MUST be specified in the message,
1551 which MUST follow the format described in <a href="#section-4.3">section 4.3</a>.
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564 <span class="grey">Petrucci, et al. Informational [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1567
1568
1569 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Delivery Point</span>
1570
1571 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Checks on Incoming Messages</span>
1572
1573 When a message arrives at the Delivery Point, the system verifies:
1574
1575 o message type
1576
1577 o whether or not a PEC notification has to be returned.
1578
1579 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Delivery PEC Notification</span>
1580
1581 A delivery PEC notification is issued only after a correct PEC
1582 transport envelope (sections <a href="#section-2.2.2">2.2.2</a> and <a href="#section-3.1.5">3.1.5</a>) has been delivered to
1583 the recipient's mailbox.
1584
1585 In all other cases (e.g., PEC anomaly envelopes, PEC notifications),
1586 the delivery PEC notification is not issued. Regardless, the message
1587 received at the Delivery Point MUST be delivered to the recipient's
1588 mailbox unchanged.
1589
1590 This notification tells the user that his/her message has been
1591 successfully delivered to the specified recipient. It includes
1592 readable text that certifies the date and time of delivery, sender
1593 and receiver data, and the subject. It also contains an XML
1594 certification data file and other optional parts for functionalities
1595 offered by the provider.
1596
1597 The following fields are inserted in the header:
1598
1599 X-Ricevuta: avvenuta-consegna
1600 Date: [delivery date]
1601 Subject: CONSEGNA: [original subject]
1602 From: posta-certificata@[mail domain]
1603 To: [original sender]
1604 X-Riferimento-Message-ID: [msgid]
1605
1606 The value of the "X-TipoRicevuta:" header field in the PEC transport
1607 envelope is derived from the original message, thus allowing the
1608 sender to determine the type of delivery PEC notification requested
1609 from the primary recipients of the original message. The
1610 notification MUST follow the format described in <a href="#section-4.3">section 4.3</a>.
1611
1612 <span class="h5"><a class="selflink" id="section-3.3.2.1" href="#section-3.3.2.1">3.3.2.1</a>. Delivery PEC Notification: Complete</span>
1613
1614 This is the default value for delivery PEC notifications. When no
1615 value for "X-TipoRicevuta:" is specified, or when it contains the
1616 value "completa" (complete), the system will require a complete
1617
1618
1619
1620 <span class="grey">Petrucci, et al. Informational [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1623
1624
1625 delivery PEC notification from addressees in the "To:" field, while a
1626 concise PEC notification (<a href="#section-3.3.2.3">section 3.3.2.3</a>) will be required from
1627 those in the "Cc:" field. The distinction between primary recipients
1628 and those in carbon copy is done through an analysis of the "To:" and
1629 "Cc:" fields. For PEC notifications sent on behalf of primary
1630 recipients, a complete copy of the original message along with any
1631 attachments is inserted in the notification. In case the system in
1632 charge of delivery is not able to determine the recipient type due to
1633 ambiguity problems in the "To:" and "Cc:" fields, delivery MUST be
1634 considered as if addressed to a primary recipient and include the
1635 complete copy of the original message.
1636
1637 The notification body contains a readable text part that relates
1638 certification data according to the following model:
1639
1640 Delivery PEC notification
1641 On [date] at [time] ([time zone]), the message "[subject]"
1642 originating from "[original sender]" and addressed to
1643 "[recipient]"
1644 was placed in the destination's mailbox.
1645 Message identifier: [PEC msgid of corresponding
1646 PEC transport envelope]
1647
1648 The same certification data is inserted in an XML file and added to
1649 the notification (<a href="#section-4.4">section 4.4</a>), along with any other parts that MAY
1650 be inserted by the provider for provider-specific services. Parsing
1651 MUST be done on the XML part only. The delivery PEC notification
1652 MUST be issued on behalf of every recipient of the message, and MUST
1653 follow the format described in <a href="#section-4.3">section 4.3</a>.
1654
1655 <span class="h5"><a class="selflink" id="section-3.3.2.2" href="#section-3.3.2.2">3.3.2.2</a>. Delivery PEC Notification: Brief</span>
1656
1657 In order to decrease the amount of data flowing, it is possible for
1658 the sender to ask for a delivery PEC notification in "brief" format.
1659 The brief delivery PEC notification contains the original message and
1660 a ciphered hash value for each of its parts. The hash value SHOULD
1661 be calculated on base64 encoded parts. As specified in <a href="#section-5.3">section 5.3</a>,
1662 PEC messages MUST transit only on machines that belong to the PEC
1663 network and that MUST NOT alter the encoding of the message during
1664 its transition/processing.
1665
1666 NOTE: Even though PEC uses these relaxed specifications, PEC
1667 interoperability tests between over 20 service providers have never
1668 revealed any problems. This is probably due to mail servers leaning
1669 more towards leaving the messages they receive intact without
1670
1671
1672
1673
1674
1675
1676 <span class="grey">Petrucci, et al. Informational [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1679
1680
1681 applying any changes. But issues might arise if a server decides to
1682 modify encoded parts; for example, change the base64 line length,
1683 whose hash value calculated at the receiver's end would then differ
1684 from that at the sender's side.
1685
1686 To be able to verify the transmitted contents it is necessary for the
1687 sender to keep the unaltered original copy of the part(s) to which
1688 the hash values refer.
1689
1690 If the PEC transport envelope contains the header:
1691
1692 X-TipoRicevuta: breve
1693
1694 the Delivery Point emits a brief delivery PEC notification on behalf
1695 of the primary recipients, and a concise one (<a href="#section-3.3.2.3">section 3.3.2.3</a>) on
1696 behalf of carbon copy recipients. The value of the header field in
1697 the PEC transport envelope is derived from the original message.
1698
1699 The notification body contains a readable text part according to a
1700 model that relates the following certification data:
1701
1702 Brief delivery PEC notification
1703 On [date] at [time] ([time zone]), the message "[subject]"
1704 originating from "[original sender]" and addressed to
1705 "[recipient]"
1706 was placed in the destination's mailbox.
1707 Message identifier: [PEC msgid of corresponding
1708 PEC transport envelope]
1709
1710 The same certification data is inserted in an XML file and added to
1711 the notification (<a href="#section-4.4">section 4.4</a>), along with other parts that MAY be
1712 included for specific provider-supplied services. Parsing MUST be
1713 done on the XML part only. The delivery PEC notification is issued
1714 on behalf of every recipient of the message, and MUST follow the
1715 format described in <a href="#section-4.3">section 4.3</a>.
1716
1717 The MIME structure of the original message is unaltered as it is
1718 added to the notification, but each MIME part with a "name" parameter
1719 in the header field "Content-Type:" or a "filename" parameter in the
1720 header field "Content-Disposition:" MUST be substituted by a text
1721 file containing that MIME part's hash value.
1722
1723 When the original message has an S/MIME format, it is necessary not
1724 to alter the integrity of the message structure. Verification of the
1725 S/MIME part in the original message takes place when the MIME type of
1726 the top-level entity (which coincides with the message itself) is
1727 checked. An S/MIME message MAY have the following MIME types (as per
1728 [<a href="#ref-SMIMEV3" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification&quot;">SMIMEV3</a>]):
1729
1730
1731
1732 <span class="grey">Petrucci, et al. Informational [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1735
1736
1737 o multipart/signed
1738
1739 Represents an original message signed by the sender using the
1740 structure described in [<a href="#ref-MIME-SECURE" title="&quot;Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted&quot;">MIME-SECURE</a>]. The message is made up of
1741 two MIME parts: the first is the message itself before the
1742 application of the sender's signature, whereas the second contains
1743 signature data. The second part (generally of type
1744 "application/pkcs7-signature" or "application/x-pkcs-signature")
1745 contains data added during the signing phase and MUST be left
1746 unchanged to avoid compromising the overall message structure;
1747
1748 o "application/pkcs7-mime" or "application/x-pkcs7-mime"
1749
1750 The message is composed of a sole CMS object within the MIME part.
1751 Given that attachments cannot be separated from the CMS object,
1752 the MIME part is left intact (i.e., it is not replaced by the hash
1753 value); therefore, the brief PEC notification is the same as the
1754 complete PEC notification.
1755
1756 If the original message contains parts whose "Content-Type:" is
1757 "message/rfc822", i.e., contains an email message as attachment, the
1758 entire attached message is substituted with its corresponding hash
1759 value.
1760
1761 Therefore, when emitting a brief delivery PEC notification, the
1762 provider MUST:
1763
1764 1. identify and extract all the parts from the first MIME part of the
1765 multipart/signed S/MIME message;
1766
1767 2. calculate the hash values of all the files attached by the sender
1768 to the original message;
1769
1770 3. substitute originals with their hash values.
1771
1772 In general, in the case of original messages in S/MIME format, the
1773 copy of the message inserted within the brief delivery PEC
1774 notification will have the following characteristics:
1775
1776 o if the original message is signed, the S/MIME structure and
1777 signature-relative data will remain unchanged. The message will
1778 generate an error in a future signature integrity verification
1779 phase following the substitution of attachments with the
1780 corresponding hash values.
1781
1782 o if the original message contains the "application/pkcs7-mime" or
1783 "application/x-pkcs7-mime" MIME type, attachments present in the
1784 message will not be substituted by their hash values, due to
1785
1786
1787
1788 <span class="grey">Petrucci, et al. Informational [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1791
1792
1793 impossibility of identification within a CMS structure. The
1794 content of the brief delivery PEC notification will coincide with
1795 that of a normal delivery PEC notification.
1796
1797 The algorithm used for hash calculation is the [<a href="#ref-SHA1" title="&quot;US Secure Hash Algorithm 1 (SHA1)&quot;">SHA1</a>], calculated on
1798 the entire content of the part. To allow distinction between hash
1799 files and the files to which they refer, the suffix ".hash" is added
1800 to the original filename. The hash value is written in the file
1801 using a hexadecimal representation as a single sequence of 40
1802 characters. The MIME type of these attachments is set to
1803 "text/plain" to highlight their textual nature.
1804
1805 <span class="h5"><a class="selflink" id="section-3.3.2.3" href="#section-3.3.2.3">3.3.2.3</a>. Delivery PEC Notification: Concise</span>
1806
1807 If the PEC transport envelope contains the header:
1808
1809 X-TipoRicevuta: sintetica
1810
1811 the Delivery Point emits, both to primary and carbon copy recipients,
1812 a concise delivery PEC notification that does not contain the
1813 original message.
1814
1815 The message body of the notification contains a readable text part
1816 according to a model that relates the following certification data:
1817
1818 Concise delivery PEC notification
1819 On [date] at [time] ([time zone]), the message "[subject]"
1820 originating from "[original sender]" and addressed to
1821 "[recipient]"
1822 was placed in the destination's mailbox.
1823 Message identifier: [PEC msgid of corresponding
1824 PEC transport envelope]
1825
1826 The same certification data is inserted within an XML file and added
1827 to the notification (<a href="#section-4.4">section 4.4</a>), along with additional parts that
1828 MAY be included for provider-specific services. Parsing MUST be done
1829 on the XML part only. The notification is sent to each one of the
1830 recipients to whom the message is delivered, and MUST follow the
1831 format described in <a href="#section-4.3">section 4.3</a>.
1832
1833 The concise delivery PEC notification follows the same emission rules
1834 as the delivery PEC notification; added to it is only the XML file
1835 containing the certification data, not the original message.
1836
1837
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Petrucci, et al. Informational [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1847
1848
1849 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. Non-Delivery PEC Notification</span>
1850
1851 If an error occurs during the delivery of a correct PEC transport
1852 message, the system returns to the sender a non-delivery PEC
1853 notification that indicates the error condition.
1854
1855 The header will contain the following fields:
1856
1857 X-Ricevuta: errore-consegna
1858 Date: [date of notification emission]
1859 Subject: AVVISO DI MANCATA CONSEGNA: [original subject]
1860 From: posta-certificata@[mail domain]
1861 To: [original sender]
1862 X-Riferimento-Message-ID: [msgid]
1863
1864 The notification body contains a readable text part according to a
1865 model that relates the following data:
1866
1867 Non-delivery PEC notification
1868 On [date] at [time] ([time zone]), in the message "[subject]"
1869 originating from "[original sender]" and addressed to
1870 "[recipient]"
1871 an error was detected [brief error description].
1872 The message was refused by the system.
1873 Message identifier: [PEC msgid of corresponding
1874 PEC transport envelope]
1875
1876 The same certification data is inserted within an XML file and added
1877 to the notification in order to allow for automatic checks (<a href="#section-4.4">section</a>
1878 <a href="#section-4.4">4.4</a>). Parsing MUST be done on the XML part only. Additional parts
1879 MAY be included by the PEC provider for provider-specific services.
1880 The notification MUST follow the format described in <a href="#section-4.3">section 4.3</a>.
1881
1882 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Sender and Receiver Belonging to the Same Domain</span>
1883
1884 PEC messages MUST be processed even if both sender and receiver(s)
1885 belong to the same PEC domain.
1886
1887 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Example: Complete Transaction between Two PEC Domains</span>
1888
1889 A correct transaction between two PEC domains goes through the
1890 following steps:
1891
1892 o The sending user sends an email to his provider's Access Point;
1893
1894 o The Access Point runs all checks and emits a server-user
1895 acceptance PEC notification to the user;
1896
1897
1898
1899
1900 <span class="grey">Petrucci, et al. Informational [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1903
1904
1905 o The Access Point creates a PEC transport envelope and forwards it
1906 to the Incoming Point of the receiving provider;
1907
1908 o The receiver's Incoming Point verifies the PEC transport envelope
1909 and creates a server-server acceptance PEC notification to be sent
1910 to the sending provider;
1911
1912 o The sender's Incoming Point verifies the validity of the server-
1913 server acceptance PEC notification and forwards it to the Delivery
1914 Point;
1915
1916 o The sender's Delivery Point saves the server-server acceptance PEC
1917 notification in the provider's service mailbox;
1918
1919 o The receiver's Incoming Point forwards the PEC transport envelope
1920 to the receiver's Delivery Point;
1921
1922 o The receiver's Delivery Point verifies the contents of the PEC
1923 transport envelope and saves it in the recipient's mailbox;
1924
1925 o The receiver's Delivery Point creates a delivery PEC notification
1926 and sends it to the sender's Incoming Point;
1927
1928 o The sender's Incoming Point verifies the validity of the delivery
1929 PEC notification and forwards it to the sender's Delivery Point;
1930
1931 o The sender's Delivery Point saves the delivery PEC notification in
1932 the sending user's mailbox;
1933
1934 o The receiving user has the message at his disposition.
1935
1936 NOTE: Some of these steps might occur in parallel, thus the
1937 interaction might complete in a different order.
1938
1939 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Formats</span>
1940
1941 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Temporal Reference</span>
1942
1943 For all operations carried out during message, notification, and log
1944 elaboration processes by the Access, Incoming, and Delivery Points,
1945 it is necessary to have an accurate temporal reference available.
1946 All events (generation of PEC notifications, transport envelopes,
1947 logs, etc.) that constitute the transaction of message elaboration at
1948 the Access, Incoming, and Delivery Points MUST employ a sole temporal
1949 value obtained from within the transaction itself.
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Petrucci, et al. Informational [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
1959
1960
1961 Doing this renders the instant of message elaboration unambiguous
1962 within PEC logs, notifications, messages, etc., generated by the
1963 server.
1964
1965 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. User Date/Time</span>
1966
1967 Temporal indications supplied by the service in readable format (text
1968 in PEC notifications, transport envelopes, etc.) are provided with
1969 reference to the legal time at the moment of the operation.
1970 Following is the specification using the syntax description notation
1971 defined in [<a href="#ref-ABNF" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">ABNF</a>].
1972
1973 date-fullyear = 4DIGIT
1974 date-month = 2DIGIT ; 01-12
1975 date-mday = 2DIGIT ; 01-28, 01-29, 01-30, 01-31 based on
1976 ; month/year
1977 time-hour = 2DIGIT ; 00-23
1978 time-minute = 2DIGIT ; 00-59
1979 time-second = 2DIGIT ; 00-58, 00-59, 00-60 based on leap second
1980 ; rules
1981
1982 time-offset = "(" ("+" / "-") time-hour ":" time-minute ")"
1983
1984 partial-time = time-hour ":" time-minute ":" time-second
1985
1986 full-date = date-mday "/" date-month "/" date-fullyear
1987 full-time = partial-time time-offset
1988
1989 NOTE: For number of days in a month, leap year, and leap second
1990 restrictions see section 5.7 of [<a href="#ref-TIMESTAMP" title="&quot;Date and Time on the Internet: Timestamps&quot;">TIMESTAMP</a>].
1991
1992 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Format of a PEC Message Body</span>
1993
1994 This section describes the characteristics of the various components
1995 of PEC messages and notifications generated by a PEC system. If one
1996 of the message parts contains characters with values outside of the
1997 range 0-127 (7-bit ASCII), that part will have to be adequately
1998 encoded so that 7-bit transportation compatibility is guaranteed
1999 (e.g., quoted-printable, base64 as per [<a href="#ref-MIME1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">MIME1</a>]).
2000
2001 Before applying the signature, the message body has Content-Type:
2002 multipart/mixed. Each part is described in the sections below. The
2003 first part is the user readable text generated by the PEC system,
2004 while the second and third parts are interchangeable in order and
2005 contain the original message and the XML file for the certification
2006 data.
2007
2008
2009
2010
2011
2012 <span class="grey">Petrucci, et al. Informational [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2015
2016
2017 <span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. User Readable Text</span>
2018
2019 Character set: ISO-8859-1 (Latin-1)
2020 MIME type: text/plain or multipart/alternative
2021
2022 The multipart/alternative MIME type MAY be used to add an HTML
2023 version of the body of system-generated messages. In this case, two
2024 sub-parts MUST be present: one of type text/plain, the other
2025 text/html. For the HTML part:
2026
2027 o it MUST contain the same information as related in the text part;
2028
2029 o it MUST NOT contain references to elements (e.g., images, sounds,
2030 font, style sheets), neither internal to the message (added MIME
2031 parts) nor external (e.g., hosted on the provider's server);
2032
2033 o it MUST NOT have active content (e.g., JavaScript, VBscript, Plug-
2034 in, ActiveX).
2035
2036 <span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. Original Message</span>
2037
2038 MIME type: message/rfc822
2039 Attachment name: postacert.eml
2040
2041 <span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. Certification Data</span>
2042
2043 Character set: UTF-8
2044 MIME type: application/xml
2045 Attachment name: certdata.xml
2046
2047 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Certification Data Scheme</span>
2048
2049 Following is the DTD relative to the [<a href="#ref-XML" title="&quot;Extensible Markup Language (XML) 1.0 (Fifth Edition)&quot;">XML</a>] file that contains
2050 certification data attached to PEC notifications.
2051
2052 &lt;!--Use the element "postacert" as root--&gt;
2053 &lt;!--"tipo" indicates the typology of the PEC message--&gt;
2054 &lt;!--The attribute "errore" can have the following values--&gt;
2055 &lt;!--"nessuno" = no error--&gt;
2056 &lt;!--"no-dest" (with type="errore-consegna") = --&gt;
2057 &lt;!-- wrong recipient--&gt;
2058 &lt;!--"no-dominio" (with type="errore-consegna") = --&gt;
2059 &lt;!-- wrong domain--&gt;
2060 &lt;!--"virus" (with type="errore-consegna") = virus--&gt;
2061 &lt;!--"virus" (with type="non-accettazione") = virus--&gt;
2062 &lt;!--"altro" = generic error--&gt;
2063 &lt;!ELEMENT postacert (intestazione, dati)&gt;
2064 &lt;!ATTLIST postacert
2065
2066
2067
2068 <span class="grey">Petrucci, et al. Informational [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2071
2072
2073 tipo (accettazione |
2074 non-accettazione |
2075 presa-in-carico |
2076 avvenuta-consegna |
2077 posta-certificata |
2078 errore-consegna |
2079 preavviso-errore-consegna |
2080 rilevazione-virus) #REQUIRED
2081 errore (nessuno |
2082 no-dest |
2083 no-dominio |
2084 virus |
2085 altro) "nessuno"&gt;
2086
2087 &lt;!--Header of the original message--&gt;
2088 &lt;!ELEMENT intestazione (mittente,
2089 destinatari+,
2090 risposte,
2091 oggetto?)&gt;
2092
2093 &lt;!--Sender ("From:" field) of the original message--&gt;
2094 &lt;!ELEMENT mittente (#PCDATA)&gt;
2095
2096 &lt;!--Complete list of recipients ("To:" and "Cc:" fields)--&gt;
2097 &lt;!--of the original message--&gt;
2098 &lt;!--"tipo" indicates the typology of the recipient--&gt;
2099 &lt;!ELEMENT destinatari (#PCDATA)&gt;
2100 &lt;!ATTLIST destinatari
2101 tipo (certificato | esterno) "certificato"&gt;
2102
2103 &lt;!--Value of the "Reply-To:" field of the original message--&gt;
2104 &lt;!ELEMENT risposte (#PCDATA)&gt;
2105 &lt;!--Value of the "Subject:" field of the original message--&gt;
2106 &lt;!ELEMENT oggetto (#PCDATA)&gt;
2107
2108 &lt;!--PEC message data--&gt;
2109 &lt;!ELEMENT dati (gestore-emittente,
2110 data,
2111 identificativo,
2112 msgid?,
2113 ricevuta?,
2114 consegna?,
2115 ricezione*,
2116 errore-esteso?)&gt;
2117
2118 &lt;!--Descriptive string of the provider that certifies --&gt;
2119 &lt;!--the data--&gt;
2120 &lt;!ELEMENT gestore-emittente (#PCDATA)&gt;
2121
2122
2123
2124 <span class="grey">Petrucci, et al. Informational [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2127
2128
2129 &lt;!--Date/time of message elaboration--&gt;
2130 &lt;!--"zona" is the difference between local time and UTC in --&gt;
2131 &lt;!--"[+|-]hhmm" format--&gt;
2132 &lt;!ELEMENT data (giorno, ora)&gt;
2133 &lt;!ATTLIST data
2134 zona CDATA #REQUIRED&gt;
2135
2136 &lt;!--Day in "dd/mm/yyyy" format--&gt;
2137 &lt;!ELEMENT giorno (#PCDATA)&gt;
2138 &lt;!--Local hour in "hh:mm:ss" format--&gt;
2139 &lt;!ELEMENT ora (#PCDATA)&gt;
2140
2141 &lt;!--PEC msgid--&gt;
2142 &lt;!ELEMENT identificativo (#PCDATA)&gt;
2143
2144 &lt;!--msgid of the original message before modifications--&gt;
2145 &lt;!ELEMENT msgid (#PCDATA)&gt;
2146
2147 &lt;!--For PEC transport envelopes and delivery notifications--&gt;
2148 &lt;!--indicate the type of PEC notification requested by the--&gt;
2149 &lt;!--sender--&gt;
2150 &lt;!ELEMENT ricevuta EMPTY&gt;
2151 &lt;!ATTLIST ricevuta
2152 tipo (completa |
2153 breve |
2154 sintetica ) #REQUIRED&gt;
2155
2156 &lt;!--For delivery, non-delivery, virus-induced non-delivery, --&gt;
2157 &lt;!-- virus detection, and timeout PEC notifications--&gt;
2158 &lt;!--Recipient address to which delivery has been carried --&gt;
2159 &lt;!--out/tried--&gt;
2160 &lt;!ELEMENT consegna (#PCDATA)&gt;
2161 &lt;!--For server-server acceptance PEC notifications--&gt;
2162 &lt;!--recipients for whom it is the relative PEC notification--&gt;
2163 &lt;!ELEMENT ricezione (#PCDATA)&gt;
2164
2165 &lt;!--In case of error--&gt;
2166 &lt;!--brief description of the error--&gt;
2167 &lt;!ELEMENT errore-esteso (#PCDATA)&gt;
2168
2169 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. PEC Providers Directory Scheme</span>
2170
2171 The PEC providers directory is created through a centralized LDAP
2172 server that contains the providers' data and their corresponding PEC
2173 mail domains.
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Petrucci, et al. Informational [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2183
2184
2185 The following are the directory scheme's attributes:
2186
2187 - providerCertificateHash: hash of provider's certificate
2188
2189 - providerCertificate: provider certificate
2190
2191 - providerName: provider name
2192
2193 - mailReceipt: provider reception email address
2194
2195 - managedDomains: managed domains
2196
2197 - LDIFLocationURL: provider LDIF record URL
2198
2199 - providerUnit: secondary operating environment name
2200
2201 The directory's base root is "o=postacert" and the
2202 "DistinguishedName" of single records is of the type
2203 "&lt;providerName=&lt;name&gt;,o=postacert&gt;". Search within the directory is
2204 carried out mainly in case-sensitive mode using the
2205 "providerCertificateHash" attribute (during envelope signature
2206 verification phase) or the "managedDomains" attribute (during message
2207 acceptance phase). It is possible for the record of a single
2208 provider to contain multiple "providerCertificate" attributes with
2209 the related "providerCertificateHash" attributes in order to allow
2210 the handling of the renewal of expiring certificates. The provider
2211 MUST make sure to update its record with sufficient advance before
2212 the certificate expiration date, by adding a new certificate whose
2213 validity overlaps that of the previous one.
2214
2215 The data of all PEC providers is encompassed in a [<a href="#ref-LDIF" title="&quot;The LDAP Data Interchange Format (LDIF) - Technical Specification&quot;">LDIF</a>] file, which
2216 is available as an [<a href="#ref-HTTPS" title="&quot;HTTP Over TLS&quot;">HTTPS</a>] object and can be found at the URL to
2217 which the 'LDIFLocationURL' attribute in the "dn: o=postacert" record
2218 points (see <a href="#section-4.5.6">section 4.5.6</a>). To guarantee authenticity, that file
2219 MUST be signed by the provider for the operations regarding its PEC
2220 services using the method described for single providers. The file,
2221 the signature, and the X.509v3 certificate MUST be inserted in a
2222 PKCS#7 structure in binary ASN.1 DER format as a file with ".p7m"
2223 extension. The centralized [<a href="#ref-LDAP" title="&quot;Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map&quot;">LDAP</a>] system downloads that file on a
2224 daily basis and, after suitable verifications of the signature,
2225 applies it to the provider's record.
2226
2227 Through the [<a href="#ref-LDIF" title="&quot;The LDAP Data Interchange Format (LDIF) - Technical Specification&quot;">LDIF</a>] file, single providers MUST keep a copy of the
2228 directory locally, updated on a daily basis, in order to improve
2229 system performance by avoiding continuous request dispatches to the
2230 central system for every message elaboration phase.
2231
2232
2233
2234
2235
2236 <span class="grey">Petrucci, et al. Informational [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2239
2240
2241 If secondary environments are present, the [<a href="#ref-LDIF" title="&quot;The LDAP Data Interchange Format (LDIF) - Technical Specification&quot;">LDIF</a>] file indicated in
2242 the main environment's record MUST relate the contents of all the
2243 provider-relevant records.
2244
2245 NOTE: This specification uses an unregistered LDAP DN name space
2246 that may lead to conflict with other registered or
2247 unregistered names.
2248
2249 <span class="h4"><a class="selflink" id="section-4.5.1" href="#section-4.5.1">4.5.1</a>. providerCertificateHash Attribute</span>
2250
2251 The 'providerCertificateHash' attribute is a hexadecimal
2252 representation of the hash in SHA1 format of the X.509v3 certificate
2253 used by the provider for PEC notifications and envelope signatures.
2254
2255 ( 1.3.6.1.4.1.16572.2.2.1 NAME 'providerCertificateHash'
2256 DESC 'Hash SHA1 of X.509 certificate in hexadecimal format'
2257 EQUALITY caseIgnoreIA5Match
2258 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
2259
2260 The IA5String ( 1.3.6.1.4.1.1466.115.121.1.26 ) syntax is defined in
2261 [<a href="#ref-LDAP-SYNTAXES" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">LDAP-SYNTAXES</a>].
2262
2263 <span class="h4"><a class="selflink" id="section-4.5.2" href="#section-4.5.2">4.5.2</a>. providerCertificate Attribute</span>
2264
2265 The 'providerCertificate' attribute holds a set of certificate(s)
2266 used by the provider to sign PEC notifications and transport
2267 envelopes.
2268
2269 ( 1.3.6.1.4.1.16572.2.2.2 NAME 'providerCertificate'
2270 DESC 'X.509 certificate in ASN.1 DER binary format'
2271 SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 )
2272
2273 The Certificate syntax ( 1.3.6.1.4.1.1466.115.121.1.8 ) is defined in
2274 [<a href="./rfc4523" title="&quot;Lightweight Directory Access Protocol (LDAP) Schema Definitions for X.509 Certificates&quot;">RFC4523</a>].
2275
2276 As required by this attribute type's syntax, values of this attribute
2277 are requested and transferred using the attribute description
2278 "providerCertificate;binary" [<a href="./rfc4522" title="&quot;Lightweight Directory Access Protocol (LDAP): The Binary Encoding Option&quot;">RFC4522</a>].
2279
2280 <span class="h4"><a class="selflink" id="section-4.5.3" href="#section-4.5.3">4.5.3</a>. providerName Attribute</span>
2281
2282 The 'providerName' attribute contains the name of the PEC provider.
2283 All records MUST contain their provider's name in this attribute.
2284
2285
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Petrucci, et al. Informational [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2295
2296
2297 ( 1.3.6.1.4.1.16572.2.2.3 NAME 'providerName'
2298 DESC 'PEC provider name'
2299 EQUALITY caseIgnoreMatch
2300 SUBSTR caseIgnoreSubstringsMatch
2301 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
2302 SINGLE-VALUE )
2303
2304 The Directory String ( 1.3.6.1.4.1.1466.115.121.1.15 ) syntax is
2305 defined in [<a href="#ref-LDAP-SYNTAXES" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">LDAP-SYNTAXES</a>].
2306
2307 <span class="h4"><a class="selflink" id="section-4.5.4" href="#section-4.5.4">4.5.4</a>. mailReceipt Attribute</span>
2308
2309 The 'mailReceipt' attribute contains the provider's email address
2310 within the provider to which server-server acceptance and virus
2311 detection PEC notifications are sent. This address is a limited
2312 version of the addr-spec construct described in [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] (without
2313 angle brackets); it only permits the dot-atom-text form on both the
2314 left- and right-hand sides of the "@", and does not have internal
2315 CFWS.
2316
2317 ( 1.3.6.1.4.1.16572.2.2.4 NAME 'mailReceipt'
2318 DESC 'E-mail address of the service mailbox'
2319 EQUALITY caseIgnoreIA5Match
2320 SUBSTR caseIgnoreIA5SubstringsMatch
2321 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
2322 SINGLE-VALUE )
2323
2324 The IA5String ( 1.3.6.1.4.1.1466.115.121.1.26 ) syntax is defined in
2325 [<a href="#ref-LDAP-SYNTAXES" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">LDAP-SYNTAXES</a>].
2326
2327 <span class="h4"><a class="selflink" id="section-4.5.5" href="#section-4.5.5">4.5.5</a>. managedDomains Attribute</span>
2328
2329 The 'managedDomains' attribute holds a set of domains [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>] that are
2330 handled by a PEC provider. Domains are limited to dot-atom form
2331 ([<a href="./rfc1034" title="&quot;Domain names - concepts and facilities&quot;">RFC1034</a>], [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]).
2332
2333 ( 1.3.6.1.4.1.16572.2.2.5 NAME 'managedDomains'
2334 DESC 'Domains handled by the PEC provider'
2335 EQUALITY caseIgnoreIA5Match
2336 SUBSTR caseIgnoreIA5SubstringsMatch
2337 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
2338
2339 The IA5String ( 1.3.6.1.4.1.1466.115.121.26 ) syntax is defined in
2340 [<a href="#ref-LDAP-SYNTAXES" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">LDAP-SYNTAXES</a>].
2341
2342 The 'managedDomains' attribute holds a set of domains [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>] that are
2343 handled by a PEC provider. Domains are limited to dot-atom form
2344 ([<a href="./rfc1034" title="&quot;Domain names - concepts and facilities&quot;">RFC1034</a>], [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]).
2345
2346
2347
2348 <span class="grey">Petrucci, et al. Informational [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2351
2352
2353 <span class="h4"><a class="selflink" id="section-4.5.6" href="#section-4.5.6">4.5.6</a>. LDIFLocationURL Attribute</span>
2354
2355 The 'LDIFLocationURL' attribute contains an [<a href="#ref-HTTPS" title="&quot;HTTP Over TLS&quot;">HTTPS</a>] URL that points
2356 to the location of the [<a href="#ref-LDIF" title="&quot;The LDAP Data Interchange Format (LDIF) - Technical Specification&quot;">LDIF</a>] file defining the provider's record.
2357 When the attribute is present in the record "dn: o=postacert", then
2358 it contains the definition of the entire directory in [<a href="#ref-LDIF" title="&quot;The LDAP Data Interchange Format (LDIF) - Technical Specification&quot;">LDIF</a>] format.
2359 The LDIF file will have a MIME type of application/pkcs7-mime, with
2360 the parameter smime-type/signed-data. [<a href="#ref-SMIMEV3" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification&quot;">SMIMEV3</a>] The LDIF file is
2361 encoded using the UTF-8 character set.
2362
2363 Secondary environment records MUST NOT contain the 'LDIFLocationURL'
2364 attribute which is obtained from the main environment's attributes
2365 for all records connected to the provider.
2366
2367 ( 1.3.6.1.4.1.16572.2.2.6 NAME 'LDIFLocationURL'
2368 DESC 'URL of the LDIF file that defines the entry'
2369 EQUALITY caseExactMatch
2370 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
2371 SINGLE-VALUE )
2372
2373 The Directory String ( 1.3.6.1.4.1.1466.115.121.1.15 ) syntax is
2374 defined in [<a href="#ref-LDAP-SYNTAXES" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">LDAP-SYNTAXES</a>].
2375
2376 <span class="h4"><a class="selflink" id="section-4.5.7" href="#section-4.5.7">4.5.7</a>. providerUnit Attribute</span>
2377
2378 The 'providerUnit' attribute contains the name of secondary operating
2379 environments -- an attribute not present for the main environment.
2380 It is possible for the provider to define several distinct records,
2381 each indicating a single, different, secondary operating environment,
2382 for which it is possible to declare specific attributes that are, if
2383 need be, distinct from those relative to the main and other
2384 environments.
2385
2386 The "DistinguishedName" of the records relative to the secondary
2387 operating environments are of the type
2388 "&lt;providerUnits=&lt;environment&gt;,providerName=&lt;name&gt;,o=postacert&gt;".
2389 Every provider MUST have a record associated to its own main
2390 environment, distinguishable for the absence of the "providerUnit"
2391 attribute within the record and the DistinguishedName.
2392
2393 ( 1.3.6.1.4.1.16572.2.2.7 NAME 'providerUnit'
2394 DESC 'Name of the secondary operative environment'
2395 EQUALITY caseIgnoreMatch
2396 SUBSTR caseIgnoreSubstringsMatch
2397 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
2398 SINGLE-VALUE )
2399
2400
2401
2402
2403
2404 <span class="grey">Petrucci, et al. Informational [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2407
2408
2409 The Directory String ( 1.3.6.1.4.1.1466.115.121.1.15 ) syntax is
2410 defined in [<a href="#ref-LDAP-SYNTAXES" title="&quot;Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules&quot;">LDAP-SYNTAXES</a>].
2411
2412 <span class="h4"><a class="selflink" id="section-4.5.8" href="#section-4.5.8">4.5.8</a>. LDIFLocationURLObject Object Class</span>
2413
2414 The schema definition of the 'LDIFLocationURLObject' object class:
2415
2416 ( 1.3.6.1.4.1.16572.2.1.1 NAME 'LDIFLocationURLObject'
2417 SUP top AUXILIARY
2418 MAY ( LDIFLocationURL ) )
2419
2420 <span class="h4"><a class="selflink" id="section-4.5.9" href="#section-4.5.9">4.5.9</a>. Provider Object Class</span>
2421
2422 The schema definition of the 'provider' object class:
2423
2424 ( 1.3.6.1.4.1.16572.2.1.2 NAME 'provider'
2425 SUP top STRUCTURAL
2426 MUST ( providerCertificateHash
2427 providerCertificate
2428 providerName
2429 mailReceipt
2430 managedDomains )
2431
2432 MAY ( description
2433 LDIFLocationURL
2434 providerUnit )
2435
2436 <span class="h4"><a class="selflink" id="section-4.5.10" href="#section-4.5.10">4.5.10</a>. LDIF File Example</span>
2437
2438 The following LDIF file represents an example of a providers'
2439 directory, containing a base root and two fictitious providers. The
2440 inserted certificates are two self-signed certificates used for
2441 example purposes only:
2442
2443 dn: o=postacert
2444 objectclass: top
2445 objectclass: organization
2446 objectClass: LDIFLocationURLObject
2447 o: postacert
2448 LDIFLocationURL: <a href="https://igpec.rupa.example.com/igpec.ldif.p7m">https://igpec.rupa.example.com/igpec.ldif.p7m</a>
2449 description: Base root for the PEC providers directory
2450 dn: providerName=Anonymous Certified Mail S.p.A.,o=postacert
2451 objectclass: top
2452 objectclass: provider
2453 providerName: Anonymous Certified Mail S.p.A.
2454 providerCertificateHash:
2455 7E7AEF1059AE0F454F2643A95F69EC3556009239
2456 providerCertificate;binary::
2457
2458
2459
2460 <span class="grey">Petrucci, et al. Informational [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2463
2464
2465 MIIDBjCCAm+gAwIBAgIBADANBgkqhkiG9w0BAQQFADBmMQswCQYDVQQGEw
2466 JJVDEpMCcGA1UEChMgQW5vbmltYSBQb3N0YSBDZXJ0aWZpY2F0YSBTLnAu
2467 QS4xLDAqBgkqhkiG9w0BCQEWHXBvc3RhLWNlcnRpZmljYXRhQGFucG9jZX
2468 J0Lml0MB4XDTAyMTIwOTE3MjQxNVoXDTAzMTIwOTE3MjQxNVowZjELMAkG
2469 A1UEBhMCSVQxKTAnBgNVBAoTIEFub25pbWEgUG9zdGEgQ2VydGlmaWNhdG
2470 EgUy5wLkEuMSwwKgYJKoZIhvcNAQkBFh1wb3N0YS1jZXJ0aWZpY2F0YUBh
2471 bnBvY2VydC5pdDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAr8J+qK
2472 KdxV9LzDMPqwnEy0P8H/KwbI0Szs8p6UZajZdpeUK0Ncbrv1QyXZNNtSMC
2473 2uL09HDyx8agjgZWdhypnehguiSK3busha15RSpMGhiqxmz2b0HhOG73Gf
2474 alZelqrwqmElna4MNUaLhbOvTd/sqPUS378w5IaIhWxzy34XcCAwEAAaOB
2475 wzCBwDAdBgNVHQ4EFgQUN8lC0znQWEs0xspZ/aBzsaGvRZMwgZAGA1UdIw
2476 SBiDCBhYAUN8lC0znQWEs0xspZ/aBzsaGvRZOhaqRoMGYxCzAJBgNVBAYT
2477 AklUMSkwJwYDVQQKEyBBbm9uaW1hIFBvc3RhIENlcnRpZmljYXRhIFMucC
2478 5BLjEsMCoGCSqGSIb3DQEJARYdcG9zdGEtY2VydGlmaWNhdGFAYW5wb2Nl
2479 cnQuaXSCAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQA58B
2480 Z+q1qSKpuffzTBpMtbeFkDIxMqMa+ycnxdMNvcWgCm1A9ZiFJsvqYhDDqA
2481 XxfHjkrzXuSZkYq6WiQCsLp0aYVy40QCIwbOunhrvsxh3vsG5CgN76JzZ9
2482 5Z/1OCFNhLfqf1VH2NSS8TaYCCi/VO7W1Q1KkcA2VlxlQP7McSUw==
2483 mailReceipt: [email protected]
2484 LDIFLocationURL: https://anpocert.example.com/anpocert.ldif.p7m
2485 managedDomains: mail.anpocert.example.com
2486 managedDomains: cert.company.example.com
2487 managedDomains: costmec.example.com
2488 description: Certified mail services for companies
2489
2490 dn: providerName=Postal Services S.p.A,o=postacert
2491 objectclass: top
2492 objectclass: provider
2493 providerName: Postal Services S.p.A
2494 providerCertificateHash:
2495 e00fdd9d88be0e2cc766b893315caf93d5701a6a
2496 providerCertificate;binary::
2497 MIIDHjCCAoegAwIBAgIBADANBgkqhkiG9w0BAQQFADBuMQswCQYDVQQGEw
2498 JJVDEfMB0GA1UEChMWU2Vydml6aSBQb3N0YWxpIFMuci5sLjEPMA0GA1UE
2499 CxMGRC5DLkMuMS0wKwYJKoZIhvcNAQkBFh5wb3N0YS1jZXJ0aWZpY2F0YU
2500 BzZXJwb3N0YWwuaXQwHhcNMDIxMjA5MTczMjE2WhcNMDMxMjA5MTczMjE2
2501 WjBuMQswCQYDVQQGEwJJVDEfMB0GA1UEChMWU2Vydml6aSBQb3N0YWxpIF
2502 Muci5sLjEPMA0GA1UECxMGRC5DLkMuMS0wKwYJKoZIhvcNAQkBFh5wb3N0
2503 YS1jZXJ0aWZpY2F0YUBzZXJwb3N0YWwuaXQwgZ8wDQYJKoZIhvcNAQEBBQ
2504 ADgY0AMIGJAoGBAKoc7n6zA+sO8NATMcfJ+U2aoDEsrj/cObG3QAN6Sr+l
2505 ygWxYXLBZNfSDWqL1K4edLr4gCZIDFsq0PIEaYZhYRGjhbcuJ9H/ZdtWdX
2506 xcwEWN4mwFzlsASogsh5JeqS8db3A1JWkvhO9EUfaCYk8YMAkXYdCtLD9s
2507 9tCYZeTE2ut9AgMBAAGjgcswgcgwHQYDVR0OBBYEFHPw7VJIoIM3VYhuHa
2508 eAwpPF5leMMIGYBgNVHSMEgZAwgY2AFHPw7VJIoIM3VYhuHaeAwpPF5leM
2509 oXKkcDBuMQswCQYDVQQGEwJJVDEfMB0GA1UEChMWU2Vydml6aSBQb3N0YW
2510 xpIFMuci5sLjEPMA0GA1UECxMGRC5DLkMuMS0wKwYJKoZIhvcNAQkBFh5w
2511 b3N0YS1jZXJ0aWZpY2F0YUBzZXJwb3N0YWwuaXSCAQAwDAYDVR0TBAUwAw
2512 EB/zANBgkqhkiG9w0BAQQFAAOBgQApqeXvmOyEjwhMrXezPAXELMZwv4qq
2513
2514
2515
2516 <span class="grey">Petrucci, et al. Informational [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2519
2520
2521 r5ri4XuxTq6sS9jRsEbZrS+NmbcJ7S7eFwNQMNxYFVJqdWoLh8qExsTLXn
2522 sKycSnHbCfuphrKvXjQvR2da75U4zGSkroiyvJ2s9TtiCcT3lQtIjmvrFb
2523 aSBiyzj+za7foFUCQmxCLtDaA==
2524 mailReceipt: [email protected]
2525 LDIFLocationURL: https://postalser.example.com/ldif.txt.p7m
2526 managedDomains: postal-services.example.com
2527 managedDomains: receivedmail.example.com
2528 description: Certified mail services for the public
2529
2530 The following LDIF file represents an example of a PEC providers'
2531 directory, containing a base root and two fictitious providers, the
2532 first of which handles a secondary environment as well. The
2533 certificates inserted are two self-signed certificates used for
2534 example purposes only:
2535
2536 dn: o=postacert
2537 objectclass: top
2538 objectclass: organization
2539 objectClass: LDIFLocationURLObject
2540 o: postacert
2541 LDIFLocationURL: <a href="https://igpec.rupa.example.com/igpec.ldif.p7m">https://igpec.rupa.example.com/igpec.ldif.p7m</a>
2542 description: Base root for the PEC providers directory
2543
2544 dn: providerName=Anonymous Certified Mail S.p.A.,o=postacert
2545 objectclass: top
2546 objectclass: provider
2547 providerName: Anonymous Certified Mail S.p.A.
2548
2549 providerCertificateHash:
2550 7E7AEF1059AE0F454F2643A95F69EC3556009239
2551 providerCertificate;binary::
2552 MIIDBjCCAm+gAwIBAgIBADANBgkqhkiG9w0BAQQFADBmMQswCQYDVQQGEw
2553 JJVDEpMCcGA1UEChMgQW5vbmltYSBQb3N0YSBDZXJ0aWZpY2F0YSBTLnAu
2554 QS4xLDAqBgkqhkiG9w0BCQEWHXBvc3RhLWNlcnRpZmljYXRhQGFucG9jZX
2555 J0Lml0MB4XDTAyMTIwOTE3MjQxNVoXDTAzMTIwOTE3MjQxNVowZjELMAkG
2556 A1UEBhMCSVQxKTAnBgNVBAoTIEFub25pbWEgUG9zdGEgQ2VydGlmaWNhdG
2557 EgUy5wLkEuMSwwKgYJKoZIhvcNAQkBFh1wb3N0YS1jZXJ0aWZpY2F0YUBh
2558 bnBvY2VydC5pdDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAr8J+qK
2559 KdxV9LzDMPqwnEy0P8H/KwbI0Szs8p6UZajZdpeUK0Ncbrv1QyXZNNtSMC
2560 2uL09HDyx8agjgZWdhypnehguiSK3busha15RSpMGhiqxmz2b0HhOG73Gf
2561 alZelqrwqmElna4MNUaLhbOvTd/sqPUS378w5IaIhWxzy34XcCAwEAAaOB
2562 wzCBwDAdBgNVHQ4EFgQUN8lC0znQWEs0xspZ/aBzsaGvRZMwgZAGA1UdIw
2563 SBiDCBhYAUN8lC0znQWEs0xspZ/aBzsaGvRZOhaqRoMGYxCzAJBgNVBAYT
2564 AklUMSkwJwYDVQQKEyBBbm9uaW1hIFBvc3RhIENlcnRpZmljYXRhIFMucC
2565 5BLjEsMCoGCSqGSIb3DQEJARYdcG9zdGEtY2VydGlmaWNhdGFAYW5wb2Nl
2566 cnQuaXSCAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQA58B
2567 Z+q1qSKpuffzTBpMtbeFkDIxMqMa+ycnxdMNvcWgCm1A9ZiFJsvqYhDDqA
2568 XxfHjkrzXuSZkYq6WiQCsLp0aYVy40QCIwbOunhrvsxh3vsG5CgN76JzZ9
2569
2570
2571
2572 <span class="grey">Petrucci, et al. Informational [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2575
2576
2577 5Z/1OCFNhLfqf1VH2NSS8TaYCCi/VO7W1Q1KkcA2VlxlQP7McSUw==
2578 mailReceipt: [email protected]
2579 LDIFLocationURL: http://anpocert.example.com/anpocert.ldif.p7m
2580 managedDomains: mail.anpocert.example.com
2581 managedDomains: cert.company.example.com
2582 managedDomains: costmec.example.com
2583 description: Certified mail services for companies
2584 dn: providerUnit=Secondary Environment, providerName=Anonymous
2585 Certified Mail S.p.A.,o=postacert
2586 objectclass: top
2587 objectclass: provider
2588 providerName: Certified Mail S.p.A.
2589 providerUnit: Secondary Environment
2590 providerCertificateHash:
2591 7E7AEF1059AE0F454F2643A95F69EC3556009239
2592 providerCertificate;binary::
2593 MIIDBjCCAm+gAwIBAgIBADANBgkqhkiG9w0BAQQFADBmMQswCQYDVQQGEw
2594 JJVDEpMCcGA1UEChMgQW5vbmltYSBQb3N0YSBDZXJ0aWZpY2F0YSBTLnAu
2595 QS4xLDAqBgkqhkiG9w0BCQEWHXBvc3RhLWNlcnRpZmljYXRhQGFucG9jZX
2596 J0Lml0MB4XDTAyMTIwOTE3MjQxNVoXDTAzMTIwOTE3MjQxNVowZjELMAkG
2597 A1UEBhMCSVQxKTAnBgNVBAoTIEFub25pbWEgUG9zdGEgQ2VydGlmaWNhdG
2598 EgUy5wLkEuMSwwKgYJKoZIhvcNAQkBFh1wb3N0YS1jZXJ0aWZpY2F0YUBh
2599 bnBvY2VydC5pdDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAr8J+qK
2600 KdxV9LzDMPqwnEy0P8H/KwbI0Szs8p6UZajZdpeUK0Ncbrv1QyXZNNtSMC
2601 2uL09HDyx8agjgZWdhypnehguiSK3busha15RSpMGhiqxmz2b0HhOG73Gf
2602 alZelqrwqmElna4MNUaLhbOvTd/sqPUS378w5IaIhWxzy34XcCAwEAAaOB
2603 wzCBwDAdBgNVHQ4EFgQUN8lC0znQWEs0xspZ/aBzsaGvRZMwgZAGA1UdIw
2604 SBiDCBhYAUN8lC0znQWEs0xspZ/aBzsaGvRZOhaqRoMGYxCzAJBgNVBAYT
2605 AklUMSkwJwYDVQQKEyBBbm9uaW1hIFBvc3RhIENlcnRpZmljYXRhIFMucC
2606 5BLjEsMCoGCSqGSIb3DQEJARYdcG9zdGEtY2VydGlmaWNhdGFAYW5wb2Nl
2607 cnQuaXSCAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQA58B
2608 Z+q1qSKpuffzTBpMtbeFkDIxMqMa+ycnxdMNvcWgCm1A9ZiFJsvqYhDDqA
2609 XxfHjkrzXuSZkYq6WiQCsLp0aYVy40QCIwbOunhrvsxh3vsG5CgN76JzZ9
2610 5Z/1OCFNhLfqf1VH2NSS8TaYCCi/VO7W1Q1KkcA2VlxlQP7McSUw==
2611 mailReceipt: [email protected]
2612 managedDomains: management.anpocert.example.com
2613 managedDomains: personnel.anpocert.example.com
2614 description: Corporate internal services
2615 dn: providerName=Postal Services S.r.l.,o=postacert
2616 objectclass: top
2617 objectclass: provider
2618 providerName: Postal Services S.r.l.
2619 providerCertificateHash:
2620 e00fdd9d88be0e2cc766b893315caf93d5701a6a
2621 providerCertificate;binary::
2622 MIIDHjCCAoegAwIBAgIBADANBgkqhkiG9w0BAQQFADBuMQswCQYDVQQGEw
2623 JJVDEfMB0GA1UEChMWU2Vydml6aSBQb3N0YWxpIFMuci5sLjEPMA0GA1UE
2624 CxMGRC5DLkMuMS0wKwYJKoZIhvcNAQkBFh5wb3N0YS1jZXJ0aWZpY2F0YU
2625
2626
2627
2628 <span class="grey">Petrucci, et al. Informational [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2631
2632
2633 BzZXJwb3N0YWwuaXQwHhcNMDIxMjA5MTczMjE2WhcNMDMxMjA5MTczMjE2
2634 WjBuMQswCQYDVQQGEwJJVDEfMB0GA1UEChMWU2Vydml6aSBQb3N0YWxpIF
2635 Muci5sLjEPMA0GA1UECxMGRC5DLkMuMS0wKwYJKoZIhvcNAQkBFh5wb3N0
2636 YS1jZXJ0aWZpY2F0YUBzZXJwb3N0YWwuaXQwgZ8wDQYJKoZIhvcNAQEBBQ
2637 ADgY0AMIGJAoGBAKoc7n6zA+sO8NATMcfJ+U2aoDEsrj/cObG3QAN6Sr+l
2638 ygWxYXLBZNfSDWqL1K4edLr4gCZIDFsq0PIEaYZhYRGjhbcuJ9H/ZdtWdX
2639 xcwEWN4mwFzlsASogsh5JeqS8db3A1JWkvhO9EUfaCYk8YMAkXYdCtLD9s
2640 9tCYZeTE2ut9AgMBAAGjgcswgcgwHQYDVR0OBBYEFHPw7VJIoIM3VYhuHa
2641 eAwpPF5leMMIGYBgNVHSMEgZAwgY2AFHPw7VJIoIM3VYhuHaeAwpPF5leM
2642 oXKkcDBuMQswCQYDVQQGEwJJVDEfMB0GA1UEChMWU2Vydml6aSBQb3N0YW
2643 xpIFMuci5sLjEPMA0GA1UECxMGRC5DLkMuMS0wKwYJKoZIhvcNAQkBFh5w
2644 b3N0YS1jZXJ0aWZpY2F0YUBzZXJwb3N0YWwuaXSCAQAwDAYDVR0TBAUwAw
2645 EB/zANBgkqhkiG9w0BAQQFAAOBgQApqeXvmOyEjwhMrXezPAXELMZwv4qq
2646 r5ri4XuxTq6sS9jRsEbZrS+NmbcJ7S7eFwNQMNxYFVJqdWoLh8qExsTLXn
2647 sKycPSnHbCfuphrKvXjQvR2da75U4zGSkroiyvJ2s9TtiCcT3lQtIjmvrF
2648 baSBiyzj+za7foFUCQmxCLtDaA==
2649 mailReceipt: [email protected]
2650 LDIFLocationURL: http://postalser.example.com/ldif.txt.p7m
2651 managedDomains: postal-services.example.com
2652 managedDomains: receivedmail.example.com
2653 description: Certified mail services for the public
2654
2655 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security-Related Aspects</span>
2656
2657 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Digital Signature</span>
2658
2659 It is recommended that a dedicated hardware module be used to handle
2660 private key and signature operations, the specifications of which are
2661 outside the scope of this document. It's up to the PEC providers to
2662 conform to security requisites expected for the service.
2663
2664 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Authentication</span>
2665
2666 User access to PEC services through the Access Point MUST be allowed
2667 only upon successful user authentication on the system.
2668
2669 For example, authentication might use user-ID and password, or, if
2670 available and considered necessary for the type of service provided,
2671 an electronic ID card or the national services card. Choice of
2672 authentication method is left to the better judgment of the service
2673 provider. Authentication is necessary to guarantee as much as
2674 possible that the message is sent by a PEC user whose identification
2675 data is congruent with the specified sender, so as to avoid
2676 falsification of the latter.
2677
2678
2679
2680
2681
2682
2683
2684 <span class="grey">Petrucci, et al. Informational [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2687
2688
2689 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Secure Interaction</span>
2690
2691 To guarantee that the original message remains unaltered during
2692 transaction, envelopment and signature are applied on outgoing
2693 messages at the Access Point, and subsequent verification of incoming
2694 messages is done at the Incoming Point.
2695
2696 All communications within the PEC network MUST use secure channels.
2697 Integrity and confidentiality of connections between PEC provider and
2698 user MUST be guaranteed through the use of secure protocols, such as
2699 those based on [<a href="#ref-TLS" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">TLS</a>] and those that create a secure transport channel
2700 on which non-secure protocols can transmit (e.g., IPsec).
2701
2702 The interaction between providers MUST take place using SMTP on
2703 [<a href="#ref-TLS" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">TLS</a>], as per [<a href="#ref-SMTP-TLS" title="&quot;SMTP Service Extension for Secure SMTP over Transport Layer Security&quot;">SMTP-TLS</a>]. The Incoming Point MUST provide and
2704 announce its support for the STARTTLS extension, as well as accept
2705 both unencrypted connections (for ordinary mail) and protected ones.
2706 To guarantee complete traceability in the flow of PEC messages, these
2707 MUST NOT transit on systems external to the PEC network. When
2708 exchanging messages between different providers, all transactions
2709 MUST take place between machines that belong to the PEC network or
2710 are directly managed by the provider. An "MX" type record MAY be
2711 associated to each PEC domain defined within the system for name
2712 resolution, in which case secondary reception systems specified in
2713 that record MUST be under direct control of the provider. All in
2714 conformance with [<a href="#ref-SMTP" title="&quot;Simple Mail Transfer Protocol&quot;">SMTP</a>].
2715
2716 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Virus</span>
2717
2718 Another important security aspect that concerns the PEC system, is
2719 related to the technical and functional architecture that MUST block
2720 the presence of viruses from endangering the security of all handled
2721 messages. It is therefore REQUIRED to have installations and
2722 continuous updates of anti-virus systems that hinder infections as
2723 much as possible without intervening on the content of the certified
2724 mail, in compliance with what has been discussed thus far.
2725
2726 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. S/MIME Certificate</span>
2727
2728 In this document the S/MIME certificate profile is defined for use in
2729 the certification of PEC messages done by the providers. The
2730 proposed profile of the S/MIME certificate is based on the IETF
2731 standards [<a href="#ref-SMIMECERT" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling&quot;">SMIMECERT</a>] and [<a href="#ref-CRL" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">CRL</a>], which in turn are based on the
2732 standard ISO/IEC 9594-8:2001.
2733
2734
2735
2736
2737
2738
2739
2740 <span class="grey">Petrucci, et al. Informational [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2743
2744
2745 <span class="h4"><a class="selflink" id="section-5.5.1" href="#section-5.5.1">5.5.1</a>. Provider-Related Information (Subject)</span>
2746
2747 The information related to the PEC provider holder of the certificate
2748 MUST be inserted in the Subject field (Subject DN). More precisely,
2749 the Subject DN MUST contain the PEC provider's name as it is in the
2750 "providerName" attribute published in the PEC providers directory
2751 (<a href="#section-4.5">section 4.5</a>), but the Subject DN does not have to match the Provider
2752 entry DN in the LDIF. The providerName MUST be present in the
2753 CommonName or OrganizationName attributes of the "Subject:" field in
2754 the certificate.
2755
2756 Certificates MUST contain an Internet mail address, which MUST have a
2757 value in the subjectAltName extension, and SHOULD NOT be present in
2758 the Subject Distinguished Name.
2759
2760 Valid subjectDN are:
2761
2762 C=IT, O=AcmePEC S.p.A, CN=Posta Certificata
2763
2764 C=IT, O=ServiziPEC S.p.A, CN=Posta Certificata
2765
2766 Valorization of other attributes in the Subject DN, if present, MUST
2767 be done in compliance with [<a href="#ref-CRL" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">CRL</a>].
2768
2769 <span class="h4"><a class="selflink" id="section-5.5.2" href="#section-5.5.2">5.5.2</a>. Certificate Extensions</span>
2770
2771 Extensions that MUST be present in the S/MIME certificate are:
2772
2773 o Key Usage
2774
2775 o Authority Key Identifier
2776
2777 o Subject Key Identifier
2778
2779 o Subject Alternative Name
2780
2781 The Basic Constraints extension (Object ID:2.5.29.19) MUST NOT be
2782 present.
2783
2784 The valorization of the above listed extensions for the described
2785 profile follows.
2786
2787 The Key Usage extension (Object ID: 2.5.29.15) MUST have the
2788 digitalSignature bit (bit 0) activated and MUST be marked as
2789 critical. The extension MAY contain other active bits corresponding
2790 to different Key Usage, as long as that doesn't contrast with the
2791 indications in [<a href="#ref-CRL" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">CRL</a>].
2792
2793
2794
2795
2796 <span class="grey">Petrucci, et al. Informational [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2799
2800
2801 The Authority Key Identifier (Object ID: 2.5.29.35) MUST contain at
2802 least the keyIdentifier field and MUST NOT be marked as critical.
2803
2804 The Subject Key Identifier extension (Object ID: 2.5.29.14) MUST
2805 contain at least the keyIdentifier field and MUST NOT be marked as
2806 critical.
2807
2808 The Subject Alternative Name (Object ID: 2.5.29.17) MUST contain at
2809 least the rfc822Name field and MUST NOT be marked as critical.
2810
2811 Adding other extensions that have not been described in this document
2812 is to be considered OPTIONAL, as long as it remains compliant with
2813 [<a href="#ref-CRL" title="&quot;Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">CRL</a>]; such added extensions MUST NOT be marked as critical.
2814
2815 <span class="h4"><a class="selflink" id="section-5.5.3" href="#section-5.5.3">5.5.3</a>. Example</span>
2816
2817 Following is an example of an S/MIME certificate compliant with the
2818 minimal requisites described in this profile. Values used are of
2819 fictitious providers generated for example purposes only.
2820
2821 <span class="h5"><a class="selflink" id="section-5.5.3.1" href="#section-5.5.3.1">5.5.3.1</a>. General-Use Certificate in Annotated Version</span>
2822
2823 An asterisk near the label of an extension means that such an
2824 extension has been marked as critical.
2825
2826 VERSION: 3
2827 SERIAL: 11226 (0x2bda)
2828 INNER SIGNATURE:
2829 ALG. ID: id-sha1-with-rsa-encryption
2830 PARAMETER: 0
2831 ISSUER:
2832 Country Name: IT
2833 Organization Name: Certifier 1
2834 Organizational Unit Name: Certification Service Provider
2835 Common Name: Certifier S.p.A.
2836 VALIDITY:
2837 Not Before: Oct 5, 04 09:04:23 GMT
2838 Not After: Oct 5, 05 09:04:23 GMT
2839 SUBJECT:
2840 Country Name: IT
2841 Organization Name: AcmePEC S.p.A.
2842 Common Name: Certified Mail
2843 PUBLIC KEY: (key size is 1024 bits)
2844 ALGORITHM:
2845 ALG. ID: id-rsa-encryption
2846 PARAMETER: 0
2847 MODULUS: 0x00afbeb4 5563198a aa9bac3f 1b29b5be
2848 7f691945 89d01569 ca0d555b 5c33d7e9
2849
2850
2851
2852 <span class="grey">Petrucci, et al. Informational [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2855
2856
2857 ...
2858 d15ff128 6792def5 b3f884e6 54b326db
2859 cf
2860 EXPONENT: 0x010001
2861 EXTENSIONS:
2862 Subject Alt Name:
2863 RFC Name: [email protected]
2864 Key Usage*: Digital Signature
2865 Authority Key Identifier: 0x12345678 aaaaaaaa bbbbbbbb
2866 cccccccc dddddddd
2867 Subject Key Identifier: 0x3afae080 6453527a 3e5709d8 49a941a8
2868 a3a70ae1
2869 SIGNATURE:
2870 ALG. ID: id-sha1-with-rsa-encryption
2871 PARAMETER: 0
2872 VALUE: 0x874b4d25 70a46180 c9770a85 fe7923ce
2873 b22d2955 2f3af207 142b2aba 643aaa61
2874 ...
2875 d8fd10b4 c9e00ebc c089f7a3 549a1907
2876 ff885220 ce796328 b0f8ecac 86ffb1cc
2877
2878 <span class="h5"><a class="selflink" id="section-5.5.3.2" href="#section-5.5.3.2">5.5.3.2</a>. General-Use Certificate in Dump ASN.1</span>
2879
2880 0 30 794: SEQUENCE {
2881 4 30 514: SEQUENCE {
2882 8 A0 3: [0] {
2883 10 02 1: INTEGER 2
2884 : }
2885 13 02 2: INTEGER 11226
2886 17 30 13: SEQUENCE {
2887 19 06 9: OBJECT IDENTIFIER
2888 : sha1withRSAEncryption (1 2 840 113549 1 1 5)
2889 30 05 0: NULL
2890 : }
2891 32 30 101: SEQUENCE {
2892 34 31 11: SET {
2893 36 30 9: SEQUENCE {
2894 38 06 3: OBJECT IDENTIFIER countryName (2 5 4 6)
2895 43 13 2: PrintableString 'IT'
2896 : }
2897 : }
2898 47 31 28: SET {
2899 49 30 26: SEQUENCE {
2900 51 06 3: OBJECT IDENTIFIER organizationName (2 5 4 10)
2901 56 13 19: PrintableString 'Certificatore 1'
2902 : }
2903 : }
2904 77 31 22: SET {
2905
2906
2907
2908 <span class="grey">Petrucci, et al. Informational [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2911
2912
2913 79 30 20: SEQUENCE {
2914 81 06 3: OBJECT IDENTIFIER organizationalUnitName (2 5 4 11)
2915 86 13 13: PrintableString 'Certification Service Provider'
2916 : }
2917 : }
2918 101 31 32: SET {
2919 103 30 30: SEQUENCE {
2920 105 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
2921 110 13 23: PrintableString 'Certificatore S.p.A.'
2922 : }
2923 : }
2924 : }
2925 135 30 30: SEQUENCE {
2926 137 17 13: UTCTime '041005090423Z'
2927 152 17 13: UTCTime '051005090423Z'
2928 : }
2929 167 30 66: SEQUENCE {
2930 169 31 11: SET {
2931 171 30 9: SEQUENCE {
2932 173 06 3: OBJECT IDENTIFIER countryName (2 5 4 6)
2933 178 13 2: PrintableString 'IT'
2934 : }
2935 : }
2936 182 31 23: SET {
2937 184 30 21: SEQUENCE {
2938 186 06 3: OBJECT IDENTIFIER organizationName (2 5 4 10)
2939 191 13 14: PrintableString 'AcmePEC S.p.A.'
2940 : }
2941 : }
2942 207 31 26: SET {
2943 209 30 24: SEQUENCE {
2944 211 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
2945 216 13 17: PrintableString 'Posta Certificata'
2946 : }
2947 : }
2948 : }
2949 235 30 159: SEQUENCE {
2950 238 30 13: SEQUENCE {
2951 240 06 9: OBJECT IDENTIFIER rsaEncryption (1 2 840 113549
2952 1 1 1)
2953 251 05 0: NULL
2954 : }
2955 253 03 141: BIT STRING 0 unused bits
2956 : 30 81 89 02 81 81 00 AF BE B4 55 63 19 8A AA 9B
2957 : AC 3F 1B 29 B5 BE 7F 69 19 45 89 D0 15 69 CA 0D
2958 : 55 5B 5C 33 D7 E9 C8 6E FC 14 46 C3 C3 09 47 DD
2959 : CD 10 74 1D 76 4E 71 14 E7 69 42 BE 1C 47 61 85
2960 : 4D 74 76 DD 0B B5 78 4F 1E 84 DD B4 86 7F 96 DF
2961
2962
2963
2964 <span class="grey">Petrucci, et al. Informational [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
2967
2968
2969 : 5E 7B AF 0E CE EA 12 57 0B DF 9B 63 67 4D F9 37
2970 : B7 48 35 27 C2 89 F3 C3 54 66 F7 DA 6C BE 4F 5D
2971 : 85 55 07 A4 97 8C D1 5F F1 28 67 92 DE F5 B3 F8
2972 : [ Another 12 bytes skipped ]
2973 : }
2974 397 A3 123: [3] {
2975 399 30 121: SEQUENCE {
2976 401 30 39: SEQUENCE {
2977 403 06 3: OBJECT IDENTIFIER subjectAltName (2 5 29 17)
2978 408 04 32: OCTET STRING
2979 : 30 1E 81 1C 70 6F 73 74 61 2D 63 65 72 74 69 66
2980 : 69 63 61 74 61 40 61 63 6D 65 70 65 63 2E 69 74
2981 : }
2982 442 30 14: SEQUENCE {
2983 444 06 3: OBJECT IDENTIFIER keyUsage (2 5 29 15)
2984 449 01 1: BOOLEAN TRUE
2985 452 04 4: OCTET STRING
2986 : 03 02 07 80
2987 : }
2988 458 30 31: SEQUENCE {
2989 460 06 3: OBJECT IDENTIFIER authorityKeyIdentifier (2 5 29 35)
2990 465 04 24: OCTET STRING
2991 : 30 16 11 11 11 11 AA AA AA AA AA BB BB BB BB CC CC
2992 : CC CC DD DD DD DD
2993 : }
2994 491 30 29: SEQUENCE {
2995 493 06 3: OBJECT IDENTIFIER subjectKeyIdentifier (2 5 29 14)
2996 498 04 22: OCTET STRING
2997 : 04 14 3A FA E0 80 64 53 52 7A 3E 57 09 D8 49 A9
2998 : 41 A8 A3 A7 0A E1
2999 : }
3000 : }
3001 : }
3002 : }
3003 522 30 13: SEQUENCE {
3004 524 06 9: OBJECT IDENTIFIER
3005 : sha1withRSAEncryption (1 2 840 113549 1 1 5)
3006 535 05 0: NULL
3007 : }
3008 537 03 257: BIT STRING 0 unused bits
3009 : 87 4B 4D 25 70 A4 61 80 C9 77 0A 85 FE 79 23 CE
3010 : B2 2D 29 55 2F 3A F2 07 14 2B 2A BA 64 3A AA 61
3011 : 1F F0 E7 3F C4 E6 13 E2 09 3D F0 E1 83 A0 C0 F2
3012 : C6 71 7F 3A 1C 80 7F 15 B3 D6 1E 22 79 B8 AC 91
3013 : 51 83 F2 3A 84 86 B6 07 2B 22 E8 01 52 2D A4 50
3014 : 9F C6 42 D4 7C 38 B1 DD 88 CD FC E8 C3 12 C3 62
3015 : 64 0F 16 BF 70 15 BC 01 16 78 30 2A DA FA F3 70
3016 : E2 D3 0F 00 B0 FD 92 11 6C 55 45 48 F5 64 ED 98
3017
3018
3019
3020 <span class="grey">Petrucci, et al. Informational [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3023
3024
3025 : [ Another 128 bytes skipped ]
3026 : }
3027
3028 <span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. PEC Providers Directory</span>
3029
3030 The contents of the PEC providers directory MUST be queried via
3031 [<a href="#ref-HTTP" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">HTTP</a>] on a Secure Socket Layer (SSL), as described in [<a href="#ref-TLS" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">TLS</a>],
3032 exclusively by licensed providers that have the necessary user
3033 certificates; this access modality guarantees authenticity,
3034 integrity, and confidentiality of data. Each provider downloads the
3035 LDIF file through an [<a href="#ref-HTTPS" title="&quot;HTTP Over TLS&quot;">HTTPS</a>] session, which is authenticated by
3036 checking the X.509 certificate issued by a certification authority.
3037
3038 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. PEC System Client Technical and Functional Prerequisites</span>
3039
3040 This section lists the prerequisites that must be respected by a
3041 client in order to guarantee the minimal operative functionalities to
3042 the user of a general PEC system:
3043
3044 o handling of Access and Delivery Points through secure channels;
3045
3046 o handling of user authentication in message dispatch and reception
3047 which make use of standard protocols, such as [<a href="#ref-IMAP" title="&quot;INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1&quot;">IMAP</a>], [<a href="#ref-POP3" title="&quot;Post Office Protocol - Version 3&quot;">POP3</a>], and
3048 [<a href="#ref-HTTP" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">HTTP</a>];
3049
3050 o support for MIME format according to [<a href="#ref-MIME1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">MIME1</a>] and [<a href="#ref-MIME5" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples&quot;">MIME5</a>];
3051
3052 o support for "ISO-8859-1 (Latin-1)" character set;
3053
3054 o support for S/MIME v3 standard, as in [<a href="#ref-SMIMEV3" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification&quot;">SMIMEV3</a>], for verification
3055 of signatures applied to PEC envelopes and notifications.
3056
3057 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
3058
3059 All security considerations from [<a href="#ref-CMS" title="&quot;Cryptographic Message Syntax (CMS)&quot;">CMS</a>] and [<a href="#ref-SMIMEV3" title="&quot;Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification&quot;">SMIMEV3</a>] apply to
3060 applications that use procedures described in this document.
3061
3062 The centralized LDAP server is a critical point for the security of
3063 the whole PEC system. An attack could compromise the whole PEC
3064 system. PEC providers that periodically download the LDIF file
3065 SHOULD use the best security technology to protect it from local
3066 attacks. A PEC provider could be compromised if an attacker changed
3067 a certificate or modified the list of domains associated to it in the
3068 LDIF file that was copied to the PEC provider system.
3069
3070
3071
3072
3073
3074
3075
3076 <span class="grey">Petrucci, et al. Informational [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3079
3080
3081 When verifying the validity of the signature of a message, the
3082 recipient system SHOULD verify that the certificate included in the
3083 [<a href="#ref-CMS" title="&quot;Cryptographic Message Syntax (CMS)&quot;">CMS</a>] message is present in the LDIF file (<a href="#section-4.5">section 4.5</a>) and that the
3084 domain extracted by the [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>] "From:" header is listed in the
3085 managedDomains attribute associated to said certificate.
3086
3087 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
3088
3089 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Registration of PEC Message Header Fields</span>
3090
3091 This document defines new header fields used in the messages that
3092 transit in the PEC network. As specified and required by
3093 [<a href="#ref-HEADERS-IANA" title="&quot;Registration Procedures for Message Header Fields&quot;">HEADERS-IANA</a>], this document registers new header fields as
3094 Provisional Message Header Fields as follows.
3095
3096 <span class="h4"><a class="selflink" id="section-8.1.1" href="#section-8.1.1">8.1.1</a>. Header Field: X-Riferimento-Message-ID:</span>
3097
3098 Applicable protocol: mail [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
3099
3100 Status: provisional
3101
3102 Author/Change controller:
3103
3104 Claudio Petrucci
3105 DigitPA
3106 Viale Carlo Marx 31/49
3107 00137 Roma
3108 Italy
3109 EMail: [email protected]
3110
3111 Specification document: this document, <a href="#section-2.2.1">section 2.2.1</a>, <a href="#appendix-A">Appendix A</a>.
3112
3113 <span class="h4"><a class="selflink" id="section-8.1.2" href="#section-8.1.2">8.1.2</a>. Header Field: X-Ricevuta:</span>
3114
3115 Applicable protocol: mail [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
3116
3117 Status: provisional
3118
3119 Author/Change controller:
3120
3121 Claudio Petrucci
3122 DigitPA
3123 Viale Carlo Marx 31/49
3124 00137 Roma
3125 Italy
3126 EMail: [email protected]
3127
3128
3129
3130
3131
3132 <span class="grey">Petrucci, et al. Informational [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3135
3136
3137 Specification document: this document, sections <a href="#section-2.1.1.1.1">2.1.1.1.1</a>, <a href="#section-3.1.2">3.1.2</a>,
3138 3.1.3, 3.1.4, 3.1.6, 3.2.1, 3.2.3, 3.2.4,
3139 3.3.2, 3.3.3, <a href="#appendix-A">Appendix A</a>.
3140
3141 <span class="h4"><a class="selflink" id="section-8.1.3" href="#section-8.1.3">8.1.3</a>. Header Field: X-VerificaSicurezza:</span>
3142
3143 Applicable protocol: mail [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
3144
3145 Status: provisional
3146
3147 Author/Change controller:
3148
3149 Claudio Petrucci
3150 DigitPA
3151 Viale Carlo Marx 31/49
3152 00137 Roma
3153 Italy
3154 EMail: [email protected]
3155
3156 Specification document: this document, sections <a href="#section-2.1.1.1.3">2.1.1.1.3</a>, <a href="#section-3.1.3">3.1.3</a>,
3157 3.2.4, <a href="#appendix-A">Appendix A</a>.
3158
3159 <span class="h4"><a class="selflink" id="section-8.1.4" href="#section-8.1.4">8.1.4</a>. Header Field: X-Trasporto:</span>
3160
3161 Applicable protocol: mail [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
3162
3163 Status: provisional
3164
3165 Author/Change controller:
3166
3167 Claudio Petrucci
3168 DigitPA
3169 Viale Carlo Marx 31/49
3170 00137 Roma
3171 Italy
3172 EMail: [email protected]
3173
3174 Specification document: this document, sections <a href="#section-3.1.5">3.1.5</a>, <a href="#section-3.2.2">3.2.2</a>,
3175 <a href="#appendix-A">Appendix A</a>.
3176
3177 <span class="h4"><a class="selflink" id="section-8.1.5" href="#section-8.1.5">8.1.5</a>. Header Field: X-TipoRicevuta:</span>
3178
3179 Applicable protocol: mail [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
3180
3181 Status: provisional
3182
3183
3184
3185
3186
3187
3188 <span class="grey">Petrucci, et al. Informational [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3191
3192
3193 Author/Change controller:
3194
3195 Claudio Petrucci
3196 DigitPA
3197 Viale Carlo Marx 31/49
3198 00137 Roma
3199 Italy
3200 EMail: [email protected]
3201
3202 Specification document: this document, sections <a href="#section-3.1.5">3.1.5</a>, <a href="#section-3.3.2">3.3.2</a>,
3203 3.3.2.1, 3.3.2.2, 3.3.2.3, <a href="#appendix-A">Appendix A</a>.
3204
3205 <span class="h4"><a class="selflink" id="section-8.1.6" href="#section-8.1.6">8.1.6</a>. Header Field: X-Mittente:</span>
3206
3207 Applicable protocol: mail [<a href="#ref-EMAIL" title="&quot;Internet Message Format&quot;">EMAIL</a>]
3208
3209 Status: provisional
3210
3211 Author/Change controller:
3212
3213 Claudio Petrucci
3214 DigitPA
3215 Viale Carlo Marx 31/49
3216 00137 Roma
3217 Italy
3218 EMail: [email protected]
3219
3220 Specification document: this document, sections <a href="#section-3.2.3">3.2.3</a>, <a href="#appendix-A">Appendix A</a>.
3221
3222 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Registration of LDAP Object Identifier Descriptors</span>
3223
3224 This document defines new LDAP attributes and object classes for
3225 object identifier descriptors. As specified and required by
3226 [<a href="#ref-LDAP-IANA" title="&quot;Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)&quot;">LDAP-IANA</a>], this document registers new descriptors as follows per
3227 the Expert Review.
3228
3229 <span class="h4"><a class="selflink" id="section-8.2.1" href="#section-8.2.1">8.2.1</a>. Registration of Object Classes and Attribute Types</span>
3230
3231 Subject: Request for LDAP Descriptor Registration
3232
3233 Descriptor (short name): See comments
3234
3235 Object Identifier: See comments
3236
3237 Person &amp; email address to contact for further information:
3238 See "Author/Change Controller"
3239
3240 Usage: See comments
3241
3242
3243
3244 <span class="grey">Petrucci, et al. Informational [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3247
3248
3249 Specification: (I-D)
3250
3251 Author/Change Controller:
3252
3253 Claudio Petrucci
3254 DigitPA
3255 Viale Carlo Marx 31/49
3256 00137 Roma
3257 Italy
3258 EMail: [email protected]
3259
3260 Comments:
3261
3262 The following object identifiers and associated object classes/
3263 attribute types are requested to be registered.
3264
3265 OID Descriptor Usage
3266 ------------------------ --------------------- ------
3267 1.3.6.1.4.1.16572.2.1.1 LDIFLocationURLObject O
3268 1.3.6.1.4.1.16572.2.1.2 provider O
3269 1.3.6.1.4.1.16572.2.2.1 providerCertificateHash A
3270 1.3.6.1.4.1.16572.2.2.2 providerCertificate A
3271 1.3.6.1.4.1.16572.2.2.3 providerName A
3272 1.3.6.1.4.1.16572.2.2.4 mailReceipt A
3273 1.3.6.1.4.1.16572.2.2.5 managedDomains A
3274 1.3.6.1.4.1.16572.2.2.6 LDIFLocationURL A
3275 1.3.6.1.4.1.16572.2.2.7 providerUnit A
3276
3277 Legend
3278 -------------------
3279 O =&gt; Object Class
3280 A =&gt; Attribute Type
3281
3282 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
3283
3284 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
3285
3286 [<a id="ref-ABNF">ABNF</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
3287 Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
3288 January 2008.
3289
3290 [<a id="ref-CMS">CMS</a>] Housley, R., "Cryptographic Message Syntax (CMS)",
3291 STD 70, <a href="./rfc5652">RFC 5652</a>, September 2009.
3292
3293 [<a id="ref-CRL">CRL</a>] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
3294 Housley, R., and W. Polk, "Internet X.509 Public Key
3295 Infrastructure Certificate and Certificate Revocation
3296 List (CRL) Profile", <a href="./rfc5280">RFC 5280</a>, May 2008.
3297
3298
3299
3300 <span class="grey">Petrucci, et al. Informational [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3303
3304
3305 [<a id="ref-EMAIL">EMAIL</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC</a>
3306 <a href="./rfc5322">5322</a>, October 2008.
3307
3308 [<a id="ref-HEADERS-IANA">HEADERS-IANA</a>] Klyne, G., Nottingham, M., and J. Mogul,
3309 "Registration Procedures for Message Header Fields",
3310 <a href="https://www.rfc-editor.org/bcp/bcp90">BCP 90</a>, <a href="./rfc3864">RFC 3864</a>, September 2004.
3311
3312 [<a id="ref-HTTP">HTTP</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
3313 Masinter, L., Leach, P., and T. Berners-Lee,
3314 "Hypertext Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>,
3315 June 1999.
3316
3317 [<a id="ref-HTTPS">HTTPS</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
3318
3319 [<a id="ref-IMAP">IMAP</a>] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL -
3320 VERSION 4rev1", <a href="./rfc3501">RFC 3501</a>, March 2003.
3321
3322 [<a id="ref-LDAP">LDAP</a>] Zeilenga, K., Ed., "Lightweight Directory Access
3323 Protocol (LDAP): Technical Specification Road Map",
3324 <a href="./rfc4510">RFC 4510</a>, June 2006.
3325
3326 [<a id="ref-LDAP-IANA">LDAP-IANA</a>] Zeilenga, K., "Internet Assigned Numbers Authority
3327 (IANA) Considerations for the Lightweight Directory
3328 Access Protocol (LDAP)", <a href="https://www.rfc-editor.org/bcp/bcp64">BCP 64</a>, <a href="./rfc4520">RFC 4520</a>, June 2006.
3329
3330 [<a id="ref-LDAP-SYNTAXES">LDAP-SYNTAXES</a>] Legg, S., Ed., "Lightweight Directory Access Protocol
3331 (LDAP): Syntaxes and Matching Rules", <a href="./rfc4517">RFC 4517</a>, June
3332 2006.
3333
3334 [<a id="ref-LDIF">LDIF</a>] Good, G., "The LDAP Data Interchange Format (LDIF) -
3335 Technical Specification", <a href="./rfc2849">RFC 2849</a>, June 2000.
3336
3337 [<a id="ref-MIME1">MIME1</a>] Freed, N. and N. Borenstein, "Multipurpose Internet
3338 Mail Extensions (MIME) Part One: Format of Internet
3339 Message Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996.
3340
3341 [<a id="ref-MIME5">MIME5</a>] Freed, N. and N. Borenstein, "Multipurpose Internet
3342 Mail Extensions (MIME) Part Five: Conformance
3343 Criteria and Examples", <a href="./rfc2049">RFC 2049</a>, November 1996.
3344
3345 [<a id="ref-SUBMISSION">SUBMISSION</a>] Gellens, R. and J. Klensin, "Message Submission for
3346 Mail", <a href="./rfc4409">RFC 4409</a>, April 2006.
3347
3348 [<a id="ref-POP3">POP3</a>] Myers, J. and M. Rose, "Post Office Protocol -
3349 Version 3", STD 53, <a href="./rfc1939">RFC 1939</a>, May 1996.
3350
3351
3352
3353
3354
3355
3356 <span class="grey">Petrucci, et al. Informational [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3359
3360
3361 [<a id="ref-REQ">REQ</a>] Bradner, S., "Key words for use in RFCs to Indicate
3362 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
3363
3364 [<a id="ref-SHA1">SHA1</a>] Eastlake 3rd, D. and P. Jones, "US Secure Hash
3365 Algorithm 1 (SHA1)", <a href="./rfc3174">RFC 3174</a>, September 2001.
3366
3367 [<a id="ref-MIME-SECURE">MIME-SECURE</a>] Galvin, J., Murphy, S., Crocker, S., and N. Freed,
3368 "Security Multiparts for MIME: Multipart/Signed and
3369 Multipart/Encrypted", <a href="./rfc1847">RFC 1847</a>, October 1995.
3370
3371 [<a id="ref-SMIMEV3">SMIMEV3</a>] Ramsdell, B. and S. Turner, "Secure/Multipurpose
3372 Internet Mail Extensions (S/MIME) Version 3.2 Message
3373 Specification", <a href="./rfc5751">RFC 5751</a>, January 2010.
3374
3375 [<a id="ref-SMIMECERT">SMIMECERT</a>] Ramsdell, B. and S. Turner, "Secure/Multipurpose
3376 Internet Mail Extensions (S/MIME) Version 3.2
3377 Certificate Handling", <a href="./rfc5750">RFC 5750</a>, January 2010.
3378
3379 [<a id="ref-SMTP">SMTP</a>] Klensin, J., "Simple Mail Transfer Protocol", <a href="./rfc5321">RFC</a>
3380 <a href="./rfc5321">5321</a>, October 2008.
3381
3382 [<a id="ref-SMTP-DSN">SMTP-DSN</a>] Moore, K., "Simple Mail Transfer Protocol (SMTP)
3383 Service Extension for Delivery Status Notifications
3384 (DSNs)", <a href="./rfc3461">RFC 3461</a>, January 2003.
3385
3386 [<a id="ref-SMTP-TLS">SMTP-TLS</a>] Hoffman, P., "SMTP Service Extension for Secure SMTP
3387 over Transport Layer Security", <a href="./rfc3207">RFC 3207</a>, February
3388 2002.
3389
3390 [<a id="ref-TIMESTAMP">TIMESTAMP</a>] Klyne, G. and C. Newman, "Date and Time on the
3391 Internet: Timestamps", <a href="./rfc3339">RFC 3339</a>, July 2002.
3392
3393 [<a id="ref-TLS">TLS</a>] Dierks, T. and E. Rescorla, "The Transport Layer
3394 Security (TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>,
3395 August 2008.
3396
3397 [<a id="ref-XML">XML</a>] W3C, "Extensible Markup Language (XML) 1.0 (Fifth
3398 Edition)", W3C Recommendation, November 2008,
3399 &lt;<a href="http://www.w3.org/TR/2006/REC-xml-20060816/">http://www.w3.org/TR/2006/REC-xml-20060816/</a>&gt;.
3400
3401 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
3402
3403 [<a id="ref-RFC1034">RFC1034</a>] Mockapetris, P., "Domain names - concepts and
3404 facilities", STD 13, <a href="./rfc1034">RFC 1034</a>, November 1987.
3405
3406
3407
3408
3409
3410
3411
3412 <span class="grey">Petrucci, et al. Informational [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3415
3416
3417 [<a id="ref-RFC4522">RFC4522</a>] Legg, S., "Lightweight Directory Access Protocol
3418 (LDAP): The Binary Encoding Option", <a href="./rfc4522">RFC 4522</a>, June
3419 2006.
3420
3421 [<a id="ref-RFC4523">RFC4523</a>] Zeilenga, K., "Lightweight Directory Access Protocol
3422 (LDAP) Schema Definitions for X.509 Certificates",
3423 <a href="./rfc4523">RFC 4523</a>, June 2006.
3424
3425 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span>
3426
3427 The Italian document on which this document is based, is a product of
3428 the collaboration of many with the supervision of the National Center
3429 for Informatics in the Public Administration of Italy (DigitPA).
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468 <span class="grey">Petrucci, et al. Informational [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3471
3472
3473 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Italian Fields and Values in English</span>
3474
3475 NOTE: The right column represents a translation of the Italian fields
3476 for readability's sake only. Header fields that MUST be used
3477 are the ones in the left column.
3478
3479 X-Riferimento-Message-ID Reference Message Identifier
3480 X-Ricevuta Notification
3481 non-accettazione non acceptance
3482 accettazione server-user acceptance
3483 preavviso-errore-consegna delivery error advance notice
3484 presa-in-carico server-server acceptance
3485 rilevazione-virus virus detection
3486 errore-consegna delivery error
3487 avvenuta-consegna message delivered
3488 X-Mittente Sender
3489 X-VerificaSicurezza Security Verification
3490 errore error
3491 X-Trasporto Transport
3492 posta-certificata certified mail
3493 errore error
3494 X-TipoRicevuta Notification Type
3495 completa complete
3496 breve brief
3497 sintetica concise
3498
3499 certificatore certificator
3500
3501 Subject values:
3502
3503 Accettazione SERVER-USER ACCEPTANCE
3504 Posta certificata CERTIFIED MAIL
3505 Presa in carico SERVER-SERVER ACCEPTANCE
3506 Consegna DELIVERY
3507 Anomalia messaggio MESSAGE ANOMALY
3508 Problema di sicurezza SECURITY PROBLEM
3509 Avviso di non accettazione NON ACCEPTANCE PEC NOTIFICATION
3510 Avviso di non accettazione VIRUS DETECTION INDUCED NON
3511 per virus ACCEPTANCE PEC NOTIFICATION
3512 Avviso di mancata consegna NON DELIVERY PEC NOTIFICATION
3513 Avviso di mancata consegna NON DELIVERY DUE TO VIRUS PEC
3514 per virus NOTIFICATION
3515 Avviso di mancata consegna NON DELIVERY DUE TO TIMEOUT PEC
3516 per sup. tempo massimo NOTIFICATION
3517
3518
3519
3520
3521
3522
3523
3524 <span class="grey">Petrucci, et al. Informational [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3527
3528
3529 Italian terms in the DTD relative to the certification XML file:
3530
3531 accettazione server-user acceptance
3532 altro other
3533 avvenuta-consegna delivered
3534 certificato certificate
3535 consegna delivery
3536 data date
3537 dati data
3538 destinatari recipients
3539 esterno external
3540 errore error
3541 errore-consegna delivery error
3542 errore-esteso extensive error
3543 gestore-emittente transmitting provider
3544 giorno day
3545 identificativo identifier
3546 intestazione header
3547 mittente sender
3548 no-dest(inatario) no recipient
3549 no-dominio no domain
3550 non-accettazione non acceptance
3551 nessuno none
3552 oggetto subject
3553 ora hour
3554 posta-certificata certified mail
3555 preavviso-errore-consegna delivery error advance notice
3556 presa-in-carico server-server acceptance
3557 ricevuta notification
3558 ricezione receipt (the act of receiving)
3559 rilevazione-virus virus detection
3560 risposte replies
3561 tipo type
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580 <span class="grey">Petrucci, et al. Informational [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc6109">RFC 6109</a> Certified Electronic Mail April 2011</span>
3583
3584
3585 Authors' Addresses
3586
3587 Claudio Petrucci
3588 DigitPA
3589 Viale Marx 31/49
3590 00137 Roma
3591 Italy
3592
3593 EMail: [email protected]
3594
3595 Francesco Gennai
3596 ISTI-CNR
3597 Via Moruzzi, 1
3598 56126 Pisa
3599 Italy
3600
3601 EMail: [email protected]
3602
3603
3604 Alba Shahin
3605 ISTI-CNR
3606 Via Moruzzi, 1
3607 56126 Pisa
3608 Italy
3609
3610 EMail: [email protected]
3611
3612
3613 Alessandro Vinciarelli
3614 Via delle Vigne di Morena 113
3615 00118 Roma
3616 Italy
3617
3618 EMail: [email protected]
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636 Petrucci, et al. Informational [Page 65]
3637 </pre>