ISO/IEC ISP 12062-2:2003

Information technology — International Standardized Profiles AMH2n — Message Handling Systems — Interpersonal Messaging — Part 2: AMH21 — IPM Content

ISO/IEC ISP 12062:2003(E) covers the interchange of messages between Interpersonal Messaging (IPM) User Agents (UAs). These specifications form part of the Interpersonal Messaging application functions, as defined in ISO/IEC ISP 12062 (all parts), and are based on the Common Messaging content type-independent specifications in ISO/IEC ISP 10611 (all parts).

Technologies de l'information — Profils normalisés internationaux AMH2n — Systèmes de messagerie — Messagerie entre personnes — Partie 2: AMH21 — Contenu de IPM

General Information

• Status: Withdrawn
• Publication Date: 02-Jul-2003
• Withdrawal Date: 02-Jul-2003
• ICS: 35.100.05 - Multilayer applications
• 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: 04-Jul-2016

Relations

• Revises: ISO/IEC ISP 12062-2:1997 - Information technology — International Standardized Profiles AMH2n — Message Handling Systems — Interpersonal Messaging — Part 2: AMH21 — IPM Content
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARDIZED ISP
PROFILE 12062-2
Third edition
2003-06-15

Information technology — International
Standardized Profiles AMH2n — Message
Handling Systems — Interpersonal
Messaging —
Part 2:
AMH21 — IPM Content
Technologies de l'information — Profils normalisés internationaux
AMH2n — Systèmes de messagerie — Messagerie entre personnes —
Partie 2: AMH21 — Contenu de IPM




Reference number
ISO/IEC ISP 12062-2:2003(E)
©
ISO/IEC 2003

