ATTF/4-IP/5 International Civil Aviation Organization

Fourth ATN Transition Task Force Meeting Mumbai, India, 8 - 12 April 2002

Agenda Item 10: Any Other Business

INFORMATION FOR THE INCORPORATION OF THE IP ( PROTOCOL) IN THE ATN

(Presented by Japan)

Summary

This paper presents information for the incorporation of the (IP) into the ATN environment.

1. Introduction

1.1 Internet Protocol (IP) is recently used worldwide. As the ATN is based on the ISO OSI Standards, there is no direct interoperability between IP and ATN.

2. Discussion

2.1 Considering the worldwide use of the IP (Internet Protocol) technology, ATNP WG had started investigation how to incorporate the IP into the ATN environment. At the ATNP WG Meetings in Phuket, Thailand, 12-20 March 2002, there were considerable discussions made. Though many issues have to be discussed at the next meeting, this paper presents a Draft Position Statement of WG B as in the Attachment-1, as well as some related information on this matter in Attachment-2.

3. Action by the Meeting

3.1 The meeting is invited to note the information provided in this paper.

Attachment-1: “Draft Position Statement of ATNP WG B on the use of IP Subnetworks as part of the ATN”; Appendix E to the ICAO ATNP Draft Report of the Third Joint Working Group Meeting (JWG/3) dated 20 March 2002

Attachment-2: “Information for the incorporation of the IP (Internet Protocol) in the ATN”; hardcopies of slides in Microsoft Power Point format

Attachment 1 to IP/5

DRAFT POSITION STATEMENT OF ATNP WG B ON THE USE OF IP SUBNETWORKS AS PART OF THE ATN

Considerations

1. The ATN was designed to embrace all air-ground and ground-ground communications technologies. IP subnetworks can and should be available for use by the ATN.

2. Non-ICAO Air-Ground networks are being developed that use IP for non-safety airborne applications. Where the Quality of Service provided is acceptable for ATC Applications, such networks could be useable as part of the ATN.

3. The ICAO specification for the ATN uses OSI protocols, specifically CLNP and TP4, to support and reliable end-to-end connection mode communications. ICAO Applications and Upper Layers Communications Services including Security Services depend upon the availability of TP4. There has been considerable industry investment, of both resources and time, in these protocols, including the development and validation of the ICAO specification and the development and certification of ATN compliant products to ensure that they meet the safety, mobility and QoS requirements of the ATN applications.

4. TCP/IP communications protocols although functionally similar cannot replace the OSI protocols specified by ICAO without a similar level of investment in time and effort to produce certified products. Off the shelf implementations are not acceptable as they neither include additional features deemed necessary for ATC use nor have they been developed using the lifecycles and methodologies appropriate for certifiable software.

5. The ATN Mobile strategy permits mobile platforms to :

• act as a subnetwork and receive incoming connections on well known and statically assigned network addresses, and to make outgoing connections to ground systems; • seamlessly move between different mobile networks without disrupting end-to-end communications; • simultaneously use more than one mobile network; and • support Policy Based Routing Decisions in order to choose between alternative routes to the same destination.

Mobile IP strategies are directed to the support of single systems and support only the first two of the above functionalities. Mobile IP also introduces a special point into the network (the Home Agent) and has issues associated with a potential single point of failure, inefficient routing due to the necessity of routing through a Home Agent, and security due to apparent “spoofing” by a mobile system.

Attachment 1 to IP/5 2

Conclusions:

It is appropriate, on both economic and technical grounds, to continue the use of CLNP and TP4 as the ATN core protocols whilst developing specifications to enable the use of IP subnetworks as ATN subnetworks for both ground-ground and air-ground use, where there is industry demand.

1. ATNP WGB SG1 will develop SARPs to permit the use of ground-ground IP subnetworks as ATN subnetworks for both BIS to BIS and within local domains.

2. Should demand ever develop, ATNP WGB SG1 could develop SARPs to enable the use of Air- Ground IP subnetworks for Airborne to Air-Ground Router interconnections.

