ATN

Doc 9896
Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocols
Approved by the Secretary General and published under his authority
First Edition 2010
International Civil Aviation Organization
Doc 9896
Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocols
Approved by the Secretary General and published under his authority
First Edition 2010
International Civil Aviation Organization
Published in separate English, French, Russian and Spanish editions by the INTERNATIONAL CIVIL AVIATION ORGANIZATION 999 University Street, Montral, Quebec, Canada H3C 5H7
For ordering information and for a complete listing of sales agents and booksellers, please go to the ICAO website at www.icao.int
First edition 2010
Doc 9896, Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocols Order Number: 9896 ISBN 978-92-9231-439-2
ICAO 2010 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, without prior permission in writing from the International Civil Aviation Organization.
AMENDMENTS
Amendments are announced in the supplements to the Catalogue of ICAO Publications; the Catalogue and its supplements are available on the ICAO website at www.icao.int. The space below is provided to keep a record of such amendments.
RECORD OF AMENDMENTS AND CORRIGENDA AMENDMENTS No. Date Entered by No. Date CORRIGENDA Entered by
(iii)
FOREWORD
This document defines the data communications protocols and services to be used for implementing the International Civil Aviation Organization (ICAO) aeronautical telecommunication network (ATN) using the Internet protocol suite (IPS). The material contained in this document supplements ICAO Standards and Recommended Practices (SARPs) as contained in Annex 10 Aeronautical Telecommunications, Volume III, Part I, Chapter 3. Editorial practices in this document are as follows: The detailed technical specifications in this document that include the operative verb shall are essential to be implemented to secure proper operation of the ATN. The detailed technical specifications in this document that include the operative verb should are recommended for implementation in the ATN. However, particular implementations may not require this specification to be implemented. The detailed technical specifications in this document that include the operative verb may are optional. The use or non use of optional items shall not prevent interoperability between ATN/IPS nodes. This manual is divided into the following parts: Part I Detailed Technical Specifications: This part contains a general description of ATN/IPS. It covers the network, transport and security requirements for the ATN/IPS. Part II Internet Protocol Suite (IPS) Applications: This part contains a description of applications supported by the ATN/IPS. It includes convergence mechanisms and application services that allow legacy ATN/open system interconnection (OSI) applications to operate over the ATN/IPS transport layer. Part III Guidance Material: This part contains guidance material on ATN/IPS communications including information on architecture, as well as general information to support the implementation of ATN/IPS.
______________________
(v)
TABLE OF CONTENTS
Page Abbreviations and Terms ............................................................................................................................... PART I. DETAILED TECHNICAL SPECIFICATIONS I-1-1 I-1-1 I-2-1 I-2-1 I-2-2 I-2-2 I-2-4 I-2-5 I-2-7 I-APP-1 (ix)
Chapter 1. Introduction ................................................................................................................................ 1.1 General overview ........................................................................................................................... Chapter 2. 2.1 2.2 2.3 2.4 2.5 2.6 Requirements ............................................................................................................................. ATN/IPS administration .................................................................................................................. Link layer requirements .................................................................................................................. Internet layer requirements............................................................................................................. Transport layer requirements ......................................................................................................... Security requirements..................................................................................................................... Performance ................................................................................................................................... Autonomous system (AS) numbering plan .......................................................................
Appendix to Part I. PART II. Chapter 1. 1.1 1.2 1.3 1.4 1.5 1.6 PART III. Chapter 1. 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9
INTERNET PROTOCOL SUITE (IPS) APPLICATIONS Introduction ................................................................................................................................ Objective ........................................................................................................................................ Legacy ATN applications ................................................................................................................ Ground applications........................................................................................................................ Air-ground applications ................................................................................................................... Transport layer ............................................................................................................................... Dialogue service (DS) state tables ................................................................................................. GUIDANCE MATERIAL Introduction ................................................................................................................................ General overview ........................................................................................................................... Background .................................................................................................................................... General guidance ........................................................................................................................... Protocol stack ................................................................................................................................. Quality of Service (QoS) ................................................................................................................. Mobility guidance ............................................................................................................................ Security guidance ........................................................................................................................... Voice-over Internet protocol (VoIP) ................................................................................................ IPS implementations....................................................................................................................... Reference documents .................................................................................................... ______________________ III-1-1 III-1-1 III-1-2 III-1-2 III-1-7 III-1-15 III-1-19 III-1-22 III-1-29 III-1-31 III-APP-1 II-1-1 II-1-1 II-1-1 II-1-1 II-1-2 II-1-21 II-1-27
Appendix to Part III.
(vii)
ABBREVIATIONS AND TERMS
The abbreviations used in this manual are defined as follows: AAC AF AH AIDC AINSC AMHS ANSP AOC AS ATC ATM ATN ATS ATSC ATSMHS ATSU BGP CN CRL DiffServ ECC ECP EF ESP FIR FMTP HA HC HMAC IANA ICMP ICV IETF IKEv2 IP IPS IPsec IPv4 IPv6 ISO LIR LM MM MN Aeronautical administrative communications Assured forwarding Authentication header ATS interfacility data communications Aeronautical industry service communication ATS message handling system Air navigation service provider Aeronautical operational communications Autonomous system Air traffic control Air traffic management Aeronautical telecommunication network Air traffic services Air traffic services communication ATS message handling services ATS unit Border gateway protocol Correspondent node Certificate revocation list Differentiated services Elliptic curve cryptography Encryption control protocol Expedited forwarding Encapsulating security payload Flight information region Flight management transfer protocol Home agent Handover control Hash message authentication code Internet assigned numbers authority Internet control message protocol Integrity check value Internet Engineering Task Force Internet key exchange version 2 Internet protocol Internet protocol suite Internet protocol security Internet protocol version 4 Internet protocol version 6 International Organization for Standardization Local Internet registry Location management Mobility management Mobile node
(ix)
(x) MoA MSP MTU OLDI OSI PHB PPP QoS RFC RIR ROHC RTP SARPs TCP TLS TOS UDP Memorandum of Agreement Mobility service provider Maximum transmission unit Online data interchange Open system interconnection Per-hop behaviour Point-to-point protocol Quality of Service Request for comments Regional Internet registry Robust header compression Real time transport protocol Standards and Recommended Practices Transmission control protocol Transport layer security Type of service User datagram protocol
Manual on the ATN using IPS Standards and Protocols
The following definitions are consistent with Internet Engineering Task Force (IETF) terminology: Access network. A network that is characterized by a specific access technology. Administrative domain. An administrative entity in the ATN/IPS. An administrative domain can be an individual State, a group of States, an aeronautical industry organization (e.g. an air-ground service provider), or an air navigation service provider (ANSP) that manages ATN/IPS network resources and services. From a routing perspective, an administrative domain includes one or more autonomous systems. ATN/IPS internetwork. The ATN/IPS internetwork consists of IPS nodes and networks operating in a multinational environment. Autonomous system. A connected group of one or more IP prefixes, run by one or more network operators, which has a single, clearly defined routing policy. Global mobility. Global mobility is mobility across access networks. Handover control. The handover control (HC) function is used to provide the session continuity for the on-going session of the mobile node. Host. A host is a node that is not a router. A host is a computer connected to the ATN/IPS that provides end users with services. Host-based mobility management. A mobility management (MM) scheme in which MM signalling is performed by the mobile node. Inter-domain routing (exterior routing protocol). Protocols for exchanging routing information between autonomous systems. In some cases, they may be used between routers within an autonomous system, but they primarily deal with exchanging information between autonomous systems. Intra-domain routing (interior routing protocol). Protocols for exchanging routing information between routers within an autonomous system.
Abbreviations and terms IPS mobile node. An IPS node that uses the services of one or more mobility service providers (MSPs). Local mobility. Local mobility is network layer mobility within an access network.
(xi)
Location management. The location management (LM) function is used to keep track of the movement of a mobile node and to locate the mobile node for data delivery. Mobility service provider (MSP). A service provider that provides mobile IPv6 service (i.e. home agents), within the ATN/IPS. An MSP is an instance of an administrative domain (AD) which may be an air communications service provider (ACSP), air navigation service provider (ANSP), airline, airport authority, government organization, etc. Network-based mobility management. A mobility management (MM) scheme in which the MM signalling is performed by the network entities on behalf of the mobile node. Node. A device that implements IPv6. Router. A router is a node that forwards Internet protocol (IP) packets not explicitly addressed to itself. A router manages the relaying and routing of data while in transit from an originating end system to a destination end system.
______________________
Part I
Detailed Technical Specifications
Chapter 1 INTRODUCTION
1.1
GENERAL OVERVIEW
1.1.1 This manual contains the minimum communication standards and protocols that will enable implementation of an ICAO aeronautical telecommunication network (ATN) based on the Internet protocol suite (IPS), referred to as the ATN/IPS. The scope of this manual is on interoperability across administrative domains in the ATN/IPS internetwork, although the material in this manual may also be used within an administrative domain. Implementation of the ATN/IPS, including the standards and protocols included in this manual, will take place on the basis of regional air navigation agreements between ICAO Contracting States in accordance with Annex 10, Volume III, Part I, Chapter 3, 3.3.2. Planning and Implementation Regional Groups (PIRGs) coordinate such agreements. 1.1.2 The ATN/IPS protocol architecture is illustrated in Figure I-1-1. The ATN/IPS has adopted the same four-layer model as defined in Internet Society (ISOC) Internet standard STD003. Note. STD003 is a combination of Internet Engineering Task Force (IETF) RFC 1122 and RFC 1123. 1.1.3 This model has four abstraction layers called the link layer, the Internet or Internet protocol (IP) layer, the transport layer and the application layer. 1.1.4 As depicted in Figure I-1-1, this manual does not adopt any specific link layer protocol as this is a local or bi-lateral issue which does not affect overall interoperability. 1.1.5 This manual adopts the Internet protocol version 6 (IPv6) for internet layer interoperability. Implementation of IPv4 in ground networks, for transition to IPv6 (or as a permanent network) is not addressed in this manual. IPv6 is to be implemented in air-ground networks. The border gateway protocol 4 (BGP-4) with extensions is adopted for inter-domain routing. 1.1.6 The transmission control protocol (TCP) and user datagram protocol (UDP) are adopted for connection-oriented and connectionless services at the transport layer. 1.1.7 Part II of this document includes convergence mechanisms and application services that allow legacy ATN/open system interconnection (OSI) applications to operate over the ATN/IPS transport layer. 1.1.8 Part III of this document includes guidance material to support ATN/IPS implementation.
I-1-1
I-1-2
Application layer OSI/IPS convergence
Application layer OSI/IPS convergence
Peer-to-peer connections
Transport layer (TCP, UDP) Transport layer (TCP, UDP)
Inter-domain router
Internet layer (IP v6) Internet layer (IP v6, BGP-4+)
Inter-domain router
Internet layer (IP v6, BGP4+) Internet layer (IP v6)
Link layer
Link layer
Link layer
Link layer
Local or intra-domain subnetwork Inter-domain subnetwork
Local or intra-domain subnetwork
Figure I-1-1.
ATN/IPS protocol architecture
______________________
Chapter 2 REQUIREMENTS
2.1
ATN/IPS ADMINISTRATION
The ATN/IPS 2.1.1 The ATN/IPS internetwork consists of IPS nodes and networks operating in a multinational environment in support of air traffic services communication (ATSC) as well as aeronautical industry service communication (AINSC), such as aeronautical administrative communications (AAC) and aeronautical operational communications (AOC). 2.1.2 In this manual, an IPS node is a device that implements IPv6. There are two types of IPS nodes: an IPS router is an IPS node that forwards Internet protocol (IP) packets not explicitly addressed to itself; and an IPS host is an IPS node that is not a router. 2.1.3 From an administrative perspective, the ATN/IPS internetwork consists of a number of interconnected administrative domains. An administrative domain can be an individual State, a group of States (e.g. an ICAO region), an air communications service provider (ACSP), an air navigation service provider (ANSP), or any other organizational entity that manages ATN/IPS network resources and services. 2.1.4 Each administrative domain participating in the ATN/IPS internetwork shall operate one or more IPS routers which execute the inter-domain routing protocol specified in this manual. 2.1.5 From a routing perspective, inter-domain routing protocols are used to exchange routing information between autonomous systems (AS), where an AS is a connected group of one or more IP address prefixes. The routing information exchanged includes IP address prefixes of differing lengths. For example, an IP address prefix exchanged between ICAO regions may have a shorter length than an IP address prefix exchanged between individual States within a particular region. 2.1.6 Administrative domains should coordinate their policy for carrying transit traffic with their counterparts.
ATN/IPS mobility 2.1.7 ATN/IPS mobility is based on IPv6 mobility standards, operated by mobility service providers (MSP).
Note. An MSP in the ATN/IPS is an instance of an administrative domain which may be an ACSP, ANSP, airline, airport authority, government or other aviation organization. 2.1.8 ATN/IPS MSPs shall operate one or more home agents (HAs).
I-2-1
I-2-2 2.2
Manual on the ATN using IPS Standards and Protocols LINK LAYER REQUIREMENTS
The specification of the link layer characteristics for an IPS node is a local issue.
2.3
INTERNET LAYER REQUIREMENTS
General IPv6 internetworking 2.3.1 2.3.2 RFC 1981. 2.3.3 IPS nodes shall implement IPv6 as specified in RFC 2460. IPS nodes shall implement IPv6 maximum transmission unit (MTU) path discovery as specified in
IPS nodes shall set the flow label field of the IPv6 header to zero, as it is not used in the ATN/IPS.
Mobile IPv6 2.3.4 2.3.5 IPS mobile nodes (MNs) shall implement mobile IPv6 as specified in RFC 3775. IPS HAs shall implement mobile IPv6 as specified in RFC 3775.
2.3.6 IPS MNs and HAs may implement extensions to mobile IPv6 to enable support for network mobility as specified in RFC 3963. 2.3.7 IPS nodes that implement mobile IPv6 route optimization should allow route optimization to be administratively enabled or disabled, with the default being disabled. Note. The use of mobile IPv6 route optimization is not mandated by this specification until further standard RFCs have been developed by the IETF.
Network addressing 2.3.8 2.3.9 IPS nodes shall implement IPv6 addressing architecture as specified in RFC 4291. IPS nodes shall use globally scoped IPv6 addresses when communicating over the ATN/IPS.
2.3.10 Administrative domains shall obtain IPv6 address prefix assignments from their local Internet registry (LIR) or regional Internet registry (RIR). 2.3.11 MSPs shall obtain a /32 IPv6 address prefix assignment for the exclusive use of IPS mobile nodes or mobile networks.
Part I Detailed Technical Specifications Chapter 2 Requirements 2.3.12 MSPs should use the IPv6 address structure for aircraft assignments (see Figure I-2-1).
32 bits Mobility service provider RIR/LIR 24 bits ICAO aircraft address 8 bits Subnet ID 64 bits Interface ID
I-2-3
Figure I-2-1 Note 1. Under this structure, each aircraft constitutes a /56 IPv6 end site, which is based on the ICAO 24-bit aircraft address as defined in Annex 10, Volume III, Part I, Appendix to Chapter 9. Note 2. For onboard services (ATS, AOC, AAC, etc.), an aircraft may have either multiple subnets interconnected to a mobile router, multiple MSPs or a combination of both. 2.3.13 MSPs shall advertise their /32 aggregate prefix to the ATN/IPS.
Inter-domain routing Note 1. Inter-domain routing protocols are used to exchange routing information among AS. Note 2. For routing purposes, an AS has a unique identifier called an AS number. Note 3. A single administrative domain may be responsible for the management of several AS. Note 4. The routing protocol within an AS is a local matter determined by the managing organization. 2.3.14 RFC 4271. IPS routers which support inter-domain dynamic routing shall implement the BGP-4 as specified in
2.3.15 IPS routers which support inter-domain dynamic routing shall implement the BGP-4 multiprotocol extensions as specified in RFC 2858. 2.3.16 Administrative domains shall use AS numbers for ATN/IPS routers that implement BGP-4.
2.3.17 Administrative domains that use private AS numbers shall follow the AS numbering plan described in the Appendix to Part I of this document. Note. Administrative domains that require additional private AS numbers should coordinate through ICAO. 2.3.18 IPS routers which support inter-domain dynamic routing should authenticate routing information exchanges as specified in RFC 2385.
Error detection and reporting 2.3.19 IPS nodes shall implement Internet Control Message Protocol (ICMPv6) as specified in RFC 4443.
I-2-4
Manual on the ATN using IPS Standards and Protocols Quality of Service (QoS)
2.3.20 Administrative domains shall make use of differentiated services (DiffServ) as specified in RFC 2475 as a means to provide Quality of Service (QoS) to ATN/IPS applications and services. 2.3.21 Administrative domains shall enable ATN/IPS DiffServ class of service to meet the operational and application requirements. 2.3.22 Administrative domains supporting voice-over IP services shall assign those services to the expedited forwarding (EF) per-hop behavior (PHB) as specified in RFC 3246. 2.3.23 Administrative domains shall assign ATN application traffic to the assured forwarding (AF) PHB as specified in RFC 2597. Note. Assured forwarding allows the ATN/IPS operator to provide assurance of delivery as long as the traffic does not exceed the subscribed rate. Excess traffic has a higher probability of being dropped if congestion occurs. 2.3.24 Administrative domains that apply measures of priority to the AF PHBs shall assign relative measures based on the ATN mapping of priorities defined in Annex 10, Volume III, Part I, Chapter 3, Table 3-1.
IP version transition 2.3.25 Administrative domains should use the dual IP layer mechanism for IPv6 to IPv4 compatibility as described in RFC 4213. Note. This provision ensures that ATN/IPS hosts also support IPv4 for backward compatibility with local IPv4 applications.
2.4
TRANSPORT LAYER REQUIREMENTS
Transmission control protocol (TCP) 2.4.1 2.4.2 IPS nodes shall implement the transmission control protocol (TCP) as specified in RFC 793. IPS nodes may implement TCP extensions for high performance as specified in RFC 1323.
User datagram protocol (UDP) 2.4.3 IPS hosts shall implement the user datagram protocol as specified in RFC 768.
Transport protocol port numbers 2.4.4 IPS nodes shall support and make use of the TCP and/or UDP port numbers defined in Part II, 2.1.1.2, 2.1.2.3 and 2.3.2 of this document.
Part I Detailed Technical Specifications Chapter 2 Requirements 2.5 SECURITY REQUIREMENTS
I-2-5
Note. The use of the following security requirements for communications in the ATN/IPS should be based on a system threat and vulnerability analysis. 2.5.1 This section defines IPS node security requirements and capabilities but does not impose their use for communications in the ATN/IPS.
Ground-ground security Note. IP layer security in the ground-ground ATN/IPS internetwork is implemented using Internet protocol security (IPsec) and the Internet key exchange version 2 (IKEv2) protocol.
Ground-ground IPsec/IKEv2 2.5.2 IPS nodes in the ground-ground environment shall comply with the security architecture for the Internet protocol as specified in RFC 4301. 2.5.3 IPS nodes in the ground-ground environment shall implement the IP encapsulating security payload (ESP) protocol as specified in RFC 4303. 2.5.4 IPS nodes in the ground-ground environment may implement the IP authentication header (AH) protocol as specified in RFC 4302. 2.5.5 IPS nodes in the ground-ground environment shall implement the Internet key exchange version (IKEv2) protocol as specified in RFC 4306. 2.5.6 IPS nodes in the ground-ground environment shall implement the cryptographic algorithm implementation requirements for the ESP and AH, if AH is implemented as specified in RFC 4835. 2.5.7 IPS nodes in the ground-ground environment shall implement the null encryption algorithm as specified in RFC 4835, but not the null authentication algorithm, when establishing Internet protocol security (IPsec) associations. 2.5.8 IPS nodes in the ground-ground environment shall implement the cryptographic algorithms for use in the IKEv2 as specified in RFC 4307, when negotiating algorithms for key exchange. 2.5.9 IPS nodes in the ground-ground environment should use the Internet X.509 public key infrastructure certificate and certificate revocation list (CRL) profile as specified in RFC 5280, when digital signatures are used as the IKEv2 authentication method. 2.5.10 IPS nodes in the ground-ground environment should use the Internet X.509 public key infrastructure ertificate policy and certificate practices framework as specified in RFC 3647, when digital signatures are used as the IKEv2 authentication method. Note. The Air Transport Association (ATA) Digital Security Working Group (DSWG) has developed a certificate policy (ATA Specification 42) for use in the aviation community. ATA Specification 42 includes certificate and CRL profiles that are suitable for aeronautical applications and interoperability with an aerospace industry public key infrastructure (PKI) bridge. These profiles provide greater specificity than, but do not conflict with, RFC 5280.
I-2-6
Manual on the ATN using IPS Standards and Protocols Air-ground security
Air-ground access network security 2.5.11 IPS mobile nodes shall implement the security provisions of the access network to enable access network security. Note. For example, the WiMAX, 3GPP, and 3GPP2 access networks have authentication and authorization provisions.
Air-ground IPsec/IKEv2 2.5.12 IPS nodes in the air-ground environment shall comply with the security architecture for the Internet protocol as specified in RFC 4301. 2.5.13 RFC 4303. IPS nodes in the air-ground environment shall implement the IP ESP protocol as specified in
2.5.14 IPS nodes in the air-ground environment shall implement AUTH_HMAC_SHA2_256-128 as the integrity algorithm for ESP authentication as specified in RFC 4868, when establishing IPsec security associations. 2.5.15 IPS nodes in the air-ground environment which implement encryption shall implement AES-GCM with an 8 octet integrity check value (ICV) and with a key length attribute of 128 bits for ESP encryption and authentication as specified in RFC 4106. 2.5.16 RFC 4306. 2.5.17 IPS nodes in the air-ground environment shall implement the IKEv2 protocol as specified in
IPS nodes in the air-ground environment shall implement IKEv2 with the following transforms: a) b) PRF_HMAC_SHA_256 as the pseudo-random function as specified in RFC 4868. 256-bit random encryption control protocol (ECP) group for Diffie-Hellman key exchange values as specified in RFC 4753. ECDSA with SHA-256 on the P-256 curve as the authentication method as specified in RFC 4754. AES-CBC with 128-bit keys as the IKEv2 encryption transforms as specified in RFC 3602. HMAC_SHA_256-128 as the IKEv2 integrity transform as specified in RFC 4868.
c)
d) e)
2.5.18 IPS nodes in the air-ground environment should use the Internet X.509 public key infrastructure certificate and certificate revocation list (CRL) profile as specified in RFC 5280, when digital signatures are used as the IKEv2 authentication method. 2.5.19 IPS nodes in the air-ground environment should use the Internet X.509 public key infrastructure certificate policy and certificate practices framework as specified in RFC 3647, when digital signatures are used as the IKEv2 authentication method.
Part I Detailed Technical Specifications Chapter 2 Requirements
I-2-7
Note. The Air Transport Association (ATA) Digital Security Working Group (DSWG) has developed a certificate policy (ATA Specification 42) for use in the aviation community. ATA Specification 42 includes certificate and CRL profiles that are suitable for aeronautical applications and interoperability with an aerospace industry PKI bridge. These profiles provide greater specificity than, but do not conflict with, RFC 5280. 2.5.20 IPS nodes in the air-ground environment, shall implement mobile IPv6 operation with IKEv2 and the revised IPsec architecture as specified in RFC 4877.
Air-ground transport layer security 2.5.21 IPS mobile nodes and correspondent nodes may implement the transport layer security (TLS) protocol as specified in RFC 5246. 2.5.22 IPS mobile nodes and correspondent nodes shall implement the TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA as specified in RFC 4492 when making use of TLS. cipher suite
Air-ground application layer security 2.5.23 IPS mobile nodes and correspondent nodes may implement application layer security at the IPS dialogue service boundary, which is specified in Part II, 1.4, of this document. 2.5.24 IPS mobile nodes and correspondent nodes shall append a keyed hashed message authentication code (HMAC) as specified in RFC 2104 using SHA-256 as the cryptographic hash function, when application layer security is used. 2.5.25 An HMAC tag truncated to 32 bits shall be computed over the user data concatenated with a 32-bit send sequence number for replay protection, when application layer security is used. 2.5.26 IKEv2 shall be used for key establishment as specified in 2.5.12 to 2.5.20, when application layer security is used.
2.6 2.6.1
PERFORMANCE
IPS nodes may implement RFC 2488 in order to improve performance over satellite links.
2.6.2 IPS nodes may implement the RObust header compression (ROHC) framework as specified in RFC 4995 in order to optimize bandwidth utilization. 2.6.3 If ROHC is supported, then the following ROHC profiles shall be supported as applicable: a) b) c) d) the ROHC profile for TCP/IP specified in RFC 4996; the ROHC profile for real time transport protocol (RTP)/UDP/ESP specified in RFC 3095; the IP-only ROHC profile specified in RFC 4843; and the ROHC over point-to-point protocol (PPP) profile specified in RFC 3241. ______________________
APPENDIX to Part I Autonomous System (AS) Numbering Plan

