ISO/IEC 10021-5:1996/Cor 1:1998

Information technology — Message Handling Systems (MHS): Message store: Abstract service definition — Part 5: — Technical Corrigendum 1

Technologies de l'information — Systèmes de messagerie (MHS): Mémoire de messages: Définition du service abstrait — Partie 5: — Rectificatif technique 1

General Information

• Status: Withdrawn
• Publication Date: 02-Sep-1998
• Withdrawal Date: 02-Sep-1998
• ICS: 35.240.20 - IT applications in office work
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 16-Nov-2000

Relations

• Revised: ISO/IEC 10021-5:1999 - Information technology — Message Handling Systems (MHS): Message store: Abstract service definition — Part 5:
• Effective Date: 15-Apr-2008
• Corrects: ISO/IEC 10021-5:1996 - Information technology — Message Handling Systems (MHS): Message store: Abstract service definition — Part 5:
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 10021-5:1996 - Information technology — Message Handling Systems (MHS): Message store: Abstract service definition — Part 5:
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 10021-5:1996
TECHNICAL CORRIGENDUM 1
bc
Published 1998-09-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 1
Technologies de l’information — Systèmes de messagerie (MHS): Dépôt de message: Définition de service abstrait
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to International Standard ISO/IEC 10021-5:1996 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 33, Distributed application services.

ICS 35.240.20 Ref. No. ISO/IEC 10021-5:1996/Cor.1:1998(E)
Descriptors: data processing, information interchange, network interconnection, open systems interconnection, data transmission, text
communication, messages, message handling systems, message store.
©
  ISO/IEC 1998
Printed in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 10021-5 : 1996/Cor.1 : 1998 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY – MESSAGE HANDLING SYSTEMS (MHS):
MESSAGE STORE: ABSTRACT SERVICE DEFINITION
TECHNICAL CORRIGENDUM 1
1) New subclause 5.8
Add a new subclause as follows:
5.8 ASN.1 Packed Encoding Rules
Although the abstract syntax in this Service Definition contains extension markers, it has not been verified that these are
present in all instances that would be required before Packed Encoding Rules could safely be used.
2) New subclause 5.9
Add a new subclause as follows:
5.9 Interpretation of UTC Time values
Dates and times in the MHS protocols are represented using the ASN.1 UTCTime type which uses only two decimal digits to
represent the year, leaving the century unspecified. Since MHS systems must deal with dates both in the past (e.g. submission
times of old messages which may be held in local storage or forwarded) and in the future (expiry time, deferred delivery time),
it is important to observe a standard convention to avoid inaccurate display or malfunction of the MHS when dates from
different centuries are compared.
The two decimal digits give 100 different years that can be expressed; an implementation has to associate each of these values
with a particular century. The chosen convention is that dates up to ten years prior to the current time and up to forty years
ahead of the current time should be associated with the corresponding century, with the interpretation of the remaining 49
values being implementation dependent. For example, for a system operating in 1996, the values "86" to "99" are interpreted
as 1986 to 1999 and the values "00" to "36" are interpreted as 2000 to 2036, and the values "37" to "85" are implementation
dependent.
NOTE – This convention permits two possible implementation strategies. An implementation can choose a fixed interpretation of all the
year values, such that the convention is satisfied throughout the expected life of the product, or it can interpret the dates dynamically,
based on the current date, such that the implementation remains valid indefinitely. For example, an implementation could choose the
fixed range 1970 to 2069 for the available values, meaning that the implementation would require revision if it is still in use by the year
2029.
3) Subclauses 11.2.25, 11.2.33, 11.2.44, 11.2.47, 11.2.50, 11.2.61, 11.2.63, 11.2.65 and 11.2.74 –
Annex C
In the subclauses enumerated below, amend the OTHER MATCHING-RULES field of the ASN.1 ATTRIBUTE definition by
replacing } with , .} in order to indicate that the object set is extensible. For example:
OTHER MATCHING-RULES {someMatch}, is changed to
OTHER MATCHING-RULES {someMatch, .},
ITU-T Rec. X.413 (1995)/Cor.1 (1997 E) 1

---------------------- Page: 2 ----------------------
ISO/IEC 10021-5 : 1996/Cor.1 : 1998 (E)
The following ATTRIBUTE productions are affected:
Subclause Attribute
11.2.25 DL-expansion-history
11.2.33 Message-group-name
11.2.44 Originally-intended-recipient-name
11.2.47 Originator-name
11.2.50 Other-recipient-names
11.2.61 Recipient-names
11.2.63 Redirection-history
11.2.65 Reporting-DL-name
11.2.74 This-recipient-name
Apply the same modifications to the corresponding productions in Annex C.
4) Subclause 7.1.2
1 Modification of the retrieval-status attribute
Append the following to item h):
This Specification defines one additional capability of the MS. If, and only if, the MS-configuration-request parameter of the
MS-bind-argument is true, and the MS supports the use of the Modify abstract-operation to change the value of the retrieval-
status attribute, then the following MS-EXTENSION shall be present:
modify-retrieval-status MS-EXTENSION ::= {
ModifyRetrievalStatus IDENTIFIED BY id-ext-modify-retrieval-status }
ModifyRetrievalStatus ::= INTEGER {
no-restriction (0),
listed-to-processed (1) }
If the value no-restriction is present, then the MS supports any modification of the retrieval-status attribute. If the value listed-
to-processed is present, then retrieval-status may be modified provided that its existing value is listed and the replacement
value is processed.
5) Annex B
Insert the productions shown above in Annex B following the production for MSBindResult. Add id-ext-modify-retrieval-
status, after id-crt-ms-access-94, in the IMPORTS FROM MSObjectIdentifiers.
6) Subclause 11.2.68
In 11.2.68 (Retrieval-status) of Recommendation X.413, replace the second and third sentence with the following:
The modify abstract-operation and auto-modify auto-action, if available, may be capable of amending the attribute.
7) Subclause 11.6
Replace the f
...