In order to achieve the above, ATNP WGB SG-1 will develop SARPs and Guidance Material for an IP SNDCF to support the encapsulation of CLNP packets for their transit across an IP subnetwork. An IP subnetwork will have to meet the existing performance requirements that the ATN Technical Provisions already define. There is no intention that the public "Internet" should be used as an ATN subnetwork; the SARPs will apply to private IP subnetworks only.

AgendaAgenda ItemItem 10:10: AnyAny OtherOther BusinessBusiness InformationInformation forfor thethe incorporationincorporation ofof thethe IPIP (Internet(Internet Protocol)Protocol) inin thethe ATNATN

AttachmentAttachment 22 toto IP/5IP/5

Fourth ATN Transition Task Force Meeting Mumbai, India, 8-12 April 2002

Naoto Sakaue Advisor to Japan Civil Aviation Bureau, Japan JCAB TableTable ofof ContentsContents • Summary • Detailed Explanation – Fully ATN Based Communication – Fully IP Based Communication – IP as an ATN Subnetwork – AMHS fully based on the IP • Some Considerations • Further Issues • Conclusions

JCAB 1 SummarySummary • ICAO ATN SARPs – Communication based on the ISO OSI • Demand for the IP based protocol – IP (Internet Protocol) • RFC (Request for Comments) 791/950/919/922, etc. • IP is the Internet Protocol used worldwide • It is not included in Doc 9705 SV-5 (Internet Communication Service) – There is no direct interoperability between ATN and IP • ATN : CLNP in the Network Layer / TP4 in the Transport Layer • IP : IP in the Network Layer / TCP in the Transport Layer

– OSI : Open systems interconnection – CLNP : Connection-Less Network Protocol – TP4 : (Connection Oriented) Transport Protocol (Class 4) JCAB 2 SummarySummary • Three possibilities – Fully ATN Based Communication • ATN Compliant • KEYWORDS: ATN Stack, OSI, CNLP, TP4 – Fully IP Based Communication • IP in lieu of ATN (NOT ATN Compliant) • KEYWORDS: IP Stack, TCP/IP – IP as an ATN Subnetwork • ATN Compliant • KEYWORDS: Tunneling, Capsulation (Encapsulation/Decapsulation)

– TCP : Transmission Control Protocol – IP : Internet Protocol JCAB 3 SummarySummary • 1st case: Fully ATN Based Communication – ATN Compliant – KEYWORDS: ATN Stack, OSI, CNLP, TP4 ATN ATN ATN ATN End System Router Router End System

ATN ATN Applicatio Applicatio n n

ATN ATN ATN ATN

ATN ATN ATN

Intra- INTER- Intra- Domain Domain Domain JCAB 4 SummarySummary • 2nd case: Fully IP Based Communication – IP in lieu of ATN (NOT ATN Compliant) – KEYWORDS: IP Stack, TCP/IP

End System IP IP End System Router Router

ATN ATN Applicatio Applicatio n n

IP IP IP IP

IP IP IP

NOTE: There is no ATN Domain Concept in this case. JCAB 5 SummarySummary • 3rd case: IP as an ATN Subnetwork – ATN Compliant – KEYWORDS: Tunneling, Capsulation(En/De- capsulation) ATN ATN ATN ATN End System Router Router End System

ATN ATN Applicatio Applicatio n n ATN ATN ATN ATN IP IP ATN ATN IP IP

IP ATN IP

