ISO/IEC 10021-4:1990/Cor 4:1992
(Corrigendum)Information technology — Text Communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 4: Message Transfer System: Abstract Service Definition and Procedures — Technical Corrigendum 4
Information technology — Text Communication — Message-Oriented Text Interchange Systems (MOTIS) — Part 4: Message Transfer System: Abstract Service Definition and Procedures — Technical Corrigendum 4
Technologies de l'information — Communication de texte — Systèmes d'échange de texte en mode message — Partie 4: Système de transfert de message: Procédures et définition de service abstrait — Rectificatif technique 4
General Information
Relations
Standards Content (Sample)
- -- -
__- -
INTERNATIONAL STANDARD ISO/IEC 10021-4 : 1990
TECHNICAL CORRIGENDUM 4
- -- -
Published 1992-09-1 5
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. MEXfiYHAPOflHAR OPTAHMSAUMR fl0 CTAHflAPTM3AuMM. ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION * MEXfiYHAPOflHAR JIlEKTPOTEXHMYECKAR KOMMCCMR . COMMISSION ELECTROTECHNIQUE INTERNATIONALE
Information technology - Text Communication -
Message-Oriented Text Interchange Systems (MOTIS) -
Part 4:
Message Transfer System : Abstract Service Definition and
Procedu res
TECHNICAL CORRIGENDUM 4
Technologies de I'information - Communication de texte - Systèmes d'échange de texte en mode message -
Partie 4: Système de transfert de message: Procédures et définition de service abstrait
RECTIFICATIF TECHNIQUE 4
Technical corrigendum 4 to International Standard ISO/IEC 10021-4 : 1990 was prepared by Joint Technical Committee ISO/IEC
JTC 1, Information technology.
Page 9
Subclause 8.1.1.1.1.2
Insert a new paragraph six:
"Symmetric algorithms may be used within the above asymmetric-token (see clause 8.5.8)."
Page Il
Subclause 8.1.1.1.2.2
Insert a new last paragraph:
"Symmetric algorithms may be used within the above asymmetric-token (see clause 8.5.8)."
UDC 681.3 : 621.39 Ref. No. ISO/IEC 10021-4 : 19901Cor.4 : 1992 (E)
Descriptors: data processing, information interchange, network interconnection, open systems interconnection, data transmission, text
communication, messages, definitions, procedure.
O ISO/IEC1992
Printed in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 10021-4 : 1990/Cor.4 : 1992 (E)
Page 17
Subclause 8.2.1.1.1.1 1
Delete the following values from Explicit-conversion:
"teletex-to-telex, telex-to-ia5-text, telex-to-teletex, telex-to-g4-class-l, telex-to-videotex, ia5-text-to-telex, telex-to-g3-
facsimile, videotex-to-telex,''
Page I8
Subclause 8.2.1.1.1.14
In the first sentence of the last paragraph replace "mhs-preferred-delivery-method" with "preferredDeliveryMethod.
Page 18
Subclause 8.2.1.1.1.17
Replace the second paragraph with the following:
"This argument's value is the combination of two independent components. If present, the first component shall have one of
the following values: ordinary-mail, special-delivery, express-mail, counter-collection, counter-collection-with-
telephone-advice, counter-collection-with-telex-advice, or counter-collection-with-teletex-advice. If present, the second
component shall have the value bureau-fax-delivery."
Page 20
Subclause 8.2.1.1.1.25
Add to the end of the sentence in the third paragraph:
"with an asymmetric algorithm (see clause 8.5.8)."
Page 21
Subclause 8.2.1.1.1.26
Insert a new last paragraph:
"Symmetric algorithms may be used within the above asymmetric-token (see clause 8.5.8). If symmetric algorithms are used
for both the message-token and the content-integrity-check then the message-token can only support Non Repudiation of
Origin elements-of-service if the security policy in force provides for the involvement of a third party acting as a notary."
2
---------------------- Page: 2 ----------------------
ISO/IEC 10021-4 : 1990/Cor.4 : 1992 (E)
Page 24
Subclause 8.2.1.1.1.34
In the bullet identified by "external:" after " 1984 systems" insert:
": it shall only be used with mts-transfer-protocol-1984"
After this bullet insert a new note:
"NOTE - The interworking rules ensure that the external content-type is never used in conjunction with mts-transfer or mts-
transfer-protocol. Although the external content-type is designed to allow interworking between 1988 systems through
intermediate 1984 systems, a 1984 system may deliver (or submit) a content of the external content-type provided that the MTS-
user (or the MTA itself) performs the equivalent of the upgrading (or downgrading) rules given in ISO/EC 10021-6."
Page 25
Subclause 8 2.1.1.1.34
In the description of inner-envelope, replace:
'I, for forwarding by the recipient named on the outer-envelope to those named on the inner-envelope."
with:
'I. When delivered to the recipient named on the outer-envelope, the outer-envelope is removed and the content is deciphered,
if needed, resulting in an inner-envelope and its content. The information contained in the inner-envelope is used to transfer
the content of the inner-envelope to the recipients named on the inner-envelope."
Page 25
Subclause 8.2.1.1.1.37
The word content in the second paragraph should be in bold face.
Add at the end of the subclause:
"NOTE - The value of the octet string containing the encoded content does not change as the message crosses the MTS."
Pages 26-27
Subclause 8.2.1.1.2.4
In the third paragraph replace "the arguments of the submitted message (see clause 8.2.1.1.1)" with "the Message-submission
arguments (see clause 8.2.1.1.1) of the subject message".
Delete the last sentence of the third paragraph.
3
---------------------- Page: 3 ----------------------
ISO/IEC 10021-4 : 1990Kor.4 : 1992 (E)
Page 40
Subclause 8.3.1.1.1.4
In the first paragraph, replace the last sentence with "An additionai value of this argument shall be present for each occasion
the message was redirected.".
Page 40
Subclause 8.3.1.1.1.5
In the first paragraph, replace the last sentence with "An additional value of this argument shall be present for each occasion
the message was redirected.".
Page 40
Subclause 8.3.1.1.1.6
Replace the first paragraph with the following:
"If the originator of the message requested disclosure of other recipients, this argument contains the OR-names of the
originally-specified recipients other than the one (if any) identified by either the originally-intended-recipient-name
argument, if present, or else by the this-recipient-name argument. This argument shall be generated by the MTS if, and only
if, the message-submission abstract-operation had the disclosure-of-other-recipients argument set to disclosure-of-other-
recipients-requested and there is at least one such other recipient."
Add at the end of the subclause:
"NOTE-If DL expansion has been performed, the OR-names of the DL's members are not disclosed. The OR-name of the DL is
disclosed if, and only if, it is that of an originally-specified recipient."
Page 49
Subclause 8.3.1.2.1.11
Add new non-delivery-diagnostic-codes to the end of the list, replacing the full stop at the end of "unable-to-downgrade''
by a semi-colon:
"unable-to-complete-transfer: receiving system has indicated that it is permanently unable to complete transfer of
the subject; for example, when the transfer is of such a size that it could never be accepted:
transfer-attempts-limit-reached: the maximum number or time duration of repeat attempts to transfer the subject
was reached."
4
---------------------- Page: 4 ----------------------
ISO/IEC 10021-4 : 1990/Cor.4 : 1992 (E)
Page 49
Subclause 8.3.1.2.1.13
To improve its clarity, replace the fourth paragraph by:
"The report-origin-authentication-check contains the report-origin-authentication-algorithm-identifier and an
asymmetrically-encrypted hashed version of
the report-origin-authentication-algorithm-identi~er;
the content-identifier of the subject;
the message-security-label of the subject;
and all values of the following (per-recipient) arguments:
the actual-recipient-name,
the originally -intended-recipient-name, and:
for a delivery-report:
the message-delivery-time,
the type-of-MTS-user,
the recipient-certificate if requested by the originator of the message for
recipients to which the report relates,
the proof-of-delivery if requested by the originator of the message for recipients
to which the report relates and if the report is on a message; or
for a non-delivery-report:
the non-delivery-reason-code, and
the non-delivery-diagnostic-code."
Page 6
Subclause 8.5.2
Add a new sentence at the end of the third paragraph "If the identification is relative to the associated ADMD then that
administration-domain-name shall be present." and delete Note 2.
Page 62
Subclause 8.5.5
In the fourth paragraph replace 'I, optionally a number of extension-attributes" with " selected from those defined in
ISO/IEC 10021-2"
5
---------------------- Page: 5 ----------------------
ISOhEC 10021-4 : 1990/Cor.4 : 1992 (E)
Replace the last paragraph with
"In the abstract syntax definition in clause 9, the standard attributes are represented by built-in-standard-attributes and by
extension-sîandard-attributes and the domain-defined attnbutes are represented by built-in-domain-defined-attributes and
extension-domain-defined-attributes.
by
Clause 18.5 of ISODEC 10021-2 specifies several OR-address forms. These define which standard and domain-defined
attnbutes may be used together to construct a valid OR-address.
Clause 18.3 of ISO/iEC 10021-2 specifies rules indicating the character sets - numeric, printable, and teletex - from which the
values of a particular standard attribute may be drawn, and it also defines the valid combinations of the different variants of
that standard atîribute in the abstract syntax."
Page 62
Subclause 8.5.6
Delete the second paragraph.
In the (existing) third paragraph delete the sentence "The telex type is defined in CCITT Recommendation F.1.". In the
penultimate sentence replace "(sfd) type is" with "(sfd) type and the telex type were" and replace "SFDs" with "SFD and TLX
body parts".
After the (existing) third paragraph insert the following new paragraphs:
"Externally -defined encoded-information-types are those which are not basic encoded-information-types.
In the abstract syntax definition in clause 9, the encoded-information-types are the logical union of built-in-encoded-
information-types and extended-encoded-information-types. The latter are those to which object-identifiers have been
allocated by an appropriate authority. They include both standardised and privately-defined encoded-information-types.
A basic encoded-information-type may be represented equivalently by a bit in the built-in-encoded-information-types or
by an extended-encoded-information-type. Annex A acts as the registration authority for the object-identifiers to be used as
the extended-encoded-information-type registrations of the basic encoded-information-types.
An extemally-defined encoded-information-type is always represented by an extended-encoded-information-type. Other
standards define object-identifiers that may be used as extended-encoded-information-types."
Page 63
Subclause 8.5.7
In the second paragraph replace "A certificate contains the following parameters:" with:
"A certificate contains one or more items of certification information. Each instance of certification information contains the
following parameters:"
Change the description of the "subject-public-keys" parameter to:
"subject-public-key : the public-asymmetric-encryption-keys of the subject;"
Change the description of the "algorithms" parameter to:
"algorithm: the algorithm-identifiers, associated with a subject-public-key;"
6
---------------------- Page: 6 ----------------------
ISO/IEC 10021-4 : 1990/Cor.4 : 1992 (E)
Replace the 8th paragraph, starting "The form of a certificate" with:
"The form of 8 certificate is defined in ISODEiC 9594-8 as the data-type certificates."
Page 64
Subclause 8.5.8
Change the description of the "recipient-name'' parameter to:
"recipient-name: either the OR-address-and-or-directory-name of the intended-recipient of the token or, when
MTAs use strong authentication during a bind, the MTA-name and optionally the global-domain-identifier;"
Page 70
Figure 2 (Part 3 of 26)
iI)
Insert the keyword IMPLICIT in the production for "MessageSubmission":
extensions I11 IMPLICIT EXTENSIONS CHOSEN FR OM f
Page 72
Figure 2 (Part 5 of 26)
Insert the keyword IMPLICIT in the production for "MessageDelivery 'I:
proof : -of - T ro f el'ver OP O A
Page 74
0 Figure 2 (Part 7 of 26)
Insert the keyword IMPLICIT in the production for "PerMessageSubmissionFields":
stens ions 121 I MPLICIT PerMessaaeSubmissionExtensions DEFAULT l 1 I
Page 75
Figure 2 (Part 8 of 26)
Insert the keyword IMPLICIT in the produc tion for "PerRecipientMessageSubmissionFields":
,
extensions 121 IMPLICIT PerRecioientMessaaeSubmissionExtensions DEFAULT { 1
I
Insert the keyword IMPLICIT in the produc tion for "PerProbeSubmissionFields":
1
I
extensions i21 IM PLICIT EXTENSIONS CHOS EN FROM f
7
---------------------- Page: 7 ----------------------
ions 12 1 IMPJ,ICIT EXTENSIONS CHOSEN
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.