1CS 35. 240. 01
National Standardization Guiding Technical Documents of the People's Republic of China GB/Z18812—2002
MIME encapsulation of EDI objects2002-08-09 Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China
2003-04-01 Implementation
GB/Z18812-2002
2 Normative References
? Types of EDI Exchanges
4 MIME Header Segments
MIME Encapsulation of EDI Exchanges Based on EDIFACT6 MIME Encapsulation of FTI Exchanges Based on AVSTXI2? This guidance technical document is mainly formulated according to the standard FC:767 proposed by the Intcrmet Engineering Task Group. This guidance technical document is also issued by the China Standard Code Center. This guidance technical document is sponsored by the National Technical Committee for Standardization of Radio and Television Services. This guidance technical document was originally drafted by the China Standardization Research Center, and the drafters of this guidance technical document are Qiao Hong, Liu Liaosong, Hu Tongchang and Sun Wen. B/2.18812-2002
CB/218812-2002
Electronic Data Interchange (EDI) provides a means of transmitting structured information between trading partners. The traditional value-added network transmission mechanism hinders the promotion and application of EDI. ITinCT, with its advantages of being portable, low-cost, supporting bandwidth and easy access, has provided a new way for EDI transmission. It is the most convenient and popular method to use the Internet's mail transmission system to transmit EDI objects at the transport layer. In order to further standardize the transmission of EDI objects on the Internet, JETT has specially formulated a series of RFCs, including how to package EDI objects and how to implement secure transmission. The latter is a complete solution for using email to transmit EDI on the Internet. RFC 175Y is one of them. KAa
1Scope
MIME Encapsulation of EDI Objects
CB/18812-2002
Guidance Technical Document proposes a format for encapsulating EDI messages in the Multi-Path Interconnect Component Extension Protocol (MIME). Unless otherwise specified, a MIME object in this guidance technical document refers to a complete EDI exchange including an exchange header and an exchange trailer. This guidance technical document defines MIME objects in an MIME environment. The encapsulation does not involve the internal structure of the object. E-transactions are carried out through a transmission and exchange mechanism. This indicative technical document also provides a convenient way for it to transmit E-objects through email. This indicative technical document is applicable to various types of E-objects transmitted through email. 2 Normative references || tt || Many clauses in the specification become the terms of the technical document through the reference of the indicative technical definition. The available documents of the above period, all subsequent amendments (excluding The contents of the errata (etc.) or revisions are not applicable to this guidance technical document, however, the parties to the six guidance technical documents that have reached an agreement on whether the latest version of these documents can be used. For all reference documents without a date, the latest version shall apply to this guidance technical document. RF Multipurpose Internet Mail Extensions Part 1: Internet Mail Format RFC822 Text Message Format || TT || 3 Types of EDI Exchanges || TT || There are various E-mail requirements in the world, The guidance documents will be divided into three categories: EIJHA, a set of EII standards developed by the United Nations Economic Commission for Europe (UNECE), which can be widely used in the world. my country's EDITACT series of standards based on the HIFACT standard is recommended by the national or industry standards.
5! ANS1X12 is a national standard association in the United States. Before the EL1 standard is formulated, it should be used in the northern region. ) Other E standards, regional cities are busy organizing national research and development of other standards, which are used in a small range. 4 Related headers in MIME
MIM is based on the multi-purpose mail extension layer of the Internet. This group of Internet definitions has fully developed RFC:32 and added the following message formats:
Text message body expressed by non-ES-AI characters, non-text message, for different formats, the expansion framework-worms are divided into different structures.
The text header of the non-character case is the total. The RFC defines the standard format of text messages, but does not specify any specific format, except that it only specifies the use of USA characters in lowercase letters and adds support for non-USASCII characters. The MIME protocol suite introduces a mechanism to solve the problem of multiple text formats without any incompatibility. The header segments are as follows: MIME version segment: This segment provides a version number, stating that the version is consistent with the official MIME version, so that the mail processing end can distinguish the old version. The version number consists of two spaces, separated by a decimal point. It is used to define the message type in the future. The content type header also defines the data type of the entity through the media type and subclass identifier. Some special media may need to provide some additional information. This additional information is in the form of group parameters. The format type is marked with a symbol followed by an unlimited number of items. The type is the basic data type: the type describes the format of the data type. The parameter is a modification symbol based on the media type, but it does not affect the quality of the implementation. The setting of the parameter depends on the media type and the subtype, or it is optional. Most vertical values are only related to a specific subtype. For example, the value of the symbol \CIIARSET\ applies to any subtype of the "text<text)" class, the value of the rate\boundary\ applies to any subtype of the \Malparr! rate\processor class, and the parameter "Mig" is used to describe the algorithm for controlling the value. The function type is divided into two major types: discrete type and complex type. Among them, the discrete type is divided into three types: text, image, video, and application. There are two types of combination: message, message, and part. The seven basic types are: message, message, and part. For all media types, if the user extends them by themselves, the tag definition needs to start with \X to avoid conflicts with the standard name. Some users only use sub-types: the only grammatical restriction on the definition of the type is the name! No.
) Content-Transfer-Encoding header: This header can describe the application's overall message conversion. It is also called the result domain of the conversion. The end-code conversion is processed by the code conversion system so that it can pass through the mail transmission system with data or characters. The previous \F defines two conversion types: wooden★software conversion), \led-printable\ and \baseG1\. When the inner segment is \7hii\, "abit\ or \binary\. I show the conversion, these values are used as indicators: "mrrl-printale\ use \bate64\ encoding conversion to convert the format to 7bit data format, so that the data can be safely transmitted through certain limited protocols:
The inner segment is actually a header with content description. In some advanced applications, the content identification header must be unique. The content identification header must be unique. The inner header segment is a header that provides descriptive information about the content of the message. 5 MIMF encapsulation of EDI exchange based on EIFALI When encapsulating the IFAI type EI exchange: The relevant information in MIMF is as follows: M type: apleai.nn
MME type: EDIAC
Parameter: CHARSHT.MICAIg, etc.
The transmission end code is: bas or qguudrrialalile content identification number: user current use of the port line to change the meaning of the description section: user line description
Among them, the MIME media type is \Ap.islinn\. Regardless of the type of EDI encapsulation, the MIME media type must be changed. Applkalian is used.
When the site is installed in accordance with the ELDIFACT environment standard, the MIME media is defined as \HITFACT\. The parameter here is not selected. For example, the Chinese character state of the FI message package \CHAKSET\ is defined as \gb1393\\. All EDI data are in text format. However, some special characters (such as delimiters) may be non-printing ASCII characters. Some data may be binary. For EDI files containing this data, the Content-Transfer-Encoding header must be either blank or red-Printable
. The header and content identifier are generated and the specific conditions are specified by the network. The following is an EDI exchange with a MIME type of A:: KAN KAca
Tu:-rlitr.t(gy:lonesni:ware.corlS.bjcct:
Iror.:
[email protected] rJh:,3 Tune 200 11:30:25Wiu Verxikinl. 0
CuniruType:applicann/ETTFACTCHARSET=gblB030Cenren:-Tren:fer-Enc-di:g:basee4Conttnt Deseriation:Invaicc Meaaage---Exchange starts-
Exchange)
E exchange ends
6 MIME encapsulation plan for EDI exchange based on ANSIX12 When the ANSIX type E exchange is carried out, the relevant information in MIME is defined as follows: MhE type: Aoplicstior.
MIME -Type,HI-X12
Li Min:CHARSET,MirAIg
Inside the customer transfer code:ln4guare-prietable content identification:city household regulations and education definition of internal wear with loss of shares, with Guangbai Ning explanation
In addition to MME type into FT-XI with other meanings of the internal uniform and the first: cabinet company below to give a MTME installation ANSIX12 complete record of EI exchange proofreading example,
[email protected]:
Pror. rcdisicnder (djuyelotunoftwTt. I1.ate:u32n:go.2f.
Miae-V.rxion: It
(xucn-Type:apphcation/ELl X12Contunt Trenfer Hncoding:haseri4Conient-Lescriztion: Invni Messagy----[Exchange starts
bzxz.netE exchange>
EDI exchange bundle
7 MIMF encapsulation of EDI exchange based on other EIL systems When other systems exchange in violation of the emission & M1ME specification related information is defined as follows: MIME type: Apoliation
MIME subclass: FL-cOSCn
number, CHARSHIMHAI car
content transmission terminal: aae or otod-print able internal standard header download: use the wide range of learning and custom internal uniform description header: use:: self-description B/13812-2002
GH/188*2—2002
its MME product type changes the second "- other header section of the internal friction and the first year of the same and give a MM package of other I type EII exchange implementation plan: Tn,ed:res:aicycloncsoftwure.romSubel
FrutliSedereyrlneaafiwi rr.com[74le:Thu,3 Jun 2000 11:30:29Mime Version:l.心
Coatem-Tsje:arelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeE exchange open
FI> exchange:
----FDI Exchange Bundle---
8 Typical process of EDI object transmission via email A MIE-encapsulated EDI object is used for typical email transmission (see Figure 1). MIME packaging
SMTP
Sample document
EDL document
Business processing
Figure 1 shows the steps for email transmission.
9 Security issues
E transactions usually contain sensitive data, so the transmission needs to consider issues such as authenticity, security, accessibility, and resistance. This guiding technical document specifies the way to transmit sensitive data through 1ntern email. This document supports other services that encapsulate MIE. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, and low-modulus resistance. This refers to the security mechanism provided by the technical document itself. If the security mechanism is to be appropriate, this column must be added during the transmission process. By using the MIME-based security service, or the active ratio finally EI Jiang standard security service. The implementation of the full M1ME service barrier is as follows:
RFC: 23 and RFC263 MTMES/VIMF) message specification HGI5GP road my implementation of the MIMF
KANKAc
based on the North standard security service reference: GH2:1E812-2002
G/130%.1944 two lines of business and industry data exchange application level syntax rules (method number: 4) Part 5: format self-number batch Exchange of documents (authenticity, integrity and authenticity) Part 1: Authentication and confirmation of messages (message type AITACKGB, 1-5.9-201≤ administrative, business and transport information exchange grammar rules < English version 4:41 Part 1: Security and confirmation messages (message type K is YMAGR/ 7.18812--2002
RFC230
Multiple Reference Documents
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Message Specification
PGP Secure MIME
G5/T1815.5-19, for use in the electronic data interchange of the commercial, transportation and shipping industries (Syntax Version Number: 1) Section: Design: Secure MIMES/MIME Message Specification Enterprises (authentic, complete and source resistance! 15/4895.5-January: Bank collection, commercial and transport industries issued the application level No. 4: 6: Enterprise identification and confirmation message "The report type is ALITACK; 6/1486-3001! Administrative collection and transport industries issued the application level No. 13: Enterprise sealing and accounting management message (technical document type is long EY over AV) EKANKatt||CuniruType:applicann/ETTFACTCHARSET=gblB030Cenren:-Tren:fer-Enc-di:g:basee4Conttnt Deseriation:Invaicc Meaaage---Exchange starts-
Exchange)
E-Exchange Station End
6 MIME encapsulation based on ANSIX12 EDI exchange When the ANSIX type E-exchange is carried out, the MIME and related information are defined as follows: MhE type: Aoplicstior.
MIME-type, HI-X12
Charset, MirAIg
Content transfer code: ln4 or guaranteed-prietary content identifier: City household regulations and use of the definition of the internal wear and loss of shares, use Guangbai Ning to explain
In addition to the MME type into FT-XI, the other meanings are consistent with the first: The following is an example of EI exchange with ANSIX12 in MIME package,
[email protected]:
Pror. rcdisicnder (djuyelotunoftwTt. I1.ate:u32n:go.2f.
Miae-V.rxion: It
(xucn-Type:apphcation/ELl X12Contunt Trenfer Hncoding:haseri4Conient-Lescriztion : Invni Messagy----[Exchange Start
E Security Exchange>
EDI Exchange Station Bundle
7 MIMF Encapsulation of EDI Exchange Based on Other EIL Systems When other systems are used to exchange EDI exchanges, the M1ME specification and related information are defined as follows: MME* Type: Apoliation
MIME Subclass: FL-cOSCn
Number, CHARSHIMHAI Car
Content Transfer Terminal: aae or otod-print able internal standard header download: use the wide range of learning and custom internal uniform description header: use:: self-description B/13812-2002
GH/188*2—2002
its MME product type changes the second "- other header section of the internal friction and the first year of the same and give a MM package of other I type EII exchange implementation plan: Tn,ed:res:aicycloncsoftwure.romSubel
FrutliSedereyrlneaafiwi rr.com[74le:Thu,3 Jun 2000 11:30:29Mime Version:l.心
Coatem-Tsje:arelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeE exchange open
FI> exchange:
----FDI Exchange Bundle---
8 Typical process of EDI object transmission via email A MIE-encapsulated EDI object is used for typical email transmission (see Figure 1). MIME packaging
SMTP
Sample document
EDL document
Business processing
Figure 1 shows the steps for email transmission.
9 Security issues
E transactions usually contain sensitive data, so the transmission needs to consider issues such as authenticity, security, accessibility, and resistance. This guiding technical document specifies the way to transmit sensitive data through 1ntern email. This document supports other services that encapsulate MIE. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, and low-modulus resistance. This refers to the security mechanism provided by the technical document itself. If the security mechanism is to be appropriate, this column must be added during the transmission process. By using the MIME-based security service, or the active ratio finally EI Jiang standard security service. The implementation of the full M1ME service barrier is as follows:
RFC: 23 and RFC263 MTMES/VIMF) message specification HGI5GP road my implementation of the MIMF
KANKAc
based on the North standard security service reference: GH2:1E812-2002
G/130%.1944 two lines of business and industry data exchange application level syntax rules (method number: 4) Part 5: format self-number batch Exchange of documents (authenticity, integrity and authenticity) Part 1: Authentication and confirmation of messages (message type AITACKGB, 1-5.9-201≤ administrative, business and transport information exchange grammar rules < English version 4:41 Part 1: Security and confirmation messages (message type K is YMAGR/ 7.18812--2002
RFC230
Multiple Reference Documents
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Message Specification
PGP Secure MIME
G5/T1815.5-19, for use in the electronic data interchange of the commercial, transportation and shipping industries (Syntax Version Number: 1) Section: Design: Secure MIMES/MIME Message Specification Enterprises both rules (authentic, complete and source resistance to head rot! 15/4895.5-January: Bank collection, commercial and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 13: Part 1: Security and confirmation message (The technical type is long EY over AV) EKANKatt||CuniruType:applicann/ETTFACTCHARSET=gblB030Cenren:-Tren:fer-Enc-di:g:basee4Conttnt Deseriation:Invaicc Meaaage---Exchange starts-
Exchange)
E-Exchange Station End
6 MIME encapsulation based on ANSIX12 EDI exchange When the ANSIX type E-exchange is carried out, the MIME and related information are defined as follows: MhE type: Aoplicstior.
MIME-type, HI-X12
Charset, MirAIg
Content transfer code: ln4 or guaranteed-prietary content identifier: City household regulations and use of the definition of the internal wear and loss of shares, use Guangbai Ning to explain
In addition to the MME type into FT-XI, the other meanings are consistent with the first: The following is an example of EI exchange with ANSIX12 in MIME package,
[email protected]:
Pror. rcdisicnder (djuyelotunoftwTt. I1.ate:u32n:go.2f.
Miae-V.rxion: It
(xucn-Type:apphcation/ELl X12Contunt Trenfer Hncoding:haseri4Conient-Lescriztion : Invni Messagy----[Exchange Start
E Security Exchange>
EDI Exchange Station Bundle
7 MIMF Encapsulation of EDI Exchange Based on Other EIL Systems When other systems are used to exchange EDI exchanges, the M1ME specification and related information are defined as follows: MME* Type: Apoliation
MIME Subclass: FL-cOSCn
Number, CHARSHIMHAI Car
Content Transfer Terminal: aae or otod-print able internal standard header download: use the wide range of learning and custom internal uniform description header: use:: self-description B/13812-2002
GH/188*2—2002
its MME product type changes the second "- other header section of the internal friction and the first year of the same and give a MM package of other I type EII exchange implementation plan: Tn,ed:res:aicycloncsoftwure.romSubel
FrutliSedereyrlneaafiwi rr.com[74le:Thu,3 Jun 2000 11:30:29Mime Version:l.心
Coatem-Tsje:arelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeE exchange open
FI> exchange:
----FDI Exchange Bundle---
8 Typical process of EDI object transmission via email A MIE-encapsulated EDI object is used for typical email transmission (see Figure 1). MIME packaging
SMTP
Sample document
EDL document
Business processing
Figure 1 shows the steps for email transmission.
9 Security issues
E transactions usually contain sensitive data, so the transmission needs to consider issues such as authenticity, security, accessibility, and resistance. This guiding technical document specifies the way to transmit sensitive data through 1ntern email. This document supports other services that encapsulate MIE. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, and low-modulus resistance. This refers to the security mechanism provided by the technical document itself. If the security mechanism is to be appropriate, this column must be added during the transmission process. By using the MIME-based security service, or the active ratio finally EI Jiang standard security service. The implementation of the full M1ME service barrier is as follows:
RFC: 23 and RFC263 MTMES/VIMF) message specification HGI5GP road my implementation of the MIMF
KANKAc
based on the North standard security service reference: GH2:1E812-2002
G/130%.1944 two lines of business and industry data exchange application level syntax rules (method number: 4) Part 5: format self-number batch Exchange of documents (authenticity, integrity and authenticity) Part 1: Authentication and confirmation of messages (message type AITACKGB, 1-5.9-201≤ administrative, business and transport information exchange grammar rules < English version 4:41 Part 1: Security and confirmation messages (message type K is YMAGR/ 7.18812--2002
RFC230
Multiple Reference Documents
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Message Specification
PGP Secure MIME
G5/T1815.5-19, for use in the electronic data interchange of the commercial, transportation and shipping industries (Syntax Version Number: 1) Section: Design: Secure MIMES/MIME Message Specification Enterprises both rules (authentic, complete and source resistance to head rot! 15/4895.5-January: Bank collection, commercial and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 13: Part 1: Security and confirmation message (The technical type is long EY over AV) EKANKaMirAIg
The content of the customer transfer code is: ln4guare-prietable content identification is: the city household regulations are used to define the internal wear and loss of shares, and the Guangbai Ning description
In addition to the MME type becoming FT-XI with other meanings of the internal uniform and the first: the cabinet company gives an example of the EI exchange school of the MTME installation ANSIX12 complete record,
[email protected]:
Pror. rcdisicnder (djuyelotunoftwTt. I1.ate:u32n:go.2f.
Miae-V.rxion: It
(xucn-Type:apphcation/ELl X12Contunt Trenfer Hncoding:haseri4Conient-Lescriztion: Invni Messagy----[Exchange starts
E exchange>
EDI exchange bundle
7 MIMF encapsulation of EDI exchange based on other EIL systems When other systems exchange in violation of the transmission & M1ME specification related information is defined as follows: MIME type: Apoliation
MIME subclass: FL-cOSCn
number, CHARSHIMHAI car
content transmission terminal: aae or otod-print able internal standard header download: use the wide range of learning and custom internal uniform description header: use:: self-description B/13812-2002
GH/188*2—2002
its MME product type changes the second "- other header section of the internal friction and the first year of the same and give a MM package of other I type EII exchange implementation plan: Tn,ed:res:aicycloncsoftwure.romSubel
FrutliSedereyrlneaafiwi rr.com[74le:Thu,3 Jun 2000 11:30:29Mime Version:l.心
Coatem-Tsje:arelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeE exchange open
FI> exchange:
----FDI Exchange Bundle---
8 Typical process of EDI object transmission via email A MIE-encapsulated EDI object is used for typical email transmission (see Figure 1). MIME packaging
SMTP
Sample document
EDL document
Business processing
Figure 1 shows the steps for email transmission.
9 Security issues
E transactions usually contain sensitive data, so the transmission needs to consider issues such as authenticity, security, accessibility, and resistance. This guiding technical document specifies the way to transmit sensitive data through 1ntern email. This document supports other services that encapsulate MIE. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, and low-modulus resistance. This refers to the security mechanism provided by the technical document itself. If the security mechanism is to be appropriate, this column must be added during the transmission process. By using the MIME-based security service, or the active ratio finally EI Jiang standard security service. The implementation of the full M1ME service barrier is as follows:
RFC: 23 and RFC263 MTMES/VIMF) message specification HGI5GP road my implementation of the MIMF
KANKAc
based on the North standard security service reference: GH2:1E812-2002
G/130%.1944 two lines of business and industry data exchange application level syntax rules (method number: 4) Part 5: format self-number batch Exchange of documents (authenticity, integrity and authenticity) Part 1: Authentication and confirmation of messages (message type AITACKGB, 1-5.9-201≤ administrative, business and transport information exchange grammar rules < English version 4:41 Part 1: Security and confirmation messages (message type K is YMAGR/ 7.18812--2002
RFC230
Multiple Reference Documents
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Message Specification
PGP Secure MIME
G5/T1815.5-19, for use in the electronic data interchange of the commercial, transportation and shipping industries (Syntax Version Number: 1) Section: Design: Secure MIMES/MIME Message Specification Enterprises both rules (authentic, complete and source resistance to head rot! 15/4895.5-January: Bank collection, commercial and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 13: Part 1: Security and confirmation message (The technical type is long EY over AV) EKANKaMirAIg
The content of the customer transfer code is: ln4guare-prietable content identification is: the city household regulations are used to define the internal wear and loss of shares, and the Guangbai Ning description
In addition to the MME type becoming FT-XI with other meanings of the internal uniform and the first: the cabinet company gives an example of the EI exchange school of the MTME installation ANSIX12 complete record,
[email protected]:
Pror. rcdisicnder (djuyelotunoftwTt. I1.ate:u32n:go.2f.
Miae-V.rxion: It
(xucn-Type:apphcation/ELl X12Contunt Trenfer Hncoding:haseri4Conient-Lescriztion: Invni Messagy----[Exchange starts
E exchange>
EDI exchange bundle
7 MIMF encapsulation of EDI exchange based on other EIL systems When other systems exchange in violation of the transmission & M1ME specification related information is defined as follows: MIME type: Apoliation
MIME subclass: FL-cOSCn
number, CHARSHIMHAI car
content transmission terminal: aae or otod-print able internal standard header download: use the wide range of learning and custom internal uniform description header: use:: self-description B/13812-2002
GH/188*2—2002
its MME product type changes the second "- other header section of the internal friction and the first year of the same and give a MM package of other I type EII exchange implementation plan: Tn,ed:res:aicycloncsoftwure.romSubel
FrutliSedereyrlneaafiwi rr.com[74le:Thu,3 Jun 2000 11:30:29Mime Version:l.心
Coatem-Tsje:arelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeE exchange open
FI> exchange:
----FDI Exchange Bundle---
8 Typical process of EDI object transmission via email A MIE-encapsulated EDI object is used for typical email transmission (see Figure 1). MIME packaging
SMTP
Sample document
EDL document
Business processing
Figure 1 shows the steps for email transmission.
9 Security issues
E transactions usually contain sensitive data, so the transmission needs to consider issues such as authenticity, security, accessibility, and resistance. This guiding technical document specifies the way to transmit sensitive data through 1ntern email. This document supports other services that encapsulate MIE. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, and low-modulus resistance. This refers to the security mechanism provided by the technical document itself. If the security mechanism is to be appropriate, this column must be added during the transmission process. By using the MIME-based security service, or the active ratio finally EI Jiang standard security service. The implementation of the full M1ME service barrier is as follows:
RFC: 23 and RFC263 MTMES/VIMF) message specification HGI5GP road my implementation of the MIMF
KANKAc
based on the North standard security service reference: GH2:1E812-2002
G/130%.1944 two lines of business and industry data exchange application level syntax rules (method number: 4) Part 5: format self-number batch Exchange of documents (authenticity, integrity and authenticity) Part 1: Authentication and confirmation of messages (message type AITACKGB, 1-5.9-201≤ administrative, business and transport information exchange grammar rules < English version 4:41 Part 1: Security and confirmation messages (message type K is YMAGR/ 7.18812--2002
RFC230
Multiple Reference Documents
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Message Specification
PGP Secure MIME
G5/T1815.5-19, for use in the electronic data interchange of the commercial, transportation and shipping industries (Syntax Version Number: 1) Section: Design: Secure MIMES/MIME Message Specification Enterprises both rules (authentic, complete and source resistance to head rot! 15/4895.5-January: Bank collection, commercial and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 4: Part 6: Security and confirmation message "The report type is ALITACK; 6/1486-300January! Administrative collection and transport industries issued a digital exchange application level No. No law rules (Syntax version number: 13: Part 1: Security and confirmation message (The technical type is long EY over AV) EKANKaarelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeEExchange Open
FI>Exchange:
----FDI 8. Typical Process of EDI Object Transmission via Email A typical process of EDI object transmission via MIME is shown in Figure 1. MIME packaging SMTP sample document EDL document Business Processing Figure 1 shows the steps of EDI transmission via email. 9. Security Issues EDI transactions usually contain sensitive data, so transmission needs to consider issues such as authenticity, security, access control, and anti-counterfeiting. This guidance document specifies the method of transmitting sensitive data via email. Other methods support EDI packaging service. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, anti-low-module resistance, etc.: this refers to the security mechanism provided by the technical document itself. If the step is appropriate, this column must be added in the transmission process. By using the MIME-based security service, or the active MIME-based security service. For the implementation of the MIME service, see: RF: 23 and RFC 263 MTMES/VIMF) message specifications HGI5GP route My implementation of the MIMF
KANKAc
Based on the North standard security service, see: GH2: 1E812-2002
G/130%.1944 2. Application level syntax rules for commercial and transport data exchange (method number: 4) Part 5: Full rules for batch exchange of sub-data (authenticity, integrity and source protection) B/185.6-1! ! The language used for the exchange of documents in the banking and transport industries (syntax cost Dan) Part 1: Security authentication and confirmation (message type AITACKGB, 1-5.9-201≤ administrative, industrial and transport electronic data exchange point-to-point syntax rules <method number: 41 Part 1: Security rate Zhao and bookkeeping management message (message type K standard YMAGR/7.18812-2002
RFC230
Reference Literature
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Text
PGP Secure MIME
G5/T1815.5-19, for use in the collection, commerce and transport industries, has put forward application-level rules for electronic data interchange (syntax version number: 1): Part 6: Secure enterprise identification and confirmation messages (message type ALITACK); 6/1486-3001! Administration and transportation industry electronic exchange of digital applications photographed reverse method Xiao Ze language version number: 13 part: security enterprise seal and plan book management message (technical document type is long EY over AV) EKANKaarelication/Ell-coscutConteni-T'ransfer-EncodinRibaace4Cauntent Lhereriprull ; Jevoicr MessugeEExchange Open
FI>Exchange:
----FDI 8. Typical Process of EDI Object Transmission via Email A typical process of EDI object transmission via MIME is shown in Figure 1. MIME packaging SMTP sample document EDL document Business Processing Figure 1 shows the steps of EDI transmission via email. 9. Security Issues EDI transactions usually contain sensitive data, so transmission needs to consider issues such as authenticity, security, access control, and anti-counterfeiting. This guidance document specifies the method of transmitting sensitive data via email. Other methods support EDI packaging service. For a high-efficiency ticket, it is necessary to require more security services, such as authentication, machine resistance, anti-low-module resistance, etc.: this refers to the security mechanism provided by the technical document itself. If the step is appropriate, this column must be added in the transmission process. By using the MIME-based security service, or the active MIME-based security service. For the implementation of the MIME service, see: RF: 23 and RFC 263 MTMES/VIMF) message specifications HGI5GP route My implementation of the MIMF
KANKAc
Based on the North standard security service, see: GH2: 1E812-2002
G/130%.1944 2. Application level syntax rules for commercial and transport data exchange (method number: 4) Part 5: Full rules for batch exchange of sub-data (authenticity, integrity and source protection) B/185.6-1! ! The language used for the exchange of documents in the banking and transport industries (syntax cost Dan) Part 1: Security authentication and confirmation (message type AITACKGB, 1-5.9-201≤ administrative, industrial and transport electronic data exchange point-to-point syntax rules <method number: 41 Part 1: Security rate Zhao and bookkeeping management message (message type K standard YMAGR/7.18812-2002
RFC230
Reference Literature
Secure MIMES/MIME) Message Specification
RE:2 Secure MIMES/MIME Text
PGP Secure MIME
G5/T1815.5-19, for use in the collection, commerce and transport industries, has put forward application-level rules for electronic data interchange (syntax version number: 1): Part 6: Secure enterprise identification and confirmation messages (message type ALITACK); 6/1486-3001! Administration and transportation industry electronic exchange of digital applications photographed reverse method Xiao Ze language version number: 13 part: security enterprise seal and plan book management message (technical document type is long EY over AV) EKANKa
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.