Intra- INTER- Intra- Domain Domain Domain JCAB 6 SummarySummary • Recent ATNP WG Meeting (March 2002, Phuket) – Fully ATN Based Communication • All Air/Ground and Ground/Ground Applications • Context Management, System Management, Security, Directory • AMHS planning in the Asia/Pacific region (including FAA) – Fully IP Based Communication • No requirement for the A/G and AIDC Application • Some requirement by Eurocontrol and SITA for the investigation of the AMHS fully based on the IP instead of ATN • There are many issues and WG continues investigation JCAB 7 – IP as an ATN Subnetwork SummarySummary • Draft Position Statement of ATNP WG B (March 2002) – Considerations • ATN uses OSI protocol (CNLP and TP4) • There has been considerable industry investment on ATN • TCP/IP protocols cannot replace the OSI protocol easily • ATN Mobile Routing cannot be satisfied by Mobile IP strategies – Conclusions • To continue the use of CNLP and TP4 as the ATN core protocols • To use IP subnetworks as ATN subnetworks for A/G and G/G use – To use G/G IP subnetworks as ATN subnetworks for JCAB both BIS to BIS and within local domains 8 – To use A/G IP subnetworks between Airborne Router DetailedDetailed explanationexplanation • Fully ATN Based Communication • Fully IP Based Communication • IP as an ATN Subnetwork • AMHS fully based on the IP

JCAB 9 FuFullylly ATNATN BaseBasedd CommunicationCommunication • ATN Full Stack in End System ATN AMHS 7. Application Application Layer ACSE RTSE ULCS 6. Presentation Presentation Layer 5. Session Session Layer 4. Transport COTP (TP4) COTP (TP4) Layer ATN CLNP/ES-IS CLNP/ES-IS Application 3. Network Layer SNDCF SNDCF ATN (TR) 2. Datalink Datalink Datalink ATN (NW) Layer 1. Physical Physical Physical (DL/PHY) Layer A/G AMHS Symbol Application End System for ATN or AIDC End System End System JCAB 10 FullyFully ATNATN BasedBased CommunicationCommunication • ATN Router in ATN Full Stack

CLNP/ES- IS IS- IS/IDRP SNDCF

Datalink ATN (NW)

Physical (DL/PHY)

ATN Symbol Router for ATN Router

JCAB 11 FullyFully ATNATN BasedBased CommunicationCommunication • ES-ES Connection in ATN Full Stack (ICAO ATN) ATN ES ATN Router ATN Router ATN ES (ATN Stack) (ATN Stack) (ATN Stack) (ATN Stack)

ATN ATN Application Application

ATN (TR) ATN (TR)

ATN (NW) ATN (NW) ATN (NW) ATN (NW)

(DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

ATN ATN ATN

Intra- INTER-Domain Intra- Domain Domain JCAB 12 FullyFully IPIP BasedBased CommunicationCommunication • Comparison between OSI Full Stack and IP (TCP/IP) Full Stack AMHS AMHS 7. Application ACSE RTSE ACSE RTSE Layer 6. Presentation Presentation Presentation Layer 5. Session Session Session Layer 4. Transport COTP (TP4) TCP (UDP) Layer ATN CLNP/ES-IS Application IP 3. Network SNDCF TCP (TR) Layer 2. Datalink Datalink Datalink IP (NW) Layer 1. Physical Physical Physical (DL/PHY) Layer ATN (AMHS) IP Symbol End System End System for IP (OSI Full (IP Full End System JCAB Stack) Stack) 13 FullyFully IPIP BasedBased CommunicationCommunication • ES in IP Full Stack (NOT connect with ATN) ATN ES ATN Router ATN Router ATN ES (IP Stack) (ATN Stack) (ATN Stack) (IP Stack)

ATN ATN Application Application

TCP (TR) TCP (TR)

IP (NW) ATN (NW) ATN (NW) IP (NW)

(DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

IP ATN IP

Intra- INTER-Domain Intra- Domain Domain JCAB 14 FullyFully IPIP BasedBased CommunicationCommunication • IP only World (NOT compliant with ICAO ATN) ATN ES IP Router IP Router ATN ES (IP Stack) (IP Stack) (IP Stack) (IP Stack)

ATN ATN Application Application

TCP (TR) TCP (TR)

IP (NW) IP (NW) IP (NW) IP (NW)

(DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

IP IP IP

NOTE: There is no ATN Domain Concept in this case. JCAB 15 IPIP asas anan ATNATN SubnetworkSubnetwork • IP as Subnetwork (under investigation in ICAO ATNATN) ES ATN Router ATN Router ATN ES (ATN/IP (ATN/IP (ATN/IP (ATN/IP Stack) Stack) Stack) Stack) ATN ATN Application Application

ATN (TR) Tunneli Tunneli ATN (TR) ng ng ATN (NW) ATN (NW) ATN (NW) ATN (NW) ATN/IP ATN/IP ATN/IP ATN/IP (DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

IP ATN IP

Intra- INTER-Domain Intra- Domain Domain JCAB 16 IPIP asas anan ATNATN SubnetworkSubnetwork • Tunneling of ATN Data through IP by Capsulation

ATN ES IP Original ATN Encapsulat Format Original ATN Data ion Data Intra-Domain IP Original ATN Network Format Data IP ATN Original ATN Decapsulat Original ATN Router Format Data Data ion

INTER-Domain Original ATN Network Data

IP ATN Original ATN Encapsulat Original ATN Router Data Format ion Data Intra-Domain IP Original ATN Network Format Data

ATN ES IP Decapsulat Original ATN Format Original ATN Data ion Data JCAB 17 IPIP asas anan ATNATN SubnetworkSubnetwork • Comparison between IP Full Stack and ATNP/IP Stack AMHS AMHS 7. Application Layer ACSE RTSE ACSE RTSE 6. Presentation Presentation Presentation Layer 5. Session Session Session Layer 4. Transport TCP (UDP) COTP (TP4) Layer ATN CLNP/ES-IS Application IP 3. Network ATN (TR) Layer IP SNDCF 2. Datalink Datalink Datalink ATN (NW) Layer ATN/IP 1. Physical Physical Physical (DL/PHY) Layer IP ATN/IP Symbol for End System End System ATN/IP (IP Full (ATN/IP End System JCAB Stack) Stack) 18 IPIP asas anan ATNATN SubnetworkSubnetwork • ATN Router in ATN Full Stack and ATN/IP Stack

CLNP/ES- CLNP/ES- IS IS IS- IS- IS/IDRP IS/IDRP SNDCF IP SNDCF

Datalink ATN (NW) Datalink ATN (NW) ATN/IP Physical (DL/PHY) Physical (DL/PHY)

ATN Symbol ATN/IP Symbol for Router for ATN Router ATN/IP Router (ATN/IP Router Stack)

JCAB 19 IPIP asas anan ATNATN SubnetworkSubnetwork • Intra-Domain IP Network ATN ES ATN Router ATN Router ATN ES (ATN/IP (ATN/IP (ATN/IP (ATN/IP Stack)ATN Stack) Stack) Stack)ATN Application Application ATN (TR) ATN (TR) ATN (NW) ATN (NW) ATN (NW) ATN (NW) ATN/IP ATN/IP ATN/IP ATN/IP (DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

IP ATN IP

ATN Intra-DomainINTER-Domain Intra-Domain ES

ATN IP Router IP Route IP Router r Route IP r

IP

JCAB 20 IPIP asas anan ATNATN SubnetworkSubnetwork • INTER-Domain (and Intra-Domain) IP Network (Bi- ATN ES ATN Router ATN Router ATN ES lateral(ATN/IP agreement) (ATN/IP (ATN/IP (ATN/IP Stack)ATN Stack) Stack) Stack)ATN Application Application ATN (TR) ATN (TR) ATN (NW) ATN (NW) ATN (NW) ATN (NW) ATN/IP ATN/IP ATN/IP ATN/IP (DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

CLNP/ES-IS IP IP IP CLNP/ES-IS IS-IS/IDRP IS-IS/IDRP ATNIntra-DomainINTER-Domain Intra-Domain ATN IP SNDCF IP SNDCF Datalink Datalink PhysicalIP IP PhysicalIP Router

IP IP Route Router ATN IP IP ATN ES r ES

JCAB 21 IPIP asas anan ATNATN SubnetworkSubnetwork • INTER-Domain (and Intra-Domain) IP Network (Bi- lateralATN/IP agreement) End System (ATN/IP Stack)ATN Application

Presentation ATN/IP Session Router ATN COTP (TP4) (ATN/IP CLNP/ES-IS CLNP/ES-ISStack) IS-IS/IDRP IP SNDCF IP SNDCF Datalink Intra- Datalink INTER- Physical Domain Physical Domain IP IP IP

JCAB 22 AAMHSMHS fullyfully basedbased onon thethe IPIP • IP only World (NOT compliant with ICAO ATN) ATN ES IP Router IP Router ATN ES (IP Stack) (IP Stack) (IP Stack) (IP Stack)

AMHS AMHS

TCP (TR) TCP (TR)

IP (NW) IP (NW) IP (NW) IP (NW)

(DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

IP IP IP

NOTE: There is no ATN Domain Concept in this case. JCAB 23 AAMHSMHS fullyfully basedbased onon thethe IPIP • ATN/AMHS and IP/AMHS (ES-ES connection is not operableATN ES) ATN Router ATN Router ATN ES (ATN Stack) (ATN Stack) (ATN Stack) (ATN Stack)

AMHS AMHS ATN (TR) ATN (TR) ATN (NW) ATN (NW) ATN (NW) ATN (NW) (DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY)

ATN ATN ATN Intra-DomainINTER-Domain Intra-Domain

IP IP IP

AMHS AMHS TCP (TR) TCP (TR) IP (NW) IP (NW) IP (NW) IP (NW) (DL/PHY) (DL/PHY) (DL/PHY) (DL/PHY) ATN ES IP Router IP Router ATN ES (IP Stack) (IP Stack) (IP Stack) (IP Stack) JCAB 24 SomeSome ConsiderationsConsiderations • Whose property? – AMHS (ATN ES) – AMHS Terminal (User Agent) – ATN Router (BIS) – ATN Network (domestic) – ATN Network (international) – ATN ES for Air/Ground Application – Air/Ground Subnetwork • Regional ATN Backbone – AMHS – AIDC – Air/Ground

JCAB 25 SomeSome ConsiderationsConsiderations • Whose property? (ATN Concept) : one example Service Provider AMHS ES ATN Router ATN ATN G/G Route Route ES r r State A Regional Backbone Network ATN A/G ATN Router A/G ES Route ES ATN r A/G Route A/G ES r AMHS ES ES

G/G AMHS G/G A/G ES ES ES ES State B JCAB 26 SomeSome ConsiderationsConsiderations • Whose property? : one example Service Provider the AMHS What is vice? ES ATN AMHS Ser ATN Router Route G/G ATN r ES Router State A Regional Backbone Network ATN A/G ATN Router A/G ES Route ES ATN r A/G Route A/G ES r AMHS ES ES

G/G AMHS G/G A/G ES ES ES ES State B JCAB 27 FurtherFurther IssuesIssues • IP as an ATN Subnetwork – IPv4 or IPv6 – Security Issues • AMHS fully based on the IP – Who will agree the Non ICAO ATN specification – More investigation, even if Non ICAO ATN • Interoperability between ATN/AMHS and IP/AMHS • Migration from AFTN to IP/AMHS (Gateway?) • When the SARPs will be completed? • Cost Benefit Analysis • Next ATNP WG – September-October, 2002 in Toulouse, JCAB 28 France (tentative) ConclusionsConclusions • Make sure which he is speaking – Fully ATN Based Communication : ATN Compliant • KEYWORDS: ATN Stack, OSI, CNLP, TP4 – Fully IP Based Communication : NOT ATN Compliant • KEYWORDS: IP in lieu of ATN, IP Stack, TCP/IP – IP as an ATN Subnetwork : ATN Compliant • KEYWORDS: Tunneling, Capsulation (Encapsulation/Decapsulation) • Watch the further activities by ATNP WG on the IP • Remember the ATN policy – Common infrastructure for all the ATN application • Regional ATN Backbone is the common network for ATN – End to End Connection • Between one ATN End System and another ATN End JCAB System 29 S i dd i l dS