Network Working Group A. Robert
Request for Comments: 2351 SITA
Category: Informational May 1998
Network Working Group A. Robert
Request for Comments: 2351 SITA
Category: Informational May 1998
Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP
通过IP映射航空公司预订、票务和消息传递流量
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Security Disclaimer:
安全免责声明：
This document fails to adequately address security concerns. The protocol itself does not include any security mechanisms. The document notes that traffic can be authenticated based on external mechanisms that use static identifiers or what are apparently clear-text passwords, neither of which provide sound security. The document notes in general terms that traffic can be secured using IPSEC, but leaves this form of sound security strictly optional.
本文件未能充分解决安全问题。协议本身不包括任何安全机制。该文档指出，可以基于使用静态标识符或明文密码的外部机制对流量进行身份验证，这两种密码都不能提供良好的安全性。该文档概括地指出，可以使用IPSEC保护流量，但严格地说，这种形式的声音安全是可选的。
Abstract
摘要
This memo specifies a protocol for the encapsulation of the airline specific protocol over IP.
本备忘录规定了通过IP封装航空公司特定协议的协议。
Table of Conents
要素表
1. INTRODUCTION 2 2. TERMINOLOGY & ACRONYMS 4 3. LAYERING 7 4. TRAFFIC IDENTIFICATION 7 5. TCP PORT ALLOCATION 8 6. MATIP SESSION ESTABLISHMENT 8 7. OVERALL PACKET FORMAT FOR TYPE A & TYPE B 9 8. MATIP FORMAT FOR TYPE A CONVERSATIONAL TRAFFIC 10 8.1 Control Packet Format 10 8.1.1 Session Open format (SO) 10 8.1.2 Open Confirm format (OC) 12 8.1.3 Session Close (SC) 14 8.2 Data Packet Format 14
1. 导言2。术语和首字母缩略词4 3。分层7 4。交通识别7 5。TCP端口分配8 6。MATIP会议的建立8 7。A型和B型的总数据包格式9 8。A类会话流量的MATIP格式10 8.1控制包格式10 8.1.1会话开放格式（SO）10 8.1.2开放确认格式（OC）12 8.1.3会话关闭（SC）14 8.2数据包格式14
9. MATIP FORMAT FOR TYPE A HOST-TO-HOST TRAFFIC 15 9. 1 Control Packet Format 15 9.1.1 Session Open format (SO) 15 9.1.2 Open Confirm format (OC) 17 9.1.3 Session Close (SC) 17 9.2 Data Packet Format 18 10. MATIP FORMAT FOR TYPE B TRAFFIC 19 10.1 Control packet format 19 10.1.1 Session Open format (SO) 19 10.1.2 Open confirm format (OC) 20 10.1.3 Session Close (SC) 21 10.2 Data packet format 21 11. SECURITY CONSIDERATIONS 22 12. AUTHOR'S ADDRESS 22 13. FULL COPYRIGHT STATEMENT 23
9. A型主机对主机通信的MATIP格式15 9。1控制包格式15 9.1.1会话开放格式（SO）15 9.1.2开放确认格式（OC）17 9.1.3会话关闭（SC）17 9.2数据包格式18 10。B类流量的MATIP格式19 10.1控制包格式19 10.1.1会话开放格式（SO）19 10.1.2开放确认格式（OC）20 10.1.3会话关闭（SC）21 10.2数据包格式21 11。安全考虑22 12。提交人地址22 13。完整版权声明23
The airline community has been using a worldwide data network for over 40 years, with two main types of traffic:
航空公司社区使用全球数据网络已有40多年，主要有两种类型的流量：
Transactional traffic
事务流量
This is used typically for communication between an airline office or travel agency and a central computer system for seat reservations and ticket issuing. A dumb terminal or a PC accesses the central system (IBM or UNISYS) through a data network.
这通常用于航空公司办公室或旅行社与中央计算机系统之间的通信，用于座位预订和机票发放。哑终端或PC通过数据网络访问中央系统（IBM或UNISYS）。
This traffic is also called TYPE A and is based on real-time query/response with limited protection, high priority and can be discarded. The user can access only one predetermined central computer system. In case of no response (data loss), the user can duplicate the request.
该流量也称为A型流量，基于实时查询/响应，保护有限，优先级高，可以丢弃。用户只能访问一个预定的中央计算机系统。如果没有响应（数据丢失），用户可以复制请求。
Messaging
消息传递
This is an e-mail application where real-time is not needed. However a high level of protection is required. The addressing scheme uses an international format defined by IATA and contains the city and airline codes.
这是一个不需要实时处理的电子邮件应用程序。然而，需要高水平的保护。寻址方案使用国际航空运输协会定义的国际格式，包含城市和航空公司代码。
This traffic is also called TYPE B and is transmitted with a high level of protection, multi-addressing and 4 levels of priority.
这种通信量也称为B型，以高级别保护、多寻址和4级优先级进行传输。
The detailed formats for TYPE A and TYPE B messages are defined in the IATA standards.
IATA标准中定义了A类和B类报文的详细格式。
At the bottom level, synchronous protocols have been built since 1960's and well before the OSI and SNA standards.
在底层，同步协议自20世纪60年代开始建立，远远早于OSI和SNA标准。
At present, there is a big number of legacy equipment installed in thousands of airline offices around the world. Many airlines do not have immediate plans to replace their terminals with more modern equipment using open standards. They are in search of more economical ways for connecting these terminals to the present reservation system.
目前，全球数千家航空公司的办公室都安装了大量的遗留设备。许多航空公司并没有立即计划用使用开放标准的更现代化的设备来取代其航站楼。他们正在寻找更经济的方式将这些终端连接到目前的预订系统。
Most airlines are willing to migrate from airline specific protocols to standardized protocols in order to benefit from the lower cost of new technologies, but the migration has been slow done to the following factors:
大多数航空公司愿意从特定于航空公司的协议迁移到标准化协议，以便从新技术的较低成本中获益，但由于以下因素，迁移速度较慢：
- Applications have not been migrated. - Dumb terminals using airline protocols P1024B (IBM ALC) or P1024C (UNISYS UTS) are still numerous.
- 应用程序尚未迁移。-使用航空公司协议P1024B（IBM ALC）或P1024C（UNISYS UTS）的哑终端仍然很多。
There are currently many different proprietary solutions based on gateways available to take advantage of low cast networking, but they are not scalable and cannot interact.
目前有许多基于网关的不同专有解决方案可用于利用低播网络，但它们不可扩展且无法交互。
In the future, TCP/IP will be more commonly used as a common transport means for traffic types because:
将来，TCP/IP将更常用作流量类型的通用传输方式，因为：
- TCP/IP is the standard protocol of UNIX based applications - TCP/IP stacks are inexpensive - TCP/IP is used on intranets.
- TCP/IP是基于UNIX的应用程序的标准协议-TCP/IP堆栈价格低廉-TCP/IP用于内部网。
The purpose of this RFC is to define the mapping of the airline traffic types over TCP/IP. The airlines implementing it in their systems should have a TCP/IP stack to enable the traffic exchange below:
此RFC的目的是定义TCP/IP上的航空流量类型映射。在其系统中实施的航空公司应具有TCP/IP协议栈，以实现以下流量交换：
!----! ( )
! !----------( )
!----! ( )
Type B HOST ( NETWORK )
( )
( ) !---o
!----! ( )--------! D !---o Type A stations
!----!----------( ) !---o
!----! ( )
TYPE A HOST !
!
!
!
--------
! !
--------
Network Messaging System
!----! ( )
! !----------( )
!----! ( )
Type B HOST ( NETWORK )
( )
( ) !---o
!----! ( )--------! D !---o Type A stations
!----!----------( ) !---o
!----! ( )
TYPE A HOST !
!
!
!
--------
! !
--------
Network Messaging System
(D) : Gateway TYPE A router
（D） ：网关类型A路由器
The different airline traffic flows concerned by this RFC are:
本RFC涉及的不同航空交通流包括：
- TYPE A Host / Terminal - TYPE A Host / TYPE A host - TYPE B Host / Network messaging System
- A型主机/终端-A型主机/A型主机-B型主机/网络消息传递系统
In the case of dumb terminals, a conversion is required on the terminal side in order to have an IP connection between the host and the router. However, the IP connection is directly between the central airline host and the intelligent workstation if the latter has a direct connection to the network, a TCP/IP stack and a terminal emulation
对于哑终端，需要在终端侧进行转换，以便在主机和路由器之间建立IP连接。但是，如果智能工作站直接连接到网络、TCP/IP堆栈和终端仿真，则IP连接直接在中央航空公司主机和智能工作站之间
ALC Airline Line Control: IBM airline specific protocol (see P1024B)
ALC航线控制：IBM航线特定协议（参见P1024B）
ASCII American Standard Code for Information Interchange
美国信息交换标准码
ASCU Agent Set Control Unit: Cluster at the user side.
ASCU代理集控制单元：用户端群集。
AX.25 Airline X.25: Airline application of the X.25 OSI model (published by IATA)
AX.25航空公司X.25:X.25 OSI模型的航空公司应用（由IATA发布）
BAUDOT Alphabet defined in ITU-T Number 5. BAUDOT uses 5 bits. Padded BAUDOT uses 7 bits with the Most significant bit (bit 7) for the parity and the bit 6 equal to 1.
ITU-T第5号中定义的波多字母。波多特使用5位。填充波多特使用7位，最高有效位（第7位）用于奇偶校验，第6位等于1。
BATAP Type B Application to Application Protocol. Protocol to secure the TYPE B traffic. It was specified by SITA and is now published by IATA (SCR Vol. 3)
BATAP类型B应用程序到应用程序协议。用于保护类型B流量的协议。它由SITA指定，现在由IATA出版（SCR第3卷）
EBCDIC Extended Binary Coded Decimal Interchange Code
扩展二进制编码十进制交换码
Flow ID Traffic Flow identifier used in host to host traffic to differentiate traffic flow types.
流量ID用于主机到主机流量的流量标识符，用于区分流量类型。
HLD High Level Designator: Indicates the entry or exit point of a block in the network.
HLD高级指示符：表示网络中块的入口或出口点。
IA Interchange Address: ASCU identifier in P1024B protocol.
IA交换地址：P1024B协议中的ASCU标识符。
IATA International Air Transport Association
国际航空运输协会
IP Internet Protocol
网际协议
IPARS International Program Airline Reservation System: IPARS code is used in ALC
IPARS国际计划航空公司预订系统：在ALC中使用IPARS代码
HTH Host to Host (traffic).
HTH主机到主机（流量）。
LSB Least Significant Bit
最低有效位
MATIP Mapping of Airline Traffic over Internet Protocol
互联网协议上航空流量的MATIP映射
MSB Most Significant Bit
最高有效位
OC Open Confirm (MATIP command)
OC打开确认（MATIP命令）
OSI Open Standard Interface
开放标准接口
P1024B SITA implementation of the ALC, the IBM airlines specific protocol. It uses 6-bit padded characters (IPARS) and IA/ TA for physical addressing.
P1024B ALC（IBM航空公司专用协议）的SITA实现。它使用6位填充字符（IPAR）和IA/TA进行物理寻址。
P1024C SITA implementation of the UTS, the UNISYS terminal protocol. It uses 7-bit (ASCII) characters and RID/ SID for physical addressing.
P1024C UTS的SITA实现，即UNISYS终端协议。它使用7位（ASCII）字符和RID/SID进行物理寻址。
RFU Reserved for Future Use
保留供将来使用的RFU
RID Remote Identifier: ASCU identifier in P1024C protocol.
RID远程标识符：P1024C协议中的ASCU标识符。
SC Session Close (MATIP command)
SC会话关闭（MATIP命令）
SCR System and Communication Reference. (IATA document)
SCR系统和通信参考。（国际航空运输协会文件）
SID Station Identifier: Terminal identifier in P1024C protocol.
SID站标识符：P1024C协议中的终端标识符。
SITA Societe International de Telecommunications Aeronautiques
国际航空电信兴业银行
SO Session Open (MATIP command)
SO会话打开（MATIP命令）
TA Terminal Address: Terminal identifier in P1024B protocol.
TA终端地址：P1024B协议中的终端标识符。
TCP Transport Control Protocol
TCP传输控制协议
TYPE A Traffic Interactive traffic or host to host
键入流量交互流量或主机到主机
TYPE B Traffic Messaging traffic in IATA compliant format with high level of reliability
B类流量信息传输采用符合IATA的格式，具有高可靠性
UTS Universal Terminal System by Unisys: (see P1024C)
Unisys的UTS通用终端系统：（见P1024C）
MATIP is an end to end protocol. Its purpose is to have a mapping standard between the TCP layer and the airline application without any routing element.
MATIP是一种端到端协议。它的目的是在TCP层和航空公司应用程序之间建立一个映射标准，而不需要任何路由元素。
+-------------------------------+
|Airline TYPE A | Airline TYPE B|
| | Application |
| |---------------|
| Application | BATAP |
+-------------------------------+
| MATIP A | MATIP B |
+-------------------------------+
| T.C.P |
+-------------------------------+
| I.P |
+-------------------------------+
| MEDIA |
+-------------------------------+
+-------------------------------+
|Airline TYPE A | Airline TYPE B|
| | Application |
| |---------------|
| Application | BATAP |
+-------------------------------+
| MATIP A | MATIP B |
+-------------------------------+
| T.C.P |
+-------------------------------+
| I.P |
+-------------------------------+
| MEDIA |
+-------------------------------+
In TYPE A conversational traffic, the airline host application recognizes the ASCU due to 4 bytes (H1, H2, A1, A2). These bytes are assigned by the host and are unique per ASCU. Thus, a host can dynamically recognize the ASCU independent of IP address.
在类型A会话流量中，航空公司主机应用程序根据4个字节（H1、H2、A1、A2）识别ASCU。这些字节由主机分配，每个ASCU都是唯一的。因此，主机可以独立于IP地址动态识别ASCU。
H1 H2 A1 A2 bytes follow one of the three cases below:
H1 H2 A1 A2字节遵循以下三种情况之一：
- A1,A2 only are used and H1H2 is set to 0000. - H1,H2 identify the session and A1A2 the ASCU inside the session. - H1,H2,A1,A2 identify the ASCU.
- 仅使用A1、A2，H1H2设置为0000。-H1、H2标识会话，A1A2标识会话内的ASCU。-H1、H2、A1、A2识别ASCU。
The first two cases are fully compatible with the AX.25 mapping where H1H2 may be equivalent to the HLD of the concentrator, i.e., 2 bytes hexadecimal. The third rule allows more flexibility but is not compatible with AX.25.
前两种情况与AX.25映射完全兼容，其中H1H2可能等效于集中器的HLD，即2字节十六进制。第三条规则允许更大的灵活性，但与AX.25不兼容。
In TYPE A host to host traffic the identification field is also present and is equal to 3 bytes H1 H2 Flow ID (optional). H1H2 are reserved for remote host identification (independently of the IP address) and must be allocated bilaterally.
在类型A主机到主机流量中，也存在标识字段，该字段等于3字节H1 H2流量ID（可选）。H1H2保留用于远程主机标识（独立于IP地址），必须双边分配。
In Type B traffic, identification of End Systems may be carried out by the use of HLDs, or directly by the pair of IP addresses.
在B类流量中，终端系统的识别可通过使用HLD或直接通过IP地址对来执行。
IANA (Internet Assigned Numbers Authority) has allocated the following ports for MATIP TYPE A and TYPE B traffic: MATIP Type A TCP port = 350 MATIP Type B TCP port = 351
IANA（互联网分配号码管理局）已为MATIP类型A和类型B流量分配了以下端口：MATIP类型A TCP端口=350 MATIP类型B TCP端口=351
Therefore the traffic type A or B is selected according to the TCP port.
因此，根据TCP端口选择流量类型A或B。
Prior to any exchange between two applications, a single MATIP session is established above the TCP connection in order to identify the traffic characteristic such as:
在两个应用程序之间进行任何交换之前，在TCP连接上方建立单个MATIP会话，以识别流量特征，例如：
- Subtype of traffic for TYPE A (Type A host to host or Type A conversational ) - Multiplexing used (for Type A) - Data header - Character set
- 类型A的流量子类型（类型A主机到主机或类型A会话）-使用多路复用（类型A）-数据头-字符集
A separate session and TCP connection must be established for each set of parameters (e.g., P1024B, P1024C traffic between two points needs two separate sessions).
必须为每组参数建立单独的会话和TCP连接（例如，两点之间的P1024B、P1024C通信需要两个单独的会话）。
The establishment of a MATIP session can be initiated by either side. No keep-alive mechanism is defined at MATIP level. Session time out relies on the TCP time-out parameters.
MATIP会话的建立可以由任何一方发起。在MATIP级别未定义保持活动机制。会话超时取决于TCP超时参数。
There are three commands defined to manage the MATIP session:
定义了三个命令来管理MATIP会话：
- Session Open (SO) to open a session. - Open Confirm (OC) to confirm the SO command. - Session close (SC) to close the current session.
- 会话打开（SO）以打开会话。-打开确认（OC）以确认SO命令。-会话关闭（SC）关闭当前会话。
A MATIP session can be up only if the associated TCP connection is up. However it is not mandatory to close the TCP connection when closing the associated MATIP session.
仅当关联的TCP连接已启动时，MATIP会话才能启动。但是，在关闭关联的MATIP会话时，并不强制关闭TCP连接。
Typical exchange is:
典型的交换是：
TCP session establishment
TCP会话建立
Session Open --------->
<----------- Open confirm
data exchange
---------------------->
Session Open --------->
<----------- Open confirm
data exchange
---------------------->
<-------------------------
.
.
.
Session Close ----------------->
.
.
.
<------------------------- Session Open
Open confirm ------------------->
data exchange
<-------------------------
---------------------->
<-------------------------
.
.
.
Session Close ----------------->
.
.
.
<------------------------- Session Open
Open confirm ------------------->
data exchange
<-------------------------
---------------------->
The Session Open command may contain configuration elements. An Session Open command received on a session already opened (i.e., same IP address and port number) will automatically clear the associated configuration and a new configuration will be set up according to the information contained in the new open session command.
会话打开命令可能包含配置元素。在已打开的会话（即相同的IP地址和端口号）上收到的会话打开命令将自动清除相关配置，并根据新打开会话命令中包含的信息设置新配置。
As illustrated above, the open and close commands are symmetrical.
如上所示，打开和关闭命令是对称的。
For type A conversational traffic, the SO and OC commands contain information for the identification of the ASCUs and the session. ASCUs are identified within a session by two or 4 bytes. A flag is set to indicate if the ASCU is identified by 4 bytes (H1H2A1A2) or by 2 bytes (A1A2). In the latter case, H1H2 is reserved for session identification.
对于A类会话通信量，SO和OC命令包含用于识别ASCU和会话的信息。ASCU在会话中由两个或4个字节标识。设置标志以指示ASCU是由4个字节（H1H2A1A2）还是由2个字节（A1A2）标识。在后一种情况下，H1H2保留用于会话标识。
The SO command is sent to open the MATIP session. In Type A conversational it may contains the list of ASCUs configured in this session.
发送SO命令以打开MATIP会话。在会话类型A中，它可能包含在此会话中配置的ASCU列表。
The OC command confirms the SO command. It can refuse or accept it, totally or conditionally. In Type A, it contains the list of the ASCUs either rejected or configured in the session.
OC命令确认SO命令。它可以完全或有条件地拒绝或接受它。在类型A中，它包含会话中被拒绝或配置的ASCU列表。
The first 4 bytes of the MATIP header follow the following rules.
MATIP头的前4个字节遵循以下规则。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |C| Cmd | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |C| Cmd | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Ver The `Ver' (Version) field represents the version of the MATIP. It must contain the value 001 otherwise the packet is considered as invalid.
Ver“Ver”（版本）字段表示MATIP的版本。它必须包含值001，否则该数据包被视为无效。
C Identifies a CONTROL packet. When set to 1, the packet is a Control packet When set to 0, the packet is a Data packet
C标识一个控制包。当设置为1时，分组是控制分组。当设置为0时，分组是数据分组
Cmd This field identifies the control command if the flag C is set to 1.
Cmd如果标志C设置为1，则此字段标识控制命令。
Length This field indicates the number of bytes of the whole packet, header included.
长度此字段指示整个数据包（包括报头）的字节数。
Notes : Fields identified as optional (Opt) are not transmitted if not used.
注意：如果未使用，则不传输标识为可选（Opt）的字段。
There are 3 control packets to open or close the session at the MATIP level.
有3个控制数据包用于在MATIP级别打开或关闭会话。
To be able to identify the session and before sending any data packets, a Session Open command is sent. It can be initiated by either side. In case of collision, the open session from the side having the lower IP address is ignored.
为了能够识别会话，在发送任何数据包之前，会发送会话打开命令。它可以由任何一方启动。如果发生冲突，则忽略具有较低IP地址的一侧的打开会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 1 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 1|0| CD | STYP |0 0 0 0| RFU |MPX|HDR| PRES. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| H1 | H2 | RFU |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | RFU | Nbr of ASCUs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nbr of ASCUs | ASCU list (opt) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 1 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 1|0| CD | STYP |0 0 0 0| RFU |MPX|HDR| PRES. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| H1 | H2 | RFU |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | RFU | Nbr of ASCUs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nbr of ASCUs | ASCU list (opt) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RFU Reserved for future use. Must be set to zero.
RFU保留供将来使用。必须设置为零。
CD This field specifies the Coding 000 : 5 bits (padded baudot) 010 : 6 bits (IPARS) 100 : 7 bits (ASCII) 110 : 8 bits (EBCDIC) xx1 : R.F.U
CD此字段指定编码000:5位（填充波多特）010:6位（IPAR）100:7位（ASCII）110:8位（EBCDIC）xx1:R.F.U
STYP This is the traffic subtype (type being TYPE A). 0001 : TYPE A Conversational
STYP这是流量子类型（类型为A型）。0001:A型对话
MPX This flag specifies the multiplexing used within the TCP session. Possible values are: 00 : Group of ASCU with 4 bytes identification per ASCU (H1H2A1A2) 01 : Group of ASCUs with 2 bytes identification per ASCU (A1A2) 10 : single ASCU inside the TCP session.
MPX此标志指定TCP会话中使用的多路复用。可能的值为：00：每个ASCU具有4字节标识的ASCU组（H1H2A1A2）01：每个ASCU具有2字节标识的ASCU组（A1A2）10：TCP会话内的单个ASCU。
HDR
This field specifies which part of the airline's specific address is
placed ahead of the message texts transmitted over the session.
Possible values are:
00 : ASCU header = H1+H2+A1+A2
01 : ASCU Header = A1+A2
10 : No Header
11 : Not used
HDR
This field specifies which part of the airline's specific address is
placed ahead of the message texts transmitted over the session.
Possible values are:
00 : ASCU header = H1+H2+A1+A2
01 : ASCU Header = A1+A2
10 : No Header
11 : Not used
The MPX and HDR must be coherent. When ASCUs are multiplexed, the data must contain the ASCU identification. The table below summarizes the allowed combinations:
MPX和HDR必须一致。当ASCU多路传输时，数据必须包含ASCU标识。下表总结了允许的组合：
+--------------------------+
| MPX | 00 | 01 | 10 |
+--------------------------+
| HDR | |
| 00 | Y | Y | Y |
| 01 | N | Y | Y |
| 10 | N | N | Y |
+--------------------------+
+--------------------------+
| MPX | 00 | 01 | 10 |
+--------------------------+
| HDR | |
| 00 | Y | Y | Y |
| 01 | N | Y | Y |
| 10 | N | N | Y |
+--------------------------+
PRES This field indicates the presentation format 0001 : P1024B presentation 0010 : P1024C presentation 0011 : 3270 presentation
PRES此字段表示演示文稿格式0001:P1024B演示文稿0010:P1024C演示文稿0011:3270演示文稿
H1 H2 These fields can logically identify the session if MPX is not equal to 00. When this field is not used, it must be set to 0. If used in session (MPX <> 0) with HDR=00, H1H2 in data packet must have the same value as set in SO command.
H1 H2如果MPX不等于00，这些字段可以从逻辑上标识会话。不使用此字段时，必须将其设置为0。如果在HDR=00的会话（MPX<>0）中使用，数据包中的H1H2必须与SO命令中设置的值相同。
Nbr of ASCUs Nbr_of_ASCUs field is mandatory and gives the number of ASCUs per session. A 0 (zero) value means unknown. In this case the ASCU list is not present in the `Open Session' command and must be sent by the other end in the `Open Confirm' command.
ASCUs的Nbr Nbr_of_ASCUs字段为必填字段，并给出每个会话的ASCU数。0（零）值表示未知。在这种情况下，“打开会话”命令中不存在ASCU列表，必须由另一端在“打开确认”命令中发送。
ASCU LIST Contains the list of identifier for each ASCU. If MPX=00 it has a length of four bytes (H1H2A1A2) for each ASCU, otherwise it is two bytes (A1A2).
ASCU列表包含每个ASCU的标识符列表。如果MPX=00，则每个ASCU的长度为四个字节（H1H2A1A2），否则为两个字节（A1A2）。
The OC (Open Confirm) command is a response to an SO (Session Open) command and is used to either refuse the session or accept it conditionally upon checking hte configuration of each ASCU.
OC（打开确认）命令是对SO（会话打开）命令的响应，用于在检查每个ASCU的配置时拒绝会话或有条件地接受会话。
In case of acceptance, the OC indicates the number and the address of the rejected ASCUs, if any. Alternatively, it indicates the list of ASCUs configured for that MATIP session if the list provided by the SO command was correct or the number of ASCUs configured in the session was unknown (n. of ASCU equals 0).
在验收的情况下，OC指出被拒绝的ASCU的编号和地址（如有）。或者，如果SO命令提供的列表正确或会话中配置的ASCU数量未知（ASCU的n等于0），则它指示为该MATIP会话配置的ASCU列表。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| cause |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| cause |
+-+-+-+-+-+-+-+-+
Cause This field indicates the reason for the MATIP session refusal:
原因此字段指示MATIP会话拒绝的原因：
0 0 0 0 0 0 0 1 : No Traffic Type matching between Sender & Recipient 0 0 0 0 0 0 1 0 : Information in SO header incoherent
0 0 0 0 1:发件人和收件人之间没有通信类型匹配0 0 0 0 1 0:SO标头中的信息不一致
1 0 0 0 0 1 0 0 up to : Application dependent 1 1 1 1 1 1 1 1
1 0 0 0 0 1 0 0至：依赖于应用程序的1 1 1 1
Other values reserved.
保留其他值。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 R 0 0 0 0 0| Nbr of ASCUs |Nbr of ASCU(opt| ASCU LIST |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 R 0 0 0 0 0| Nbr of ASCUs |Nbr of ASCU(opt| ASCU LIST |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
R Flag indicating an error in the ASCU configuration provided in the SO command.
R标志，指示SO命令中提供的ASCU配置中的错误。
NBR of ASCUs If the MPX value is equal to 00 in the SO command, this field is two bytes long. Otherwise, it is one byte. If the R flag is set, the Nbr_of_ASCUs field represents the number of ASCUs in error. Otherwise, it indicates the number of ASCUs configured for that MATIP session.
ASCUs的NBR如果SO命令中的MPX值等于00，则此字段的长度为两个字节。否则，它是一个字节。如果设置了R标志，则Nbr_of_ASCUs字段表示出错的ASCU数量。否则，它表示为该MATIP会话配置的ASCU数量。
Notes: The length of this field is either one or two bytes. In the SO command, the length is always two bytes. This discrepancy comes from backward compatibility with AX25 (see chapter 4). In the SO command, it is possible to use a free byte defined in the AX25 call user data. Unfortunately, there is no such free byte in the AX25 clear user data.
注意：此字段的长度为一个或两个字节。在SO命令中，长度始终为两个字节。这种差异来自与AX25的向后兼容性（参见第4章）。在SO命令中，可以使用AX25调用用户数据中定义的空闲字节。不幸的是，AX25清除用户数据中没有这样的空闲字节。
ASCU LIST Depending on the R flag, this field indicates the list of ASCUs (A1A2 or H1H2A1A2) either in error or within the session.
ASCU列表根据R标志，此字段表示ASCU列表（A1A2或H1H2A1A2）错误或会话内。
The SC (Session Close) command is used to close an existing MATIP session.
SC（会话关闭）命令用于关闭现有的MATIP会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Close Cause |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Close Cause |
+-+-+-+-+-+-+-+-+
Close Cause Indicates the reason for the session closure:
关闭原因指示会话关闭的原因：
0 0 0 0 0 0 0 0 : Normal Close
0 0 0 0 0：正常关闭
1 0 0 0 0 1 0 0 up to : Application dependent 1 1 1 1 1 1 1 1
1 0 0 0 0 1 0 0至：依赖于应用程序的1 1 1 1
Other values reserved.
保留其他值。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |0|0 0 0 0 0 0 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ID (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |0|0 0 0 0 0 0 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ID (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ID This field is optional and has a different length and format according to the value of HDR, PRES indicated during the session establishment.
ID此字段是可选的，根据会话建立期间指示的HDR、PRES值，具有不同的长度和格式。
+------------------------------+-------------------------------+
|HDR | PRES = P1024B and 3270 | PRES = P1024C |
+------------------------------+-------------------------------+
|00 |ID = 4 bytes H1-H2-A1-A2 | ID = 5 bytes H1-H2-A1-0x01-A2 |
+------------------------------+-------------------------------+
|01 |ID = 2 bytes A1-A2 | ID = 3 bytes A1-0x01-A2 |
+------------------------------+-------------------------------+
|10 |ID = 0 bytes | ID = 0 bytes |
+------------------------------+-------------------------------+
+------------------------------+-------------------------------+
|HDR | PRES = P1024B and 3270 | PRES = P1024C |
+------------------------------+-------------------------------+
|00 |ID = 4 bytes H1-H2-A1-A2 | ID = 5 bytes H1-H2-A1-0x01-A2 |
+------------------------------+-------------------------------+
|01 |ID = 2 bytes A1-A2 | ID = 3 bytes A1-0x01-A2 |
+------------------------------+-------------------------------+
|10 |ID = 0 bytes | ID = 0 bytes |
+------------------------------+-------------------------------+
H1, H2 value must match the value given in the SO command if MPX is different from 0.
如果MPX不同于0，则H1、H2值必须与SO命令中给出的值匹配。
Payload payload begins with the terminal identification: - One byte Terminal identifier (TA) in P1024B - Two bytes SID/DID Terminal identifier in P1024C.
有效负载以终端标识开始：-P1024B中的一字节终端标识符（TA）-P1024C中的两字节SID/DID终端标识符。
There are 3 control packets to open or close the session at the MATIP level.
有3个控制数据包用于在MATIP级别打开或关闭会话。
To be able to identify the session and before sending any data packet, a Session Open command is sent. It can be initiated by either side. In case of collision, the open session from the side having the lower IP address is ignored.
为了能够识别会话，在发送任何数据包之前，发送会话打开命令。它可以由任何一方启动。如果发生冲突，则忽略具有较低IP地址的一侧的打开会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 1 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 1|0| CD | STYP |0 0 0 0| RFU |MPX|HDR|0 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| H1 | H2 | RFU |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow ID(opt)|
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 1 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 1|0| CD | STYP |0 0 0 0| RFU |MPX|HDR|0 0 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| H1 | H2 | RFU |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow ID(opt)|
+-+-+-+-+-+-+-+-+
RFU Reserved for future use. Must be set to zero.
RFU保留供将来使用。必须设置为零。
CD This field specifies the Coding, as defined in section 8.1.1.1.
CD该字段指定第8.1.1.1节中定义的编码。
STYP This is the traffic subtype (type being Type A). 0010 : TYPE A IATA Host to Host 1000 : SITA Host to Host
STYP这是流量子类型（类型为A型）。0010:A型IATA主机对主机1000:SITA主机对主机
MPX This flag specifies the multiplexing used within the MATIP session in TYPE A SITA host to host. Possible values are:
MPX此标志指定在SITA主机对主机类型的MATIP会话中使用的多路复用。可能的值为：
00 : irrelevant 01 : multiple flow inside the TCP connection 10 : single flow inside the TCP connection
00:01:TCP连接内的多个流10:TCP连接内的单个流
HDR This field specifies which part of the airline's specific address is placed ahead of the message text transmitted over the session. Possible values are:
HDR此字段指定航空公司特定地址的哪一部分位于会话中传输的消息文本之前。可能的值为：
00 : used in TYPE A SITA Host to Host Header = H1+H2+Flow ID
01 : used in TYPE A SITA Host to Host Header = Flow ID
10 : No Header (default for IATA host to Host)
11 : Not used
00 : used in TYPE A SITA Host to Host Header = H1+H2+Flow ID
01 : used in TYPE A SITA Host to Host Header = Flow ID
10 : No Header (default for IATA host to Host)
11 : Not used
The MPX and HDR must be coherent. When flow are multiplexed, the data must contain the flow identification. The table below summarizes the possible combinations:
MPX和HDR必须一致。当流被多路复用时，数据必须包含流标识。下表总结了可能的组合：
+---------------------+
| MPX | 01 | 10 |
+---------------------+
| HDR | | |
| 00 | Y | Y |
| 01 | Y | Y |
| 10 | N | Y |
+---------------------+
+---------------------+
| MPX | 01 | 10 |
+---------------------+
| HDR | | |
| 00 | Y | Y |
| 01 | Y | Y |
| 10 | N | Y |
+---------------------+
H1 H2 These fields can be used to identify the session. When this field is not used, it must be set to 0. If HDR=00, H1H2 in data packet must have the same value as set in SO command.
H1 H2这些字段可用于标识会话。不使用此字段时，必须将其设置为0。如果HDR=00，数据包中的H1H2必须与SO命令中设置的值相同。
Flow ID This field is optional and indicates the Flow ID (range 3F - 4F Hex).
流量ID此字段为可选字段，表示流量ID（范围3F-4F十六进制）。
The OC (Open Confirm) command is a response to an SO (Session Open) command and is used to either refuse the session or accept it.
OC（打开确认）命令是对SO（会话打开）命令的响应，用于拒绝会话或接受会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| cause |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| cause |
+-+-+-+-+-+-+-+-+
Cause This field indicates the reason for the MATIP session refusal
原因此字段指示MATIP会话拒绝的原因
0 0 0 0 0 0 0 1 : No Traffic Type matching between Sender & Recipient 0 0 0 0 0 0 1 0 : Information in SO header incoherent
0 0 0 0 1:发件人和收件人之间没有通信类型匹配0 0 0 0 1 0:SO标头中的信息不一致
1 0 0 0 0 1 0 0 up to : Application dependent 1 1 1 1 1 1 1 1
1 0 0 0 0 1 0 0至：依赖于应用程序的1 1 1 1
Other values reserved.
保留其他值。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+
The SC (Session Close) command is used to close an existing MATIP session.
SC（会话关闭）命令用于关闭现有的MATIP会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Close Cause |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Close Cause |
+-+-+-+-+-+-+-+-+
Close Cause Indicates the reason for the session closure:
关闭原因指示会话关闭的原因：
0 0 0 0 0 0 0 0 : Normal Close
0 0 0 0 0：正常关闭
1 0 0 0 0 1 0 0 up to : Application dependent 1 1 1 1 1 1 1 1
1 0 0 0 0 1 0 0至：依赖于应用程序的1 1 1 1
Other values reserved
保留其他值
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |0|0 0 0 0 0 0 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ID (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |0|0 0 0 0 0 0 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ID (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ID This field is optional and has a different length and format according to the value of HDR indicated during the session establishment.
ID此字段是可选的，根据会话建立期间指示的HDR值，具有不同的长度和格式。
+-------------------------------+
|HDR | I.D. |
+-------------------------------+
|00 |ID = 3 bytes H1-H2 FLOW ID|
+-------------------------------+
|01 |ID = FLOW ID |
+-------------------------------+
|10 |ID nor present |
+-------------------------------+
+-------------------------------+
|HDR | I.D. |
+-------------------------------+
|00 |ID = 3 bytes H1-H2 FLOW ID|
+-------------------------------+
|01 |ID = FLOW ID |
+-------------------------------+
|10 |ID nor present |
+-------------------------------+
Payload packet The payload format is relevant to the MATIP layer. It is formatted according to the IATA host to host specifications and agreed bilaterally by the sender and the receiver.
有效载荷数据包有效载荷格式与MATIP层相关。它根据IATA主机对主机规范进行格式化，并经发送方和接收方双方同意。
There are 3 control packets used to open or close the session at the MATIP level for exchanging Type B data
有3个控制数据包用于在MATIP级别打开或关闭会话，以交换类型B数据
Before sending any data packets, it is recommended to let the systems establishing a session check that they are indeed able to communicate (i.e., Both systems agree on the characteristics of the traffic that will cross the connection). For this purpose, a two way handshake, using the Session commands defined hereafter, is performed immediately after the establishment of the TCP level connection. Either side can initiate this procedure. In case of collision, the open session from the side having the lower IP address is ignored.
在发送任何数据包之前，建议让建立会话的系统检查它们是否确实能够通信（即，两个系统都同意将通过连接的流量的特征）。为此，在建立TCP级连接后，立即使用下文定义的会话命令执行双向握手。任何一方都可以启动此程序。如果发生冲突，则忽略具有较低IP地址的一侧的打开会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 1 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0| C D | PROTEC| BFLAG | Sender HLD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recipient HLD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 1 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0| C D | PROTEC| BFLAG | Sender HLD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recipient HLD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length This field indicates the number of bytes of the whole command, header included. The only possible values are equal to 6 bytes or 10 bytes.
长度此字段指示整个命令（包括标头）的字节数。唯一可能的值等于6字节或10字节。
CD This field specifies the Coding, as defined in section 8.1.1.1.
CD该字段指定第8.1.1.1节中定义的编码。
PROTEC Identifies the end to end Messaging Responsibility Transfer protocol used. 0010: BATAP All other values available.
PROTEC识别所使用的端到端消息传递责任传输协议。0010:BATAP所有其他可用值。
BFLAG (X means `do not care'
BFLAG（X表示“不在乎”
X X 0 0 means that the fields `Sender HLD, Recipient HLD' do not exist in this packet. In this case, the exact length of the packet is 6 Bytes.
X 0 0表示“发件人HLD，收件人HLD”字段在此数据包中不存在。在这种情况下，数据包的确切长度是6字节。
X X 1 0 means that the `Sender HLD, Recipient HLD' are carried respectively in bytes 9,10 and 11,12 of this packet. In this case, the exact length of the packet is 10 Bytes.
X X 1 0表示“发送方HLD，接收方HLD”分别在该数据包的字节9,10和11,12中携带。在这种情况下，数据包的确切长度是10字节。
0 0 X X means that the connection request has been transmitted from a host (Mainframe system)
0 X X表示连接请求已从主机（大型机系统）传输
0 1 X X means that the connection request has been transmitted from a gateway)
0 1 X X表示连接请求已从网关传输）
Sender HLD HLD of the Type B System sending the Session Open.
发送会话打开的B类系统的发件人HLD HLD。
Recipient HLD HLD of the Type B system to which session opening is destined.
会话打开目的地B类系统的收件人HLD HLD。
The OC (Open Confirm) command is a response to an SO (Session Open) command and is used to either refuse the session or accept it.
OC（打开确认）命令是对SO（会话打开）命令的响应，用于拒绝会话或接受会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|1| Cause |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|1| Cause |
+-+-+-+-+-+-+-+-+
Length of this packet is 5 Bytes.
此数据包的长度为5字节。
Cause Indicates the cause of the rejection
原因表示拒绝的原因
0 0 0 0 0 1 : No Traffic Type matching between Sender & Recipient 0 0 0 0 1 0 : Information in SO header incoherent 0 0 0 0 1 1 : Type of Protection mechanism are different 0 0 0 1 0 0 up to 1 1 1 1 1 1 : R.F.U
0 0 0 0 1:发件人和收件人之间没有通信类型匹配0 0 0 0 1 0:SO标头中的信息不一致0 0 0 0 1 1:保护机制的类型不同0 0 1 0 0到1 1 1:R.F.U
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|
+-+-+-+-+-+-+-+-+
Length of this packet is 5 Bytes.
此数据包的长度为5字节。
The SC (Session Close) command is used to close an existing MATIP session.
SC（会话关闭）命令用于关闭现有的MATIP会话。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Close Cause |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |1|1 1 1 1 1 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Close Cause |
+-+-+-+-+-+-+-+-+
Close Cause Indicates the reason for the session closure: 0 0 0 0 0 0 0 0 : Normal Close 1 0 0 0 0 1 0 0 up to 1 1 1 1 1 1 1 1 : Application dependent
关闭原因表示会话关闭的原因：0 0 0 0 0 0 0：正常关闭1 0 0 0 0 0 0 0 1 0 0 0到1 1 1 1 1 1 1：依赖于应用程序
Other values reserved
保留其他值
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |0|0 0 0 0 0 0 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|0|0|0| Ver |0|0 0 0 0 0 0 0| length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Payload |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length This field indicates the number of bytes of the whole packet, header included.
长度此字段指示整个数据包（包括报头）的字节数。
Payload Type B message formatted according to the IATA standard and conforming to the rules of the accessed TYPE B service
根据IATA标准格式化并符合所访问B类服务规则的有效负载B类消息
The security is a very sensitive point for airline industry. Security for the MATIP users can take place at different levels:
对于航空业来说，安全是一个非常敏感的问题。MATIP用户的安全性可以在不同的级别进行：
The ASCU must be defined to enable the session with the host application. The control can be achieved in two ways: either the ASCU address (H1 H2 A1 A2) is defined at the application level by the means of a static configuration, or the ASCU is identified by a User ID / password. In most cases, the User ID and Password are verified by a dedicated software running in the central host. But they can also be checked by the application itself.
必须定义ASCU以启用与主机应用程序的会话。控制可以通过两种方式实现：ASCU地址（H1 H2 A1 A2）通过静态配置在应用程序级别定义，或者ASCU通过用户ID/密码标识。在大多数情况下，用户ID和密码由中央主机上运行的专用软件进行验证。但它们也可以由应用程序本身进行检查。
The MATIP sessions being transported over TCP/IP, It can go through a firewall. Depending on the firewall level, the control can be performed at network (IP addresses) or TCP application layer.
通过TCP/IP传输MATIP会话时，它可以通过防火墙。根据防火墙级别，可以在网络（IP地址）或TCP应用层执行控制。
For higher level of security all compliant implementations MAY implement IPSEC ESP for securing control packets. Replay protection, the compulsory cipher suite for IPSEC ESP, and NULL encryption MAY be implemented. Optionally, IPSEC AH MAY also be supported. All compliant implementations MAY also implement IPSEC ESP for protection of data packets. Replay prevention and integrity protection using IPSEC ESP mandated cipher suit MAY be implemented. NULL encryption also MAY be supported. Other IPSEC ESP required ciphers MAY also be supported.
为了获得更高级别的安全性，所有兼容的实现都可以实现IPSEC ESP以保护控制数据包。可以实现重播保护、IPSEC ESP的强制密码套件和空加密。或者，也可以支持IPSEC AH。所有兼容的实现也可以实现IPSEC ESP以保护数据包。可以使用IPSEC ESP强制密码套件实施重播预防和完整性保护。也可能支持空加密。还可能支持其他IPSEC ESP所需的密码。
Alain Robert S.I.T.A. 18, rue Paul Lafargue 92904 PARIS LA DEFENSE 10 FRANCE
阿兰·罗伯特S.I.T.A.法国巴黎国防10号保罗·拉法格街18号92904
Phone: 33 1 46411491 Fax: 33 1 46411277 EMail: arobert@par1.par.sita.int
电话：33 1 46411491传真：33 1 46411277电子邮件：arobert@par1.par.sita.int
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。