Note. This numbering plan covers ICAO Contracting States, non-Contracting States and Territories. ICAO region APAC APAC ESAF NACC NACC SAM NACC WACAF APAC NACC APAC NACC NACC WACAF NACC APAC SAM SAM ESAF SAM ESAF APAC WACAF ESAF APAC WACAF NACC WACAF NACC WACAF WACAF SAM APAC SAM WACAF APAC NACC WACAF NACC APAC WACAF APAC Country/organization/location Afghanistan American Samoa (United States) Angola Anguilla (United Kingdom) Antigua and Barbuda Argentina Aruba (Netherlands) Ascension and St. Helena (United Kingdom) Australia Bahamas Bangladesh Barbados Belize Benin Bermuda (United Kingdom) Bhutan Venezuela Bolivia Botswana Brazil British Indian Ocean Territory Brunei Darussalam Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands (United Kingdom) Central African Republic Chad Chile China Colombia Congo Cook Islands Costa Rica Cte d'Ivoire Cuba Democratic People's Republic of Korea Democratic Republic of the Congo Timor-Leste AS number 64512 64513 64514 64515 64516 64517 64518 64519 64520 64521 64522 64523 64524 64525 64526 64527 64528 64529 64530 64531 64532 64533 64534 64535 64536 64537 64538 64539 64540 64541 64542 64543 64544 64545 64546 64547 64548 64549 64550 64551 64552 64553
I-APP-1
I-APP-2
ICAO region ESAF NACC NACC APAC SAM MID NACC WACAF ESAF ESAF SAM NACC WACAF WACAF WACAF NACC APAC NACC WACAF WACAF SAM SAM NACC NACC APAC APAC APAC APAC MID MID EUR/NAT NACC APAC APAC MID ESAF MID APAC APAC MID ESAF APAC MID ESAF WACAF MID APAC ESAF ESAF APAC
Country/organization/location Djibouti Dominica Dominican Republic Easter Island (Chile) Ecuador Egypt El Salvador Equatorial Guinea Eritrea Ethiopia Falklands Islands (United Kingdom) French Antilles Gabon Gambia Ghana Grenada Guam (United States) Guatemala Guinea Guinea-Bissau Guyana French Guiana Haiti Honduras Hong Kong, China Wallis and Futuna Islands (France) India Indonesia Iran, Islamic Republic of Iraq Israel Jamaica Japan Johnston Island (United States) Jordan Kenya Bahrain Kingman Reef (United States) Kiribati Kuwait Runion (France) Lao People's Democratic Republic Lebanon Lesotho Liberia Libyan Arab Jamahiriya Macao, China Madagascar Malawi Malaysia
AS number 64554 64555 64556 64557 64558 64559 64560 64561 64562 64563 64564 64565 64566 64567 64568 64569 64570 64571 64572 64573 64574 64575 64576 64577 64578 64579 64580 64581 64582 64583 64584 64585 64586 64587 64588 64589 64590 64591 64592 64593 64594 64595 64596 64597 64598 64599 64600 64601 64602 64603
Part I Detailed Technical Specifications Appendix Autonomous system (AS) numbering plan
I-APP-3
ICAO region APAC WACAF APAC APAC EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT MID EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT
Country/organization/location Maldives Mali Mariana Islands (United States) Marshall Islands Albania Armenia Austria Azerbaijan Belarus Belgium Bosnia and Herzegovina Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland France Georgia Germany Greece Hungary Iceland Ireland Italy Kazakhstan Kyrgyzstan Latvia Liechtenstein Lithuania Luxembourg The former Yugoslav Republic of Macedonia Malta Republic of Moldova Monaco Netherlands Norway Poland Portugal Romania Russian Federation Serbia Slovakia Slovenia Spain Sweden Tajikistan Switzerland The Holy See
AS number 64604 64605 64606 64607 64608 64612 64616 64620 64624 64628 64632 64636 64640 64644 64648 64652 64656 64660 64664 64668 64672 64676 64680 64684 64688 64692 64696 64700 64704 64706 64708 64712 64716 64720 64724 64728 64732 64736 64740 64744 64748 64752 64756 64760 64764 64768 64772 64776 64780 64782
I-APP-4
ICAO region EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT EUR/NAT WACAF ESAF NACC APAC APAC APAC NACC ESAF APAC ESAF APAC APAC NACC APAC APAC NACC WACAF WACAF APAC MID APAC APAC APAC SAM APAC SAM
Country/organization/location Turkey Turkmenistan Ukraine United Kingdom Uzbekistan Algeria Andorra Gibraltar (United Kingdom) Greenland (Denmark) Montenegro Morocco San Marino Tunisia Regional - Europe Regional - Europe EUROCONTROL EUROCONTROL EUROCONTROL EUROCONTROL EUROCONTROL EUROCONTROL EUROCONTROL EUROCONTROL Mauritania Mauritius Mexico Micronesia, Federated States of Midway (United States) Mongolia Montserrat (United Kingdom) Mozambique Myanmar Namibia Nauru Nepal Netherlands Antilles New Caledonia (France) New Zealand Nicaragua Niger Nigeria Niue (New Zealand) Oman Pakistan Palau Palestinian Territory, occupied Palmyra (United States) Panama Papua New Guinea Paraguay
AS number 64784 64788 64792 64796 64800 64804 64808 64812 64816 64820 64824 64828 64832 65108 65112 65208 65212 65216 65220 65224 65228 65232 65236 65237 65238 65239 65240 65241 65242 65243 65244 65245 65246 65247 65248 65249 65250 65251 65252 65253 65254 65255 65256 65257 65258 65259 65260 65261 65262 65263
Part I Detailed Technical Specifications Appendix Autonomous system (AS) numbering plan
I-APP-5
ICAO region SAM APAC APAC APAC NACC MID APAC APAC ESAF NACC NACC NACC APAC WACAF MID WACAF ESAF WACAF APAC APAC ESAF ESAF APAC MID SAM ESAF MID APAC WACAF APAC NACC NACC APAC ESAF ESAF MID ESAF NACC SAM APAC APAC NACC NACC APAC MID ESAF ESAF
Country/organization/location Peru Philippines Pitcairn Island (United Kingdom) French Polynesia Puerto Rico (United States) Qatar Republic of Korea Fiji Rwanda Saint Kitts and Nevis Saint Lucia Saint Vincent and the Grenadines Samoa Sao Tome and Principe Saudi Arabia Senegal Seychelles Sierra Leone Singapore Solomon Islands Somalia South Africa Sri Lanka Sudan Suriname Swaziland Syrian Arab Republic Thailand Togo Tonga Trinidad and Tobago Turks and Caicos Islands (United Kingdom) Tuvalu Uganda Comoros United Arab Emirates United Republic of Tanzania United States Uruguay Vanuatu Viet Nam British Virgin Islands (United Kingdom) Virgin Islands (United States) Wake Island (United States) Western Sahara Yemen Zambia Zimbabwe ______________________
AS number 65264 65265 65266 65267 65268 65269 65270 65271 65272 65273 65274 65275 65276 65277 65278 65279 65280 65281 65282 65283 65284 65285 65286 65287 65288 65289 65290 65291 65292 65293 65294 65295 65296 65297 65298 65299 65300 65301 65302 65303 65304 65305 65306 65307 65308 65309 65310 65311
Part II
Internet Protocol Suite (IPS) Applications
Chapter 1 INTRODUCTION
1.1
OBJECTIVE
Note. This part describes how legacy ATN applications can make use of the ATN/IPS.
1.2
LEGACY ATN APPLICATIONS
Note. Legacy ATN applications are defined in the Manual of Technical Provisions for the Aeronautical Telecommunication Network (ATN) (Doc 9705) and/or the Manual on Detailed Technical Specifications for the Aeronautical Telecommunication Network (ATN) using ISO/OSI standards and protocols (Doc 9880) (in preparation). The ATN applications described in Doc 9705 and Doc 9880 specify the use of the ATN/OSI layers for communication services. This chapter describes how those applications make use of the ATN/IPS with minimal impact on the applications themselves.
1.3
GROUND APPLICATIONS
ATS message handling services (ATSMHS) Note 1. The ATSMHS application aims to provide generic message services over the ATN. Note 2. IPS hosts that support the ATSMHS application shall comply with Doc 9880, Part IIB. 1.3.1 To operate ATSMHS over ATN/IPS, IPS hosts shall: a) b) make use of RFC 2126 to directly provide TCP/IPv6 interface; or make use of RFC 1006 to provide a TCP/IPv4 interface combined with IPv4/IPv6 protocol translation device(s).
1.3.2 IPS hosts that support the ATSMHS application shall make use of TCP port number 102 as specified in RFC 1006 and RFC 2126.
ATS interfacility data communications (AIDC) Note 1. The AIDC application, as defined in the Manual of Air Traffic Services Data Link Applications (Doc 9694), exchanges information between ATS units (ATSUs) that support critical air traffic control (ATC) functions, such as the notification of flights approaching a flight information region (FIR) boundary, the coordination of boundary conditions and the transfer of control and communications authority.
II-1-1
II-1-2
Note 2. The AIDC, as defined in Doc 9880, Part IIA, is currently not planned for implementation in the ATN/IPS environment. 1.3.3 IPS hosts in the ATN that support the AIDC application exchanges may make use of the equivalent operational application described in the EUROCONTROL specifications for On-Line Data Interchange (OLDI). 1.3.4 IPS hosts in the ATN that support the OLDI application shall make use of the EUROCONTROL specifications for the flight message transfer protocol to operate the application over IPv6. 1.3.5 IPS hosts in the ATN that support the EUROCONTROL flight message transfer protocol shall make use of TCP port number 8500.
1.4
AIR-GROUND APPLICATIONS
Dialogue service 1.4.1 The dialogue service (DS), as documented in Doc 9880, Part III, serves as an interface between the ATN applications and the ATN/OSI upper layer protocols via the control function. In order to minimize the impact on the ATN applications, a new dialogue service was developed to support application implementation over the ATN/IPS. This section specifies a replacement for the ATN/OSI DS interface to the upper layers, and is named the IPS DS. 1.4.2 Figure II-1-1. The IPS DS maps TCP/UDP primitives to the ATN application DS interface as depicted in
Application user
ATN-App ASE
IPS DS
TCP/UDP
Figure II-1-1.
ATN IPS upper layers diagram
1.4.3 Primitives from the ATN/OSI DS will be mapped as detailed in the following sections. This mapping is used as a substitute for the upper layer communications service (ULCS) specification in Doc 9880, Part III. 1.4.4 The aeronautical telecommunication network packet (ATNPKT) header format defined in 1.4.11 to 1.4.15 describes a dedicated format designed to accommodate the passing of ATN application data over the ATN/IPS. Either TCP or UDP may be used with the ATNPKT header format.
Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction Controller-pilot data link communications (CPDLC), automatic dependent surveillance (ADS) and flight information services (FIS)
II-1-3
1.4.5 IPS hosts that support ATN/OSI CPDLC, ADS and FIS applications shall use the IPS DS instead of the DS defined in Doc 9880.
Context management (CM) 1.4.6 IPS hosts that support the ATN CM application shall support extensions of its abstract syntax notation (ASN) as described in Part III, 1.4.39, of this document. Note 1. This is in order to allow passing the new IPS addressing information contained in the updated CM application abstract syntax notation one (ASN.1). Note 2. The CM application is also known as the data link initiation capability (DLIC) service. Note 3. It is expected that a later edition of Doc 9880 will include these extensions taking precedence over those specified in this document.
ATN/IPS dialogue service primitives Note. In order to retain commonality with the ULCS dialogue service primitives described in Doc 9880, the IPS DS uses the same primitive names. 1.4.7 IPS nodes that support the DS functionality shall exhibit the behaviour defined by the service primitives in Tables II-1-1 and II-1-2. Table II-1-1. Service D-START D-DATA Description This is a confirmed service used to establish the binding between the communicating DS-users. This unconfirmed service is used by a DS-user to send a message from that DS-user to the peer DS-user. This is a confirmed service used to provide the orderly unbinding between the communicating DS-users, such that any data in transit between the partners is delivered before the unbinding takes effect. This unconfirmed service can be invoked to abort the relationship between the communicating DS-users. Any data in transit between them may be lost. This unconfirmed service is used to indicate to the DS-user that the dialogue service provider has aborted the relationship with the peer DS-user. Any data in transit between the communicating DS-users may be lost. This unconfirmed service is used to send a single data item from one peer DS-user to another. Any problem in delivering the data item to the recipient will not be signalled to the originator. This service is specified in Table II-1-7. Dialogue service primitives
D-END
D-ABORT
D-P-ABORT
D-UNIT-DATA
II-1-4 Table II-1-2. Service D-START
Manual on the ATN using IPS Standards and Protocols Parameters of the dialogue service primitives Parameters Called peer ID Called sys-ID Called presentation address Calling peer ID Calling sys-ID Calling presentation address DS-user version number Security requirements Quality-of-Service Result Reject source User data User data Result User data Originator User data (no parameters)
D-DATA D-END
D-ABORT
D-P-ABORT
Note. The parameters of the DS primitives are mapped to either the IP header, a field of the transport protocol header, or as transport data in the ATNPKT format defined in 1.4.11 to 1.4.15.
Dialogue service definition
Sequence of primitives 1.4.8 IPS nodes that support the DS functionality shall allow peer communicating DS-users to: a) b) c) d) establish a dialogue; exchange user data; terminate a dialogue in an orderly or abnormal fashion; be informed of DS abnormal dialogue termination due to the underlying communication failure; and be consistent with the appropriate use of the corresponding service primitives.
e)
1.4.9 Either DS-user may send data at any time after the initial D-START exchange, by using the D-DATA service. Under normal circumstances, a dialogue is released by a DS-user invoking the D-END service. A dialogue is
Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction
II-1-5
abnormally released with the D-ABORT service. If the underlying service provider abnormally releases the dialogue, the DS-users are notified with the D-P-ABORT service indication. 1.4.10 It is only valid for the DS-user to issue and receive primitives for a dialogue in the sequence specified in Table II-1-3. The table cells containing Y indicate valid primitives which may follow the DS primitive column headings. For example, only D-START ind can follow the D-END cnf primitive.
Table II-1-3.
The DS primitive May be followed by the DS primitive Y 1 2 3 4 5 6 7 8 9 10 11 12 13 D-START req D-START cnf (accepted) D-START ind D-START rsp (accepted) D-DATA req D-DATA ind D-END req D-END cnf (accepted) D-END ind D-END rsp (accepted) D-ABORT req D-ABORT ind D-P-ABORT ind
Sequence of DS primitives for one dialogue at one DS-user