---------------------- Page: 1 ----------------------
ISO/IEC ISP 12062-2:2003(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO/IEC 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2003 — All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC ISP 12062-2:2003(E)

Contents
Page
Foreword . iv
Introduction. v
1 Scope.1
2 Normative references.2
3 Terms and definitions .2
4 Abbreviations.4
5 Conformance.4
Annexes
A ISPICS Proforma for ISO/IEC ISP 12062-2 (AMH21).6
B Amendments and corrigenda.34
C Bibliography.35


© ISO/IEC 2003 — All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC ISP 12062-2:2003(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
In addition to developing International Standards, ISO/IEC JTC 1 also develops International Standardized
Profiles. An International Standardized Profile is an internationally agreed, harmonized document which
identifies a standard or group of standards, together with options and parameters, necessary to accomplish a
function or a set of functions. Draft International Standardized Profiles adopted by the joint technical
committee are circulated to national bodies for voting. Publication as an International Standardized Profile
requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC ISP 12062-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange betwen systems.
This third edition cancels and replaces the second edition (ISO/IEC ISP 12062-2:1997), which has been
technically revised.
ISO/IEC ISP 12062 consists of the following parts, under the general title Information technology —
International Standardized Profile AMH2n — Message Handling Systems — Interpersonal Messaging:
 Part 1: IPM MHS Service Support
 Part 2: AMH21 — IPM Content
 Part 3: AMH22 — IPM Requirements for Message Transfer (P1)
 Part 4: AMH23 and AMH25 — IPM Requirements for MTS Access (P3) and MTS 94 Access (P3)
 Part 5: AMH24 — IPM Requirements for Enhanced MS Access (P7)
 Part 6: AMH26 — IPM Requirements for Enhanced MS 94 Access (P7)
iv © ISO/IEC 2003 — All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC ISP 12062-2:2003(E)

Introduction
This part of ISO/IEC ISP 12062 is defined within the context of Functional
Standardization, in accordance with the principles specified by ISO/IEC
TR 10000, “Framework and Taxonomy of International Standardized
Profiles”. The context of Functional Standardization is one part of the
overall field of Information Technology (IT) standardization activities,
covering base standards, profiles, and registration mechanisms. A profile
defines a combination of base standards that collectively perform a
specific well-defined IT function. Profiles standardize the use of options
and other variations in the base standards, and provide a basis for the
development of uniform, internationally recognized system tests.
One of the rôles for an ISP is to serve as the basis for the development
(by organizations other than ISO and IEC) of internationally recognized
tests. ISPs are produced not simply to ‘legitimize’ a particular choice of
base standards and options, but to promote real system interoperability.
The development and widespread acceptance of tests based on this and
other ISPs is crucial to the successful realization of this goal.
The text for this part of ISO/IEC ISP 12062 was originally developed in
close cooperation between the MHS Expert Groups of the three Regional
Workshops: the North American OSE Implementors’ Workshop (OIW),
the European Workshop for Open Systems (EWOS) (jointly with the
corresponding expert group of the European Telecommunications
Standards Institute - ETSI) and the OSI Asia-Oceania Workshop (AOW).
The first and second editions of this part of ISO/IEC ISP 12062 were
harmonized between these three Workshops and ratified by the plenary
assemblies of all three Workshops.
Responsibility for maintenance and further development of MHS ISPs has
been transferred to ISO/IEC JTC1/SC33/WG1, who have produced this
edition to encompass additions and corrections to ISO/IEC 10021.
Because new core requirements have been added for support of
Universal Characters in addresses which will take time to be implemented
within MHS systems, it is expected that the second edition of this part of
ISO/IEC ISP 12062 will remain available for an overlap period.
© ISO/IEC 2003 — All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARDIZED PROFILE ISO/IEC ISP 12062-2:2003(E)

Information technology — International Standardized
Profiles AMH2n — Message Handling Systems —
Interpersonal Messaging —
Part 2:
AMH21 — IPM Content
1 Scope

1.1 General
This part of ISO/IEC ISP 12062 covers the interchange of messages between Interpersonal Messaging (IPM)
User Agents (UAs) (see also figure 1). These specifications form part of the Interpersonal Messaging application
functions, as defined in the parts of ISO/IEC ISP 12062, and are based on the Common Messaging content
type-independent specifications in ISO/IEC ISP 10611.
1.2 Position within the taxonomy
This part of ISO/IEC ISP 12062 is the second part of a multipart ISP identified in ISO/IEC TR 10000-2 as
“AMH2, Message Handling Systems - Interpersonal Messaging” (see also ISO/IEC TR 10000-1, 8.2 for the
definition of multipart ISPs).
This part of ISO/IEC ISP 12062 specifies the following profile:
AMH21 - IPM Content
The AMH21 profile may optionally be combined with profiles AMH23, AMH24, AMH25 or AMH26 (see annex D
of ISO/IEC ISP 12062-1) specifying OSI MHS communications protocols and supporting services for an IPM UA.
1.3 Scenario
The model used is one of indirect interchange of interpersonal messages (content types 22 and 2) between IPM
UAs via an intermediate Message Transfer System (MTS), as shown in figure 1. The provision of, and access to,
the MTS is outside the scope of this profile.

Figure 1 - AMH21 scenario
The MHS services and functions covered by the AMH21 profile are specified in ISO/IEC 10021-7. There are no
OSI upper layer services and protocols within the scope of the AMH21 profile.
© ISO/IEC 2003 — All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/IEC ISP 12062-2:2003(E)
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
Amendments and corrigenda to the base standards referenced are listed in annex B.

NOTES

1 - References in the body of this part of ISO/IEC ISP 12062 to specific clauses of ISO/IEC documents shall be considered

to refer also to the corresponding clauses of the equivalent ITU-T Recommendations (as noted below) unless otherwise
stated.

2 - Informative references are found in annex C.

C CITT Recommendation T.415 (1993), | ISO/IEC 8613-5:1994, Information technology - Open Document Architecture
(ODA) and Interchange Format - Open Document Interchange Format

ISO/IEC 8859 (all parts), Information technology - 8-bit single-byte coded graphic character sets

ISO/IEC TR 10000-1:1998, Information technology - Framework and taxonomy of International Standardized Profiles -

Part 1: General principles and documentation framework

ISO/IEC TR 10000-2:1998, Information technology - Framework and taxonomy of International Standardized Profiles -
Part 2: Principles and Taxonomy for OSI Profiles

ITU-T Recommendation F.400/X.400 (1999), Message Handling Systems - System and service overview

ISO/IEC 10021-1:2003, Information technology - Message Handling Systems (MHS) - Part 1: System and service overview

[see also ITU-T Recommendation F.400/X.400]

1)
ITU-T Recommendation X.402 (1999) | ISO/IEC 10021-2:— , Information technology - Message Handling Systems
(MHS): Overall architecture

2)
ITU-T Recommendation X.420 (1999) | ISO/IEC 10021-7:— , Information technology - Message Handling Systems

