EN ISP 12063-1:1996
(Main)Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1: EDIMG MHS Service Support (ISO/IEC ISP 12063-1:1995)
Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1: EDIMG MHS Service Support (ISO/IEC ISP 12063-1:1995)
Technologies de l'information - Profils normalisés internationaux AMH3n - Systèmes de messagerie - Messagerie EDI - Partie 1: Support de service EDIMG MHS (ISO/IEC ISP 12063-1:1995)
Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1: EDIMG MHS Service Support (ISO/IEC ISP 12063-1:1995)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1: EDIMG MHS Service Support (ISO/IEC ISP 12063-1:1995)Technologies de l'information - Profils normalisés internationaux AMH3n - Systemes de messagerie - Messagerie EDI - Partie 1: Support de service EDIMG MHS (ISO/IEC ISP 12063-1:1995)Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1: EDIMG MHS Service Support (ISO/IEC ISP 12063-1:1995)35.100.05UHãLWYHMultilayer applicationsICS:Ta slovenski standard je istoveten z:EN ISP 12063-1:1996SIST EN ISP 12063-1:1997en01-december-1997SIST EN ISP 12063-1:1997SLOVENSKI
STANDARD
SIST EN ISP 12063-1:1997
SIST EN ISP 12063-1:1997
SIST EN ISP 12063-1:1997
I I I NTE R NAT I O NA L S TAN DAR DI Z E D PROFILE ISO/IEC 12063- I First edition 1995-07-1 5 Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1: EDIMG MHS Service Support Technologies de l'information - Profils normalisés internationaux AMH3n - Systèmes de messagerie - Messagerie ED1 - Partie I: Support de service EDIMG MHS Reference number ISO/IEC ISP 12063-1 :I 995(E) SIST EN ISP 12063-1:1997
ISO/IEC ISP 12063-1 : 1995 (E) Con tents page . Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . , . , . . . . . , . . . . . . . . , . . . . . . . . . . . . . . . .III Introduction . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . iv 1 Scope . 1 2 Normative references . 1 3 Definitions . 2 4 Abbreviations . 4 5 Conformance . . . . 5 6 Basic requirements . 5 7 Functional groups . 6 8 Naming and addressing . 12 9 Error and exception handling . 12 Annexes A Elements of Service . 13 B Amendments and corrigenda . 20 C Additional recommended practices for 1984 interworking . 21 D AMH3 - overall scope and applicability . . . . 25 E Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 I- Q ISO/IEC 1995 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 the publisher. ISO/IEC Copyright Office Case Postale 56 CH-121 1 Genève 20 Switzerland Printed in Switzerland ii SIST EN ISP 12063-1:1997
ISO/IEC ISOllEC ISP 12063-1 : 1995 (E) Foreword IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of IS0 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. IS0 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint technical committee, ISO/IEC JTCl. In addition to developing International Standards, ISO/IEC JTC1 has created a Special Group on Functional Standardization for the elaboration of 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 set of functions. International Standardized Profile ISO/IEC ISP 12063-1 was prepared with the collaboration of: - OS1 Asia-Oceania Workshop (AOW) - European Workshop for Open Systems (EWOS), jointly with the European Telecommunications Standards Institute (ETSI) - OSE Implementors’ Workshop (OIW) ISO/IEC ISP 12063 consists of the following parts, under the general title Information technology - lnternational standardized Profiles AMH3n - Message Handling Systems - EDI Messaging: - Part I : EDlMG MHS Service Support , - Part 2 : AMH31- EDlMG Content - Part 3 : AMH32 - EDlMG Requirements fur Message Transfer (Pl) - Part 4 : AMH33 - EDlMG Requirements for MTS Access (P3) - Part 5 : AMH34 - EDlMG Requirements fur Enhanced MS Access (P7) Annexes A and B form an integral part of this part of ISOiIEC ISP 12063. Annexes C, D and E are for information only. iii SIST EN ISP 12063-1:1997
ISOAEC ISP 12063-1 : 1995 (E) Introduction This part of ISO/IEC ISP 12063 is defined within the context of Functional Standardization, in accordance with the principles specified by ISOAEC 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 most important roles for an ISP is to serve as the basis for the development (by organizations other than IS0 and IEC) of internationally recognized tests. lSPs 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 lSPs is crucial to the successful realization of this goal. The text for this part of ISOAEC ISP 12063 was 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 OS1 Asia-Oceania Workshop (AOW). This part of ISO/IEC ISP 12063 is harmonized between these three Workshops and it has been ratified by the plenary assemblies of all three Workshops. iv O ISO/IEC SIST EN ISP 12063-1:1997
__ INTERNATIONAL STANDARDIZED PROFILE QISaEC ISO/IEC ISP 12063-1 : 1995 (E) to be supported by all EDiMG implementations, and a number of optional functional groups, which cover significant discrete areas of related functionality which are not required to be supported by all implementations. Information technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 1 : EDIMG MHS Service Support 1 Scope 1.1 General This part of ISO/IEC ISP 12063 contains the overall specifications of the support of MHS Elements of Service and associated MHS functionality in an Electronic Data Interchange Messaging (EDIMG) environment which are generally not appropriate for consideration oniy from the perspective of a single MHS protocol. These specifications form part of the EDI Messaging application functions, as defined in the parts of ISOiIEC ISP 12063, and are based on the Common Messaging content type-independent specifications in ISO/IEC ISP 1061 1. Such specifications are in many cases applicable to more than one MHS protocol or are otherwise concerned with component functionality which, although it can be verified via protocol, is not just related to protocol support. They are therefore designed to be referenced in the MHS EDI Messaging application profiles ISO/IEC ISP 12063-2 (AMH31), ISOiIEC ISP 12063-3 (AMH32), ISO/IEC ISP 12063-4 (AMH33) and ISO/IEC ISP 12063-5 (AMH34), which specify the support of specific MHS protocols and associated functionality. This part of ISO/IEC ISP 12063 does not, on its own, specify any profiles, 3 Normative references following documents contain provisions which, through reference in this text, constitute provisions of this of ISO/IEC ISP 12063. At the time of publication, the editions indicated were valid. All documents are and parties to agreements based on this part of ISO/IEC ISP 12063 are warned against any more recent editions of the documents listed below, since the nature of references to such documents is that they may be specific to a particular edition. Members of IEC and IS0 aintain registers of currently valid International Standards and ISPs, and the Telecommunications Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. corrigenda to the base standards referenced are listed in annex B. l 1 SIST EN ISP 12063-1:1997
ISO/IEC ISP 12063-1 1995 (E) O ISO/IEC NOTES 1 - References in the body of this part of ISO/IEC 12063 to specific clauses of ISO/IEC documents refer also to the corresponding clauses of the equivalent ITU-T Recommendations (as noted below) unless otherwise stated. 2 - Informative reference are found in annex E. ISOAEC TR 10000-1 : 1992, Information technology - Framework and taxonomy of International Standardired Profiles - Part I: Framework. ISOAEC TR 10000-2: 1994, Information technology - Framework and taxonomy of International Standardized Profiles - Part 2: Principles and taxonomy for OS1 pro files. ISOAEC 10021 -1 : 1990, Information technology - Text Communication - Message-Oriented Text Interchange Systems (MOTIS) - Part I: System and Service Overview. [see also CClTT Recommendation F.400(1992)] ISO/IEC 10021 -2: 1990, Information technology - Text Communication - Message-Oriented Text Interchange Systems (MOTIS) - Part 2: Overall Architecture. [see also CClTT Recommendation X.402(1992)] ISOAEC 10021 -4: 1990, Information technology - Text Communication - Message-Oriented Text Interchange Systems (MOTIS) - Part 4: Message Transfer System: Abstract Service Definition and Procedures. [see also CClTT Recommendation X.4 1 1( 1$92)] ISOAEC 10021 -5: 1 990, Information technology - Text Communication - Message-Oriented Text Interchange Systems (MOTIS) - Part 5: Message Store: Abstract Service Definition. [see also CC177 Recommendation X.413(7992)] ISOAEC 10021 -8: 1995, Information technology - Text Communication - Message Handling Systems - Part 8 : Electronic Data Interchange Messaging Service. [see also CCITT Recommendation E#5( 199 l)] ISOiIEC 10021 -9: 1995, Information technology - Text Communication - Message Handling Systems - Part 9 : EIectronic Data Interchange Messaging System. [see also CClTT Recommendation X. 435( 199 I)] ISO/IEC ISP 1061 1 : 1994, lnformation technology - Internationai Standardized Profiles AMH7n - Message Handling Systems - Common Messaging CClTT Recommendation F.400( 1 992), Message handling services: Message handling system and service overview. e CClTT Recommendation F.435( 1 991 ), Message handling: ED1 messaging service. CCITT Recommendation X.402( 1992), Message handling systems: Overall architecture. CCllT Recommendation X.411(1992), Message handling systems - Message transfer system: Abstract service definition and procedures. CClTT Recornmendation X.413( 1 992), Message handling systems - Message store: Abstract service definition. CCllT Recommendation X.435(1991), Message handling systems: €DI messaging system. 3 Definitions For the purposes of this part of ISO/IEC ISP 12063, the following definitions apply. e Terms used in this part of ISO/IEC ISP 12063 are defined in the referenced base standards; in addition, the following terms are defined. 3.1 General 3.1.1 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. 3.1.2 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. 2 SIST EN ISP 12063-1:1997
O ISOAEC ISO/IEC ISP 12063-1 : 1995 (E) 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 extemal interface - i.e. via a standard OS1 communications protocol (other forms of exposed interface, such as a standardized programmatic interfaces, are outside the scope of this version of ISOAEC ISP 12063). 3.2 Support classification To specify the support level of Elements of Service for this part of ISOAEC ISP 12063, the following terminology is defined. 3.2.1 mandatory support (m) : for origination: for MT and MS Elements of Service: A service provider (i.e. an MTA or MS) shall be able to make the Element of Service available to a service user in the role of originator; a service user (i.e. a UA) shall be able to use the Element of Service in the role of originator. A service provider (i.e. an EDI-UA) shall implement all the procedures specified in the base standards which are associated with the provision of the Element of Service, including use of the corresponding MT or MS Element(s) of Service, as appropriate; where specified in the base standards, a service provider shall make the Element of Service available to the service user in the role of originator; in all cases, it shall be stated in the PICS whether the Element of Service is made available to the service user and, if so, how this is achieved. for EDI Elements of Service: for reception: for MT and MS Elements of Service: A service provider (i.e. a MTA or MS) shall be able to make the Element of Service available to a service user in the role of recipient; a service user (i.e. a UA) shall be able to use the Element of Service in the role of recipient. for EDI Elements of Service: A service provider (i.e. an EDI-UA) shall implement all the procedures specified in the base standards which are associated with the provision of the Element of Service, including use of the corresponding MT or MS Element(s) of Service, as appropriate; where specified in the base standards, a service provider shall make the Element of Service available to the service user in the role of recipient; in all cases, it shall be stated in the PICS whether the Element of Service is made available to the service user and, if so, how this is achieved. 2.2 optional support (O) : An implementation is not required to support the Element of Service. If support claimed, then the Element of Service shall be treated as if it were specified as mandatory support. 2.3 conditional support (c) : The Element of Service shall be supported under the conditions specified in is part of ISO/IEC ISP 12063. If these conditions are met, the Element of Service shall be treated as if it we specified as mandatory support. If these conditions are not met, the Element of Service shall be treated i if it were specified as optional support (unless otherwise stated). 2.4 out of scope (i) : The Element of Service is outside the scope of this part of ISOAEC ISP 12063 - i.e. it II not be the subject of an ISP conformance test. However, the handling of associated protocol elements may ? specified separately in the subsequent parts of ISO/IEC ISP 12063. 2.5 not applicable (-) : The Element of Service is not applicable in the particular context in which this assification is used. I 3 SIST EN ISP 12063-1:1997
ISOllEC ISP 12063-1 : 1995 (E) 3.3 Profile object identifiers O ISOAEC Profile AMH31 AMH32 AMH33 AMH34 Profiles that are specified in ISO/IEC ISP 12063 are identified by the object identifiers in table 1 Object Identifier { is0 standard edi-messaging(l2063) edimg-content (2) } { is0 standard edi-messaging( 12063) edimg-message-transfer(3) } { iso standard edi-messaging( 12063) edimg-mts-access(4) } { is0 standard edi-messaging( 12063) edimg-ms-access(5) } NOTE - These object identifiers are included for formal purposes and any use of them is not defined. They are not related to any implementation of messaging and do not appear in the protocols specified in ISOiIEC ISP 12063. Table 1 - Profile object identifiers I 4 Abbreviations 841W AF ASN.l CV DIR DL EDI EDI-MS EDI-UA EDIFACT EDlM EDIMG EDlN EH EIT EoS FG FN IPM ISP ISPICS LD MF MHS M PB MS MT MTA MTS NN os1 PD PDAU Pedi PN PS RED SEC UA x12 84 Interworking Automatic Forwarding Abstract Syntax Notation One Conversion Use of Directory Distribution List Electronic data interchange EDI message store EDI user agent EDI For Administration, Commerce and Transport EDI Message €DI Messaging EDI Notification EDIFACT Heading fields Encoded information type Element of Service Functional group Forwarded notification Interpersonal message or interpersonal messaging International Standardized Profile International Standard Protocol Implementation Conformance Statement Latest Delivery Manual Forwarding Message Handling Systems Multi part body Message store Message transfer Message transfer agent Message Transfer System Negative notification Open Systems Interconnection Physical Delivery Physical delivery access unit Protocol for electronic data interchange Positive notification Private syntax Redirection Security User agent ANSI X12 4 SIST EN ISP 12063-1:1997
O ISO/IEC Support level for Elements of Service (see 3.2): m mandatory support O optional support C conditional support i out of scope - not applicable 5 Conformance ISOllEC ISP 12063-1 : 1995 (E) No conformance requirements are specified in this part of ISO/IEC ISP 12063. NOTE - This part of ISOiIEC ISP 12063 is a reference specification of the basic requirements and functional groups covered by the AMH3n set of profiles and is additional to the protocol-specific requirements specified in the following parts of ISOAEC ISP 12063. Although this part of ISOiIEC ISP 12063 contains normative requirements, there is no separate conformance to this part (i.e. it is not identified in the MHS taxonomy in ISO/IEC TR 10000-2) since such requirements are only significant when referenced in the context of a particular protocol. Conformance requirements are specified by protocol for each MHS functional object in the following parts of ISO/IEC ISP 12063 with reference to the specifications in this part. Support of functionality as specified in this part may only be verifiable where the effect of implementation can be determined at a standardized external interface - i.e. via a standard OS1 communications protocol. Further, the provision of Elements of Service and other functionality at a service interface will not necessarily be verifiable unless such interface is realized in the form of a standard OS1 communications protocol. Other forms of exposed interface (such as a human user interface or a standardized programmable interface may be provided, but are not required for conformance to this version of ISO/IEC ISP 12063. 6 Basic requirements Annex A specifies the basic requirements for support of MHS Elements of Service (EoS) for conformance to ISO/IEC ISP 12063. Basic requirements specify the level of support required by all EDIMG implementations, as relevant to each type of MHS functional object - i.e. MTA, MS or UA (as MTS-user or MS-user, as relevant). An implementation conforming to the basic requirements of ISO/IEC ISP 12063 shall conform to the basic requirements of ISO/IEC ISP 1061 1, as appropriate to the type of MHS functional object. 'I, .1 Generation of notifications EDI-UA implementation shall be able to accept or refuse ED1 responsibility for a received EDIM. It shall be ble to generate appropriate positive and negative ED1 notifications to respond to ED1 notification requests, ither locally or by request from the EDlMG user as defined in the MHS base standards. The error codes are enerated either by the EDlMG user or by the EDI-UA. 1) shall be stated in the PICS which EDlN reason code values an EDI-UA implementation is able to generate. 4.2 Reception of notifications An EDI-UA shall be able to receive any type of ED1 notification. 4.3 Number of recipients il an EDI-UA implementation comprises any limit on the number of recipients that can be specified in an EDIM hpading, then such limit shall be stated in the PICS. I 5 SIST EN ISP 12063-1:1997
ISO/IEC ISP 12063-1 1995 (E) O ISOIIEC 6.4 Message length If an EDI-UA implementation imposes any constraint on the size of the message content, then such constraint shall be stated in the PICS. 6.5 Identification of the recipient The originating EDI-UA shall use the same OF? name in the RecipientField as in the Submission envelope. On reception of an EDIM, the EDI-UA shall identify its own recipient sub-fields in the €DIM heading fields based on OIR name in the RecipientField in the RecipientsSubField of the EDIM. The value shall be the O/R name from the first element in the redirection-history argument (if present) or else the this-recipient-name argument of the Message Delivery operation. NOTES 1 - Where the EDlM passes through intermediate MTAs implementing X.400 (84) after a redirection, a bilateral agreement will be needed since the redirection-histoiy is lost. 2 - Where the EDIM has been delivered as a result of DL expansion, the EDI-UA can not identify its own recipient sub- @ fields. 3 - The requirements in this clause are also submitted to ITU-T and ISOAEC as a perceived defect in the base standard. 6.6 Body part types and encoded information types It shall be stated in the PICS which body part types and encoded information type values an implementation supports in the roles of originator and receiver. An MTA or an MS implementation shall be able to accept any syntax. The use of PRIVATE and UNDEFINED €DI body part types is deprecated in favour of privately defining an object identifier for the specific syntax used (see 7.12). 7 Functional groups Annex A specifies any additional requirements for support of MHS EoS if support of an optional functional group (FG) is claimed, as appropriate to each type of MHS functional object. The following clauses summarize the functionality supported by each of the optional FGs and identify any particular such requirements or 0 implementation considerations which are outside the scope of formal conformance to ISOIIEC ISP 12063. A summary of the functional groups, identifying which may be supported (Y) and which are not applicable (N) for each type of MHS functional object (i.e. MTA, MS or UA - whether as MTS-user or as MS-user is not distinguished), is given in table 2. The conformance requirements for support of the various functional groups, covering support of additional protocol elements and/or procedures, are specified in parts 2, 3, 4 and 5 of ISO/IEC ISP 12063, according to the protocol(s) to which each functional group relates. 6 SIST EN ISP 12063-1:1997
3 ISO/IEC ISOllEC ISP 12063-1 : 1995 (E) Table 2 - Summary of Functional Group EDI Conversion (CV) 1 EDI Distribution List (DL) EDI Physical Delivery (PD) EDI Forwarding (AF, MF) EDI Redirection (RED) 1 EDI Latest Delivery (LD) (SEC1 , SEC2, SEC3) (SO, SOC) (S1 , s1 Cl s2, S2C) EDI Security AMH3n optional functional groups Inheritance relevant to relevant to relevant to from AMH1 n a MTA a MS a UA inherited Y N N inherited Y N N inherited Y N Y new N Y Y inherited Y N Y inherited Y N Y new N Y Y inherited N Y Y inherited Y Y Y 1 EDI Use of Directory (DIR) EDI 84 Interworking (841W) EDI Multi-Part Body (MPB) EDI ANSI X12 (X12) inherited new new new EDI Private Syntax (PS) Y N Y N Y Y N N Y N N Y inherited I Y 1 N I Y I EDI EDIFACT Heading fields (EH) ~ ~ ~~~~ ~~ ~ ~ new N Y Y 1 2 There are no additional requirements to those specified in ISO/IEC ISP 1061 1. Further requirements to those in ISO/IEC ISP 1061 1 are specified. ,1 EDI Conversion (CV) NO explicit conversions have been defined for the primary body part (which contains an EDI body part or EDlM body part) by the MTS. Implicit conversion of the primary body part is permitted, but the specification of particular conversions is beyond the scope of ISO/IEC ISP 12063. Implicit or explicit conversion of other body parts (which contain additional information, such as graphics or text) shall conform to the Common Messaging Conversion FG specified in ISO/IEC ISP 10611. Any such conversions performed by the receiving EDI-UA are outside the scope of ISO/IEC ISP 12063. NOTE -The use of some MHS security EoS require that any conversion that is performed by the receiving EDI-UA must be pone after the security services are performed. .2 EDI Distribution List (DL) he EDI Distribution List FG covers all issues relating to the performance of distribution list (DL) expansion. n implementation conforming to the EDI DL FG shall conform to the Common Messaging DL FG as specified i ISOiIEC ISP 1061 1. There are no additional requirements for an MTA in an EDIMG environment. 1 R I 7 SIST EN ISP 12063-1:1997
ISO/IEC ISP 12063-1 : 1995 (E) O ISO/IEC 7.3 EDI Physical Delivery (PD) The EDI Physical Delivery FG is concerned with access to physical delivery (i.e. postal, courier, etc, The EDI PD FG comprises WO separate and distinct parts: support of PD EoS on origination and submission; support of a co-located physical delivery access unit (PDAU). services. Support of PD EoS on submission may be relevant either for an EDI-UA or an MTA. Support of PDAU is only applicable to an MTA. The requirements for the PDAU itself are outside the scope of ISO/IEC ISP 12063 An implementation conforming to the EDI PD FG shall conform to the Common Messaging PD FG as specified in ISOAEC ISP 1061 1. An EDI-UA conforming to the EDI PD FG shall also make the PD EoS available to the EDIMG user for origination as specified in ISO/IEC ISP 1061 1. There are no additional requirements for the MTA in an EDIMG environment. 7.4 EDI Forwarding (AF, MF) The EDI Forwarding FG defines the service and functionality required to perform forwarding of EDlMs by or on behalf of an EDlMG user. The EDI Forwarding FG is specified as two classes: Automatic Forwarding (AF) and Manual Forwarding (MF). In class AF the forwarding is performed automatically by the EDI-UA or by the EDI-MS based on a set of criteria specified by the EDIMG-user. The available criteria and their invocation method shall be stated in the PICS. In class MF the forwarding is performed by the EDI-UA on explicit instruction by the EDIMG-user on each occasion. It shall be stated in the PICS whether or not removal of body parts is supported. NOTE - The MHS base standards requires that support of the notifications and information fields associated with forwarding (i.e. those mandated in this FG) is mandatory if forwarding is performed. 7.4.1 EDI Forwarding class (AF) The EDI Automatic Forwarding class (AF) supports use of the Stored EDI Message Auto-forward EoS. 7.4.2 EDI Forwarding class (MF) The EDI Manual Forwarding class (MF) supports use of the EDI Forwarding EoS by an EDI-UA. e 7.5 EDI Redirection (RED The EDI Redirection FG covers support of those EoS which provide the functionality required to perform the actions associated with the delivery of a message to a recipient other than the one initially specified by the originator. An MTA implementation conforming to the EDI RED FG shall conform to the Common Messaging RED FG as specified in ISOAEC ISP 1061 1. There are no additional requirements for an MTA in an EDlMG environment. 7.6 EDI Latest Delivery (LD) The EDI Latest Delivery FG covers support of the Latest Delivery EoS - i.e. the functionality required to cause non-delivery to occur if a latest delivery time specified by the originator has expired. An implementation conforming to the EDI LD FG shall conform to the Common Messaging LD FG as specified in ISOAEC ISP 1061 1. There are no additional requirements for an MTA or EDI-UA in an EDlMG environment. 8 SIST EN ISP 12063-1:1997
I I) Element of Service Application Security Element Non-repudiation of Content Originated 1 ISOAEC ISO/IEC ISP 12063-1 : 1 995 (E) Security Class SEC1 SEC2 SEC3 O O m O m O .7 EDI Security (SEC1, SEC2, SEC3, SO, SOC, S1, SlC, S2, S2C) Non-repudiation of EDI Notification Non-repudiation of EDI Notification Request Proof of Content Received he EDI Security FG covers the provision of security service in an EDIMG environment. As the interface etween the EDIMG user and the EDI-UA is outside the scope of this profile, implementations of security iechanisms can be in the EDI-UA or as part of a general security mechanism integrated with the EDIMG user bject. O m O O m O m m O he EDI Security FG is specified as three independent security classes denoted as SEC1 , SEC2 and SEC3. I addition to this, an EDIMG implementation can support any of the Common Messaging security classes SO, OC, S1 , Si C, S2 and S2C. Proof of Content Received Request Proof of EDI Notification Proof of EDI Notification Request n implementation claiming conformance to the EDI Security
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.