D-START req cnf ind rsp D-DATA req ind req D-END cnf ind rsp D-ABORT req ind D-P-ABORT ind
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
ATNPKT format 1.4.11 The purpose of the ATNPKT is to convey information between peer DS-users during the processing of a DS primitive. It is carried in the data part of the transport protocol (either TCP or UDP). It is used to convey parameters of the service primitives that cannot be mapped to existing IP or transport header fields. The ATNPKT will also convey information to indicate the DS protocol function (e.g. the type of DS primitive). 1.4.12 In order to provide the most efficient use of bandwidth, a variable length format is used. The variable length format will allow optimized processing of the DS primitive. This is an important issue when operating over narrow band or costly air-ground communication links. 1.4.13 The ATNPKT format contains two parts: a fixed part that is present regardless of the DS primitive; and a variable part for optional fields.
II-1-6
1.4.14 The presence of optional parameters is indicated by setting bits within the fixed part of the ATNPKT. These bits are referred to as presence flags and form the presence field. The position of an optional parameter in the variable part is determined by its position in the presence field. The ATNPKT format is shown in Figure II-1-2.
Fixed part 0 0 ATNPKT version DS primitive
8 App tech type more
16
Variable part 24
Presence flags 0 1 2 3 4 5 6 7 8 9 10 11
Figure II-1-2.
ATNPKT format
1.4.15 The optional parameter representation, in the variable part of the ATNPKT, will be determined by the parameter definition. Parameters of variable length will be represented in the LV format (i.e. length + value). Fixed length parameters will be represented by their value.
ATNPKT fields 1.4.16 ATNPKT field formats are described using the convention (<bits> /<provider> / <usage>) where: <bits> indicates the size in bits of the field value (excluding length for LV parameters); <provider> indicates whether the value is provided by the DS-user as a primitive parameter (external) or assigned by the DS-provider (internal); <usage> indicates whether or not the DS-user is to submit a value when invoking the corresponding primitive parameter (optional vs. mandatory).
Fixed part of ATNPKT ATNPKT version Note. The ATNPKT version indicates the version of the ATNPKT header. 1.4.17 The ATNPKT version shall be set to 1 and have a format of 4 bits / internal / mandatory. Note 1. The ATNPKT version is a number that will increment for any subsequent modifications to the ATNPKT. Note 2. Reserving 4 bits will allow for up to 15 versions. Note 3. This field is not exposed at the DS-users level; it will be set by the DS-provider. DS primitive Note. The DS primitive field is set by the DS-provider to indicate the type of DS primitive in the packet.
II-1-7
1.4.18 The DS primitive field shall take one of the values specified below and have a format of 4 bits / internal / mandatory: Value 1 2 3 4 5 6 7 8 9 Assigned DS primitive D-START D-START cnf D-END D-END cnf D-DATA D-ABORT D-UNIT-DATA D-ACK D-KEEPALIVE
Note 1. Reserving 4 bits will give provision for up to 16 protocol elements, allowing up to 7 additional primitives to be defined. Note 2. The D-P-ABORT is not listed, as it is not sent end-to-end. Upon receipt of an abnormal event or expiration of an inactivity timer, a D-P-ABORT will be indicated to the DS-user.
Application technology type Note. The application technology type identifies the type of application information that is being carried. Other applications may also take advantage of the IPS infrastructure, e.g. FANS-1/A, ACARS, etc. 1.4.19 The application technology type shall be set to a value of b000 to indicate ATN/IPS DS and have a format of 3 bits / internal / optional. Note. The use or definition of other values is outside the scope of this manual. The more bit Note. The more bit will be used for segmentation and reassembly of UDP datagrams; it is part of the reliability mechanisms further described in 1.5.14. 1.4.20 The more bit shall be set to 0 to indicate a single or last segment; it shall be set to 1 to indicate the first or intermediate segment and have a format of 1 bit / internal / optional.
Presence field Note. The presence field is a series of presence flags (or bits) that indicate whether or not optional fields are present in the variable part of the ATNPKT. 1.4.21 The presence field shall have a format of 12 bits / internal / mandatory.
1.4.22 A presence flag shall be set to 0 to indicate the absence of an optional field; it shall be set to 1 to indicate the presence of an optional field.
II-1-8 1.4.23
Manual on the ATN using IPS Standards and Protocols The optional field details shall comply with Table II-1-4.
Table II-1-4.
Bit 0 1 2 3 4 5 6 7 Optional field Source ID Destination ID Sequence numbers Inactivity time Called peer ID Calling peer ID Content version Security indicator Size (in bits) 16 16 8 8 24 to 64 (+8) 24 to 64 (+8) 8 8
Presence field details

Format V V V V LV LV V V
2 1
Description DS connection identifier of the sender DS connection identifier of the recipient Sequence numbers (Ns, Nr) Inactivity timer value of the sender (in minutes) Called peer ID (provided by the local DS-user) Calling peer ID (provided by the local DS-user) Version of the application data carried Security requirements: 0 no security (default value) 1 Secured dialogue supporting key management 2 Secured dialogue 3 255 reserved
Quality of Service
ATSC routing class: 0 no traffic type policy preference 1 A 2 B 3 C 4 D 5 E 6 F 7 G 8 H 9 255 reserved
Result
Result of a request to initiate or terminate a dialogue: 0 accepted (default value) 1 rejected transient 2 rejected permanent 3 255 reserved
10
Originator
Originator of the abort: 0 user (default value) 1 provider 2 255 reserved
11
User data
UDP: 0 to 8 184 (+16) TCP: variable size (+16)
LV
User data (provided by the local DS-user)
II-1-9
Note 1. An optional field is present in the variable part when the corresponding bit is set in the presence field and has one of the following formats: V = value; or LV = length (1 or 2 byte(s)) + value Note 2. The additional bits required for the length part of LV parameters is indicated between brackets (in bits) in the third column of Table II-1-4. Note 3. Refer to 1.4.39 for details regarding the size of the user data parameter.
Variable parts of ATNPKT Note. The variable parts of the ATNPKT will be provided depending on the DS primitive being invoked and the current state of the application using the IPS DS. 1.4.24 The position of an optional field in the variable part of the ATNPKT shall match the relative position of its corresponding bit in the presence field (i.e. options are in the same order as the presence flags).
Source ID Note. The source ID identifies the DS connection at the sender side; it is part of the reliability mechanisms, further described in 1.5. 1.4.25 The source ID shall be present in the D-START and D-START cnf primitives, and also when D-ABORT is transmitted after D-START and before D-START cnf is received, and have a format of 16 bits / internal / optional.
Destination ID Note. The destination ID identifies the connection at recipient side; it is part of the reliability mechanisms, further described in 1.5. 1.4.26 The destination ID shall be present in the D-START cnf, D-DATA, D-END, D-END cnf, D-ABORT, D-ACK and D-KEEPALIVE primitives and have a format of 16 bits / internal / optional.
Sequence numbers Note. The sequence numbers field contains the sequence numbers to be included in the ATNPKT. This mechanism is used to detect the loss and the duplication of UDP datagrams; it allows implicit (i.e. the service confirmation) or explicit acknowledgement (D-ACK). This field is part of the reliability mechanisms, further described in 1.5. 1.4.27 The sequence numbers field shall be present in all DS primitives over UDP and have the format 8 bits / internal / mandatory as detailed in Figure II-1-3.
II-1-10
N(S)
N(R)
Figure II-1-3.
Sequence number format
N(S) - [015] sequence number of the ATNPKT sent. N(R) - [015] expected sequence number of the next ATNPKT to be received. Note. For D-ACK and D-KEEPALIVE, only the N(R) is meaningful on transmission. 1.4.28 When using sequence numbers with D-ACK and D-KEEPALIVE over UDP, the current value of the send sequence number for N(S) may be used without subsequently incrementing it after transmission.
Inactivity time Note. The inactivity time indicates the time value (in minutes) of the inactivity timer at the sender side. This field is used as part of the reliability mechanisms, further described in 1.5. 1.4.29 The inactivity time shall be optionally present in the D-START and D-START cnf primitives and have the format 8 bits / internal / optional. 1.4.30 When this parameter is not provided by the DS-user, the default value of 4 minutes shall be used as the inactivity timer by the source DS-provider.
Called peer ID Note. The called peer ID identifies the intended peer DS-user. 1.4.31 The called peer ID shall be either a 24-bit ICAO aircraft identifier or a 38 character ICAO facility designation and have the format 24 to 64 bits / external / optional.
Calling peer ID Note. The calling peer ID identifies the initiating peer DS-user. 1.4.32 The calling peer ID shall be either a 24-bit ICAO aircraft identifier or a 38 character ICAO facility designation and have the format 24 to 64 bits / external / optional.
Content version Note. The content version field is used to indicate the applications version number. 1.4.33 The content version shall be the version of the ASN.1 syntax used for the user data field and have the format 8 bits / external / optional.
Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction Security indicator
II-1-11
Note 1. The security indicator parameter is used to convey the level of security to be applied to the dialogue. In Doc 9880, this field is referred to as security requirements; it is renamed here since requirement is not really appropriate in this case. It is really an indication from the local DS-user of which kind of security procedure is to be used to set up a secure dialogue exchange. 1.4.34 The security indicator parameter shall be one of the following values and have a format of 8 bits / external / optional: Value 0 1 2 3 255 Security level No security (default value) Secured dialogue supporting key management Secured dialogue Reserved
Note. The absence of this parameter by the DS-user results in the security level being set to the default value, i.e. no security.
Quality of Service Note. The Quality of Service (QoS) parameter is used to convey the DS-user QoS requirement which is a value corresponding to the ATSC routing class and/or residual error rate (RER). 1.4.35 The QoS parameter shall have the following values and a format of 8 bits / external / optional: 1. The DS-user-provided ATSC routing class as below: Value 0 1 2 3 4 5 6 7 8 9 255 ATSC routing class description No traffic type policy preference A B C D E F G H Reserved
II-1-12 2. The RER as defined below: Value 0 1 2
RER level Low Medium High
3. ATN application priority may be indicated by inserting differentiated service codepoint (DSCP) values in the IPv6 header as described in Part III, 1.5.9 and 1.5.10, of this document. Note. The priority is normally set by the network layer, so it is not necessary for the application to provide one. The network layer can discern the priority by the port number being used or IP address and set the differentiated service field accordingly. It should also be noted that the network management procedures may lead to packet re-marking, regardless of the initial application indications, to be consistent with local network-differentiated service definitions. 1.4.36 value. The UDP checksum may be activated for low or medium RER values and not activated for a high RER
Note. TCP checksums are always activated. The UDP checksums are activated by default. Result Note. The result is set by the destination DS-user in order to indicate whether or not the requested dialogue initiation or termination completed successfully. 1.4.37 The result shall have the format of 8 bits / external / mandatory and take one of the values below: Value 0 1 2 3 255 Originator Note. The originator indicates the source of a D-ABORT. 1.4.38 The originator shall take one of the values below and the format of 8 bit / external / optional: Value 0 1 2 255 Definition User (default) Provider Reserved Definition Accepted Rejected (transient) Rejected (permanent) Reserved
Note. When this parameter is not provided by the DS-user, the default value is assumed.
Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction User data Note. The user data contains the packed encoding rules (PER) encoded application data. 1.4.39 The user data shall have the format of UDP: 0 to 8 184, TCP: variable size / external / optional.
II-1-13
Note 1. The maximum user data size for a D-DATA service is the maximum UDP datagram size (8 192 bytes) reduced by the size of the ATNPKT header (8 bytes). For other service primitives, the maximum user data size needs to be adjusted based on the size of the fixed header part plus the size of the variable length parts for that particular service primitive. Note 2. The IPS DS will segment UDP datagrams with user data that exceeds 1 024 bytes, as described in 1.5.14, which will need to be reassembled by the receiver.
IPS DS parameter mapping Note. The IPS DS presents an identical interface of the ULCS to the ATN applications. As such, the parameters of the IPS DS are identical to those of the ULCS. However, there is a different mapping of the contents of those parameters. These modified mappings are summarized in Table II-1-5 and detailed for each primitive in Table II-1-7. Table II-1-5.
DS parameter visible to the DS-user Called peer ID IP header
IPS DS ULCS DS parameter mapping

Transport protocol header ATNPKT (See Table II-1-4) Called peer ID Comment This can be an ICAO 24-bit aircraft address or an ICAO facility designator (4 to 8 characters).
Called sys-ID
Destination port number
This is a registered port number assigned to each ATN application (see 1.5.4). IP address of the recipient ATN application.
Called presentation address Calling peer ID
Destination IP address Calling peer ID
This can be an ICAO 24-bit aircraft address or an ICAO facility designator (4 to 8 characters).
Calling sys-ID
Source port number
Using TCP, this port number is dynamically assigned by the transport protocol stack on the client side. With UDP, this port number typically has a static value which is the same as the destination port number.
Calling presentation address DS-user version number
Source IP address Content version
IP address of the originator of the ATN application. This is the applications version number.
II-1-14
DS parameter visible to the DS-user Security requirements IP header
Transport protocol header ATNPKT (See Table II-1-4) Security requirements 00 No security 01 Secured dialogue supporting key management 02 Secured dialogue 03 Reserved Comment
Quality of Service
Quality of Service
This parameter is to be transported only when provided as ATSC routing class; the RER and priority are not indicated end-toend but are optionally indicated to the IPS DS and used locally.
Result
Result
00 Accepted 01 Rejected (permanent) 02 Rejected (transient)
Reject source
00 Remote DS-user 01 Local DS-provider Provided locally in the confirmation primitive only; not transferred end-to-end.
Originator
Originator
0 User 1 Provider (default) 2-255 Reserved
User data
User data
This is the packet encoding rules (PER) encoded data provided by the application.
1.4.40 Table II-1-6:
The inclusion of optional ATNPKT parameters for each DS protocol message shall comply with
Table II-1-6.
ATNPKT parameters for DS protocol messages
(O = optional, M = mandatory, = precluded to use) (1) Source ID is present if D-ABORT is sent after D-START and before D-START cnf is received. (2) Destination ID is absent if D-ABORT is sent after D-START and before D-START cnf is received. (3) For segmented messages, this parameter is present only in the first segment. (4) For segmented messages, this parameter is present in all the segments.
D-UNITProtocol message Fixed part ATNPKT version DS primitive Application technology type M M M M M M M M M M M M M M M M M M M M M M M M M M M D-START D-START cnf D-DATA DATA D-END D-END cnf D-ABORT D-ACK DKEEPALIVE
II-1-15
D-UNITProtocol message More Presence flag Variable part Source ID Destination ID Sequence numbers Inactivity time Called peer ID Calling peer ID Content version Security indicator Quality of Service Result Originator User data M (4) M (4) O (3) O (3) O (3) O (3) O (3) O (3) O (4) M (4) M (4) M (4) O (3) O (3) O (3) M (3) O (4) M (4) M (4) M (4) M O O O O M M (4) M (4) O (4) M (4) M (4) M (3) O (4) (1) M (2) M O O M M D-START O M D-START cnf O M D-DATA O M M DATA D-END O M D-END cnf O M M M D-ABORT D-ACK
DKEEPALIVE
M M
Dialogue service primitives Note. In order to provide the services identified in 1.4.7, the primitives listed in Table II-1-7 are used. Each primitive may be either directly exposed to the DS-user (request/response primitives) or reported to the DS-user by the DS-provider (indication/confirmation primitives).
Table II-1-7. Interface primitive D-START req D-START ind D-START rsp D-START cnf
Dialogue service primitive details DS-user 3 3 3 DS-provider
Dialogue service description Request to initiate a dialogue with a peer DS-user Inform a local DS-user that a peer DS-user requested for a dialogue initiation Complete a pending dialogue initiation with either a positive or a negative response Inform a local DS-user that the peer DS-user completed the pending dialogue initiation with either a positive or a negative response Send a datagram from the local DS-user to a peer DS-user (the end-to-end delivery of the datagram is not guaranteed) Inform a local DS-user that a datagram is received from a peer DS-user
D-UNIT-DATA req D-UNIT-DATA ind
3 3
II-1-16
Interface primitive D-DATA req D-DATA ind D-END req D-END ind D-END rsp D-END cnf
Dialogue service description Send a datagram from the local DS-user to a peer DS-user over an established dialogue Inform a local DS-user that a datagram is received from a peer DS-user over an established dialogue Request to terminate a dialogue with a peer DS-user Inform a local DS-user that a peer DS-user requested a dialogue termination Complete a pending dialogue termination with either a positive or a negative response Inform a local DS-user that the peer DS-user completed the pending dialogue termination with either a positive or a negative response Request to abort a dialogue with a peer DS-user Inform a local DS-user that the peer DS-user requested to abort the dialogue Dialogue aborted by the DS-provider
DS-user 3
DS-provider
3 3 3 3
3 3 3 3
D-ABORT req D-ABORT ind D-P-ABORT ind
Dialogue service time-sequence diagrams 1.4.41 Figures II-1-4 to II-1-13 below illustrate the dialogue service protocol exchanges between source and destination DS-providers, including the ATNPKT user data part.
Dialogue service D-START request
D-START D-START indication
D-START cnf D-START response
D-START confirmation
Figure II-1-4.
D-START service
II-1-17
Dialogue service D-DATA request
D-DATA D-DATA indication
Figure II-1-5.
D-DATA service (TCP)
Dialogue service D-DATA request
D-DATA D-DATA indication
D-ACK D-ACK response
D-ACK confirmation
Figure II-1-6.
D-DATA service (UDP)
Note. Figure II-1-5 shows the D-DATA service over a TCP connection. Due to the nature of the connection, an ACK is not required. Figure II-1-6 shows the D-DATA service over UDP. In order to provide explicit acknowledgement of the receipt of the UDP packet, a D-ACK is returned by the receiver of the D-DATA ATNPKT.
II-1-18
Dialogue service D-END request
D-END D-END indication
D-END cnf D-END response
D-END confirmation
Figure II-1-7.
D-END service
Dialogue service D-ABORT request
D-ABORT D-ABORT indication
Figure II-1-8.
D-ABORT service
II-1-19
Dialogue service
D-P-ABORT indication
D-P-ABORT indication
Figure II-1-9.
D-P-ABORT service
Note. There is no ATNPKT format defined for the D-P-ABORT service, as it is a local indication to the DS-user.
Dialogue service
D-UNIT DATA request
D-UNIT-DATA D-UNIT-DATA indication
Figure II-1-10.
D-UNIT-DATA service (TCP)
II-1-20
Dialogue service D-UNIT-DATA request
D-UNIT-DATA D-UNIT-DATA indication
D-ACK D-ACK request
D-ACK indication
Figure II-1-11.
D-UNIT-DATA service (UDP)
Note. Figure II-1-10 shows the D-UNIT-DATA service over a TCP connection. Due to the nature of the connection, an ACK is not required. Figure II-1-11 shows the D-UNIT-DATA service over UDP. In order to provide explicit acknowledgement of the receipt of the UDP packet, a D-ACK is returned by the receiver of the D-UNIT-DATA ATNPKT.
Dialogue service
D-ACK request
D-ACK D-ACK indication
Figure II-1-12.
D-ACK service
II-1-21
Dialogue service D-KEEPALIVE request
D-KEEPALIVE D-KEEPALIVE indication
Figure II-1-13.
D-KEEPALIVE service
1.5
TRANSPORT LAYER
Overview 1.5.1 The IPS DS has been designed to allow a user to select either TCP or UDP for the transport protocol. For simplicity, port-related operations are not considered as primitives. 1.5.2 The transport layer primitives are given in Table II-1-8.
Table II-1-8.
Transport layer primitives used in the IPS DS Transport layer
Interface primitive OPEN CLOSE RECEIVE SEND
Description Connection establishment (referred as active on initiator side, passive on the other side) Connection termination (referred as active on initiator side, passive on the other side) Receive transport level datagram Send transport level datagram
TCP 3 3 3 3
UDP
3 3
II-1-22 1.5.3 primitives.
Manual on the ATN using IPS Standards and Protocols Table II-1-9 shows the mapping to be applied between the dialogue service and the transport layer
Table II-1-9.
Dialogue service Service Initialization
Transport layer IPS DS service mapping

