SIST EN 28601:2004
(Main)Data elements and interchange formats - Information interchange - Representation of dates and times (ISO 8601:1988 and its technical corrigendum 1:1991)
Data elements and interchange formats - Information interchange - Representation of dates and times (ISO 8601:1988 and its technical corrigendum 1:1991)
Datenelemente und Austauschformate - Informationsaustausch - Darstellung von Datum und Uhrzeit (ISO 8601:1988 und Technical Corrigendum 1:1991)
Eléments de données et formats d'échange - Echange d'information - Représentation de la date et de l'heure (ISO 8601:1988 et corrigendum technique 1:1991)
Podatkovni elementi in izmenjevalni formati – Izmenjava informacij – Prikaz datuma in časa (ISO 8601:1988 in tehnični popravek 1:1991)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Datenelemente und Austauschformate - Informationsaustausch - Darstellung von Datum und Uhrzeit (ISO 8601:1988 und Technical Corrigendum 1:1991)Eléments de données et formats d'échange - Echange d'information - Représentation de la date et de l'heure (ISO 8601:1988 et corrigendum technique 1:1991)Data elements and interchange formats - Information interchange - Representation of dates and times (ISO 8601:1988 and its technical corrigendum 1:1991)35.040Nabori
...
This May Also Interest You
REN/ESI-0019122-1v1.3.1
- Standard63 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard63 pagesEnglish languagesale 15% off
- Standard63 pagesEnglish languagesale 15% off
- Draft63 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies policy and security requirements relating to the operation and management practices of
TSPs issuing time-stamps.
These policy requirements are applicable to TSPs issuing time-stamps. Such time-stamps can be used in support of
digital signatures or for any application requiring to prove that a datum existed before a particular time.
The present document can be used by independent bodies as the basis for confirming that a TSP can be trusted for
issuing time-stamps.
The present document does not specify protocols used to access the TSUs.
NOTE 1: A time-stamping protocol is defined in IETF RFC 3161 [i.2] including optional update in IETF
RFC 5816 [i.3] and profiled in ETSI EN 319 422 [5].
The present document does not specify how the requirements identified can be assessed by an independent party,
including requirements for information to be made available to such independent assessors, or requirements on such
assessors.
NOTE 2: See ETSI EN 319 403-1 [i.9] for guidance on assessment of TSP's processes and services.
NOTE 3: The present document references ETSI EN 319 401 [4] for general policy requirements common to all
classes of TSP's services.
- Standard33 pagesEnglish languagesale 15% off
- Standard33 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard33 pagesEnglish languagesale 15% off
- Draft33 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies the interoperability profiles of the Registered Electronic Mail (REM) messages
according to the formats defined in ETSI EN 319 532-3 [6] and the concepts and semantics defined in ETSI
EN 319 532-1 [4] and ETSI EN 319 532-2 [5]. It deals with issues relating to authentication, authenticity and integrity
of the information, with the purpose to address the achievement of interoperability across REM service providers,
implemented according to the aforementioned specifications.
The present document covers all the options to profile REM services for both styles of operation: S&N and S&F.
The mandatory requirements defined in the aforementioned referenced REM services specifications are not normally
repeated here, but, when necessary, the present document contains some references to them.
More specifically, the present document:
a) Defines generalities on profiling.
b) Defines constraints for SMTP profile.
The present document also specifies a REM baseline supporting the technical interoperability amongst service providers
in different regulatory frameworks.
NOTE: Specifically but not exclusively, REM baseline specified in the present document aims at supporting
implementations of interoperable REM services by use of Trusted List Frameworks to constitute Trusted
domains and qualified REM services (instances of electronic registered delivery services) by use of EU
Trusted List system as per Regulation (EU) No 910/2014 [i.1].
- Standard97 pagesEnglish languagesale 15% off
- Standard97 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard97 pagesEnglish languagesale 15% off
- Draft97 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies XAdES digital signatures. XAdES signatures build on XML digital signatures [1], by
incorporation of signed and unsigned qualifying properties, which fulfil certain common requirements (such as the long
term validity of digital signatures, for instance) in a number of use cases.
The present document specifies XML Schema definitions for the aforementioned qualifying properties as well as
mechanisms for incorporating them into XAdES signatures.
The present document specifies formats for XAdES baseline signatures, which provide the basic features necessary for
a wide range of business and governmental use cases for electronic procedures and communications to be applicable to
a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic
documents.
The present document defines four levels of XAdES baseline signatures addressing incremental requirements to
maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the
requirements addressed at levels that are below it. Each level requires the presence of certain XAdES qualifying
properties, suitably profiled for reducing the optionality as much as possible.
Procedures for creation, augmentation, and validation of XAdES digital signatures are out of scope and specified in
ETSI EN 319 102-1 [i.6]. Guidance on creation, augmentation and validation of XAdES digital signatures including the
usage of the different properties defined in the present document is provided in ETSI TR 119 100 [i.11].
The present document aims at supporting electronic signatures in different regulatory frameworks.
NOTE: Specifically but not exclusively, XAdES digital signatures specified in the present document aim at
supporting electronic signatures, advanced electronic signatures, qualified electronic signatures,
electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU)
No 910/2014 [i.1].
- Standard74 pagesEnglish languagesale 15% off
- Standard74 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard74 pagesEnglish languagesale 15% off
- Draft74 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies a certificate profile for web site certificates that are accessed by the TLS protocol [i.1].
The profile defined in the present document builds on the CA/Browser Forum Baseline requirements [2], Extended
validation guidelines [3] and other parts of the present multipart deliverable.
The present document focuses on requirements on certificate content. Requirements on decoding and processing rules
are limited to aspects required to process certificate content defined in the present document. Further processing
requirements are only specified for cases where it adds information that is necessary for the sake of interoperability.
This profile can be used for legal and natural persons. For certificates issued to legal persons, the profile builds on the
CAB Forum EV Profile [3] or baseline requirements [2]. For certificates issued to natural persons, the profile builds
only on CAB Forum baseline requirements [2].
- Standard10 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard10 pagesEnglish languagesale 15% off
- Standard10 pagesEnglish languagesale 15% off
- Draft10 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies policy and security requirements for the issuance, maintenance and life-cycle
management of EU qualified certificates as defined in Regulation (EU) No 910/2014 [i.1]. These policy and security
requirements support reference certificate policies for the issuance, maintenance and life-cycle management of EU
qualified certificates issued to natural persons (including natural persons associated with a legal person or a website)
and to legal persons (including legal persons associated with a website), respectively.
The present document does not specify how the requirements identified can be assessed by an independent party,
including requirements for information to be made available to such independent assessors, or requirements on such
assessors.
NOTE: See ETSI EN 319 403 [i.6] for guidance on assessment of TSP's processes and services. The present
document references ETSI EN 319 411-1 [2] for general requirements on TSP issuing certificates.
- Standard31 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard31 pagesEnglish languagesale 15% off
- Standard31 pagesEnglish languagesale 15% off
- Draft31 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies procedures for:
• the creation of AdES digital signatures (specified in ETSI EN 319 122-1 [i.2], ETSI EN 319 132-1 [i.4], ETSI
EN 319 142-1 [i.6] respectively);
• establishing whether an AdES digital signature is technically valid;
whenever the AdES digital signature is based on public key cryptography and supported by Public Key Certificates
(PKCs). To improve readability of the present document, AdES digital signatures are meant when the term signature is
being used.
NOTE 1: Regulation (EU) No 910/2014 [i.15] defines the terms electronic signature, advanced electronic signature,
electronic seals and advanced electronic seal. These signatures and seals are usually created using digital
signature technology. The present document aims at supporting the Regulation (EU) No 910/2014 [i.15]
for creation and validation of advanced electronic signatures and seals when they are implemented as
AdES digital signatures.
The present document introduces general principles, objects and functions relevant when creating or validating
signatures based on signature creation and validation constraints and defines general classes of signatures that allow for
verifiability over long periods.
The following aspects are considered to be out of scope:
• generation and distribution of Signature Creation Data (keys, etc.), and the selection and use of cryptographic
algorithms;
• format, syntax or encoding of data objects involved, specifically format or encoding for documents to be
signed or signatures created; and
• the legal interpretation of any signature, especially the legal validity of a signature.
NOTE 2: The signature creation and validation procedures specified in the present document provide several
options and possibilities. The selection of these options is driven by a signature creation policy, a
signature augmentation policy or a signature validation policy respectively. Note that legal requirements
can be provided through specific policies, e.g. in the context of qualified electronic signatures as defined
in the Regulation (EU) 910/2014 [i.15].
- Standard83 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard83 pagesEnglish languagesale 15% off
- Standard83 pagesEnglish languagesale 15% off
- Draft83 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies CAdES digital signatures. CAdES signatures are built on CMS signatures [7], by incorporation of signed and unsigned attributes, which fulfil certain common requirements (such as the long term validity of digital signatures, for instance) in a number of use cases. The present document specifies the ASN.1 definitions for the aforementioned attributes as well as their usage when incorporating them to CAdES signatures. The present document specifies formats for CAdES baseline signatures, which provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. The present document defines four levels of CAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the requirements addressed at levels that are below it. Each level requires the presence of certain CAdES attributes, suitably profiled for reducing the optionality as much as possible. Procedures for creation, augmentation and validation of CAdES digital signatures are out of scope and specified in ETSI EN 319 102-1 [i.5]. Guidance on creation, augmentation and validation of CAdES digital signatures including the usage of the different properties defined in the present document is provided in ETSI TR 119 100 [i.4]. The present document aims at supporting digital signatures in different regulatory frameworks. NOTE: Specifically, but not exclusively, CAdES digital signatures specified in the present document aim at supporting electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.13].
- Standard62 pagesEnglish languagesale 15% off
- Standard62 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard62 pagesEnglish languagesale 15% off
- Draft62 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document:
1) Specifies a JSON [1] format for AdES signatures (JAdES signatures hereinafter) built on JSON Web
Signatures (JWS hereinafter) as specified in IETF RFC 7515 [2]. For this, the present document:
- Extends the JSON Web Signatures specified in IETF RFC 7515 [2] by defining an additional set of
JSON header parameters that can be incorporated in the JOSE Header (either in its JWS Protected
Header or its JWS Unprotected Header parts). Many of these new header parameters have the same
semantics as the attributes/properties defined in CAdES [i.2] and XAdES [4] digital signatures. Other
header parameters are defined to meet specific requirements that current JSON Web Signatures cannot
meet (e.g. for explicitly referencing detached JWS Payload). These new header parameters and their
corresponding types are defined in a JSON schema.
- Specifies the mechanisms for incorporating the aforementioned JSON components in JSON Web
Signatures [2] to build JAdES signatures, offering the same features as CAdES and XAdES in JSON
syntax, and therefore fulfilling the same requirements (such as the long-term validity of digital
signatures).
2) Defines four levels of JAdES baseline signatures addressing incremental requirements to maintain the validity
of the signatures over the long term. Each level requires the presence of certain JAdES header parameters,
suitably profiled for reducing the optionality as much as possible. The aforementioned levels provide the basic
features necessary for a wide range of business and governmental use cases for electronic procedures and
communications to be applicable to a wide range of communities when there is a clear need for
interoperability of digital signatures used in electronic documents.
EXAMPLE: An example of requirements raised in specific domains is signing HTTP messages exchanged by
parties in certain environments, which require signing both the HTTP body and some specific http
headers. The format specified in IETF RFC 7515 [2] does not provide any native mechanism for
individually identifying a detached JWS Payload. Clause 5.2.8 of the present document defines
sigD, a new JSON header parameter that allows to identify one or more detached data objects
which, suitably processed and concatenated, form the detached JWS Payload.
Procedures for creation, augmentation, and validation of JAdES digital signatures are out of scope.
NOTE 1: ETSI EN 319 102-1 [i.3] specifies procedures for creation, augmentation and validation of other types of
AdES digital signatures.
The present multi-part deliverable aims at supporting electronic signatures independent of any specific regulatory
framework.
NOTE 2: Specifically, but not exclusively, it is the aim that JAdES digital signatures specified in the present
multi-part deliverable can be used to meet the requirements of electronic signatures, advanced electronic
signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified
electronic seals as defined in Regulation (EU) No 910/2014 [i.1].
- Standard59 pagesEnglish languagesale 15% off
- Technical specification59 pagesEnglish languagesale 10% offe-Library read for×1 day
The present document specifies policy and security requirements for the issuance, maintenance and life-cycle
management of EU qualified certificates as defined in Regulation (EU) No 910/2014 [i.1]. These policy and security
requirements support reference certificate policies for the issuance, maintenance and life-cycle management of EU
qualified certificates issued to natural persons (including natural persons associated with a legal person or a website)
and to legal persons (including legal persons associated with a website), respectively.
The present document does not specify how the requirements identified can be assessed by an independent party,
including requirements for information to be made available to such independent assessors, or requirements on such
assessors.
NOTE: See ETSI EN 319 403 [i.6] for guidance on assessment of TSP's processes and services. The present
document references ETSI EN 319 411-1 [2] for general requirements on TSP issuing certificates.
- Standard31 pagesEnglish languagesale 15% off
- Standard31 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard31 pagesEnglish languagesale 15% off
- Draft31 pagesEnglish languagesale 10% offe-Library read for×1 day
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.