(MHS): Interpersonal messaging system
ISO/IEC ISP 12062-1:2003, Information technology - International Standardized Profiles AMH2n - Message Handling
Systems - Interpersonal Messaging - Part 1: IPM MHS Service Support
ISO 10646-1:2000, Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and
Basic Multilingual Plane
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.


Terms used in this part of ISO/IEC ISP 12062 are defined in the referenced base standards; in addition, the
following terms are defined.


1) To be published. (Revision of ISO/IEC 10021-2:1996)
2) To be published. (Revision of ISP/IEC 10021-7:1997)
2 © ISO/IEC 2003 — All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC ISP 12062-2:2003(E)
3.1 General
Basic requirement : an Element of Service, protocol element, procedural element or other identifiable feature
specified in the base standards which is required to be supported by all MHS implementations.
Functional group : a specification of one or more related Elements of Service, protocol elements, procedural
elements or other identifiable features specified in the base standards which together support a significant
optional area of MHS functionality.
NOTE - A functional group can cover any combination of MHS features specified in the base standards for which the effect
of implementation can be determined at a standardized external interface - i.e. via a standard OSI communications protocol
(other forms of exposed interface, such as a standardized programmatic interface, are outside the scope of this version of
ISO/IEC ISP 12062).
3.2 Support classification
To specify the support level of information objects and items for this part of ISO/IEC ISP 12062, the following
terminology is defined.
The following classifications are used in this part of ISO/IEC ISP 12062 to specify static conformance
requirements - i.e. capability.
The classification of information objects and items (elements) is relative to that of the containing information
element, if any. Where the constituent elements of a non-primitive element are not individually specified, then
each shall be considered to have the classification of that element. Where the range of values to be supported
for an element is not specified, then all values defined in the MHS base standards shall be supported.
mandatory support (m) : the element shall be supported. An implementation shall be able to generate the
element, and/or receive the element and perform all associated procedures (i.e. implying the ability to handle
both the syntax and the semantics of the element) as relevant, as specified in the MHS base standards. Where
support for origination (generation) and reception are not distinguished, then both capabilities shall be assumed.
NOTES
1 - In the case of character repertoires, mandatory support implies that the IPM UA implementation is able to generate
and/or receive the encodings of all characters within those repertoires. How graphic characters are originated and rendered
is outside the scope of this ISP.
2 - Where required by the base standards, mandatory support also implies that the IPM UA implementation is able to pass
the element on the origination port/reception port to/from the corresponding element on the submission port/delivery
port/retrieval port.
optional support (o) : an implementation is not required to support the element. If support is claimed, then the
element shall be treated as if it were specified as mandatory support. If the element is not supported on
reception, then it shall be ignored.
conditional support (c) : the element shall be supported under the conditions specified in this part of ISO/IEC
ISP 12062. If these conditions are met, the element shall be treated as if it were specified as mandatory support.
If these conditions are not met, the element shall be treated as if it were specified as optional support (unless
otherwise stated).
out of scope (i) : the element is outside the scope of this part of ISO/IEC ISP 12062 - i.e. it will not be the
subject of an ISP conformance test.
not applicable (–) : the element is not applicable in the particular context in which this classification is used.
© ISO/IEC 2003 — All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/IEC ISP 12062-2:2003(E)
4 Abbreviations
84IW 84 Interworking
AMH Application Message Handling
ASN.1 Abstract Syntax Notation One
BC Business Class
CV Conversion
DIR Use of Directory
DL Distribution List
EoS Element of Service
FG Functional group
FWD Manual Forwarding
IPM Interpersonal Messaging / Interpersonal Message
IPN Interpersonal Notification
ISP International Standardized Profile
LD Latest Delivery
MHS Message Handling Systems
MS Message store
MT Message transfer
MTA Message transfer agent
MTS Message Transfer System
OSI Open Systems Interconnection
PD Physical Delivery
RED Redirection
RoC Return of Content
SEC Security
UA User agent