Transport layer Interface primitive User data Protocol
Interface primitive
OPEN (passive) Dialogue establishment D-START D-START req OPEN (active) SEND D-START ind D-START rsp D-START cnf Connectionless data exchange D-UNIT-DATA D-UNIT-DATA req D-UNIT-DATA ind Connected-mode data exchange D-DATA D-DATA req D-DATA ind Orderly dialogue termination (user initiated) D-END D-END req D-END ind D-END rsp SEND RECEIVE SEND CLOSE (passive) D-END cnf RECEIVE CLOSE (active) Forced dialogue termination (user initiated) D-ABORT D-ABORT req SEND CLOSE (active) D-ABORT ind RECEIVE CLOSE (passive) Error-related dialogue termination (provider initiated) D-P-ABORT D-P-ABORT ind RECEIVE / SEND (failure) Unexpected CLOSE (passive) D-ABORT D-ABORT D-END cnf D-END D-END D-END cnf SEND RECEIVE D-DATA D-DATA SEND RECEIVE D-UNITDATA D-UNITDATA RECEIVE SEND RECEIVE D-START D-START D-START cnf D-START cnf
TCP
TCP TCP, UDP
UDP
TCP, UDP
TCP, UDP
TCP TCP, UDP TCP
TCP, UDP TCP TCP, UDP TCP
TCP, UDP TCP
Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction Port numbers
II-1-23
1.5.4 The following TCP and UDP port numbers shall be used when supporting legacy ATN applications over the ATN/IPS: 5910 5911 5912 5913 Context management Controller-pilot data link communications Flight information services Automatic dependent surveillance
Note. These port numbers are registered by the Internet Assigned Numbers Authority (IANA) at: http://www.iana.org/assignments/port-numbers
Providing dialogue service over UDP Note. UDP is mostly employed for applications requiring broadcast or multicast, but it might also be used for simple request-reply applications provided that some reliability is added at the highest levels. UDP does not guarantee the end-to-end service delivery of the datagrams. For this reason, additional mechanisms are implemented in the IPS DS to address UDP limitations, basically the truncation, loss, or duplication of UDP datagrams. These mechanisms are specified in the following paragraphs. 1.5.5 In order to add some reliability when acting over UDP, the DS-provider shall implement the mechanisms as described in Table II-1-10.
Table II-1-10. (O = optional, M = mandatory)
IPS DS UDP reliability mechanisms
Provide dialogue connection over UDP identification of connections connection timeout termination timeout Detect the loss of UDP datagrams using one-to-one acknowledgements (on a per connection basis) retransmission timer + maximum retry count explicit acknowledgement piggy-backed acknowledgement (maximum delay before acknowledgement ) Detect long-lived unpaired connections inactivity timer + keep alive transmission timer Handle UDP datagrams truncation datagram segmentation / reassembly M M M M O M O O
II-1-24
Manual on the ATN using IPS Standards and Protocols Connection-ids
1.5.6 A pair of connection-ids, the source ID and destination ID, shall be assigned during the connection phase (D-START / D-START cnf) by every participating DS peer and used over any subsequent exchanges. Note 1. DS connection identification above the UDP layer will be handled by the assignment of this pair of connection-ids. Note 2. The 2 byte size for these identifiers was chosen because this will allow the DS-provider to associate a particular semantic to the dialogue-id assigned on its side (without interfering with the involved peer DS-user). In such a case, the identifier might be an index in a context table, making it implicitly unique, but also allowing the receiving DS-provider to find out the context without having to use multiple search criteria and parsing the whole context table. 1.5.7 The source ID and destination ID shall be conveyed in the variable part of the ATNPKT based on DS primitives as described in Table II-1-11:
Table II-1-11.
(O = optional, M = mandatory) DS primitive field D-START M
Source ID and destination ID usage
Source ID Identifier given by the DSprovider who initiates the dialogue; it will allow the user to find out the dialogue context during the whole dialogue duration. Identifier given by the DSprovider who accepts the dialogue; it will allow the provider to find out the dialogue context during the whole dialogue duration. No need to transport it since it would be meaningless for the destination DS-provider. No need to transport it since it would be meaningless for the destination DS-provider. No need to transport it since it would be meaningless for the destination DS-provider.
Destination ID Unassigned at this time
D-START cnf
Identifier of the DS-provider who initiated the dialogue.
D-DATA
Identifier of the peer DS-provider.
D-END
D-END cnf
II-1-25
DS primitive field D-ABORT before D-START cnf D-ABORT other cases M
Source ID Identifier given by the DSprovider who initiated the dialogue. No need to transport it since it would be meaningless for the destination DS-provider.
Destination ID Unknown for now.
Detecting lost datagrams Note 1. The loss of UDP datagrams is detected through a one-to-one acknowledgement mechanism, on a per DS connection basis, i.e. one data packet sent and one acknowledgement to be received before more data can be sent again. Note 2. The acknowledgement may be piggy-backed with a dialogue message in the reverse direction for the same dialogue; this will be possible for instance with confirmed primitives. 1.5.8 For unconfirmed DS services, the receiving user shall use an explicit acknowledgement by sending an ATNPKT with no data and with a specific value (D-ACK) as DS primitive. Note 1. For acknowledgement purposes, the sequence numbers field of the ATNPKT variable part will be used. Note 2. This sequence number is required to avoid delivering duplicated data to the peer DS-user following retransmission (i.e. if a D-ACK has been lost), and in more exceptional circumstances, i.e. when UDP datagrams are delivered out of sequence by the network. 1.5.9 The DS-provider shall associate an incremented sequence number to outgoing ATNPKTs and store the sequence number of the last ATNPKT received from the peer DS-provider in order to acknowledge it in a subsequent transmission. 1.5.10 Both outgoing and incoming sequence numbers shall be respectively carried by the N(S) and N(R) subfields of the sequence numbers. Note 1. N(S) corresponds to the current sequence number of the ATNPKT that has been sent; N(R) is the sequence number expected of the next ATNPKT to be received. Note 2. Using sequence numbers will allow the DS-provider to detect missing or duplicated ATNPKTs. There is at most one unacknowledged ATNPKT; for this reason, there will be no grouped acknowledgements and there is no need to implement a selective reject mechanism. Note 3. The lack of a timely acknowledgement will entail a retransmission. An excessive number of retransmissions will break the DS connection. The timeout values and the maximum number of retransmissions are detailed in Table II-1-12.
II-1-26
Manual on the ATN using IPS Standards and Protocols Connection timeout
Note. In order to avoid long-lived unpaired DS connections, a simple mechanism for detecting inactivity is implemented. Both ends of the DS connection will transmit a keepalive packet when the keepalive transmission timer expires. The keepalive transmission timer is restarted by the sender each time it sends data on the connection, avoiding unnecessary keepalive transmissions. 1.5.11 A keepalive (an ATNPKT with no data and with a value of D-KEEPALIVE as DS primitive) shall be sent at each expiry of the local keepalive transmission timer. 1.5.12 The keepalive transmission timer may be set to 1/3 of the inactivity timer of the peer DS-provider, or 1/3 of the default inactivity timer. Note. The lack of reception of either data or keepalive packets for an interval of time corresponding to the inactivity time will break the DS connection. The parameter value for this time is detailed in Table II-1-12. 1.5.13 The optional ATNPKT field inactivity time may be used at dialogue initialization time (i.e. in D-START and D-START cnf) so that each DS-provider can adjust its local keepalive transmission timer. Note. Absence of the inactivity time indicates use of the default inactivity time value as in Table I-1-12.
More indicator Note. Most of the ATN application messages do not exceed 1 000 bytes. Additionally, the suggested value of 1 024 bytes does not exceed the IP payload (1 500 bytes) in the Ethernet frame (1 518 bytes). 1.5.14 A D-DATA with a user data part exceeding 1 024 bytes shall be segmented using the more bit reserved in the ATNPKT fixed part. Note. Upon receipt of a D-DATA with the more bit set, the receiving side is responsible for ordering and reassembling the segmented data.
DS-provider parameters 1.5.15 The values specified in Table II-1-12 shall be applied to the identified DS-provider parameters:
Table II-1-12. Parameter Delay before retransmission Maximum number of transmissions Inactivity time
DS-provider parameters Minimum 1 second 1 3 minutes Maximum 60 seconds 10 15 minutes Default 15 seconds 3 4 minutes
Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction 1.6 IPS DIALOGUE SERVICE (DS) STATE TABLES
II-1-27
Table II-1-13.
IPS DS state table for TCP
Events D-IDLE During initialization phase D-START req OPEN (passive) OPEN (active) Map D-START req to D-START SEND (D-START) - Enter D-STARTSENT state D-CONNECTED D-START-SENT
State D-STARTRECEIVED D-TRANSFER D-END-SENT D-ENDRECEIVED D-WAITCLOSE
D-START rsp
Map D-START cnf to D-START cnf SEND (D-START cnf) - In case of positive response : - Start tinact Enter D-TRANSFER state - Otherwise : -Enter D-WAITCLOSE state Map D-DATA req to D-DATA SEND (D-DATA) Cancel tinact - Map D-END req to D-END - SEND (D-END) - Enter D-END-SENT state Map D-END rsp to D-END cnf SEND (D-END cnf) -In case of positive response : -Enter D-WAITCLOSE state Otherwise : - Start tinact - Enter D-TRANSFER state Map D-ABORT req to D-ABORT SEND (D-ABORT) - Enter D-WAITCLOSE state Enter D-CONNECTED state Map D-START to D-START ind Map D-ABORT req to D-ABORT SEND (D-ABORT) - Enter D-WAITCLOSE state Cancel tinact - Map D-ABORT req to D-ABORT - SEND (D-ABORT) Enter D-WAITCLOSE state Map D-ABORT req to D-ABORT SEND (D-ABORT) Enter D-WAITCLOSE state Map D-ABORT req to D-ABORT SEND (D-ABORT) Enter D-WAITCLOSE state
D-DATA req DS-user events TCP events
D-END req
D-END rsp
D-ABORT req
OPEN (passive) completed RECEIVE (D-START)
II-1-28
Events D-IDLE During initialization phase OPEN (passive) Report D-START ind to DS-User Enter D-STARTRECEIVED state RECEIVE (D-START cnf) Map D-START cnf to D-START cnf Report D-START cnf to DS-user - In case of positive response : - Start tinact - Enter D-TRANSFER state Otherwise : CLOSE (active) Enter D-IDLE state D-CONNECTED D-START-SENT
RECEIVE (DDATA)
Reset tinact - Map D-DATA to D-DATA ind Report D-DATA ind to DS-user Cancel tinact - Map D-END to D-END ind - Report D-END ind to DSuser - Enter D-ENDRECEIVED state Map D-END cnf to D-END cnf Report D-END cnf to DS-user - In case of positive response : CLOSE (active) Enter D-IDLE state - Otherwise : - Start tinact - Enter D-TRANSFER state Map D-ABORT to D-ABORT ind Report D-ABORT ind to DS-user CLOSE (active) Enter D-IDLE state CLOSE (active) Enter D-IDLE state Report D-PABORT ind to DS-user - CLOSE (active) -Enter D-IDLE state Report D-PABORT ind to DS-user - CLOSE (active) -Enter D-IDLE state Cancel tinact - Map D-ABORT to DABORT ind Report D-ABORT ind to DS-user CLOSE (active) Enter D-IDLE state Cancel tinact Report D-PABORT ind to DS-User - CLOSE (active) - Enter D-IDLE state Map D-ABORT to D-ABORT ind Report D-ABORT ind to DS-user CLOSE (active) Enter D-IDLE state Report D-PABORT ind to DS-user - CLOSE (active) - Enter D-IDLE state Map D-ABORT to D-ABORT ind Report D-ABORT ind to DS-user CLOSE (active) Enter D-IDLE state Report D-PABORT ind to DS-user - CLOSE (active) - Enter D-IDLE state CLOSE (active) Enter D-IDLE state
RECEIVE (DEND)
RECEIVE (D-END cnf)
RECEIVE (D-ABORT) TCP events CLOSE (passive)
II-1-29
Events D-IDLE During initialization phase DS-provider events tinact expires OPEN (passive) D-CONNECTED D-START-SENT
Report D-PABORT ind to DS-user - Enter D-IDLE state
Table II-1-14.
IPS DS state table for UDP

