Nous utilisons des témoins pour créer une expérience d'utilisation du site Web plus sécuritaire et plus efficace pour nos clients. Pour plus d'information sur les témoins et sur la façon de les désactiver, consultez la page sur notre Politique de confidentialité.
En savoir plus
Centre de préférences en matière de confidentialité
Veuillez gérer vos choix de témoins en activant ou en désactivant les touches à bascule de consentement sous Objectifs ci-dessous.
Vous pouvez modifier vos préférences en tout temps, tel que décrit dans notre Politique sur les témoins. Politique de cookies
Information Technology - International Standardized Profiles AMH3n - Message Handling Systems - EDI Messaging - Part 3: AMH32 - EDIMG Requirements for Message Transfer (P1) (Adopted ISO/IEC ISP 12063-3:1997, second edition, 1997-12-15)
Année de publication 2000
Publié par CSA Group
Withdrawn
info Se connecter ou s’inscrire
Un compte d’utilisateur gratuit est requis pour lire ce document.
1.1 General This part of ISO/IEC ISP 12063 covers message transfer between Message Transfer Agents (MTAs) in an EDI Messaging (EDIMG) environment using the P1 Message Transfer Protocol (see also figure 1). These specifications form part of the EDI Messaging application functions, as defined in the parts of ISO/IEC ISP 12063, 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 ISOIIEC ISP 12063 is the third part of a multipart ISP identified in ISOIIEC TR 10000-2 as AMH3. Message Handling Systems - EDI Messaging (see also ISO/IEC TR 10000-1, subclause 8.2 for the definition of multipart ISPs). This part of ISOIIEC ISP 12063 specifies the fOllowing profile: AMH32 - EDIMG Requirements for Message Transfer (P1) The AMH32 profile may be combined with any T-Profiles (see ISO/IEC TR 10000) specifying the 051 connection-mode Transport service.
1.3 Scenario The model used is one of two or more MTAs intercommunicating within a Message Transfer System (MTS) using the P1 protocol, as shown in figure 1. Figure 1 . AMH32 scenario
NOTE - In an ITU- T context, a domain may be treated as an MTA for the purposes of conformance 10 the AMH32 profile. The AMH32 profile covers all aspects of the MTA Abstract Service, as defined in clause 12 of ISO/IEC 10021-4, when realised using the P1 protocol in an EDIMG environment. The 051 upper layer services and protocols to support the Message Handling Systems functions covered by the AMH32 profile are specified in subclause 1.3 of ISO/IEC ISP 10611-3.
Login or Register
View Access for this document is only available for viewers in Canada