Support level for information objects (see 3.2):
m mandatory support
o optional support
c conditional support
i out of scope
– not applicable
5 Conformance
The scope of conformance to profile AMH21 covers the functionality of, and interoperability between, IPM UAs.
Conformance to profile AMH21 does not imply the provision of a standard OSI communications protocol for
access to the MTS. Conformance to profile AMH21 does not imply the provision of an exposed IPM service
interface (whether a human user interface or a standardized programmatic interface).
This part of ISO/IEC ISP 12062 states requirements upon implementations to achieve interworking. A claim of
conformance to this part of ISO/IEC ISP 12062 is a claim that all requirements in the relevant base standards
are satisfied, and that all requirements in the following clauses and in annex A of this part of ISO/IEC ISP 12062
are satisfied. Annex A states the relationship between these requirements and those of the base standards.
5.1 Conformance statement
For each implementation claiming conformance to profile AMH21 as specified in this part of ISO/IEC ISP 12062,
a PICS shall be made available stating support or non-support of each option identified in this part of ISO/IEC
ISP 12062.
4 © ISO/IEC 2003 — All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC ISP 12062-2:2003(E)
5.2 MHS conformance
This part of ISO/IEC ISP 12062 specifies implementation options or selections such that conformant
implementations will satisfy the conformance requirements of ISO/IEC 10021 and the ITU-T X.400
Recommendations.
Implementations conforming to profile AMH21 as specified in this part of ISO/IEC ISP 12062 shall implement all
the mandatory support (m) features identified as basic requirements in annex A except those features that are
components of an unimplemented optional feature. It shall be stated which optional support (o) features are
implemented.
For implementations conforming to profile AMH21 as specified in this part of ISO/IEC ISP 12062, it shall be
stated whether or not they support any of the optional functional groups as specified in ISO/IEC ISP 12062-1
which are applicable to the scope of this profile. For each functional group for which support is claimed, an
implementation shall implement all the mandatory support (m) features identified for that functional group in
annex A except those features that are components of an unimplemented optional feature. It shall be stated
which optional support (o) features are implemented.
Implementations shall support the procedures associated with supported protocol elements as specified in the
base standards and as further specified in ISO/IEC ISP 12062-1. The MHS Elements of Service corresponding
to such procedures are indicated in annex A of ISO/IEC ISP 12062-1.
© ISO/IEC 2003 — All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/IEC ISP 12062-2:2003(E)
2
Annex A
(normative)
ISPICS Proforma
for ISO/IEC ISP 12062-2 (AMH21)

In the event of a discrepancy becoming apparent in the body of this part of ISO/IEC ISP 12062 and the tables in
this annex, this annex is to take precedence.
Clause A.1 specifies the basic requirements for conformance to profile AMH21. Clause A.2 specifies additional
requirements to those specified in A.1 for each of the optional functional groups if conformance to such a
functional group is claimed. Clause A.3 allows additional information to be provided for certain aspects of an
implementation where no specific requirements are included in ISO/IEC ISP 12062. All three clauses shall be
completed as appropriate.
In each table, the "Base" column reflects the level of support required for conformance to the base standard and
the "Profile" column specifies the level of support required by this ISP (using the classification and notation
defined in 3.2).
The “Ref” column is provided for cross-referencing purposes. The notation employed for references also
indicates composite elements which contain sub-elements (a sub-element reference is prefixed by the reference
of the composite element).
The Support column is provided for completion by the supplier of the implementation as follows:
Y the element or feature is fully supported
N the element or feature is not supported
– or blank the element or feature is not applicable (i.e. a major feature or composite protocol element
which includes this element or feature is not supported)
Where support for origination and support for reception cannot be covered by a single indication, then both
support levels shall be indicated, separated by a solidus (e.g. 'N/Y').