State
Events D-START req
D-IDLE Map D-START req to D-START - SEND (D-START) - Start tconnect - Enter D-START-SENT state
D-START-SENT
D-START-RECEIVED
D-TRANSFER
D-END-SENT
D-END-RECEIVED
D-START rsp
Map D-START cnf to D-START cnf - SEND (D-START cnf) -In case of positive response : Start tinact -Enter D-TRANSFER state Otherwise : -Enter D-IDLE state Map D-DATA req to D-DATA - SEND (D-DATA) Cancel tinact -Map D-END req to D-END SEND (D-END) - start tterm - Enter D-ENDSENT state Map D-END rsp to D-END cnf - SEND (D-END cnf) - In case of positive response : Enter D-IDLE state Otherwise : - Start tinact - Enter D-TRANSFER state Cancel tconnect -Map D-ABORT req to D-ABORT - SEND (D-ABORT) - Enter D-IDLE state Map D-ABORT req to D-ABORT - SEND (D-ABORT) - Enter D-IDLE state Cancel tinact - Map D-ABORT req to D-ABORT - SEND (D-ABORT) - Enter D-IDLE state Cancel tterm - Map D-ABORT req to D-ABORT - SEND (D-ABORT) - Enter D-IDLE state Map D-ABORT req to D-ABORT - SEND (D-ABORT) - Enter D-IDLE state
D-DATA req DS-user events
D-END req
D-END rsp
D-ABORT req
II-1-30
Events RECEIVE (DSTART)
State D-IDLE Map D-START to D-START ind - Report D-START ind to DS-user - Enter D-STARTRECEIVED state D-START-SENT D-START-RECEIVED D-TRANSFER D-END-SENT D-END-RECEIVED
RECEIVE (D-START cnf)
Cancel tconnect -Map D-START cnf to D-START cnf - Report D-START cnf to DSuser -In case of positive response : -Start tinact Enter D-TRANSFER state - Otherwise : Enter D-IDLE state Reset tinact - Map D-DATA to D-DATA ind - Report D-DATA ind to DS-user Cancel tinact -Map D-END to D-END ind Report D-END ind to DS-user - Enter D-END-RECEIVED state Cancel tterm -Map D-END cnf to D-END cnf - Report D-END cnf to DS-user - In case of positive response : Enter D-IDLE state Otherwise : - Start tinact - Enter D-TRANSFER state Map D-ABORT to D-ABORT ind - Report D-ABORT ind to DSuser - Enter D-IDLE state Report D-P-ABORT ind to DS-user - Enter D-IDLE state Report D-P-ABORT ind to DS-user - Enter D-IDLE state Report D-P-ABORT ind to DS-user - Enter D-IDLE state Cancel tinact - Map D-ABORT to D-ABORT ind - Report D-ABORT ind to DS-user - Enter D-IDLE state Cancel tterm - Map D-ABORT to D-ABORT ind - Report D-ABORT ind to DS-user - Enter D-IDLE state Map D-ABORT to D-ABORT ind - Report D-ABORT ind to DSuser - Enter D-IDLE state
RECEIVE (D-DATA) UDP events DS events
RECEIVE (D-END)
RECEIVE (D-END cnf)
RECEIVE (DABORT)
tconnect expires
tinact expires
tterm expires
______________________
Part III Guidance Material
CHAPTER 1 INTRODUCTION
1.1
GENERAL OVERVIEW
1.1.1 This part of the manual contains information to assist ICAO Contracting States in the deployment of an ATN/IPS network to support air traffic management (ATM) services. The following minimum core services should be provided by the ATN/IPS network. 1.1.2 These core services enable ATN applications to provide voice and data services using the appropriate priority and security over the ATN/IPS network. 1.1.3 The protocols discussed in this document are based on the open system interconnection (OSI) reference model. Figure III-1-1 depicts the relationship between OSI, ATN/OSI and the ATN/IPS protocols using the 4-layer model of the IETF.
OSI reference model ATN/ISO protocols ATN/IPS
Application layer 7
ATN applications (e.g. CMIP, X.400)
Presentation layer 6
Fast-byte
Consolidated application services (e.g. SMTP, SNMPv3, FTP, X.400 and Telnet)
Session layer 5
Fast-byte
Transport layer 4
Transport layer class 4 ES-IS/CLNP
TCP/UDP
Network layer 3
SNDCF X.25 PLP
IPv6 and ICMPv6
Link layer 2
LAP B (HDLC)
LLC/MAC
Physical layer 1
Physical layer (e.g. EIA-232, V.35, X.21)
Physical layer (e.g. FDDI, 802.X)
Figure III-1-1.
Protocol reference model
III-1-1
III-1-2 1.2
Manual on the ATN using IPS Standards and Protocols BACKGROUND
The ATN/IPS has been established with the specific goal of providing global ATM services based on commercial off-theshelf technologies. According to ICAO Standards and Recommended Practices (SARPs), ATN services can be provided using the ISO-based ICAO protocols as specified in Doc 9705 and Doc 9880, or as specified in this manual. This manual describes the technical approach for networking based on IPS, and will enable ICAO Contracting States to provide ATM services.
1.3 1.3.1 and VoIP.
GENERAL GUIDANCE
This section contains information about the implementation of ATN/IPS for ATN applications, multicast
The ATN/IPS
The ATN/IPS internetwork 1.3.2 The ATN/IPS internetwork is specifically and exclusively intended to provide data communications services to air traffic service (ATS) provider organizations and aircraft operating agencies supporting the following types of communications traffic: ATS communication (ATSC). Communication related to air traffic services including air traffic control, aeronautical and meteorological information, position reporting, and services related to safety and regularity of flight. This communication involves one or more air traffic service administrations. Aeronautical operational control (AOC). Communication required for the exercise of authority over the initiation, continuation, diversion or termination of flight for safety, regularity and efficiency reasons. Aeronautical administrative communication (AAC). Communication used by aeronautical operating agencies in relation to the business aspects of operating their flights and transport services. This communication is used for a variety of purposes, such as flight and ground transportation, bookings, deployment of crew and aircraft or any other logistical purposes that maintain or enhance the efficiency of overall flight operation. 1.3.3 In order to support these communications types, this manual specifies a set of technical and administrative requirements upon the entities that constitute the ATN/IPS internetwork. See Figure III-1-2. 1.3.4 Technical requirements in this manual are levied against an IPS router, an IPS host, or an IPS node when the requirement applies to both. This manual adopts the RFC 2460 definition of an IPS node as a device that implements IPv6 and distinguishes between an IPS router as a node that forwards IP packets to others, and an IPS host as a node that is not a router. 1.3.5 Administrative requirements in this manual are levied against administrative domains. An administrative domain is an organizational entity which can be an individual State, a group of States (e.g. an ICAO region or a regional organization), an air communications service provider (ACSP), an air navigation service provider (ANSP), or other organizational entity that manages ATN/IPS network resources and services.
Part III Guidance Material Chapter 1 Introduction
III-1-3
AD
AD
AD
AD
IPS host
IPS router
AD
IPS host IPS router
AD
ATN/IPS internetwork
AD
IPS host
IPS router
AD
IPS router
IPS host
IPS host
IPS router
IPS router IPS host
AD
AD
IPS host
IPS router
AD
AD
IPS router
IPS host
IPS host
IPS router
Figure III-1-2.
The ATN/IPS internetwork
1.3.6 The primary requirement is that each administrative domain participating in the ATN/IPS internetwork must operate one or more IPS routers which execute an inter-domain routing protocol called the border gateway protocol (BGP). This is essentially so that the ATN/IPS can be formed across the various administrative domains whereby any IPS host can reach any other IPS host in the ATN/IPS internetwork. 1.3.7 An inter-domain routing protocol is used to exchange routing information among autonomous systems. An autonomous system (AS), as defined in RFC 1930, is a connected group of one or more IP prefixes run by one or more network operators which has a single and clearly defined routing policy. From this definition, there are two distinct entities: one is the AS as a group of IP prefixes and the other is the network operators, i.e. the administrative domains. This distinction is meaningful in the Internet since it permits multiple organizations (i.e. administrative domains) to run BGP to an Internet service provider (ISP) which in turn connects each of these organizations to the Internet. This manual does not preclude using ISPs in this fashion; however, as noted above, requirements are levied directly on the administrative domains.
III-1-4 Coordination of policies among administrative domains
1.3.8 IPS routers will exchange information about their internal network prefixes with their immediate neighbour routers, but may also forward routing information about other network prefixes learned from other BGP neighbours. As a result, traffic between two administrative domains may be relayed by a number of intermediate administrative domains. Such traffic being carried on behalf of two others is termed transit traffic. 1.3.9 This manual does not specify which routes are to be advertised between IPS routers nor basic traffic management policies for a dynamically routed environment. Administrative domains, however, are required to coordinate their policy for carrying transit traffic with peer administrative domains. Administrative domains that participate in the ATN/IPS should ensure the proper handling of transit traffic on the following basis: an administrative domain should not advertise a network prefix if it is not prepared to accept incoming traffic to that network prefix destination; when establishing the interconnections between two administrative domains a charging mechanism may be agreed upon to support implicit corresponding transit policy; and administrative domains that relay transit traffic should ensure that the associated security and QoS policies of the traffic are maintained.
ATN/IPS internetworking with mobility 1.3.10 The fixed or ground-ground ATN/IPS described in 1.3.2 to 1.3.7 may be extended to support mobility, that is, it may be extended to support air-ground communications. This is accomplished through the use of mobile IPv6, the IETFs general mobility solution. Mobile IPv6 permits mobile nodes (MN) (i.e. aircraft in the ATN/IPS) to communicate transparently with correspondent nodes (CN) (i.e. ground automation systems in the ATN/IPS) while moving within or across air-ground networks. An administrative domain in the ATN/IPS which offers mobile IPv6 service is called a mobility service provider (MSP). Thus, the ATN/IPS is extended to support mobility through the addition of MSPs providing mobility service to mobile nodes. Figure III-1-3 depicts the ATN/IPS with an MSP. As is shown in this figure, in order to provide mobility service, the MSP must operate one or more home agents. The home agent provides a key role in that it provides location management (LM) to keep track of the movement of a mobile node and to locate the mobile node for data delivery, while it also operates as an inter-domain router providing connectivity to the rest of the ATN/IPS. (Note that this is a logical view. Different physical configurations are possible in actual implementations.) It should be noted that mobile IPv6 RFC 3775 is being updated by the IETF (RFC 3775 bis). Implementation of RFC 3775 should take those updates into account. 1.3.11 Figure III-1-3 shows the minimal configuration, e.g. for ATSC, where the MSP might be an ACSP. However, this is not the only possible configuration. An ANSP may choose to become its own MSP and obtain access service from an ACSP. To support AOC and AAC an airline may likewise become an MSP. Similarly, an airport authority may decide to become an MSP and offer service to the ATN/IPS. In this case, IP layer mobility service may be offered along with or in addition to link layer mobility. As noted in 1.3.2 to 1.3.7, the ATN/IPS is intended to support ATSC, AAC and AOC, however, the mobility approach may be used by other aviation organizations. These organizations may become MSPs and support other types of communications such as airline passenger communications (APC). In this case, an enhanced form of mobile IP service called network mobility (NEMO) may be offered.
Network transition mechanisms 1.3.12 IPv6 has been adopted by the IETF and the Internet authorities to cope with the ever increasing growth rate of the global Internet. IPv6 solves many of the technical problems associated with IPv4, in particular the limited IPv4 address space.
III-1-5
AD
AD
Correspondent node
Correspondent node Correspondent node
Correspondent node
Correspondent node
Correspondent node
Mobility service provider (MSP)
Home agent
Access router
Access router
MIPv6
Mobile node
Figure III-1-3.
The ATN/IPS with an MSP
1.3.13 The global implementation of IPv6 has already begun within ICAO regions to support air traffic management applications. It is the building block of the next generation Internet which will enable a flexible means to roll-out new technologies and services. For this reason, the ATN/IPS is based on IPv6 to take immediate advantage of new commercial off-the-shelf products and technologies. 1.3.14 The implementation of the ATN/IPS will be gradual. Many organizations will be required to perform multiple steps to ensure that ATN/IPS end systems and routers are integrated into their existing environment, in particular, for those that have deployed legacy AFTN, AFTN/CIDIN, X.25, ATN/OSI CLNP (primarily CLNP over Ethernet or X.25) and IPv4 systems. 1.3.15 Three transition mechanisms can assist organizations that are deploying the ATN/IPS in a heterogeneous environment: tunnelling: one protocol being encapsulated into another;
III-1-6
Manual on the ATN using IPS Standards and Protocols dual stack: an environment in which multiple protocols operate simultaneously; and translation: the conversion from one protocol to another.
1.3.16 An in-depth description of the first two mechanisms can be found in RFC 4213 (Basic Transition Mechanisms for IPv6 Hosts and Routers). The applicability of the above three mechanisms to the ATN/IPS are further described below.
Tunnelling 1.3.17 IPv6 has been specified to operate over a variety of lower layer interfaces such as Frame Relay, ATM, HDLC, PPP and LAN technologies. Tunnelling implies that a given protocol is encapsulated into another, meaning that IPv6 would be encapsulated into another functionally equivalent network protocol. With regard to the ATN/IPS, the key benefit of this mechanism would be for aeronautical organizations that already operate IPv4 networks to allow the ATN/IPS hosts and routers to communicate between each other over such an underlying IPv4 network. Furthermore, if the interconnecting infrastructure between the two ATN/IPS administrative domains is limited to IPv4, this mechanism can be applied. 1.3.18 It is recalled that IPv6 cannot operate over X.25; an IPv6 tunnel over IPv4 can be in turn tunnelled over an X.25 network. A specific tunnelling mechanism termed IP SNDCF is defined for ATN/OSI applications, and it is to be noted that this enables interoperability between ATN/OSI applications over an IP network but does not enable interoperability with ATN/IPS applications. 1.3.19 Tunnelling mechanisms lead to an increase of protocol overhead and the segregation of the two routed domains creates additional network management, e.g. an IPv6 routed domain over an underlying IPv4 routed domain will need to be managed in terms of QoS, security, and route optimization. In addition, this mechanism only foresees interoperability between ATN/IPS systems as it does not enable interoperability between ATN/OSI systems nor other IPv4 systems within the organization. Nevertheless, it may provide an effective way to deploy the ATN/IPS within and between two administrative domains. 1.3.20 The tunnelling mechanism is best suited to resolve lower layer communication issues between ATN/IPS IPv6 hosts and routers; but it does not provide interoperability with non-compliant ATN/IPS systems.
Dual stack 1.3.21 The dual stack mechanism implies that an implementation handles more than one communications protocol for a given application or function. Within the Internet domain a significant number of communication applications have been dual stacked, e.g. HTTP, FTP, SSH, DNS, SMTP, by supporting both IPv4 and IPv6 protocols. However, in the context of the ATN/IPS, the purpose of dual stacking is to resolve similar yet different issues. 1.3.22 The concept of dual stacking is ideally suited for systems that need to support ATN applications for both OSI and IPS. In such environments, the applications are designed in an abstract fashion to be independent of the lower layers, e.g. they are unaware which lower layer communications protocol (OSI or IP) is being used to communicate with their peer. X.400 vendors have taken this approach to support both OSI and IP environments avoiding the need to develop complex ad hoc lower layer communication gateways. Usually such implementations rely on some form of directory or lookup table associating a high-level address with a specific communications protocol address. 1.3.23 The concept of dual stacking can be extended to multiple stacking, e.g. IPv4, IPv6, X.25. ATN AMHS manufacturers usually support operation over multiple protocols such as OSI, TCP/IP and X.25.
III-1-7
1.3.24 The dual stack mechanism provides the maximum level of interoperability with peers while reducing the complexity of lower layer communication protocol gateways and additional single points of failure. It is ideally suited for applications such as the ATS message handling system (AMHS), whereby some systems have already been implemented on the basis of OSI and others on TCP/IP. A dual stack approach can be valid for air-ground data link ground systems to support CPDLC over multiple data link services, such as ATN/OSI and ATN/IPS.
Translation 1.3.25 Translation mechanisms imply the conversion from one protocol to another. This mechanism can be interpreted as a lower layer communications gateway between two protocols that share a high degree of commonality. Several translators such as RFC 2766 Network Address TranslationProtocol Translation (NAT-PT), have been developed in the context of the transition from IPv4 to IPv6 as both versions share a number of common features. 1.3.26 Within the overall transition from IPv4 to IPv6, it was envisaged that some systems may be only capable of communicating with IPv4 while others only with IPv6. Considering global Internet scalability issues and the fact that most Internet applications and systems have become dual stacked, the need for translators has declined. 1.3.27 However, translators may play an important short-term role in the case of the ATN/IPS. For example, although existing AMHS systems operate on dual stack operating systems, none of them have upgraded their application code to make use of IPv6. In other words, RFC 1006 is supported but not RFC 2126. In such particular cases and in view of the limited number of systems, the deployment of translators provides a short-term measure for such systems to comply with the ATN/IPS and interwork with RFC 2126 enabled systems. 1.3.28 IPv4/IPv6 translators increase the complexity of the IP infrastructure and its management. A dual stack approach is to be preferred but in specific cases translators may be the only short-term measure to provide compliance with the ATN/IPS.
Combining the mechanisms 1.3.29 As the ATN/IPS implementation will be gradual, it is understandable that a combination of the above three mechanisms will be applied. 1.3.30 Specific combinations of the above mechanisms can be deployed to better fit within the environment of the administrative domain environment.
1.4
PROTOCOL STACK
Physical and link layer guidance 1.4.1 Physical and link layer issues will be determined by the required service and Contracting State connections. The physical and link layer issues will be on a service-need basis and should be contained in a Memorandum of Agreement (MoA).
Network layer 1.4.2 The ATN/IPS makes use of IPv6, which uses 128 bit addresses versus 32 in IPv4. IPv6 prefixes are exchanged between administrative domains using static routes or BGP to ensure global ATN/IPS routing.
III-1-8 Address plan
1.4.3 Unlike IPv4, there is no notion of private addresses within IPv6. Similar to existing practices for X.25, each administrative domain will be required to develop an IPv6 addressing plan (refer to Part I, 2.3.8 to 2.3.13, Network addressing). This will involve the receipt of a unique IPv6 prefix and assignment procedures to networks and hosts.
Application interface to the network layer 1.4.4 Although applications generally interface to the communication service at the transport layer, it is sometimes necessary to transmit and receive datagrams at the network level. This is granted by some socket API extensions specified in RFC 3542 Advanced Sockets Application Program Interface (API) for IPv6.
Inter-domain routing 1.4.5 Inter-domain routing allows the exchange of IPv6 prefixes between administrative domains. These exchanges are supported by the configuration of static routing or the border gateway protocol (BGP) between ATN/IPS routers to ensure global ATN/IPS routing. 1.4.6 Depending on the scale of the administrative domain, further internal levels of inter- and intra-domain routing or BGP confederations may exist.
Autonomous systems (AS) numbering plan 1.4.7 AS numbers need to be assigned and configured in ATN/IPS routers to announce their autonomous systems within the routed domain. The AS numbering plan is presented in the Appendix to Part I.
ATN/IPS router ids 1.4.8 In order to establish BGP between two neighbours, each BGP peer must define a router id. If two routers make use of the same router-id value, BGP sessions cannot be established. As the router id is a 32-bit field, it is usually on the IPv4 address of the router. 1.4.9 As ATN/IPS routers may not have IPv4 interfaces or unique IPv4 addresses, a scheme needs to be recommended. Although global uniqueness of these values is not a prerequisite, to ease implementation of the ATN/IPS the following scheme is recommended (based on draft-dupont-durand-idr-ipv6-bgp-routerid-01.txt): 4 bits set to one, 16 bits set to the AS number (the global AS number plan is in the Appendix to Part I); 12 bits manually allocated within the domain (allows for 4 096 different router ids in each routing domain). Routing advertisement 1.4.10 route prefixes. ATN/IPS routers should advertise network prefixes based on consistent prefix lengths or aggregate
Part III Guidance Material Chapter 1 Introduction Traffic type segregation
III-1-9
1.4.11 BGP-4 does not natively allow setting up different sets of routes for different traffic types to the same destination. ATN/IPS requirements on traffic type segregation may be fulfilled by appropriate provisions in the ATN addressing plan; if the ATN address incorporates an indication of the traffic type, BGP-4 will transparently flood segregated route information for the various traffic types.
Traffic priority and differentiated service 1.4.12 Historically, network layer priority was selected explicitly by sending an application through the type of service (TOS) field in the IP header. Although differentiated services (RFC 2474) preserves the IP precedence semantic of the TOS field, this approach is now deprecated. This is partly because the IP precedence has been superseded by the per-hop behaviour (PHB) strategy of differentiated service, and also partly because network administrators usually do not trust application settings. Differentiated service (RFC 2474) provides a means for specifying and implementing QoS handling consistently in the ATN/IPS network. This specification is made on a per node basis, specifying behaviour of individual nodes concerning QoS (PHB). The general framework/current practices is depicted in detail in RFC 2475 Architecture for Differentiated Services. Note. Refer to paragraph 4 Quality of Service (QoS).
Multicast 1.4.13 The need to send the same information to multiple receivers is one of the main requirements of surveillance data distribution. This requirement can be supported by IPv4 and IPv6 multicast services. Other networking techniques that achieve the same multicast objective are not further considered within the scope of this document. 1.4.14 A limited number of ICAO Contracting States have deployed national IPv4 multicast services for surveillance data distribution. However, the limited range of the IPv4 multicast address space and the absence of gateways between IPv4 and IPv6 inhibits a scalable deployment for the ATN/IPS. 1.4.15 In recent years, significant technical progress has been made in the field of IP multicast, namely source-specific multicast (SSM). Contrary to existing deployments on the basis of PIM-SM (Protocol Independent MulticastSparse Mode), SSM provides added simplicity and resiliency to the routing of IP multicast traffic and is also ideally suited for surveillance needs. Its use over IPv6 is recommended in a EUROCONTROL guideline entitled EUROCONTROL Guidelines for Implementation Support (EGIS) Part 5: Communication & Navigation Specifications, Chapter 12, Surveillance Distribution over IP Multicast Profile Requirement List (PRL) available at: http://www.eurocontrol.int/communications/public/standard_page/com_network.html 1.4.16 A source-specific multicast (SSM) data channel is defined by the combination of a destination multicast address and a source unicast address. This corresponds to a single surveillance data flow made available from a specific source in the ATN/IPS (see Figure III-1-4).
| 8 | 4 | 4 | 8 | 8 | 64 | 32 | +--------+----+----+--------+--------+----------------+----------+ |11111111|0011|1110|00000000|00000000| 000000 | group ID | +--------+----+----+--------+--------+----------------+----------+

