NPR-CEN/TS 15121-1:2011 en

Postdiensten - Hybride post - Deel 1: Beveiligde elektronische postdiensten(SePS) Interfacespecificatie - Concepten, schema's en toepassingen

123,83 149,83 Incl BTW

Over deze norm

Status Definitief
Aantal pagina's 132
Commissie Post
Gepubliceerd op 01-01-2011
Taal Engels
This document specifies a standard XML interface that will enable software applications to call a secured electronic postal service (SePS), provided by a postal service, which is based on the concepts, schemas and operations described herein. The specification provides: - a definition of standard operations which can be combined to support secured electronic postal services; - a full description of all mandatory and optional request parameters required for use of these operations; - a full description of all response elements and the detailed circumstances under which they are returned. The specification also describes the functionality and edit rules of the actual technical specification artifacts, which are represented by an XML Schema (XSD) and an associated Web Services Definition Language (WSDL) specification. The versions of these applicable at the date of publication of this version of the specification are contained in this document as Annex A and Annex B respectively. These can also be obtained in electronic format from the UPU Technical Standards CD-ROM or from the UPU Standards Secretariat. In case of any conflict between Annex A and other provisions of this specification, Annex A shall be regarded as definitive. The SePS schema specification in Annex A is discreet and version specific. Postal Services are free to select which discrete interface versions they support. However, except in the case of upgrades to V1.15 adopted to ensure cross-border compatibility, postal services who upgrade from older versions of the schema (e.g. from V1.14) to a newer one are required to support backward compatibility of previously supported versions of the SePS interface specification as it applies to both processing requests/responses and honoring previously issued PostMarkedReceipts. Individual posts are free to address this backward compatibility challenge as they see fit. The Version element which is present in every request and which is included in the PostMarkedReceipt can be used to support this backwards compatibility requirement. The requirement for backward compatibility does not apply to cross-border scenarios where V1.15 has been adopted to ensure compatibility. The SePS Interface specification includes a digital signature platform supporting basic cryptographic service operations as well as a comprehensive framework for the delivery of evidentiary, witnessing, and non-repudiation services. The specification provides for continued support of legacy CMS/PKCS7 binary signatures. This approach allows subscribing applications to leverage the strengths of both protocols and can aid in the migration from one to the other. The schema will continue to support, in an interchangeable way, use of both CMS/PKCS7 and XMLDSIG artifacts. SePS implementations are free to support the "XML Signature Syntax and Processing" standard (i.e. XMLDSIG) for all elements presently carrying PKCS7 content. Selection of either format is supported across the two prevalent signature formats within this domain. XML Encryption is also supported. The specification: - complies with IETF RFC 3161 in respect of time stamp tokens, time stamp values and other time stamp attributes; - complies with all mandatory requirements (i.e. qualified as "required" or "shall" in the text) of IETF RFC 3126 and ETSI TS 101 733 as they apply to Electronic Signatures - Complete (i.e. ES-C); - complies with the IETF RFC 2630 ASN.1 layout for all PKCS objects utilised in the specification; - supports XMLDSIG signature formatting as defined in IETF RFC 3275; - complies with IETF RFC 2560 in respect of the ValidationData element. This version of the specification does not cover: - a description of the issues surrounding inter-operability between multiple postal SePS implementations when a business transaction Lifecycle requires the participation of more than one SePS implementation in a cross-border scenario involving two or more postal services; - issues surrounding SePS usage in a ‘multiple Certificate Authority’ scenario where inter-operating posts are participating in a cross-border transaction as described above; - examination of 'Certificate Authority deployment model' alternatives necessitated by the cross-border scenarios described above.


ICS-code 3.240
Nederlandse titel Postdiensten - Hybride post - Deel 1: Beveiligde elektronische postdiensten(SePS) Interfacespecificatie - Concepten, schema's en toepassingen
Engelse titel Postal Services - Hybrid Mail - Part 1: Secured electronic postal services (SePS) interface specification - Concepts, schemas and operations



Ga naar winkelwagen