2
Copyright release for ISPICS proformas
Users of this International Standardized Profile may freely reproduce the ISPICS proforma in this annex so that it can be
used for its intended purpose and may further publish the completed ISPICS.
6 © ISO/IEC 2003 — All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC ISP 12062-2:2003(E)
A.0 Identification of the implementation
A.0.1 Identification of PICS
Ref Question Response
1 Date of statement (YYYY-MM-DD)
2 PICS serial number
3 System conformance statement cross
reference

A.0.2 Identification of IUT
Ref Question Response
1 Implementation name
2 Implementation version
3 Hardware name
4 Hardware version
5 Operating system name
6 Operating system version
7 Special configuration
8 Other information


A.0.3 Identification of supplier
Ref Question Response
1 Organization name
2 Contact name(s)
3 Address

4 Telephone number
5 Telex number
6 Fax number
7 E-mail address
8 Other information
© ISO/IEC 2003 — All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/IEC ISP 12062-2:2003(E)
A.0.4 Identification of protocol
Ref Question Response
1 Title, reference number and date of
publication of the protocol standard
2 Protocol version(s) not applicable
3 Addenda/amendments/corrigenda
implemented
4 Defect reports implemented not applicable

A.0.5 Global statement of conformance
Ref Question Response Comments
1 Are all mandatory base standards
requirements implemented?

A.0.6 Statement of profile conformance
Ref Question Response Comments
1 Are all mandatory requirements of profile
AMH21 implemented?
2 Are all mandatory requirements of any of the
following optional functional groups
implemented?


2.1 IPM Manual Forwarding (FWD)



2.2 IPM Security (SEC) class(es):
2.3 IPM Use of Directory (DIR)
2.4 IPM 84 Interworking (84IW)
2.5 IPM Business Class (BC)
2.6 IPM Auto-Advise (AADV)
8 © ISO/IEC 2003 — All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC ISP 12062-2:2003(E)
A.1 Basic requirements
A.1.1 Supported information objects
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile
1 Interpersonal Message (IPM) m m m m
1.1 heading m m m m see A.1.2
1.2 body m m m m see A.1.3
2 Interpersonal Notification (IPN) m m o m see A.1.4

A.1.2 IPM heading fields
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile
1 this-IPM m m m m see A.1.5/3
2 originator m m m m see A.1.5/2
3 authorizing-users o o m m see A.1.5/2
4 primary-recipients m m m m see A.1.5/1
5 copy-recipients m m m m see A.1.5/1
6 blind-copy-recipients o o m m see A.1.5/1
7 replied-to-IPM m m m m see A.1.5/3
8 obsoleted-IPMs o o m m see A.1.5/3
9 related-IPMs o o m m see A.1.5/3
10 subject m m m m
11 expiry-time o o m m
12 reply-time o o m m
13 reply-recipients o o m m see A.1.5/2
14 importance o o m m
15 sensitivity o o m m
16 auto-forwarded o o m m
17 extensions m m m m
© ISO/IEC 2003 — All rights reserved 9

---------------------- Page: 14 ----------------------
ISO/IEC ISP 12062-2:2003(E)
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile
17.1 incomplete-copy o o o m
17.2 languages o o m m
17.3 auto-submitted o o o m
17.4 body-part-signatures o o o o see A.1.2.1/1
17.5 ipm-security-label o o o o see A.1.2.1/2
17.6 authorization-time o o o o
17.7 circulation-list-recipients o o m m see A.1.2.1/3
17.8 distribution-codes o o o o see A.1.2.1/4
17.9 extended-subject m m m m
17.10 information-category o o o o see A.1.2.1/5
17.11 manual-handling-instructions o o o o
17.12 originators-reference o o o o
17.13 precedence-policy-identifier o o o o

A.1.2.1 IPM heading subfields
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile

1 BodyPartSignatures
1.1 body-part-number m m m m
1.2 body-part-signature m m m m
1.2.1 signature-algorithm-identifier m m m m
1.2.2 body-part m m m m see A.1.3
1 1 1 1
1.2.3 body-part-security-label m m m m see footnote 2
1.3 originator-certificate-selector o o o m see footnote 3
1.4 originator-certificates o o o m see footnote 4

10 © ISO/IEC 2003 — All rights reserved

