Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP (RFC2351)
Original Publication Date: 1998-May-01
Included in the Prior Art Database: 2019-Feb-15
Internet Society Requests For Comment (RFCs)
This memo specifies a protocol for the encapsulation of the airline specific protocol over IP. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Network Working Group A. Robert Request for Comments: 2351 SITA Category: Informational May 1998
Mapping of Airline Reservation, Ticketing, and Messaging Traffic over 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 (C) The Internet Society (1998). All Rights Reserved.
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.
This memo specifies a protocol for the encapsulation of the airline specific protocol over 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
Robert Informational [Page 1]
RFC 2351 MATIP May 1998
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
The airline community has been using a worldwide data network for over 40 years, with two main types of 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.
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.
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.