Figure III-1-4. SSM multicast IPv6 address with global scope IPv6
III-1-10
Manual on the ATN using IPS Standards and Protocols The IPv6 multicast group ID shall be in the range 0x8000000 to 0xFFFFFFFF allowed for dynamic assignment by a host, as specified in RFC 3307, section 4.3 and RFC 4607, section 1.
The resulting available IPv6 SSM address range is FF3E::8000:0/97 (FF3E:0:0:0:0:0:8000:0 / 97). Assuming the appropriate access to the service, to receive an SSM, stream one requires the following three parameters: 1. 2. 3. Source address (unicast address) Multicast address (as indicated by the source application) Port (default is 8600 for ASTERIX surveillance data in Europe)
Transport layer 1.4.17 The transport layer protocols are used to provide reliable or best-effort communication services over the ATN/IPS. There are two mandatory transport protocols, TCP and UDP. TCP is used to provide reliable transport services and UDP is used to provide best-effort services. Other transport protocols may be used but cannot affect ATN/IPS communications or services.
Transmission control protocol (TCP) 1.4.18 The Internet protocol (IP) works by exchanging groups of information called packets. Packets are short sequences of bytes consisting of a header and a body. The header describes the packet's routing information, which routers on the Internet use to pass the packet along in the right direction until it arrives at its final destination. The body contains the application information. TCP is optimized for accurate delivery rather than timely delivery and sometimes incurs long delays while waiting for out-of-order messages or retransmissions of lost messages; it is not particularly suitable for real time applications like voice-over IP (VoIP). Real time applications require protocols like the real time transport protocol (RTP) running over the user datagram protocol (UDP). 1.4.19 TCP is a reliable stream delivery service that guarantees to deliver a stream of data sent from one host to another without duplication or losing data. Since packet transfer is not reliable, a technique known as positive acknowledgement with retransmission is used to guarantee reliability of packet transfers. This fundamental technique requires the receiver to respond with an acknowledgement message as it receives the data. The sender keeps a record of each packet it sends, and waits for acknowledgment before sending the next packet. The sender also keeps a timer from when the packet was sent, and retransmits a packet if the timer expires. The timer is needed in case a packet becomes lost or corrupt. 1.4.20 In the event of congestion, the IP can discard packets. For efficiency reasons, two consecutive packets on the Internet can take different routes to the destination. Packets may arrive at the destination in the wrong order. 1.4.21 The TCP software library uses the IP and provides a simpler interface to applications by hiding most of the underlying packet structures, rearranging out-of-order packets, minimizing network congestion, and retransmitting discarded packets. Thus, TCP significantly simplifies the task of writing network applications. 1.4.22 TCP provides a connection-oriented service with a reliable semantic. It operates above the network layer which does not necessarily detect and report all errors (e.g. corruption, misrouting). For this purpose, it provides: error detection based on a checksum covering the transport header and payload as well as some vital network layer information; and
Part III Guidance Material Chapter 1 Introduction recovery from errors based on retransmission of erroneous or lost packets.
III-1-11
1.4.23 TCP is also designed to detect and manage end-to-end network congestion and maximum user data segment sizes. This is essential for operation over heterogeneous sub-networks with some low bandwidth and high latency trunks, such as the actual ATN/IPS air and/or ground sub-networks.
User datagram protocol (UDP) 1.4.24 UDP provides a connectionless service with limited error detection and no recovery and no congestion management mechanisms. It is dedicated for light data exchanges, where undetected occasional loss or corruption of packets is acceptable, and when simplicity of use is the goal.
Transport layer addressing 1.4.25 Transport layer addressing relies on port numbers (16-bit integer values) that are associated with source and destination end points to identify separate data streams. Ports are classified in three categories with an associated range of values: Well-known ports are those from 0 through 1 023 and are assigned by IANA. On most systems, these ports can only be used by system (or root) processes or by programs executed by privileged users. Such predefined well-known port numbers associated to distinct TCP and/or UDP applications makes them visible (well-known) to client applications without specific knowledge or configuration. Registered ports are those from 1 024 through 49 151 and are registered by IANA following user request. Such ports play the same role as well-known ports but for widespread or less critical applications. The use of such ports does not require specific privileges. Dynamic and/or private ports are those from 49 152 through 65 535. They may be used freely by applications. 1.4.26 Port assignment is obtained on request to IANA. An up-to-date image of the port registry is available at: http://www.iana.org/assignments/port-numbers 1.4.27 This assignment plan is compulsory over the public Internet. It should be made applicable to ATN/IPS (at least concerning well-known ports) in order to avoid any conflict. 1.4.28 Furthermore, ATN/IPS hosts are required to support the following registered port numbers: tcp 102 for ATSMHS tcp 8500 for FMTP tcp/udp 5910 for CM tcp/udp 5911 for CPDLC tcp/udp 5912 for FIS tcp/udp 5913 for ADS
III-1-12 Application interface to the transport layer
1.4.29 The application interface to the TCP and UDP transport layers is provided on a wide range of platforms/operating systems as specified in RFC 3493 Basic Socket Interface Extensions for IPv6. This RFC extends the socket interface (originally developed by Berkeley University for supporting IPv4 in their BSD Unix distribution) to IPv6.
Congestion avoidance 1.4.30 In order to adapt to varying conditions for draining traffic in sub-networks, TCP implements basically four mechanisms: slow-start, congestion-avoidance, fast-retransmit and fast-recovery. These are specified in RFC 2581 TCP Congestion Control. The two first mechanisms aim at preventing important loss of packets when congestion occurs, while the two others attempt to shorten the delay for retransmitting the lost packets. These mechanisms are implemented independently in every end system; they do not completely avoid loss of packets. 1.4.31 In the case of low bandwidth sub-networks (e.g. ATN air/ground sub-networks), TCP applications may make use of the explicit congestion notification mechanism which will more likely provide a significant benefit. It is specified in RFC 3168 The Addition of Explicit Congestion Notification (ECN) to IP. This feature anticipates congestion, significantly reducing packet loss. However, it impacts the transport and network layers, and requires participation of a significant number of routers in the networks (preferentially, the routers at the edge of low speed / high latency sub-networks).
Error detection and recovery 1.4.32 TCP error detection relies on lack of timely received acknowledgements. Recovery is performed through retransmission of (supposed) lost packets. Loss of a large numbers of packets in a short period of time may heavily impede the TCP connection throughput (hence performance). This may become critical for high latency subnetworks (e.g. ATN air/ground sub-networks). Support of the TCP selective acknowledgement options may mitigate this problem by allowing selective retransmission of lost packets only (instead of the whole sequence from the first to the last packet lost). This option is specified in RFC 2018 TCP Selective Acknowledgment Options.
Performance enhancing proxies (PEPs) 1.4.33 Performance enhancing proxies (PEPs) are often employed to improve severely degraded TCP performance caused by different link characteristics in heterogeneous environments, e.g. in wireless or satellite environments that are common in aeronautical communications. Transport layer or application layer PEPs are applied to adapt the TCP parameters to the different link characteristics. RFC 3135 Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations is a survey of PEP performance enhancement techniques, and describes some of the implications of using PEPs. Most implications of using PEPs result from the fact that the end-to-end semantics of connections are usually broken. In particular, PEPs disable the use of end-to-end IPsec encryption thus having implications on mobility and handoff procedures.
Transport layer usage 1.4.34 How transport layer connections are used has great impact on the Quality of Service (QoS) experienced by the application. Application messages may have different Classes of Service (CoS); some may require reliable delivery in the correct order. Four options exist to use the TCP transport layer service:
Part III Guidance Material Chapter 1 Introduction I. Re-establishing a TCP connection for each transmission and for each service
III-1-13
Each service instance uses a dedicated TCP connection. When the application service data are generated, the transport layer connection is opened and the data are then transmitted. After successful transmission, the connection is closed. II. Establishing a TCP connection once for each service and keeping it open Each service uses a dedicated TCP connection. The connection is opened at the time of logon or first-use and closed at the time of logoff or handover. III. Re-establishing a TCP connection for each transmission of a multiplexed set of services A shared TCP connection is established for all services in the set (one application may host several services). Datagrams produced by these applications are transmitted over this shared connection. The connection is opened at the time the service datagram is generated and closed after successful transmission. Note. All services of the multiplexed set should require the same CoS and be produced by the same application. IV. Establishing a TCP connection once for a multiplexed set of services and keeping it open A shared TCP connection is opened for all services in the set (one application may host several services). Datagrams produced by these applications are transmitted over this shared connection. The connection is opened at the time of logon or first-use and is closed at the time of logoff or handover. Note. All applications of the multiplexed set should require the same CoS and be generated by the same application. 1.4.35 Multiplexing services generated by the same application but with different CoS requirements, as in options III and IV, are not advised, as network layer QoS is performed per TCP connection. TCP has no means to provide differentiated QoS within one connection, so any CoS information would at least be partially lost. Multiplexing services generated by the same application and with the same CoS requirements does not create this problem. 1.4.36 It is recommended to use at least one dedicated transport connection for each service (options I and II). The connection may be established either per service or per application. 1.4.37 If different services of one application are multiplexed to a shared TCP connection, all services must require the same CoS (options III and IV). 1.4.38 For air-ground applications, it is recommended to open the connection at the time of logon or first-use and to keep it open until logoff or handover (options II and IV).
Application layer
ASN.1 extensions to context management (CM) 1.4.39 The ATN CM application requires ASN.1 adaptations to operate over the ATN/IPS. Note. It is expected that a future edition of Doc 9880 will contain these extensions.
III-1-14 CM ASN.1 definition
1.4.40 In order to support the conveyance of address information specific to IPS, the CM application ASN.1 needs to be updated. While there are other possible methods of obtaining addressing information applications, CM also provides additional information intended to facilitate correlation of aircraft information with flight plan information. 1.4.41 New definitions of ASN.1 were added with a goal to retain backwards compatibility with previous CM implementations. When exchanging application information, the OSI ATN CM used an AEQualifierVersionAddress element. This would be supplemented with an AEEnhancedQualifierVersionAddress element, with a specific new element of APEnhancedAddress. This is shown below: AEEnhancedQualifierVersionAddress ::= SEQUENCE { aeQualifier AEQualifier, apVersion VersionNumber, apAddress APEnhancedAddress } The APEnhancedAddress element would allow the carriage of either a TSAP for OSI network usage or an IP address for IPS usage. The APEnhancedAddress is shown below: APEnhancedAddress ::= CHOICE { longTsap [0] LongTsap, shortTsap [1] ShortTsap, ipAddress [2] IPAddress, ... } 1.4.42 The IPAddress element is new and is used to convey the actual IPv6 address. A specific IPv4 definition was not included in this definition. This was done to simplify definitions and to encourage IPv6 migration. If IPv4 addresses are required by some implementations, they can still be represented in IPv6 format using the common IPv4 mapping procedure, i.e. the first 80 bits set to zero, the next 16 set to 1, and the last 32 as the representation of the IPv4 address. 1.4.43 Also, an optional port element is included. The intention was to allow the specification of a port for the IP address that pertains to a particular application. The port is not needed if the implementation uses the standard IANA port numbers assigned to the IPS applications. The IPAddress element is shown below: IPAddress ::= SEQUENCE { ipHostOrAddr port ... }
IPHostOrAddress, Port OPTIONAL,
1.4.44 The IPHostOrAddress element provides further flexibility in that a host name or an IPv6 address can be used. The host name is further defined as an IA5 string of size between 2 and 255 characters, the port as an integer from 0 to 65 536, and the IPv6 address as an octet string of size 16. These are shown below:
Part III Guidance Material Chapter 1 Introduction IPHostOrAddress ::= CHOICE { hostname [0] Hostname, ipv6Address [1] IPv6Address, } IPv6Address ::= OCTET STRING(16) Port ::= INTEGER(0..65536) Hostname ::= IA5String(SIZE(2..255))
III-1-15
CM ASN.1 usage 1.4.45 The usage of the IPv6 ASN.1 will be similar to the usage of the OSI version. This means that when CM wants to provide address information for supported applications, it needs to identify the application, version number of the application, and address of the application for each of the applications that can be supported. This needs to be done regardless of the network technology being used. 1.4.46 For an ATN application running over the IPS, the IPv6 address will be used for the addressing of each supported application. Currently, no usage of host name is defined, so only the IPv6Address element will be used in the IPHostOrAddress. The IPv6Address element will take the value of the IPv6 address of the application. 1.4.47 The port number will not need to be provided, since port numbers are already defined for the applications and therefore do not need to be conveyed end-to-end. Therefore, the IPAddress element will only contain the IPHostOrAddress. 1.4.48 The APEnhancedAddress element will use the IPAddress choice, as the TSAP definitions have no relevance to the IPS. And finally, the AEQualifier and VersionNumber elements would need to be provided as part of the AEEnhancedQualifierVersionAddress. The AEQualifier and VersionNumber elements will be filled out in the same manner as for OSI applications, i.e. the AEQualifier would reference an integer, defined in Doc 9880, Part III, from 0 to 255 that identifies the application (e.g. ADS is value 0) and the VersionNumber would be an integer from 0 to 255 that identifies the version of the application. 1.4.49 Once exchanged, the application information would be made available to other systems or processes on the air and ground systems, as necessary, in order to allow operation of the applications. This is unchanged from OSI CM.
1.5
QUALITY OF SERVICE (QoS)
Introduction 1.5.1 The IETF defined DiffServ per-hop behaviour (PHB) as a means to describe, classify and manage network traffic to support the provision of QoS on IP networks. The RFCs do not dictate how PHBs are implemented within a network and this is typically vendor dependent. 1.5.2 PHBs: In practice, private and public IP network operators provide services based on a limited number of
III-1-16
Manual on the ATN using IPS Standards and Protocols EF (Expedited Forwarding) defined in RFC 3246, intended as a low loss, low delay, low jitter service. This would typically be used for voice applications. AF (Assured Forwarding) defined in RFC 2597 and updated in RFC 3260. Assured forwarding allows the operator to provide assurance of delivery as long as the traffic does not exceed a subscribed rate. These classes would be used for delay-sensitive data applications usually labelled AFx with a drop precedence. Typically, each specific customer application would be matched to a specific AF class, and usually one AF class is associated to multimedia applications, e.g. video. AF classes are independent of each other and have the benefit of individual guaranteed bandwidth. This prevents one critical application to take all the available bandwidth and block other critical applications. Default a best-effort class which would be used for non-mission-critical and non-delay-sensitive applications.
Class definitions
Context 1.5.3 ATN/IPS communication service providers are likely to make use of the same IPS infrastructure for ATN and other non-ATN-defined applications, e.g. ATSMHS and surveillance data. Sharing of resources can be at different levels, i.e. ATN/IPS applications can use the same type of class of service as other non-ATN applications over the same IP routed infrastructure. Alternatively, ATN/IPS communication service providers may only wish to share the same physical infrastructure and operate a virtual private network (VPN) per service; in this case, a separate CoS model can be applied to each VPN service, one being the ATN/IPS. Fundamentally, ATN/IPS communication service providers have flexibility in how they enable CoS for the ATN/IPS over their infrastructure. 1.5.4 For CoS definitions, it is essential that ATN/IPS traffic is sufficiently qualified, i.e. through the use of appropriate port numbers and/or other means, in order to properly mark ingress traffic. As the IP packet enters the network core, PHBs are enforced, depending on the packet marking. ATN/IPS communication service providers will need to handle unmarked or pre-marked ingress traffic and be prepared to mark or re-mark the traffic before it is routed over their infrastructure. The internal techniques, mechanisms and policies to enforce the PHB within the communications service provider networks are considered out of scope of the ATN/IPS.
ATN/IPS PHBs/CoS 1.5.5 The ATN/IPS is to support legacy ATN applications over the IPS. Currently, this intended support covers CM(DLIC), FIS(ATIS), CPDLC, ADS-C, ATSMHS. Indeed, directory services (DIR) (see Doc 9880, Part IVA) is only specified for ATN/OSI and it is foreseen that AIDC will be implemented through regional solutions. 1.5.6 As each ATN application is mapped to a given CoS, the dynamic support of different priorities per user message category is not considered. 1.5.7 Table III-1-1 provides an example of an administrative domain that supports several applications and Classes of Service (CoS) that are labelled very high, high, normal and best-effort.
Part III Guidance Material Chapter 1 Introduction Table III-1-1. Priority/application mapping Class (CoS type) Very high (EF) High (AF) 1 0 1 2 3 Drop precedence ATN priority ATN application Voice (VoIP) ADS-C CPDLC ATN/IPS priority mapping to classes Traffic identification (ingress) TCP/UDP port RTP numbers 16384-32767 TCP 5913 UDP 5913 TCP 5911 UDP 5911 IP address
III-1-17
The source or destination address will be part of a reserved address space assigned to mobile service providers.
Normal (AF)
AIDC FIS(ATIS)
TCP 85001 TCP 5912 UDP 5912 The source or destination address will be part of a reserved address space assigned to mobile service providers. The source or destination address will be part of a reserved address space assigned to mobile service providers.
2 3
5 6
METAR CM(DLIC)
TCP 5910 UDP 5910
ATSMHS 7 Best-effort (default) 8 14
TCP 102
1. This is applicable when OLDI/FMTP is used as a means to enable AIDC services.
III-1-18
1.5.8 In order to mark ingress traffic, the ATN/IPS provider has several means to identify the traffic: destination transport port number, IP source address, and/or IP destination address. Note. Making use of the DiffServ Code Point (DSCP)/Type of Service (ToS) value set by the application or prior communication service provider may not be the optimum approach, as the value may be incorrectly configured or unknown.
DiffServ code point (DSCP) values 1.5.9 The PHB is indicated by encoding a 6-bit value called the differentiated services code point (DSCP) into the 8-bit differentiated services (DS) field of the IP packet header. The DSCP value of the field is treated as a table index to select a particular packet handling mechanism. This mapping must be configurable and administrative domains may choose different values when mapping code-points to PHBs. However, it is widely accepted that DSCP value 101110 refers to EF (Expedited Forwarding). 1.5.10 Table III-1-2 provides an example of mapping DSCP values to ATN/IPS PHBs where a number of applications share the same IP network infrastructure. In this table, air-ground applications have been assigned special class selector code-points, as specified in Doc 9880, for the ATN IP SNDCF; but within the ATN/IPS it would be better to make use of AF PHBs to avoid any interaction with legacy applications that make use of IP precedence.
Table III-1-2. DSCP value 000000 001000 001010 001100 001110 010000 010010 010100 010110 011000 011010 011100 011110 100000 100010 100100 100110
Example of DSCP to PHB mapping PHB CS0 CS1 AF11 AF12 AF13 CS2 AF21 AF22 AF23 CS3 AF31 AF32 AF33 CS4 AF41 AF42 AF43 CPDLC, ADS-C Voice signalling FIS Voice recording CM ATSMHS AIDC Application Best effort
III-1-19
DSCP value 101000 101110 110000 111000
PHB CS5 EF NC1/CS6 NC2/CS7
Application
Voice
Traffic characterization 1.5.11 Traffic characterization is a means to express the type of traffic patterns, integrity and delay requirements. It provides further information to the communication service provider in order to fully meet the user requirements within a specific network operation. Typically, traffic characterization information is part of the contracted service level agreement in which further parameters are defined, such as service delivery points, service resilience, required bursting in excess of committed bandwidth, service metric points, MTTR, and port speeds. 1.5.12 Table III-1-3 provides an example of traffic characterization for ground-ground services which are derived from the Pan-European Network Services (PENS) specifications. Table III-1-3. Average message length 70 (bytes) 150 (bytes) Example of traffic characterization Typical bandwidth (point-to-point) 12 kbps 10k bps
ATN application Voice (VoIP using G.729) OLDI/FMTP (regional AIDC) ATSMHS
Expressed integrity 1 user corrupt message in 2 000 10-6 (in terms of 1 000 bytes message blocks)
Jitter <15 ms N/A
Network delay (1-way) <100 ms <1 s
3 kbytes
N/A
20 kbps
<5 s
1.6
MOBILITY GUIDANCE
Mobile IPv6 1.6.1 This manual specifies that the IP mobility solution for the ATN/IPS is mobile IPv6 (MIPv6) as specified in RFC 3775. With mobile IP a mobile node (MN) has two addresses: a home address (HoA), which is a permanent address, and a dynamic care-of address (CoA), which changes as the mobile node changes its point of attachment (see Figure III-1-5). The fundamental technique of mobile IP is forwarding. A correspondent node (CN), which is any peer node with which a mobile node is communicating, sends packets to the home agent (HA) of the mobile node. The CN reaches the HA through normal IP routing. Upon receipt of a packet from the CN, the HA will forward these packets to the MN at its current CoA. The HA simply tunnels the original packet in another packet with its own source address and
III-1-20
a destination address of the current CoA. This is possible because of the mobile IP protocol whereby the MN sends binding update messages to the HA whenever its point of attachment changes. The binding update associates the mobile nodes HoA with its current CoA. The HA maintains a binding cash that stores the current CoA of the MN.
Home network
HoA
HA
CN
Remote network
Foreign network
AR CoA1 AR CoA2
MN
movement
Figure III-1-5.
Mobile IP
MIPv6 bidirectional tunnelling 1.6.2 In the reverse direction, the MN could simply send packets directly to the CN using normal IP routing. However, this results in triangular routing and depending on the relative location of the HA, there can be a situation where the path in one direction (e.g. CN to HA to MN) is significantly longer than the path in the reverse direction (e.g. MN to CN). A further consideration in this case occurs if the MN uses its home address as a source address, which could create a problem in that many networks perform ingress filtering of incoming packets and will not accept packets that are topologically incorrect. This would be the case with packets from the MN because they actually originate from the care-of address but the source address in the IP packet is the home address. Because of these issues, MIPv6 allows the MN to follow the same path back to the CN via the HA using bidirectional tunnelling whereby, in addition to the HA tunnelling packets to the MN, the MN reverse tunnels packets to the HA. The HA will decapsulate a tunnelled IP packet and forward it to the CN. With bidirectional tunnelling the CN is not required to support mobile IP.
MIPv6 route optimization 1.6.3 Bidirectional tunnelling solves the problems of triangular routing and ingress filtering; however, there still can be suboptimal routing since the path from the MN to the CN via the HA may be relatively long even when the MN and CN are in close proximity. With MIPv6 the situation where the path through the HA is longer than a direct path to the CN may be addressed using a technique called route optimization. With route optimization the MN sends binding updates to both the HA and the CN. In this case, the MN and CN can communicate directly and adapt to changes in the MNs CoA. RFC 3775 defines the procedures for route optimization. It requires that the MN initiate the return route procedure. This procedure provides the CN with some reasonable assurance that the MN is able to be addressed at its claimed care-of address and its home address. 1.6.4 It is generally acknowledged that there are drawbacks to route optimization. RFC 4651 presents a taxonomy and analysis of enhancements to MIPv6 route optimization. This document notes that the two reach tests of
III-1-21
the return route procedure can lead to a handoff delay unacceptable for many real time or interactive applications, whereby security and return-route procedure guarantees might not be sufficient for security-sensitive applications, and periodically refreshing a registration at a correspondent node may imply a hidden signal overhead. Because of the overhead and delay associated with the return route procedure, and because at least for ATSC it is expected that the CN and HN will be in relative close proximity, this manual requires that IPS CNs that implement mobile IPv6 route optimization allow route optimization to be administratively enabled or disabled with the default being disabled. New solutions to route optimization are expected as a result of IETF chartered work in the Mobility Extensions for IPv6 (MEXT) Working Group which includes aviation-specific requirements.
Enhancements to MIPv6 1.6.5 When a mobile node (MN) changes its point of attachment to the network, the change may cause delay, packet loss, and generally result in overhead traffic on the network. Hierarchical mobile IPv6 (HMIPv6) 1.6.6 One technology developed to address these issues is hierarchical mobile IPv6 (HMIPv6) (RFC 4140). RFC 4140 introduces extensions to mobile IPv6 and IPv6 neighbour discovery to allow for local mobility handling. HMIPv6 reduces the amount of signalling between an MN, its CNs, and its HA. HMIPv6 introduces the concept of the mobility anchor point (MAP). A MAP is essentially a local home agent for a mobile node. A mobile node entering a MAP domain (i.e. a visited access network) will receive router advertisements containing information about one or more local MAPs. The MN can bind its current location, i.e. its on-link care-of address (LCoA), with an address on the MAPs subnet, called a regional care-of address (RCoA). Acting as a local HA, the MAP will receive all packets on behalf of the mobile node it is serving and will encapsulate and forward them directly to the mobile nodes current address. If the mobile node changes its current address within a local MAP domain (LCoA), it only needs to register the new address with the MAP. The RCoA does not change as long as the MN moves within a MAP domain. RFC 4140 notes that the use of the MAP does not assume that a permanent HA is present; an MN need not have a permanent HoA or HA in order to be HMIPv6-aware or use the features of HMIPv6. HMIPv6-aware mobile nodes can use their RCoA as the source address without using a home address option. In this way, the RCoA can be used as an identifier address for upper layers. Using this feature, the mobile node will be seen by the correspondent node as a fixed node while moving within a MAP domain. This usage of the RCoA does not have similar penalties as mobile IPv6 (i.e. no bindings or home address options are sent back to the HA), but still provides local mobility management (MM) to the mobile nodes with near-optimal routing. However, such use of RCoA does not provide global mobility.
Fast handovers for mobile IPv6 (FMIPv6) 1.6.7 A further enhancement to MIPv6 is fast handovers for mobile IPv6 (FMIPv6) (RFC 4068). FMIPv6 attempts to reduce the chance of packet loss through low latency handoffs. FMIPv6 attempts to optimize handovers by obtaining information for a new access router before disconnecting from the previous access router. Access routers request information from other access routers to acquire neighbourhood information that will facilitate handover. Once the new access router is selected, a tunnel is established between the old and new router. The previous care-of address (pCoA) is bound to a new care-of address (nCoA) so that data may be tunnelled from the previous access router to the new access router during handover. Combining HMIPv6 and FMIPv6 would contribute to improved MIPv6 performance, but this comes at the cost of increased complexity.
Proxy mobile IPv6 (PMIPv6) 1.6.8 In MIPv6 as described above the MN updates the HA with binding updates messages. This mode of operation is called node-based mobility management. A complimentary approach is for access network service providers
III-1-22
to provide network-based mobility management using proxy mobile IPv6 (PMIPv6) on access links that support or emulate a point-to-point delivery. This approach to supporting mobility does not require the mobile node to be involved in the exchange of signalling messages between itself and the home agent to potentially optimize the access network service provision. A proxy mobility agent in the network performs the signalling with the home agent and does the mobility management on behalf of the mobile node attached to the network. The core functional entities for PMIPv6 are the local mobility anchor (LMA) and the mobile access gateway (MAG). The local mobility anchor is responsible for maintaining the mobile nodes reach state and is the topological anchor point for the mobile nodes home network prefix(es). The MAG is the entity that performs the mobility management on behalf of a mobile node and it resides on the access link where the mobile node is anchored. The MAG is responsible for detecting the mobile nodes movements to and from the access link and for initiating binding registrations to the mobile nodes LMA. An access network which supports network-based mobility would be indifferent to the capability in the IPv6 stack of the nodes which it serves. IP mobility for nodes which have mobile IP client functionality in the IPv6 stack as well as those nodes which do not, would be supported by enabling proxy mobile IPv6 protocol functionality in the network. The advantages of PMIPv6 are reuse of home agent functionality and the messages/format used in mobility signalling and common home agent would serve as the mobility agent for all types of IPv6 nodes. PMIPv6 like HMIPv6 is a local mobility management approach which further reduces the air-ground signalling overhead.
Network mobility (NEMO) 1.6.9 Mobile IPv6 supports the movement of an individual network node. However, there are scenarios in which it would be necessary to support the movement of an entire network in the ATN/IPS. One case is for APC, where it would be wasteful of bandwidth to have mobility signalling for every individual passenger. Another case may be when there is a common airborne router supporting multiple traffic types, provided proper security issues can be addressed. The extension to mobile IPv6 which supports these scenarios is called network mobility (NEMO). This manual lists NEMO in accordance with RFC 3963 as an option for implementation. The NEMO operational model introduces a new entity called a mobile network node (MNN) which is a node in the network that moves as a unit. It can be a host moving with other MNNs or a mobile router. The mobile router operates like any mobile IP host on the egress interface (to a fixed access router). The mobile router also negotiates a prefix list with the home agent. The home agent uses this list to forward packets arriving for the MNNs that share a common prefix to the mobile router. On the ingress interface (to the mobile network), the mobile router advertises one or more prefixes to the MNNs. Although on the surface NEMO appears to be a straight-forward extension to mobile IP, there are several considerations that are still being investigated in IETF working groups. These issues include NEMO route optimization and prefix delegation and management.
1.7
SECURITY GUIDANCE
1.7.1 This section contains a description of the rationale for the requirements in 2.5 of Part I. It provides background information when additional clarification is warranted and general guidance for implementation of security provisions.
Requirements for implementation 1.7.2 The requirement to implement security is intended to be consistent with the security architecture for IPv6, which requires that all IPv6 implementations comply with the requirements of RFC 4301. Although all ATN/IPS nodes are required to implement Internet protocol security (IPsec) and the Internet key exchange 2 (IKEv2) protocol, the actual use of these provisions is to be based on a system threat and vulnerability analysis.
Part III Guidance Material Chapter 1 Introduction Ground-ground security Ground-ground IPsec
III-1-23
1.7.3 The baseline for ground-ground security is to require network layer security in the ATN/IPS internetwork, implemented using IPsec. IPsec creates a boundary between unprotected and protected interfaces. IPsec is typically used to form a virtual private network (VPN) among gateways (NIST 800-77). A gateway may be a router or another security device such as a firewall. In this context, other security devices are considered to be ATN/IPS nodes. The gateway-to-gateway model protects communications among ATN/IPS networks between regions or between States or organizations in a particular region. IPsec may also be used in a host-to-gateway environment, typically to allow hosts on a non-secure network to gain access to protected resources. IPsec may also be used in a host-to-host environment where end-to-end protection of applications is provided. 1.7.4 To achieve interoperability across the ATN/IPS internetwork, this manual specifies support for the IPsec security architecture, the encapsulating security payload (ESP) protocol and a common set of cryptographic algorithms. The architecture is as specified in RFC 4301. ESP is as specified in RFC 4303 and the cryptographic algorithms which may be used are specified in RFC 4835. This ATN/IPS manual further specifies that ESP encryption is optional but authentication is always performed. 1.7.5 This manual specifies that ATN/IPS nodes in the ground-ground environment may implement the IP authentication header (AH) protocol as specified in RFC 4302. This is in recognition that while AH may exist in certain products, its use in IPsec has been downgraded. RFC 4301 states, Support for AH has been downgraded to MAY because experience has shown that there are very few contexts in which ESP cannot provide the requisite security services. Note that ESP can be used to provide only integrity, without confidentiality, making it comparable to AH in most contexts.
Ground-ground IKEv2 1.7.6 The IPsec architecture (RFC 4301) specifies support for both manual and automated key management. As the ATN/IPS evolves, use of manual key management will not scale well. Therefore, this manual specifies that nodes in the ground-ground environment shall implement the Internet key exchange 2 (IKEv2) protocol as specified in RFC 4306 for automated key management. IKEv2 is the latest version of this protocol. The IKEv2 specification is less complicated than the first version of the protocol which should contribute to better interoperability among different implementations. 1.7.7 As is the case for ESP, the IKEv2 protocol requires a set of mandatory-to-implement algorithms for interoperability. This manual requires that nodes in the ground-ground environment implement the cryptographic algorithms specified in RFC 4307.
Alternatives to IPsec/IKEv2 for ground-ground security 1.7.8 Alternatives to network security may be appropriate in certain operating environments. Alternatives to IPsec may be applied at the data link, transport, or application layer. NIST SP 800-772 describes the main alternatives, characterizes the alternatives in terms of strengths and weaknesses, and identifies potential cases where these may be used.
2. Refer to http://csoc.nist.gov/publication/nistpubs/800-77/sp800-77.pdf
III-1-24
Manual on the ATN using IPS Standards and Protocols Air-ground security
Air-ground IPsec 1.7.9 Similar to the ground-ground environment, to achieve interoperability in the air-ground environment this manual specifies that ATN/IPS nodes support the IPsec security architecture and the ESP protocol. As in the ground case, the architecture is as specified in RFC 4301 and ESP is as specified in RFC 4835. However, rather than implement all of the cryptographic algorithms which are identified in RFC 4835, specific default algorithms are identified for authentication and for encryption and authentication together. This is in consideration of bandwidth-limited air-ground links and so as not to have unused codes in the avionics platform. 1.7.10 The authentication algorithm selected for use when confidentiality is not also selected is AUTH_HMAC_SHA2_256-128 as specified in RFC 4868. This algorithm uses a 256-bit key to compute a hash message authentication code (HMAC) tag using the SHA-256 hash function. The tag is truncated to 128 bits. The same algorithm is used for integrity in IKEv2 as described below. 1.7.11 If ESP encryption is used, this manual specifies that the advanced encryption standard (AES) be used in Galois/Counter Mode (GCM). AES-GCM is used with an 8 octet integrity check value (ICV) and with a key length attribute of 128 as specified in RFC 4106. AES-GCM is a combined mode algorithm which offers both confidentiality and authentication in a single operation. Combined mode algorithms offer efficiency gains when compared with sequentially applying encryption and then authentication. When AES-GCM is used the ICV consists solely of the AESGCM authentication tag and a separate HMAC tag is not applied.
Air-ground IKEv2 1.7.12 Because manual key management is not practical in the air-ground environment, this manual requires that ATN/IPS nodes implement the Internet key exchange 2 (IKEv2) protocol as specified in RFC 4306. As is the case of ESP in consideration of bandwidth limitations, and so that there will not be unused codes in the avionics platform, this manual specifies a set of default algorithms for use in IKEv2. The selection of transforms is intended to be compatible with the selections of the Air Transport Association (ATA), the Digital Security Working Group (DSWG), the Airlines Electronic Engineering Committee (AEEC) and the Data Link Security (DSEC) working groups, to the extent possible; however, this manual only uses transforms that have been registered with IANA. Five transforms are used by IKEv2. 1. There is a pseudo-random function (PRF) which is used in IKEv2 for generating keying material and for authentication of the IKE security association. This manual requires the use of PRF_HMAC_SHA_256 as specified in RFC 4868 as the PRF. IKEv2 uses the Diffie-Hellman key exchange protocol to derive a shared secret value used by the communicating peers. The Diffie-Hellman calculation involves computing a discrete logarithm using either finite field or elliptic curve arithmetic. When elliptic curve cryptography is used, the conventional choices are to use either prime characteristic or binary curves. This manual selects a prime characteristic curve and requires the use of the 233-bit random ECP group as specified in RFC 4753. When public key certificates are used in IKEv2 for entity authentication certain data must be signed in the IKEv2 exchange. This manual requires that signing be performed using the elliptic curve digital signature algorithm (ECDSA) using SHA-256 as the hash algorithm on the 256-bit prime characteristic curve as specified in RFC 4754.
2.
3.
Part III Guidance Material Chapter 1 Introduction 4.
III-1-25
The authentication exchange of IKEv2 has a payload that is encrypted and integrity-protected. This manual specifies that AES-CBC with 128-bit keys as specified in RFC 3602 be used as the IKEv2 encryption transform. This manual specifies that the encrypted payload be integrity protected using HMAC-SHA-256128 as specified in RFC 4868.
5.
1.7.13 The above suite of algorithms together with the use of AES-GCM for ESP encryption is the Suite-BGCM-128 set specified in RFC 4869. This suite is expected to be available as a commercial-off-the-shelf (COTS) implementation and should provide adequate cryptographic strength beyond 2030. See NIST SP 800-57 for additional guidance on cryptographic algorithm and key size selection. 1.7.14 The use of IKEv2, while offering the advantage of COTS availability and flexibility in signalling algorithms, authentication mechanisms, and other parameters, will result in more overhead than might otherwise be incurred in a custom aviation-specific solution. IKEv2 requires at least four messages to be exchanged to establish a session key for air-ground communications. In addition, the encryption algorithms in IKEv2 and ESP result in message expansion. While this expansion may be negligible for large messages, it will represent a more significant percentage for small messages. While this is a significant consideration for bandwidth-constrained data links, it is expected to be less of an issue when there is a high-speed data link approved for safety services.
Securing air-ground end-to-end communications 1.7.15 Figure III-1-6 depicts the options for securing end-to-end communications in the ATN/IPS air-ground environment. IKEv2 and ESP of IPsec are required to be implemented. This manual also defines options for TLS and for IKEv2 with application-level security. In all cases, this manual defines a default set of cryptographic algorithms.
Air-ground end-to-end network layer security 1.7.16 As described in 1.7.9 to 1.7.14, for air-ground end-to-end network layer security, this manual requires that ESP be implemented along with IKEv2 for key establishment. Figure III-1-6 depicts the CN interfacing to a PKI certificate server. The interface method is considered a local matter. This may be a lightweight directory access protocol (LDAP) interface to a database of X.509 certificates and certificate revocation lists (CRLs) or another certificate management protocol. As noted above, a Suite-B set of algorithms as specified in RFC 4869 is being used for ESP and IKEv2. The United States National Security Agency Suite B certificate and CRL profile identify the certificate management messages over CMS protocol, as specified in RFC 2797, which is the preferred protocol. The actual authentication method used in an administrative domain is a local matter and will depend on the application. IKEv2 permits pre-shared keys or digital certificates to be used with digital certificates considered to be a stronger method. It would be possible to use pre-shared keys in the downlink direction and to use digital certificates in the uplink direction. Since there is no practical way for the MN to independently check a CRL, short-lived certificates could be used in the uplink direction. In the downlink direction, if digital certificates are used, it is recommended that rather than the MN sending an actual certificate, the MN should use the IKEv2 hash and URL method. With this method the MN sends the URL of a PKI certificate server where the CN can retrieve its certificate. This method uses certificates for authentication when strong authentication is required. This is the preferred approach in the end-to-end environment even though it would be possible to use IKEv2 and the extensible authentication protocol (ESP) with an authentication, authorization, and accounting (AAA) infrastructure. It is expected that the PKI bridge concept being developed by the Air Transport Association (ATA) Digital Security Working Group (DSWG) will facilitate operating a PKI on a global basis. Under the PKI bridge concept, each administrative domain may certify to a central bridge rather than each administrative domain cross-certifying with every other administrative domain. (Paragraph 1.7.25 contains more guidance on PKI profiles and certificate policy.)
III-1-26
Correspondent node
PKI certificate server
Home agent
IKEv2/IPsec(ESP), TLS, IKEv2/Appl-Scty
Access router
Access router
Mobile node
Figure III-1-6.
Options for air-ground end-to-end security
Air-ground end-to-end transport layer security 1.7.17 This manual permits ATN/IPS mobile nodes and correspondent nodes to implement the transport layer security (TLS) protocol as specified in RFC 5246. This permits applications that already use TLS to operate in the ATN/IPS air-ground environment. If TLS is used, then the following cipher suite, as defined in RFC 4492, is required: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA 1.7.18 This cipher suite is for: 1. 2. 3. The transport layer security (TLS) protocol. Version 1.0 or 1.1 may be used. Elliptic Curve Diffie Hellman (ECDH) key agreement. Elliptic curve digital signature algorithm (ECDSA) for client authentication.
III-1-27
4.
The advanced encryption standard (AES) with 128 block size in cipher block chaining (CBC) mode for confidentiality. The secure hash algorithm (SHA), version 1 for integrity (i.e. for HMAC).
5.
1.7.19 This cipher suite is selected because it has algorithms in common with those identified for air-ground IPsec and IKEv2. Note that this cipher suite is a required implementation for servers and is also a suite that clients may implement to be compliant with RFC 4492.
Air-ground end-to-end application layer security 1.7.20 This manual permits ATN/IPS mobile nodes and correspondent nodes to implement an application layer security at the IPS dialogue service boundary. This alternative is intended for legacy ATN applications which may already implement an application layer security in the ATN/OSI environment. In this case, mobile nodes and correspondent nodes shall append an HMAC-SHA-256 keyed message authentication code to application messages. HMAC-SHA-256 is already required for ESP and IKEv2 so there is essentially no additional cryptography for this option. The HMAC tag truncated to 32 bits is computed over the user data concatenated with a send sequence number for replay protection. Since IKEv2 is a requirement and if application layer security is used for air-ground security, IKEv2 is again used for key establishment.
Securing access network and mobile IP signalling 1.7.21 Figure III-1-7 depicts options for securing access service provider (ASP) or mobility service provider (MSP) signalling. The distinction between an ASP and an MSP has become useful in IETF working groups examining the use of AAA back-end infrastructures for mobility security. According to RFC 4640, an ASP is a network operator that provides direct IP packet forwarding to and from the end host. An MSP is a service provider that provides mobile IPv6 service. In the figure the AAA-NA service is used for network access and the AAA-MIP server is used for access to mobile IP service.
AAA-MIP server
Home agent
Access service provider (ASP)
MIPv6 security AAA-NA server Network access security
Mobile node
III-1-28 Figure III-1-7. Securing mobile IP signalling
Manual on the ATN using IPS Standards and Protocols ASP or MSP security
1.7.22 Consistent with RFC 3775, this manual requires that IPsec be used specifically for protection of mobile IP signalling in conformance to RFC 4877. RFC 4877 is an update of RFC 3776 and describes how IKEv2 is to be used for automated key management. RFC 4877 in particular describes how IKEv2 with EAP as the authentication method may be used. When extensible authentication is used in IKEv2 there is an additional exchange after the IKE_SA_INIT and IKE_SA_AUTH exchanges. In this case, the MN will not include an authentication payload in the IKE_SA_AUTH exchange but rather will include an EAP payload in the next message. The HA then interacts with the AAA-MIP server to complete the authentication exchange and, if successful, completes the IKEv2 exchange.
Air-ground access network security 1.7.23 Mobile nodes shall implement the security provisions of the access network. The security provisions of an access network are those associated with access control to the network itself and are typically implemented using an AAA infrastructure. 1.7.24 The IETF mobility working groups and other standards development organizations have recognized that, although mobile IPv6 and proxy mobile IPv6 were originally designed without integration with an AAA infrastructure, it may be more efficient to authenticate users using credentials stored at the AAA server. Furthermore, use of an AAA infrastructure may facilitate other bootstrapping functions such as dynamic configuration of other parameters (i.e. the home address and home agent address) in order to accomplish mobility registration. EAP between the MN and authenticator may operate over the access network link level protocol or in conjunction with IKEv2 as described for securing mobile IP signalling. EAP between the authenticator and AAA server operates over RADIUS (RFC 2865) or DIAMETER (RFC 3588).
Public key infrastructure profile and certificate policy 1.7.25 this manual requires that ATN/IPS nodes use the Internet X.509 public key infrastructure certificate and certificate revocation list (CRL) profile as specified in RFC 5280 and the Internet X.509 public key infrastructure certificate policy and certificate practices framework as specified in RFC 3647. This manual notes that the Air Transport Association (ATA) Digital Security Working Group (DSWG) has developed a certificate policy (ATA Specification 42) for use in the aviation community. ATA Specification 42 includes certificate and CRL profiles that are suitable for aeronautical applications. These profiles provide greater specificity than, but do not conflict with, RFC 5280. The ATA Specification 42 profiles are interoperable with an aerospace industry PKI bridge. Interoperability with an operational aerospace and defence PKI bridge will provide the opportunity to leverage existing infrastructure rather than develop an infrastructure unique to the ATN/IPS and will more readily achieve interoperability and policy uniformity in a multinational, multi-organizational aerospace and defence environment.
General guidance for implementation of security 1.7.26 Many government agencies have developed additional guidance and profiles for implementing security. In the United States the NIST 800 series of recommendations is an example of general security implementation guidance covering a broad range of topics. 1.7.27 In the IETF there have been many Internet drafts dealing with security. Two informational RFCs of particular interest are RFC 4942 and RFC 4864. RFC 4942 gives an overview of security issues associated with IPv6. The issues are grouped into three general categories: issues due to the IPv6 protocol itself; issues due to transition mechanisms; and issues due to IPv6 deployment. RFC 4864 notes that network address translation (NAT) is not
III-1-29
required in IPv6 and describes how local network protection (LNP) mechanisms can provide the security benefits associated with NAT. In particular, RFC 4864 describes how the IPv6 tools for privacy addresses, unique local addresses, DHCPv6 prefix delegation, and untraceable IPv6 addresses may be used to provide the perceived security benefits of NAT, including the following: gateway between the Internet and an internal network; simple security (derived from stateful packet inspection); user/application tracking; privacy and topology hiding; independent control of addressing in a private network; global address pool conservation; and multihoming and renumbering. RFC 4864 describes the additional benefits of native IPv6 and universal unique addressing, including the following: universal anyto-any connectivity, auto-configuration, native multicast services, increased security protection, mobility, and merging networks.
1.8
VOICE-OVER INTERNET PROTOCOL (VoIP)
Note. EUROCAE publishes a series of documents on VoIP for ATM which may be used as additional specification material. These documents are numbered ED 136, ED 137, ED 138. 1.8.1 are: The key advantages associated with the use of a packet network for the transmission of digitized voice
bandwidth allocation efficiency; the ability to use modern voice compression methods; associate economics with shared network use; reduced costs; enhanced reliability of packet networks; and the ability to use multiple logical connections over a single physical circuit.
Standards and protocols 1.8.2 There are two standardized frameworks for implementing VoIP, ITU-T H.323 and IETF SIP. Although both protocols may be used for VoIP applications, the original focus of each protocol is different. The focus of H.323 is to handle voice and multimedia calls, including supplementary services, while SIP was designed as a generic transaction protocol for session initiation not bound to any specific media (e.g. audio or video). Details of relevant protocols are described in the following paragraphs.
ITU-T H.323 1.8.3 As shown in Figure III-1-8, H.323 operates in the application layer to support multimedia, data and signalling protocols. Also depicted in Figure III-1-8 are the various protocols used to convey multimedia traffic over TCP/UDP/IP networks.
III-1-30
Multimedia
Data transfer
Signalling
Audio Codecs G.711 G.728 G.729
Video Codecs H.261 H.263 RTCP (real time transport control protocol)
T.120 (real time)
H.450.1 series (supplementary services)
T.130 (audiovisual control)
H.225.0 RAS Q.931 (call signalling)
H.235 (security) H.245 (control signalling)
RTP
UDP (user datagram protocol)
TCP (transfer control protocol)
IP (Internet protocol) v4 or v6
Figure III-1-8. H.323 core architecture
Multimedia 1.8.4 This group of protocols converts between analogue (e.g. voice) and digital signals, which are fed into, or taken from, the UDP/IP network. Some of these protocols include: audio codecs these compress digital voice for low bandwidth transmission, and decompress digital voice received from the network for feeding to the user audio device (e.g. speaker, headphone); video codecs these compress digital video for constrained bandwidth, and decompress digital video received from the network for feeding to the user video device; and RTP (real time transport protocol) and RTP control protocol (RTCP) these are control protocols for the payloads fed into the network. RTP regulates the end-to-end delivery of audio and video in real time over IP networks. RTCP regulates the control services in multimedia transmissions, and monitors the quality of its distribution, including synchronization of receivers.
Data transfer 1.8.5 This class of protocols provides real time, multi-point data communications and application services over IP networks (e.g. collaborative decision-making with video, voice, and data exchange). Data transfers between generic applications and the IP network are processed by the ITU-T T.120 protocol, which can operate over various transports, including PSTN and ISDN.
III-1-31
1.8.6 ITU-T T.130 is a protocol still under development for controlling audio-visual sessions for real time multimedia conferencing, and for ensuring high QoS.
1.8.7
Signalling ITU-T H.225.0 call signalling is used to set up connections and exchange call signalling between H.323 end points (terminals and gateways), which are transported as real time data and carried over the TCP/UDP/IP network. H.225.0 uses ITU-T Q.931 for call set-up and tear-down. ITU-T H.245 control signalling is used to exchange end-to-end messages between H.323 end points. The control messages are carried over H.245 logical control channels, which are relayed between conference session end points. ITU-T H.235 provides security services within the H.323 framework, such as authentication, encryption, integrity and non-repudiation.
ITU-T H.450.1 deals with the procedures and signalling protocol between H.323 entities for the control of supplementary services. Other protocols within the ITU-T H.450 series (i.e. H.450.2-12) provide specific supplementary services (e.g. call transfer, call hold, call waiting, and call priority).
MGCP/MEGACO 1.8.8 Shown in Figure III-1-9 is the SIP protocol suite. SIP is an application layer control protocol that provides advanced signalling and control functionality for large-range multimedia communications. SIP is an alternative to H.323, that establishes, modifies, and terminates multimedia sessions, which can be used for IP telephony. SIP is an important component in the context of other protocols to enable complete multimedia architecture, as shown in Figure III-1-10. These include RTP for real time data transport and QoS assurance, RTSP for controlling streaming media, MEGACO for controlling gateways to the PSTN, and SDP for describing multimedia sessions. These sessions include Internet multimedia conferences, Internet telephone calls, and multimedia distribution over TCP/UDP/IPv4, or IPv6, as shown in Figure III-1-11.
1.9
IPS IMPLEMENTATIONS
Online data interchange (OLDI) 1.9.1 Online data interchange (OLDI) combined with the flight message transfer protocol (FMTP) is a means to enable AIDC operational requirements for the coordination and transfer of aircraft between adjacent air traffic control units. The relationship between AIDC and OLDI messages is described in the Manual of Air Traffic Services Data Link Applications (Doc 9694), Part VI, Chapter 1, Appendix. The OLDI specification does not mandate the implementation of OLDI messages but specifies the requirements that need to be met when implementing such facilities. If OLDI messages are implemented as the result of regulatory provisions, or based on bilateral agreement between air traffic control units, then the requirements outlined as mandatory in this specification for those messages become mandatory for implementation. This is required in order to meet the purposes of the messages and to ensure interoperability between systems. The coordination procedure requires that systems identify whether transfers are in accordance with the Letters of Agreements (LoAs). The process which checks such compliance is referred to in the OLDI specification as the filter. The database used for the filter may include the following:
III-1-32
SIP suite
PINT (interface to PSTN signalling, e.g. Ss7, ATS QSIG) Data Services (e.g. using RTSP) Application and system control AV I/O equipment
Call transfer/conferences/call hold/ call monitoring and other supplementary services
Audio
Video
Extension headers
SIP
Methods
Message body (e.g. SDP)
RTP
TCP IP
Figure III-1-9.
UDP
SIP protocol suite
MEGACO gateway
IP network
PSTN
Figure III-1-10.
VoIP interface to PSTN via MEGACO
III-1-33
SIP server
SIP/TCP or UDP
IP network
IP network
IP network
RTP/UDP
Figure III-1-11.
VoIP with SIP
agreed coordination points; eligible (or ineligible) flight levels which may also be associated with the coordination points; aerodromes of departure; destinations;
agreed direct routes; time and/or distance limits prior to the COP, after which any coordination message is considered non-standard; and any other conditions, as bilaterally agreed. 1.9.2 All items in this list may be combined to define more complex conditions. The format of the messages (see ICAO Procedures for Air Navigation Services Air Traffic Management (PANS-ATM) (Doc 4444) or EUROCONTROL Standard Document for ATS Data Exchange Presentation (ADEXP) to be transmitted and received has to be agreed bilaterally. The address of the ATS units providing the services has to be agreed bilaterally and has to be different from the addresses of the other units to which the ATS units are already connected or planned to be connected. The ATS unit addresses are part of the OLDI message.
Flight message transfer protocol (FMTP) 1.9.3 The flight message transfer protocol (FMTP) is a communications stack based on TCP/IPv6 to support the transmission of OLDI messages. FMTP is a state machine that handles connection establishment and session management. Each FMTP system requires an identification value that is to be exchanged during connection
III-1-34
establishment. The identification values have to be agreed bilaterally and must be different from the values of the other units to which the ATS units are already connected or planned to be connected. 1.9.4 The FMTP specification assumes the transfer of ASCII characters, but implementations of the protocol may extend this support to other character sets or binary transfers. Further guidance material on FMTP is available from EUROCONTROL at the following website: http://www.eurocontrol.int/communications/public/standard_page/com_network.html
Testing OLDI/FMTP 1.9.5 EUROCONTROL has developed a test tool named EUROCONTROL inter centre test tool (ETIC) to validate OLDI/FMTP implementations and build test scenarios. The tool can be made available upon request at: etic@eurocontrol.int.
AMHS 1.9.6 AMHS has already achieved operational status over TCP/IP in the European and North American regions. It is to be noted that the European deployments make use of IPv6 for network interconnections in line with Part II of this document.
______________________
APPENDIX to Part III REFERENCE DOCUMENTS
IETF STANDARDS AND PROTOCOLS The following documents are available publicly at http://www.ietf.org and form part of this manual to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this manual, the provisions of this manual shall take precedence. Request for comments (RFCs) netlmm-mn-ar-if Network-based Localized Mobility Management Interface between Mobile Node and Mobility Access Gateway, May 2007 RFC 768 User Datagram Protocol, August 1980 RFC 793 Transmission Control Protocol (TCP), September 1981 RFC 1006 ISO Transport Service on top of TCP, May 1987 RFC 1122 Requirements for Internet Hosts Communication Layers RFC 1123 Requirements for Internet Hosts Application and Support RFC 1323 TCP Extensions for High Performance, May 1992 RFC 1981 Path Maximum Transmission Unit (MTU) Discovery for IP Version 6, August 1996 RFC 2126 ISO Transport Service on top of TCP, March 1997 RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature Option RFC 2460 Internet Protocol, Version 6 (IPv6) Specification, December 1998 RFC 2474 Definition of Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998 RFC 2475 An Architecture for Differentiated Service RFC 2488 Enhancing TCP over Satellite Channels, January 1999 RFC 2597 Assured Forwarding PHB Group RFC 2858 Multiprotocol Extensions for Border Gateway Protocol (BGP-4), June 2000 RFC 3095 Robust Header Compression (ROHC): Framework and Four Profiles; RTP, UDP, ESP, and Uncompressed RFC 3241 Robust Header Compression (ROHC) over PPP RFC 3246 An Expedited Forwarding PHB (Per-Hop Behaviour) RFC 3602 The AES-CBC Cipher Algorithm and Its Use with IPsec RFC 3647 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework RFC 3775 Mobility Support in IPv6, June 2004 RFC 3963 Network Mobility (NEMO) Basic Support Protocol RFC 4106 The use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP) RFC 4213 Basic Transition Mechanisms for IPv6 Hosts and Routers RFC 4271 A Border Gateway Protocol 4 (BGP-4), January 2006 RFC 4291 IP Version 6 Addressing Architecture, February 2006 RFC 4301 Security Architecture for the Internet Protocol, December, 2005 RFC 4302 Internet Protocol (IP) Authentication Header, December 2005 RFC 4303 IP Encapsulating Security Payload (ESP), December 2005 RFC 4306 Internet Key Exchange (IKEv2) Protocol, December 2005 RFC 4307 Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2), December 2005 RFC 4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification, March 2006
III-APP-1
III-APP-2 RFC 4492 RFC 4555 RFC 4753 RFC 4754 RFC 4830 RFC 4831 RFC 4835 RFC 4843 RFC 4868 RFC 4877 RFC 4996 RFC 5246 RFC 5280
Manual on the ATN using IPS Standards and Protocols Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS), May 2006 IKEv2 Mobility and Multihoming Protocol (MOBIKE), June 2006 Encryption Control Protocol (ECP) Groups for IKE and IKEv2 IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA) Problem Statement for Network-Based Localized Mobility Management (NETLMM), April 2007 Goals for Network-Based Localized Mobility Management (NETLMM), April 2007 Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) ,April 2007 An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID) Using HMAC-SHA-256, HMAC-SHA-384 and HMAC-SHA-512 with IPsec Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture Robust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TP) The Transport Layer Security (TSL) Protocol Version 1.2 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
RELEVANT ICAO PUBLICATIONS In the event of a conflict between this manual and the provisions in Annex 10, the provisions of Annex 10 shall take precedence. Annex 2 Rules of the Air Annex 3 Meteorological Service for International Air Navigation Annex 10 Aeronautical Telecommunications, Volume III Communication Systems, Part I Digital Data Communication Systems Annex 11 Air Traffic Services Procedures for Air Navigation Services Air Traffic Management (PANS-ATM) (Doc 4444) ICAO Manuals Manual of Air Traffic Services Data Link Applications (Doc 9694) Manual of Technical Provisions for the Aeronautical Telecommunication Network (ATN) (Doc 9705) Comprehensive Aeronautical Telecommunication Network (ATN) Manual (Doc 9739) Manual on Detailed Technical Specifications for the Aeronautical Telecommunication Network (ATN) using ISO/OSI Standards and Protocols (Doc 9880) (in preparation)
EUROCONTROL SPECIFICATIONS The following documents are available publicly at http://www.eurocontrol.int/ses and form part of this manual to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this manual, the provisions of this manual shall take precedence. EUROCONTROL-SPEC-0100-EUROCONTROL Specification of Interoperability and Performance Requirements for the Flight Message Transfer Protocol (FMTP), Edition 2.0, June 2007 EUROCONTROL-SPEC-0106-EUROCONTROL Specification for On-Line Data Interchange (OLDI), Edition 4.1, January 2008
END

