ISO/IEC 10021-5:1996/Cor 3:2000
(Corrigendum)Information technology — Message Handling Systems (MHS): Message store: Abstract service definition — Part 5: — Technical Corrigendum 3
Information technology — Message Handling Systems (MHS): Message store: Abstract service definition — Part 5: — Technical Corrigendum 3
Technologies de l'information — Systèmes de messagerie (MHS): Mémoire de messages: Définition du service abstrait — Partie 5: — Rectificatif technique 3
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 10021-5:1996
TECHNICAL CORRIGENDUM 2
TECHNICAL CORRIGENDUM 3
Published 2000-05-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION � МЕЖДУНАРОДНАЯОРГАНИЗАЦИЯПОСТАНДАРТИЗАЦИИ � ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION � МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ � COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Message Handling Systems (MHS):
Message store: Abstract service definition
TECHNICAL CORRIGENDUM 2
TECHNICAL CORRIGENDUM 3
Technologies de l'information — Systèmes de messagerie (MHS): Dépôt de message: Définition de service abstrait
RECTIFICATIF TECHNIQUE 2
RECTIFICATIF TECHNIQUE 3
Technical Corrigenda 2 and 3 to International Standard ISO/IEC 10021-5:1996 were prepared byJoint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information
exchange between systems.
ICS 35.240.20 Ref. No. ISO/IEC 10021-5:1996/Cor.2:2000(E)
ISO/IEC 10021-5:1996/Cor.3:2000(E)
© ISO/IEC 2000 – All rights reserved
Printed in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 10021-5:1996/Cor.2:2000 (E) & Cor.3:2000 (E)
INTERNATIONAL STANDARD
ISO/IEC 10021-5 : 1995/Cor.2 (1997) E & Cor.3 (1998) E
ITU-T Rec. X.413 (1995)/Cor.2 (1997E) & Cor.3 (1998E)
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY – MESSAGE HANDLING SYSTEMS (MHS):
MESSAGE STORE: ABSTRACT SERVICE DEFINITION
TECHNICAL CORRIGENDUM 2 AND CORRIGENDUM 3
1 Subclause 6.5.2
Append the following to 6.5.2, bullet b):
This component is disregarded in the case where the auto-action-type supports only a single registration.
In 6.5.2, bullet c), change "(O)" to "(C)".
Append the following to 6.5.2, bullet c):
This shall be present if the auto-action-type identifies an auto-action for which a registration parameter is
defined, and is absent otherwise.
2 Subclause 7.1.1
In 7.1.1, bullet b) second paragraph third sentence "If strong-authentication .", append "or certificate-
selector". In the fourth sentence replace "initiator-bind-token and initiator-certificate" by "initiator-bind-token,
initiator-certificate and certificate-selector". Insert after the fourth sentence "The initiator-certificate shall
contain the OR-address of the MS-user in the x400Address component in its subject alternative name field (see
12.3.2.1 of ITU-T Rec. X.509 | ISO/IEC 9594-8), unless the security-policy provides an alternative binding of
the certificate to the MS-user.".
3 Subclause 7.1.2
In 7.1.2, in the ASN.1 replace:
additional-capabilities [9] MSExtensions OPTIONAL,
by:
bind-result-extensions [9] MSExtensions OPTIONAL,
In 7.1.2, bullet a) second paragraph third sentence "If strong-authentication .", append ", and, optionally, a
responder-certificate or certificate-selector". In the fourth sentence replace "responder-bind-token is" by
"responder-bind-token, responder-certificate and certificate-selector are". Insert after the fourth sentence "The
responder-certificate shall contain the OR-address of the MS in the x400Address component in its subject
alternative name field (see 12.3.2.1 of ITU-T Rec. X.509 | ISO/IEC 9594-8), unless the security-policy provides
an alternative binding of the certificate to the MS.".
ITU-T Rec. X.413 (1995)/Cor.2 (1997E) & Cor.3 (1998E) 1
---------------------- Page: 2 ----------------------
ISO/IEC 10021-5:1996/Cor.2:2000 (E) & Cor.3:2000 (E)
Replace bullet h) by:
h) Bind-result-extensions (C): This parameter allows for future general and content-specific
extensions to MS-bind-result. If the MS supports one or more additional capabilities whose
specification defines an MS-extension to indicate that capability, the specified extensions
shall be present. MS-extensions to indicate additional capabilities defined in this Service
Definition are listed in Annex F; further extensions may be defined in future editions of this
Service Definition, in content-specific Specifications, or to indicate proprietary capabilities.
4 Subclause 8.1.6
In 8.1.6, replace item d) with the following:
d) MS-submission-extensions (O): This component allows for general and content-specific extensions to
MS-submission-options. The Specification for a given content-type defines its use of this component.
In the absence of the component, no MS-submission-extensions are specified. This Service Definition
defines the following extension:
– Originator-token (O): This extension is used where the submitted message contains a
message-token which contains encrypted-data that has been encrypted such that it cannot
subsequently be decrypted by the originator. This extension enables the originator to supply a
message-token constructed as if the originator were a recipient of the message, to be stored in
the submitted-message entry but not submitted to the MTS. Subsequently, the originator may
retrieve this information and use it to recover the original message.
originator-token MS-EXTENSION ::= {
OriginatorToken IDENTIFIED BY id-ext-originator-token}
OriginatorToken ::= MessageToken
(CONSTRAINED BY {-- Must contain an asymmetric-token with an
-- encrypted-data
component --}
The originator-token contains a message-token argument of the Message-submission
abstract-operation (see 8.2.1.1.1.26 of ITU-T Rec. X.411 | ISO/IEC 10021-4) which contains
an encrypted-data component that is encrypted using the public key of the message originator.
NOTES
1 When storage-on-submission is used, the originator retains a copy of the message in the MS,
but is not treated as a recipient in the message submission envelope. This extension provides the
originator with the security arguments that are encrypted on a per-recipient basis for the conventional
recipients of the message. Note that content-integrity-check does not need to be duplicated here, as it is
only a signature, and so the originator is implicitly able to use any of the values provided for the other
recipients.
2 If Content Confidentiality is provided using a symmetric encryption algorithm with a content-
confidentiality-key (session key) which is itself encrypted such that it requires each recipient's private
key to decrypt it, then the message’s originator would have no means of decrypting the copy of the
message as stored in the MS on submission. This MS-submission-extension enables the MS-user to
supply a value with the submitted message, which is stored in the submitted-message entry but is not
included in the message submitted to the MTS. This contains the session key for the message, encrypted
with the public key of the submitting MS-user. When the MS-user subsequently retrieves the submitted-
message, his private key may be used to decrypt the session key, and hence decrypt the message.
3 Where Content Confidentiality is provided by use of a symmetric algorithm, and a method
other than the message-token is used to distribute the key, then the originating MS-user must employ a
different mechanism to retain the key and so enable subsequent decryption of the stored-message.
4 Where Content Confidentiality is provided directly by use of an asymmetric algorithm, it is
unlikely that storage on submission will be useful, except where the key pair is shared between users,
including the originating MS-user, who thus has access to both public and private keys.
2 ITU-T Rec. X.413 (1995)/Cor.2 (1997E) & Cor.3 (1998E)
---------------------- Page: 3 ----------------------
ISO/IEC 10021-5:1996/Cor.2:2000 (E) & Cor.3:2000 (E)
5 Subclause 8.2.5.1
In 8.2.5.1 and Annex B, in the production for Register-MSArgument, replace the lines for old and new
credentials by:
old-credentials [0] Credentials (WITH COMPONENTS { simple }),
new-credentials [1] Credentials (WITH COMPONENTS { simple })}
OPTIONAL,
6 Subclause 8.2.7. 2
In 8.2.7.2, replace bullet a) with the following, preserving the Note:
a) Entries-modified (C): This identifies the entries selected for modification. It is present if the
selector component was present in the modify-argument, and at least one entry was selected
for modification. It is absent otherwise.
7 Table 2
In Table 2, in the row Message-identifier, in columns submitted-message entry and submitted-probe entry,
change "P" to "C".
In Table 2, replace the row for "Message-token" by:
Presence in: Support level by Single/
Available Available
MS multi-
for for
delivered- delivered- returned- submitted- submitted- draft- Stored- Message-
List Summar-
valued
Attribute-type name
message report content message probe message message log entry-
ize
entry entry entry entry* entry* entry* entry-class class*
Message-token* C – – C – C O O S Y N
8 Subclause 11.2.34 (renumbered to 11.2.35 by Amendment 1)
In 11.2.34, paragraph 1, after the second sentence insert:
Where Message-submission or Probe-submission fails, the attribute is absent from any entry created in the
Message-log entry class. Where Message-submission or Probe-submission succeeds, the attribute is present in
any entry created in the Stored-message entry class.
9 Subclause 11.2.40 (renumbered to 11.2.41 by Amendment 1)
Replace the first paragraph of clause 11.2.40 by:
This general attribute contains the message-token argument of the Message-delivery abstract-operation or the
originator-token argument of the Message-submission abstract-operation. When present in submitted-message
entries, this attribute contains an encrypted-data component that is encrypted using the public key of the
message originator rather than that of any recipient. It may be generated by the originator of the message. See
8.2.1.1.1.26 of ITU-T Rec. X.411 | ISO/IEC 10021-4 and 8.1.6.
ITU-T Rec. X.413 (1995)/Cor.2 (1997E) & Cor.3 (1998E) 3
---------------------- Page: 4 ----------------------
ISO/IEC 10021-5:1996/Cor.2:2000 (E) & Cor.3:2000 (E)
10 Table 4
In Table 4, replace the row for "Message-token" by:
Single
Source
Source parameter
/multi
generated
Attribute-type name Generation rules
valued
by
Message-token S message-token Md The attribute-value is the value of the
source parameter.
originator-token Ms The attribute-value is the value of the
source parameter.
11 Clause 13
Append the following to clause 13 (before 13.1
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.