La Posta Elettronica Certificata - Italian Certified Electronic Mail
RFC 6109
| Document | Type |
RFC - Informational
(April 2011; Errata)
Was draft-gennai-smime-cnipa-pec (individual in gen area)
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6109 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jari Arkko | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) C. Petrucci
Request for Comments: 6109 DigitPA
Category: Informational F. Gennai
ISSN: 2070-1721 A. Shahin
ISTI-CNR
A. Vinciarelli
April 2011
La Posta Elettronica Certificata - Italian Certified Electronic Mail
Abstract
Since 1997, the Italian laws have recognized electronic delivery
systems as legally usable. In 2005, after two years of technical
tests, the characteristics of an official electronic delivery
service, named certified electronic mail (in Italian "Posta
Elettronica Certificata") were defined, giving the system legal
standing.
The design of the entire system was carried out by the National
Center for Informatics in the Public Administration of Italy
(DigitPA), followed by efforts for the implementation and testing of
the service. The DigitPA has given the Italian National Research
Council (CNR), and in particular the Institute of Information Science
and Technologies at the CNR (ISTI), the task of running tests on
providers of the service to guarantee the correct implementation and
interoperability. This document describes the certified email system
adopted in Italy. It represents the system as it is at the moment of
writing, following the technical regulations that were written based
upon the Italian Law DPR. November 2, 2005.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It has been approved for publication by the Internet
Engineering Steering Group (IESG). Not all documents approved by the
IESG are a candidate for any level of Internet Standard; see Section
2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6109.
Petrucci, et al. Informational [Page 1]
RFC 6109 Certified Electronic Mail April 2011
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Petrucci, et al. Informational [Page 2]
RFC 6109 Certified Electronic Mail April 2011
Table of Contents
1. Introduction ....................................................5
1.1. Scope ......................................................5
1.2. Notational Conventions .....................................6
1.2.1. Requirement Conventions .............................6
1.2.2. Acronyms ............................................6
1.2.3. Terminology and Definitions .........................7
2. PEC Model .......................................................8
2.1. System-Generated Messages ..................................8
2.1.1. Message Types ......................................10
2.2. Basic Structure ...........................................12
2.2.1. Access Point .......................................12
2.2.2. Incoming Point .....................................14
2.2.3. Delivery Point .....................................16
2.2.4. Storage ............................................17
2.2.5. Provider Service Mailbox ...........................17
2.2.6. Provider Service Email Address .....................17
2.3. Log .......................................................17
3. Message Processing .............................................18
3.1. Access Point ..............................................18
3.1.1. Formal Checks on Messages ..........................18
3.1.2. Non-Acceptance PEC Notification Due to
Formal Exceptions ..................................19
3.1.3. Non-Acceptance PEC Notification Due to
Show full document text