ATN

Uploaded by

Copyright:

Available Formats

ATN

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ATN

Uploaded by

Copyright:

Available Formats

Doc 9896

Approved by the Secretary General and published under his authority

First Edition 2010

International Civil Aviation Organization

Approved by the Secretary General and published under his authority

First Edition 2010

International Civil Aviation Organization

First edition 2010

Appendix to Part III.

ABBREVIATIONS AND TERMS

Manual on the ATN using IPS Standards and Protocols

Manual on the ATN using IPS Standards and Protocols

Application layer OSI/IPS convergence

Application layer OSI/IPS convergence

Local or intra-domain subnetwork Inter-domain subnetwork

Local or intra-domain subnetwork

ATN/IPS protocol architecture

INTERNET LAYER REQUIREMENTS

TRANSPORT LAYER REQUIREMENTS

Part I Detailed Technical Specifications Chapter 2 Requirements 2.5 SECURITY REQUIREMENTS

Part I Detailed Technical Specifications Chapter 2 Requirements

APPENDIX to Part I Autonomous System (AS) Numbering Plan

Manual on the ATN using IPS Standards and Protocols

Manual on the ATN using IPS Standards and Protocols

LEGACY ATN APPLICATIONS

Manual on the ATN using IPS Standards and Protocols

ATN IPS upper layers diagram