---------------------- Page: 15 ----------------------
ISO/IEC ISP 12062-2:2003(E)
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile
2 IPMSecurityLabel
2.1 content-security-label m m m m see footnote 2
2.2 heading-security-label o m o m see footnote 2
2.3 body-part-security-labels m m m m see footnote 2

3 CirculationMember
3.1 member-name m m m m see A.1.5/1
3.2 checked m m m m
3.2.1 simple o m o m
3.2.2 timestamped o m o m
3.2.3 signed o o o o
3.2.3.1 algorithm-identifier m m m m
3.2.3.2 this-IPM m m m m see A.1.5/3
3.2.3.3 timestamp m m m m

4 DistributionCode
4.1 oid-code o o o o
4.2 alphanumeric-code o o o m
4.3 or-descriptor o o o m see A.1.5/2

5 InformationCategory
5.1 reference o o o o
5.2 description o o o m
1 shall be present if the corresponding body-part-security-labels component is present IPMSecurityLabel.
2 see A.1.6/3 in ISO/IEC ISP 10611-3
3 see A.1.5/11 in ISO/IEC ISP 10611-3
4 see A.1.6/11 in ISO/IEC ISP 10611-3
© ISO/IEC 2003 — All rights reserved 11

---------------------- Page: 16 ----------------------
ISO/IEC ISP 12062-2:2003(E)

A.1.3 IPM body
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile

1 ia5-text o o o m
1.1 parameters m m m m
1.1.1 repertoire o o m m
1.2 data m m m m
2 voice i i i i
3 g3-facsimile o o o o
3.1 parameters m m m m
3.1.1 number-of-pages o o o m
3.1.2 non-basic-parameters o o o m
3.1.2.1 two-dimensional o o o m
3.1.2.2 fine-resolution o o o m
3.1.2.3 unlimited-length o o o o
3.1.2.4 b4-length o o o o
3.1.2.5 a3-width o o o o
3.1.2.6 b4-width o o o o
3.1.2.7 uncompressed o o o o
3.2 data m m m m
4 g4-class-1 o o o o
5 teletex o o o o see footnote 1
5.1 parameters m m m m
5.1.1 number-of-pages o o o m
5.1.2 telex-compatible o o m m
5.1.3 non-basic-parameters o o o m
5.2 data m m m m
6 videotex o o o o
12 © ISO/IEC 2003 — All rights reserved

---------------------- Page: 17 ----------------------
ISO/IEC ISP 12062-2:2003(E)
Ref Element Origination Reception Support Notes/References
 Base Profile Base Profile
6.1 parameters m m m m
6.1.1 syntax o o o m
6.2 data m m m m
7 encrypted o o o o
7.1 parameters m m m m
7.2 data m m m m
8 message o o o m
8.1 parameters m m m m
8.1.1 delivery-time o o o m
8.1.2 delivery-envelope o o o m
8.2 data m m m m
9 mixed-mode o o o o
10 bilaterally-defined o o o o
11 nationally-defined o o o o
12 extended m m m m see A.1.3.1
1 The teletex body part type should be used purely for teletex documents, obeying page rules, etc. It should not be
used to transfer unstructured T.61 character data

A.1.3.1 Extended body part support
It shall be indicated below which standard extended body part types are supported. It shall be stated in A.3.4
whether any other specific extended body part types are supported.
Ref Extended Body Part Type Origination Reception Support Notes/References
 Base Profile Base Profile
1 ia5-text-body-part o o o m see A.1.3/1
2 g3-facsimile-body-part o o o o see A.1.3/3
3 g4-class1-body-part o o o o see A.1.3/4
4 teletex-body-part o o o o see A.1.3/5
5 videotex-body-part o o o o see A.1.3/6
© ISO/IEC 2003 — All rights reserved 13

---------------------- Page: 18 ----------------------
ISO/IEC ISP 12062-2:2003(E)
Ref Extended Body Part Type Origination Reception Support Notes/References
 Base Profile Base Profile
6 encrypted-body-part o o o o
7 message-body-part o o o m see A.1.3/8
8 mixed-mode-body-part o o o o
9 bilaterally-defined-body-part o o o o
10 nation
...