II-1-4 Table II-1-2. Service D-START

Dialogue service definition

Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction

Sequence of DS primitives for one dialogue at one DS-user

Manual on the ATN using IPS Standards and Protocols

Fixed part 0 0 ATNPKT version DS primitive

8 App tech type more

Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction

Presence field details

ATSC routing class: 0 no traffic type policy preference 1 A 2 B 3 C 4 D 5 E 6 F 7 G 8 H 9 255 reserved

Originator of the abort: 0 user (default value) 1 provider 2 255 reserved

UDP: 0 to 8 184 (+16) TCP: variable size (+16)

User data (provided by the local DS-user)

Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction

Manual on the ATN using IPS Standards and Protocols

Sequence number format

II-1-12 2. The RER as defined below: Value 0 1 2

Manual on the ATN using IPS Standards and Protocols

RER level Low Medium High

IPS DS ULCS DS parameter mapping

Destination port number

Called presentation address Calling peer ID

Destination IP address Calling peer ID

Source port number

Calling presentation address DS-user version number

Source IP address Content version

Manual on the ATN using IPS Standards and Protocols

DS parameter visible to the DS-user Security requirements IP header

00 Accepted 01 Rejected (permanent) 02 Rejected (transient)

0 User 1 Provider (default) 2-255 Reserved

1.4.40 Table II-1-6:

ATNPKT parameters for DS protocol messages

Part II Internet Protocol Suite (IPS) Applications Chapter 1 Introduction