Transmission By

CNS SG/22 – WP/05 Agenda Item 3.1 02/07/18

International civil aviation organization

TWENTY SECOND MEETING OF THE COMMUNICATIONS/NAVIGATION AND SURVEILLANCE SUB-GROUP (CNS SG/22) OF APANPIRG

Bangkok, Thailand, 16 - 20 July 2018

Agenda Item 3: Aeronautical Fixed Service (AFS)

3.1 Review Report of the Fifth Meeting of the Aeronautical Communication Services Implementation Coordination Group (ACSICG/5) including the outcome of the outcome of CRV Workshop & VPN Operations Group meetings (CRV OG/3 & CRV-OG/4)

OUTCOMES OF THE FIFTH MEETING OF THE AERONAUTICAL COMMUNICATION SERVICES IMPLEMENTATION COORDINATION GROUP (ACSICG/5)

(Presented by the Secretariat)

SUMMARY

This paper presents the outcomes of the Fifth Meeting of the Aeronautical Communication Services Implementation Coordination Group (ACSICG/5) which was held in Bangkok, Thailand, from 12 to 14 June 2018.

1. INTRODUCTION

1.1 The Fifth Meeting of the Aeronautical Communication Services (ACS) Implementation Co-ordination Group (ACSICG/5) of APANPIRG was held at ICAO Regional Office, Bangkok, Thailand, from 12 to 14 June 2018.

1.2 The Meeting was attended by 61 participants from Bangladesh, Bhutan, Cambodia, China, Hong Kong China, Macao China, Fiji, India, Indonesia, Japan, Malaysia, New Caledonia, New Zealand, the Philippines, Republic of Korea, Singapore, Sri Lanka, Thailand, USA and FREQUENTIS.

CNS SG/22 – WP/05 -2- Agenda Item 3.1 02/07/18

1.3 The meeting considered 12 working papers and 14 information papers. The papers and report of ACSICG/5 meeting are available at: https://www.icao.int/APAC/Meetings/Pages/2018-ACSICG5.aspx

2. DISCUSSION

Review outcome of APANPIRG/28 and other relevant meetings

2.1 The meeting reviewed the outcome of APANPIRG/28 (WP/02) and CNS SG/21 meetings on aeronautical communication and works accomplished by the Fourth Meeting of ACSICG.

2.2 The meeting reviewed and updated the ATN/AMHS/AIDC implementation status table based on the outcome of APA TF/4 meeting held in early April 2018 and the latest information on planning and implementation of ATN/AMHS presented to the meeting. The updated implementation status was consolidated and provided in Appendix A to this Report.

ATN/AMHS implementation progress

2.3 The meeting reviewed implementation issues and status updates from a number of States on ATN/AMHS implementation progress. The updated implementation status was consolidated in the same Appendix A to this paper.

Air Traffic Service Message Handling Service (AMHS) over IPS

3.2 The USA proposed to replace existing Aeronautical Telecommunication (ATN) Router usage based on ICAO Doc. 9880 with the Internet Protocol (IP) Router as specified in ICAO Doc. 9896, ATN Internet Protocol Suites (IPS) between Backbone Boundary Intermediate System (BBIS) Administrations.

3.3 The BBIS and BIS Administrations were encouraged to use IPS routers for AMHS connections. The BBIS States were mandated to use ATN routers as specified in ICAO Doc. 9880 and that was due to the need of Inter-Domain Routing Protocol (IDRP) to route traffic. As the APAC Region moving forward to utilize the Common aeRonautical Virtual Private Network (CRV), Multi-Protocol Label Switching (MPLS) will be the primary routing protocol for the network. Thus, ATN router's IDRP function will be disable. BBIS States should connect with each other using IPS router when CRV is utilized. Therefore, the meeting recommended to gradually phase out the use of ATN router to reduce operational cost while improving service restore time as less equipment are involved. In view of the foregoing, the meeting endorsed the following Draft Conclusion for consideration by CNS SG/22 Meeting:

-3- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718

Draft Conclusion ACSICG/5/1 – Using IPS Router between BBIS Administrations

What: Utilize IPS router and phase out X.25 and IP SNDCF (ATN) Expected impact: router by allowing IPS routers to inter-connect between BBIS ☐ Political / Global Administrations when CRV or other inter-regional IP networks being ☒ Inter-regional utilized. ☐ Economic ☐ Environmental ☒ Ops/Technical Why: Compliance with ICAO Doc. Follow-up: ☒Required from States 9896 When: 20-July-18 Status: Draft to be adopted by PIRG Who: ☒CNS Sub group ☒APAC States ☐ICAO APAC RO ☐ICAO HQ ☐Other: XXXX

3.4 In this connection, the meeting also considered necessary to review and update the Strategy for Implementation of Communications systems to support Air Navigation Service adopted through Conclusion APANPIRG/28/18.

ATSMHS Transition from X.25 Protocol to IP Suites

3.5 CRV network provides IP interface only which requires change from the existing AMHS connections with X.25 protocol to the IP network protocol. For example, China has implemented the AMHS connections with Hong Kong China, India and Republic of Korea over X.25 protocol (ATN Router) while connection with Thailand over IP protocol (IP Router). Currently, sample of Technical Memorandum Cooperation (TMC) provided by ICAO includes Bilateral Test Procedures of XOT over VPN/Internet, X.25 over leased circuit and X.400 P1 TP0 over TCP/IP.

3.6 For existing AMHS connections over X.25 (ATN Router) that IP connectivity test had not been conducted previously, additional IP link connectivity tests shall be carried out before migration from X.25 to IP protocol when joining the CRV. These additional tests shall be supplemented in the TMC. Accordingly, the meeting formulated the following draft Conclusion for consideration by CNS Sub-group:

Draft Conclusion ACSICG/5/2 - Arrangement for conducting IP connectivity test What: That, considering the need for supporting the procedure of the Expected impact: X.25 protocol transition to IPS and no IP connectivity test having ☐ Political / Global been conducted for AMHS connections over X.25 using ATN ☐ Inter-regional Router. In such case, States/Administrations are urged to conduct IP ☐ Economic connectivity tests when joining the CRV or through other IP network. ☐ Environmental These additional tests may be agreed bilaterally through additional ☒ Ops/Technical agreement for IP connectivity test as supplements to the TMC between Administrations.

Why: Need to alternate simple arrangements for Administration to conduct required test without Follow-up: ☒ Required from States need to amendment TMC When: 20-Jul-18 Status: Adopted by Subgroup Who: ☒ CNS SG ☒ APAC States ☐ ICAO APAC RO ☐ ICAO HQ ☐ Other: XXXX

CNS SG/22 – WP/05 -4- Agenda Item 3.1 02/07/18

AMHS FTBP for MET IWXXM Data

3.7 The meeting reviewed WP/2 presented by the United Kingdom/AMC Operator at AFSG/22 meeting of the European Air Navigation Planning Group (EANPG) on considerations for AMHS FTBP to support distribution of IWXXM data. In this regard, the meeting recalled that APANPIRG/28 adopted Conclusion 28/16 regarding Upgrade AMHS to support IWXXM traffic in the APAC Region.

3.8 The meeting discussed the various issues on FTBP highlighted in the paper and took a note of the report of AFSG/22 meeting for the paper. The meeting considered the following three issues:

1) Security: MET User has to make arrangement for scanner, screener or filter. Attachments to AMHS as a FTBP could be attacked with virus or malware. There are two options to prevent the virus/malware infection to the system:

a) scan all attachments at Message Transfer Agent (MTA) and isolate/remove infected files before distribute to end users; or

b) scan at user terminals. per industry, install antivirus functions and scan at MTA would delay processing by 10-20% while install antivirus at user terminals might have the infected files to be spread into the user’s network.

2) Bandwidth: to analyze the AMHS User capability and its potential bandwidth requirement. This is due the study by NATS UK that was reported AFSG/22 concluded that IWXXM attachment as FTBP would result in fivefold increasing of bandwidth when compared to legacy format - TAC. TAC will be continued to be distributed in addition to IWXXM distribution. Thus, the bandwidth requirement from MET generated system to AMHS will be six times larger than current requirement.

3) AMHS User capability: need for iWXXM generated systems to be registered with AMC. States/Administrations are required to verify with AMC before distribute iWXXM data. This is a critical step to ensure the readiness of the service.

Support for the exchange of IWXXM formatted MET data via AMHS

3.9 New Zealand informed the meeting that the NZ MetService had established a Disaster Recovery (DR) centre in Auckland. This DR centre uses a P3 AMHS connection to the Airways AMHS system. The connection was deployed operationally in July 2016. The replacement of the NZ MetService’s existing IP-based AFTN connection from its main operational centre in Kelburn with a P3 AMHS connection to the Airways AMHS system is scheduled for July 2018.

3.9.1 Testing of the Kelburn AMHS connection to the Airways Development AMHS system was progressing well and has included the exchange of attachments in the form of File Transfer Body Parts (FTBPs). The Kelburn AMHS connection is due to go live operational by the end of July 2018. As such, the NZ MetService is positioned for the exchange of Meteorological (MET) data in IWXXM format via AMHS, well ahead of the 2020 deadline.

-5- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718

3.9.2 Operational use of IWXXM is of course dependent on the organizations that they exchange data with having:

 AMHS capabilities/connectivity; and  The ability to generate and/or consume MET data in IWXXM format.

3.9.3 Provision of Graphical MET products in Pre-Flight Briefings and some other initiatives for the provision of aeronautical-related data were also introduced in the paper.

Report on the outcomes of CRV OG/3 and CRV OG/4 meetings (WP/06)

4.1 The Secretariat presented the reports on CRV achievements resulted from CRV OG/3 and CRV OG/4 meetings.

CRV OG/3

4.2 The Third Meeting of the Common Regional VPN Operations Group of APANPIRG was held from 18 to 20 December 2017 in Bangkok. The document and meeting report of CRV OG/3 are available on the ICAO APAC meeting website at: https://www.icao.int/APAC/Meetings/Pages/2017-CRV_OG3.aspx

4.2.1 The main achievements of CRV OG/3 meeting are listed below:

- Noted Action Item 54/20 of DGCA Conf//54 urging States/Administrations to implement CRV project by 2020 in the APAC Region;

- The transition period to CRV from 2018 to 2020 should be harmonized as much as possible between stakeholders in order to achieve the benefits of CRV implementation;

- Confirmed CRV Pilot Project Test Plan/Pilot Service Acceptance Testing;

- Technical Trial on APAC CRV was successfully conducted by Hong Kong China and Thailand in December 2017 to verify the operational readiness of the APAC CRV;

- Initially Reviewed VoIP Interface Control Document (ICD) presented by USA;

- Synchronized the starting and ending dates of CRV contract commencing 1 January 2018 and would end on 31 December 2023 for the initial 5-year period and plus 5 one- year term option. Any States join after 31 December 2023, the CRV program needs to be approved by mutual agreement between ICAO / CRV OG and PCCW Global. Additional charges may be incurred by the new users and the minimum contract commitment should be no less than 12 months;

- Final review of the CRV engineering package;

- Reviewed the CRV implementation plan Ver. 0.5; and

- COM centres in APAC Region may connect with Khabarovsk and/or with Irkutsk centres via CRV.

CNS SG/22 – WP/05 -6- Agenda Item 3.1 02/07/18

CRV OG/4

4.3 The Fourth Meeting of the Common aeRonautical VPN Operations Group of APANPIRG hosted by Fiji Airports and the Civil Aviation Authority of Fiji was held from 18 to 20 April 2018. In conjunction with the meeting, a CRV Workshop focusing solution for Pacific States was conducted on 16- 17 April 2018. The document and meeting report of CRV OG/4 are provided on the ICAO APAC meeting website at: https://www.icao.int/APAC/Meetings/Pages/2018-CRV-WS---CRV-OG4.aspx

4.3.1 The meeting elected Mr. Kelepi Dainaki, Manager Air Navigation Engineering Services from Fiji Airports as co-chair for the CRV Operation Group.

4.3.2 The main achievements of CRV OG/4 meeting are listed below:

- Noted that a mini CRV workshop was conducted in March 2018 in Cairo and coordination for CRV issues with MID Region would be postponed to the next OG meeting (CRV OG/5), until MID CRV OG is established when some States in MID Region confirmed joining CRV project;

- Noted that the Asia/Pacific Ministerial Conference on Civil Aviation (APACMC) adopted the Declaration on Civil Aviation or Beijing Declaration. The Ministers commit to implement by 2022 the Asia/Pacific Seamless ATM Plan including Common ground/ground telecommunication infrastructure to support ANS applications;

- The meeting discussed the procedure to accommodate additional potential partners to join CRV and agreed that new applications outside of CRV operation concept need to be approved by CRV OG;

- Reviewed the outcome of SWIM TF/2 meeting and the requirement for communication infrastructure related to CRV to support SWIM. The meeting considered that there is a need to provide more information back to the SWIM Task Force on the purpose of the CRV. The CRV will be uniquely placed to be able to provide private IP (not public internet) connections between States for the exchange of SWIM. CRV OG requested that the SWIM Task Force engages the OG to further discuss the communications infrastructure requirements to support the implementation of SWIM in the Asia Pacific Region. It may be beneficial to conduct the CRV OG and the SWIM Task Force at the same time so that a constructive conversation can be achieved. The meeting further noted the need to develop an initial Asia/Pacific Regional Architecture for SWIM, but urged the SWIM Task Force to engage with the CRV OG to work towards ensuring that viability of the CRV to carry SWIM;

- CRV pilot project had been further delayed and the estimated to sign the contract with PCCW Global in early May 2018 and the CRV service readiness would be in September 2018. The meeting urged States involved with pilot project for Proof of Concept take all efforts working together with PCCW Global to complete the pilot project as early as possible;

- made progress of the CRV Pilot Project Test Plan/Pilot Service Acceptance Testing for the confirmation of key aspects of the CRV network;

-7- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718

- PCCW Global was requested to reissue an updated (a)-1 Terms and Conditions between PCCW Global and CRV User; and

- States were requested to note the proposed changes to (a)-1 Terms and Conditions between PCCW Global and CRV User and to review the proposed contract end dates amendments with their legal teams.

CRV Implementation Plan and VoIP and Analog Voice ICD for CRV

4.4 The meeting reviewed and endorsed the CRV Implementation Plan presented by Singapore. The plan serves as guidance for States/Administrations who wish to join the CRV. The CRV implementation roadmap, implementation requirements and stakeholders’ (CRV members and CRV service provider) responsibilities etc. are contained in this plan.

4.4.1 The meeting also updated the ‘National CRV Points of Contact’, ‘Local CRV Points of Contact’ which was integrated into the CRV Implementation Plan. The meeting further agreed to recommend this plan for adoption as Version 1.0 by CNS SG/22 meeting through a consolidated draft Conclusion.

CRV Voice over Internet Protocol (VoIP) and Analog Voice ICD

4.5 The VoIP ICD was developed as a companion to the IP ICD to include VoIP and Analog Voice interfaces for voice access to CRV. The VoIP and Analog Voice ICD will be useful as a guideline for Ground to Ground Voice communications.

4.6 In view of the foregoing, the meeting endorsed following draft Conclusion formulated by CRV OG/4 meeting.

Draft Conclusion ACSICG/5/3 (CRV OG/4/1) - CRV Implementation Plan and VoIP ICD What: That, Expected impact: a) the CRV Implementation Plan provided in Appendix B to the ☐ Political / Global report be adopted as Version 1.0; ☐ Inter-regional ☐ Economic b) CRV Voice over Internet Protocol (VoIP) and Analog Voice ICD ☐ Environmental provided in Appendix C be adopted as Version 1.0. ☒ Ops/Technical Why: Need to provide guidance to States Follow-up: ☒ Required from States and Administration for CRV implementation When: 20-Jul-18 Status: Adopted by Subgroup Who: ☒ Sub groups ☒ APAC States ☐ ICAO APAC RO ☐ ICAO HQ ☐ Other: XXXX

4.7 The meeting noted that the CRV Operation Manual would need further updates based on the experience gained in the CRV pilot project for Proof of Concept.

Addtional APAC CRV Portal

4.8 In addtion to the CRV portal on the ICAO site, additional portal/website is developed to facilitate easier sharing of documentation and applications during the initial stages of the CRV implemenstion and running of CRV.

CNS SG/22 – WP/05 -8- Agenda Item 3.1 02/07/18

Transition from Point-to-Point BBIS & BIS State to CRV Network connection

4.9 Based on a proposal from Fiji, BBIS States/Administration were encouraged to commence the transition of AMHS to CRV network as early as possible so as to allow more BIS State/Administrations to establish connections over CRV. Accordingly, the meeting endorsed the following draft Conclusion for consideration by CNS SG/22 meeting.

Draft Conclusion ACSICG/5/4 (CRV OG/4/2) - ATN/BBIS States/Administration use CRV for AFTN/AMHS Traffic What: That, States/Administrations with ATN/BBIS be urged to Expected impact: implement CRV network as early as possible as it would also provide ☐ Political / Global AFTN/AMHS routing function for BIS Administrations. ☐ Inter-regional ☐ Economic ☐ Environmental ☒ Ops/Technical Why: Compliance with ICAO Doc. 9896 Follow-up: ☒Required from States

When: 20-Jul-18 Status: Referred back to Subgroup Who: ☒CNS Sub-group ☒APAC States ☐ICAO APAC RO ☐ICAO HQ ☐Other: XXXX

Governance of the APAC CRV

4.10 The meeting noted that the CRV Terms of Rererence would be reviewed in global context. The meeting reconfirmed that the correct spelling of CRV should be “Common aeRonautical Virtual Private Network. Reference was made to the title in the initial Terms of Reference of CRV OG recommended by the CRV Task Force. Australia, China, Fiji, New Zealand, Singapore, Thailand and the USA will prepare a revised Terms of Reference for consideration by CRV OG/5 meeting.

Next Meetings of CRV OG

4.11 The CRV OG/5 is scheduled for either November or earl December 2018. It was suggested that meeting be held in Hong Kong China with support by the ICAO's CRV Service Provider, PCCW Global. The members of the CRV Operations Group would then have an opportunity to visit Network Operations Centre of PCCW Global. The Secretariat will coordinate with member States/Administrations concerned regarding the exact venue and time of the meeting.

4.12 The meeting also discussed the need for a joint meeting session with the SWIM Task Force. The meeting agreed that CRV OG/6 is scheduled coincide with the next SWIM TF provisionally in March/April 2019. This meeting will also serve as the first CRV OG/PCCW Annual Service Review Meeting.

IPv4 and IPv6 planning

4.13 The USA informed the meeting of the evolution of IP address in the air traffic control service. The plan is underway to support the use of IPv6 address as the IPv4 address is depleting and would not sustain the Air-to-Ground communication that will be based on Internet Protocol Suite (IPS). It was informed that ARINC Standards for airborne equipment and air-

-9- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718 ground interoperability currently are based on IP Version 4 (IPv4) (e.g. ARINC 664, ARINC 822A, etc.) IP Version 6 (IPv6) deployment now is growing around the world. Around 25% of worldwide traffic is now full IPv6 (end 2017) against less than 1% 5 years ago (end 2012). The AEEC IPS Subcommittee develops some steps of the proposed approach as mentioned in the paper.

IPv4 Address in the CRV Implementation Plan

4.14 The meeting discussed about use of APAC IPv4 addresses Plan in the Appendix B to CRV Implementation Plan. When adopted the IPv4 address assignment, it was not clearly specified the address is designated for State, ANSP, Service provider (e.g. CRV provider), or for AMHS. Therefore, the meeting proposed that the designated IPv4 address to be assigned for CRV Customer Edge (CE) router. This would allow ANSPs who subscribed service with CRV can share the service with their respective applications (e.g. AMHS, AFTN, ADS-B, AIM and SWIM) as needed.

Report of the Second Meeting of the APAC SWIM Task Force (SWIM TF/2)

5.1 The noted the outcome of the Second Meeting of the APAC SWIM Task Force (SWIM TF/2) which was held in Bangkok from 9 to 12 April 2018. The meeting was attended by 68 participants from 18 States/Administrations. The meeting report and papers presented to the meeting are provided at the following meeting site: https://www.icao.int/APAC/Meetings/Pages/2018-SWIM-TF2.aspx

5.2 The meeting noted the progress and updates made by tasks leaders on the assigned tasks by the SWIM Task Force including progress and issues, further follow up action items against each task.

5.3 The meeting recalled that the Task Force was established by the CNS SG and its report path is to the Sub-group through ACSICG. Considering the nature of Task Force work plan and the statements of work developed, the meeting agreed to the revised TOR of SWIM Task Force. The main changes in the TOR are the report path directly to the CNS Sub-group rather than through ACSICG. Consequential changes to the list of coordinating bodies in the Region listed in the TOR. In any case, a specific task of the SWIM Task Force has been designed to perform the horizontal coordination with all the TF/WG under APANPIRG which have a contribution to or a dependency on the SWIM implementation. Accordingly, the meeting endorsed the following draft Decision:

Draft Decision ACSICG/5/5 (SWIM TF/2/1) - Revised Terms of Reference for the SWIM TF What: That, considering the recommendation from CNS SG/21 that Expected impact: SWIM TF report directly to CNS SG, the revised Terms of Reference ☐ Political / Global of SWIM Task Force placed at Appendix D to the Report be adopted. ☐ Inter-regional ☐ Economic ☐ Environmental ☒ Ops/Technical Why: To reflect a direct reporting line from SWIM TF to CNS SG, as recommended by CNS SG/21 and noting that the TOR already include the Follow-up: ☐Required from States requirement to coordinate with other relevant groups formed under APANPIRG and its sub- groups. When: 20-July - 18 Status: Draft to be adopted by Sub-Group Who: ☒CNS SG ☐APAC States ☒ICAO APAC RO ☐ICAO HQ ☒Other:

CNS SG/22 – WP/05 -10- Agenda Item 3.1 02/07/18

5.4 Regarding the needs for SWIM service, the meeting formulated a Draft Conclusion SWIM TF/2/2 proposing to conduct a survey to support the future planning of SWIM services to be implemented in the APAC Region. The purpose of the survey is to promote available SWIM services, and to invite States to provide information on new services having implemented and/or to be implemented.

5.5 Contents of the survey would cover a number of SWIM services such as “Flight, Navigation, Operation/Maintenance, Surveillance, Meteorological Service” with rating scale in a few categories of “1 - Not useful, 2 – Useful, 3 - Very useful, 0 – Yet known” to collect views from SWIM stakeholders. States would be requested to distribute the survey to the stakeholders who need indicate their needs.

5.6 The SWIM TF/2 meeting noted that initial draft of the survey was too complex for understanding by the member States and the Task Force further agreed that the draft survey should be simplified for the initial circulation and then possible a more complex followed-up survey would be conducted within one to two years, when the community become more understanding about SWIM.

5.7 ICAO Regional Office was requested to circulate the survey once the simplified draft of survey is endorsed finally by the SWIM Task Force. States/Administrations then are urged to respond to the survey through the following Conclusion:

Draft Conclusion ACSICG/5/6 (SWIM TF/2/2) - Asia/Pacific SWIM Survey

What: That, States are urged to respond to a survey on Expected impact: System-Wide Information Management (SWIM), to be circulated ☐ Political / Global through an ICAO State Letter. ☐ Inter-regional ☐ Economic ☐ Environmental ☒ Ops/Technical Why: To commence initial education and information gathering on SWIM Follow-up: ☒Required from States understanding and readiness in the APAC Region When: 20-Jul-18 Status: Draft to be adopted by Sub-Group Who: ☒ CNS Sub group ☒ APAC States ☒ICAO APAC RO ☐ICAO HQ ☐Other: XXXX

5.8 The meeting noted that the SWIM TF/3 meeting is scheduled for March or April 2019. The meeting would be five days including one-day SWIM Seminar. The SWIM Task Force would explore the possibility of holding the SWIM TF plenary meetings back-to-back with other relevant meetings such as CRV OG or ACSICG.

Data Communication Implementation Task Force

6.1 The meeting noted that the APA Task Force updated the AIDC implementation priorities against the hot-spot identified by RASMAG and APANPIRG. The progress and target date of implementation are highlighted below:

• Jakarta and Chennai - Oct.2019;  Jakarta and Ujung Pandang - Oct. 2019; • Jakarta /Melbourne FIRs - Oct. 2019;

-11- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718

• Chennai and Kuala Lumpur was implemented on 15 May 2017 with a limited set of messages and LOA to be signed by 1 May 2018; • Manila and Fukuoka - coordination in progress; • Manila and Taipei - 4Q2018; • Manila and Hong Kong - 1Q2019; • Manila and Ho Chi Minh - 1Q2019; • Manila and Singapore: 4Q2018; • Manila and Kota Kinabalu: - 4Q2019; • Manila and Ujung Pandang: - 4Q2018 • Urumqi/Lahore: New IDD service provider selected by Pakistan and communication being improved and LHD reduced; • Beijing/Ulaanbaatar: coordination is underway for testing and implementation; • Hong Kong/Guangzhou AIDC operational trial planed for 2Q2018; and • Mumbai/Karachi and Muscat – coordination is underway for implementation and Mumbai side is ready (new hot-spot 1 identified by RASMAG/22)

6.3 The meeting also noted that a Proposal for Amendment (PfA) to ANP Table CNS II APAC-1- AIDC Implementation Plan to reflect the latest requirements for AIDC implementation had been processed through a consolidated PfA with serial No.: APAC-II 18/01 - CNS-MET/AIM with ref: AN 3/3 - AP005/18 (CNS/MET/AIM) dated 30 January 2018. States/Administrations have been notified of the approval with the AIDC implementation plan further updated by APA TF/4 meeting.

6.4 The meeting noted the possible solutions to AFTN latency issues including parameters adjustment and use of dedicated links instead of AFTN and through joining the CRV project.

AIDC Implementation Status in Hong Kong China 6.5 Hong Kong China updated the meeting on the latest status of the AIDC planning and implementation with their neighbouring ATSUs.

 following successful operational trials conducted in April-May 2018, the AIDC operation between Hong Kong and Guangzhou ACCs has commenced since May 2018; and

 AIDC technical and interoperability tests were successfully completed with Manila ACC in May 2018. In anticipation of the commissioning of the new ATMS in Manila ACC, the AIDC operation between Hong Kong and Manila ACCs is planned to commence in 2019.

Review AFTN Routing Directory Changes

7.1 Through the paper, the Secretariat reviewed the guidelines, technical provisions and operational requirements for the AFTN Routing Directory updates and highlighted some changes need to be made to the current Edition of the AFTN Routing Directory Asia and Pacific Regions available at the following APAC webpage: https://www.icao.int/APAC/Documents/edocs/cns/AFTN_Routing_Directory.pdf

7.2 The meeting agreed to:

 rename the directory to AFTN/ATSMHS Routing Directory for Asia and Pacific Regions;

CNS SG/22 – WP/05 -12- Agenda Item 3.1 02/07/18

 some acceptable changes to the directory based on the previous proposals highlighted in WP/11;

 information of AFTN circuit signal Speed at the back of the Routing Directory from page 25 to 28 be replaced with the category of service i.e. “ATSMHS or AFTN”. Whether the connection to be over CRV is also required in an additional column. States/Administrations participating in the meeting will provide this information to the secretariat for consolidation within two weeks after the meeting.

Routing Directory Changes suggested by India to facilitate least number of Hops

7.3 India presented a summary of current state of AFTN Routing Table with respect to India and proposed some updates to improve the traffic routing by least number of hops for relaying messages from its point of origin to its final destination consequent upon implementation of new circuits and AMHS by most of the States in Asia/Pacific.

7.4 The meeting noted the proposed changes and corrections consolidated in the Attachment to WP/9 to AFTN Routing Directory and requested the Secretariat to make necessary changes based on the proposals.

7.5 In addtion, China and Hong Kong China also proposed some changes to the routing directory. In view of the foregoing, the meeting formulated following draft Conclusion for consideration by CNS SG/22 Meeting.

Draft Conclusion ACSICG/5/7 - Revised AFTN/ATSMHS Routing Directory

What: That, the AFTN/ATSMHS Routing Directory for Expected impact: the APAC Region provided in Appendix E be further updated and ☐ Political / Global distributed to States/Administrations. ☐ Inter-regional ☐ Economic ☐ Environmental ☒ Ops/Technical Why: A number of new ATSMHS connections have been established and some AFTN circuits has become no operational. Consequential Follow-up: xRequired from States amendments to the AFTN/ATSMHS Routing Directory are required. When: 10-Sep-18 Status: Adopted by Subgroup Who: ☒CNS SG ☒APAC States ☒ICAO APAC RO ☐ICAO HQ ☐Other: XXXX

-13- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718

Updates on the Asia/Pacific AMC Information

7.6 Aerothai, the designated as contact point of the ASIA/PAC Region for coordination with EUROCONTROL ATS Messaging Management Center (AMC) informed the meeting that 20 Administrations have provided registration information to AMC including Australia, Bangladesh, Bhutan, Cambodia, China, Hong Kong China, Macao China, Fiji, India, Indonesia, Japan, Lao PDR, Malaysia, Myanmar, Nepal, New Zealand, Pakistan, Philippines, Republic of Korea, Singapore, Sri Lanka, Thailand and United States.

7.7 The meeting noted the updates shown in IP/7 on the inter-regional AMHS connections relevant to APAC resulted from the last AIRAC Cycle. States/Administrations were urged to make necessary updates to the AMC information with two forms attached to IP/7:

 Appendix F – Pro forma for modification of AMHS MD Identifier and/or Addressing Scheme (for major change); and

 AMC Information Form for updating AMHS implementation and other information.

7.8 With regards to AMHS User Capabilities information to prepare for IWXXM information exchange, AEROTHAI was tasked to contact AMC and request information on AMHS User Capabilities form. Aerothai will coordinate with regional Point of Contacts of MTA to provide information of AMHS User Capabilities for updates to AMC.

AMHS Implementation Planner

7.9 Under this agenda item, the meeting also discussed whether need to maintain AMHS Implementation Planner which was kept updated till ACSICG/3 meeting by India. Considering AMHS having implemented by many States and planning phase for most States is over. The need for harmonized actions for negotiation and testing etc. is no longer required for collective review. Therefore, the meeting agreed to discontinue maintenance the AMHS Implementation planner by ACSICG.

Work programme and Communication Strategy

8.1 The meeting reviewed and updated the list of action items presented in the ACSICG work programme. The updated work programme for ACSICG is provided in Appendix F to this Report.

8.2 While reviewing action items in the work programme, the meeting further updated the Strategy for Implementation of Communication Systems to support Air Navigation Service in the Asia/Pacific Region based on the latest developments and information presented to the meeting. The meeting recommended to adopt revised strategy through the following draft Conclusion:

CNS SG/22 – WP/05 -14- Agenda Item 3.1 02/07/18

Draft Conclusion ACSICG/5/8 - Revised Strategy for Implementation of Communication systems to support Air Navigation Service What: That, the revised Strategy for implementation of Communication Expected impact: systems to support Air Navigation Service provided in Appendix G to the ☐ Political / Global Report be adopted. ☐ Inter-regional ☒ Economic ☐ Environmental ☒ Ops/Technical Why: The Strategy for implementation of Communication systems for APAC Region was adopted Follow-up: ☒ Required from States by APANPIRG in 2017. The strategy requires to be updated based on the latest development. When: 14-Sep-17 Status: Adopted by PIRG Who: ☒ APANPIRG ☒APAC States ☐ICAO APAC RO ☐ICAO HQ ☐Other:

9.1 There were four papers on aeronautical mobile communication were presented to the meeting which should be reviewed under agenda item 4 of this meeting (CNS SG/22).

Study on undetected simultaneous transmissions

9.2 Hong Kong China shared with the meeting on the outcome of their study on undetected simultaneous transmissions which impose potential safety risks to air navigation services. As part of the Safety Management System (SMS), Hong Kong China had proactively conducted technical analysis on the air-ground VHF communication at the Hong Kong International Airport (HKIA). The measures implemented to mitigate the potential risks was introduced. Hong Kong China also recommended to develop some regional guidance materials on the subject.

9.2.1 The occurrences of undetected simultaneous transmissions were at a relatively low level. The mitigating measures implemented by Hong Kong included publishing an Aeronautical Information Circular (AIC), reiterating the importance of correct radiotelephone discipline, the usage of correct and precise communications technique, as well as standard phraseology. Further, new technologies capable of detecting simultaneous transmissions with alerting functions are available. States/Administrations with high traffic density were encouraged to undertake similar technical studies with a view to identifying mitigating measures.

Space-based VHF Voice Communication Service

9.3 Singapore proposed a potential solution using VHF radios relay installed on satellites. Space-based ADS-B provides a means of surveillance over oceanic and remote continental areas. However, there are no similar ready solutions for the case of VHF communication, as Direct Controller Pilot Communication (DCPC), to support radar-like separation minima in these areas.

9.3.1 Singapore has been working with satellite and communications vendors - Gomspace AS (Gomspace) and Singapore Technologies Engineering Electronics (STEE) to conduct design studies and

-15- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718 trials/proof-of-concept for satellite-mounted VHF voice communication relay system (“space-based VHF”) on Low Earth Orbit (LEO) satellites. Some potential challenges were highlighted in the paper. ConOps and satellite constellation were also briefly introduced including a constellation of 64 clusters of satellites operating at 600 km altitude in near-equatorial orbit. The link budget for space-based VHF, communication latencies and mitigation to potential interference to other adjacent radio stations were also described.

9.3.2 The design study was expected to be completed by the end of 2018 and followed by a proof-of-concept (POC) demonstration in end of 2019. The POC would include launching of a few satellites equipped with the VHF relay stations. Therefore, ICAO was requested to provide three frequencies for POC. CAAS is working with the Singapore radio regulator, on ITU allocation of VHF frequencies for space-based VHF voice services purpose, to table for WRC-2023 agenda approval at WRC-2019. In this connection, States and ICAO were invited to support the ITU application process of allocating the aeronautical VHF frequency band for space-based VHF communication service.

9.3.3 Considering the space-based VHF communication services is a first-of-its-kind, innovative solution for use in associated with appropriate surveillance sensors such as space based ADS-B, to provide radar-like separation minima in oceanic and domestic airspace, including the category R airspace as specified in the seamless ATM plan, the meeting endorsed the operation requirement for such communication service and supported the study. Accordingly, the meeting agreed to the following draft Conclusion:

Draft Conclusion ACSICG/5/9 – Support allocation of radio spectrum for space based VHF communications What: That, Expected impact: a) States and ICAO are invited to initiate and support the ☐ Political / Global ITU application process of allocating an appropriate ☒ Inter-regional aeronautical VHF frequency band for space-based ☒Economic aeronautical mobile communication service; b) States and ICAO to support the study project of space ☒ Environmental based VHF aeronautical mobile communication service ☒ Ops/Technical that would enhance the safety, capacity and efficiency of air navigation services; and c) ICAO is invited to assign three aeronautical VHF frequencies for the Proof-of-Concept tests.

Why: Need to support the study on space based VHF aeronautical mobile communication for Category R and other suitable airspaces in order to Follow-up: ☒Required from States and ICAO provide seamless VHF communication service to support radar like separation minima in the area. When: 5-Sep.-18 Status: Draft to be adopted by APANPIRG Who: ☒CNS Sub group ☒APAC States ☒ICAO APAC RO ☒ICAO HQ ☐Other: XXXX

Improvement of the Radio Wave Environment in Incheon Intl. Airport

9.4 Republic of Korea presented two proposals to improve the worsening radio wave environment in Incheon International Airport. The first proposal is the plan to implement Best Signal Selection (BSS) method for radio frequency channels. The second proposal was to possibility to extend frequency allotment group for surface communications in ICAO Annex 10, Vol. V.

CNS SG/22 – WP/05 -16- Agenda Item 3.1 02/07/18

9.4.1 The meeting was informed that the Incheon International Airport (IIA) had completed Phase 3 construction plan including opening Terminal 2 in January 2018. Currently, the airport deals with more than 1000 aircraft movements per day. About 7% of flights increased each year. More facilities and constructions being built would exacerbate radio wave environment. The phase 4 plan includes expansion of Terminal 2 and construction of 4th runway. Thus, additional frequencies for surface movement communications would be required. The BSS was used only for a few frequencies to overcome radio interference in 2017. The signals were transmitted from spots at air side and measured reception level at Terminal 1 and Terminal 2 (where receivers installed). When using BSS, receiving sensitivity is generally good in the whole area of air side.

9.4.2 Radio frequencies used in the airport were in accordance with the radio frequency allotment plan specified in ICAO Annex 10 Vol.V. Republic of Korea would propose to extend the frequency group assigned for surface movement communications to provide surface movement control, apron control, clearance delivery, etc.

9.4.3 The Secretariat clarified, modification to allotment plan in Annex 10 Vol. V would take longer process in accordance with established procedure. It would also impact to the other services allocated in the same aeronautical VHF bands. Additional allocation for aeronautical use by ITU would be through World Radio Conferences being held every 5 years. The allotment plan agreed by ASIA/PAC RAN meeting in 1993 still being used in addition to the global plan. The frequencies in the national allocation may also be explored for such purpose. It was suggested to look for urgent solution before a proposal to amendment to the allotment plan in Annex 10, Vol. V

Using VoIP for Safety Critical Communication

9.5. Frequentis AG made a presentation on seamless migration to IP providing information on the needs, and benefits of domain specific standards on the example of ED-137 for VoIP in air traffic management. For controllers and pilots, utilization of VoIP networks translates into poor audio quality unless adequate counter-measures are taken both on the physical layer (to provide redundancy and interfaces) and the application layer (to provide domain related functionality).

9.6 Mandatory industry related standard such as ED-137 and ICAO Doc9896 define boundaries for VoIP in ATM. Compliance with this standard is the baseline for safe communication and for interoperability between single elements of the infrastructure. However, with the right partner and technology, providers have an opportunity to further optimize ATM communications, helping controllers and pilots work together in a more effective and less stressful way than ever. The paper further introduced the needs to address following aspects of VoIP:

- Enabling echo-free voice communications with bi-directional dynamic delay compensation;

- Tuning in closely with radio side-tone configuration;

- Safely covering large areas with CLIMAX and best signal selection; and

- Ensuring critical communication by adopting admission control.

-17- CNS SG/22 – WP/05 Agenda Item 3.1 02/0718

Future Meetings

9.7 The ACSICG/6 meeting is scheduled for a period of 3 days in late April or early May 2019 after the SWIM TF/3 meeting and CRV OG/6 scheduled concurrently for April or May 2019. The meeting is likely conducted back to back with CRV OG/6 meeting. The tentative dates for meetings proposed by ACSICG: 6 – 10 May 2019 for SWIM TF/3; 8-10 May 2019 for CRV OG/6 and 13 to 15 May 2019 for ACSICG/6. Thailand offered to host ACSICG/6 and possible CRV OG/6 and SWIM/3 meetings at a venue to be determined. The exact dates and venue of the meeting would be confirmed by APANPIRG/29 meeting in September 2018.

9.8 The CRV OG/5 is scheduled for November or early December 2018 in Hong Kong China.

3. ACTION BY THE MEETING

3.1 The meeting is invited to:

a) note the information contained in this paper; b) review the AIDC- ATN-AMHS Implementation status in Appendix A; c) noted the ACSICG work programme provided in Appendix F to the meeting report; d) review the CRV Implementation Plan provided in Appendix B; e) review the CRV VoIP and Analog Voice ICD provided in Appendix C; f) review the revised ToR of SWIM Task Force provided in Appendix D; g) review AFTN/ATSMHS Routing Directory provided in Appendix E; h) review the revised communication strategy provided in Appendix G; i) endorse or adopt, as required, eight draft conclusions and decisions in this paper; and j) discuss any relevant matter as appropriate.

______

ACSICG/5 Appendix A to the Report

ATN/AMHS/AIDC Implementation Status in the APAC Region

AFGHANISTAN

AUSTRALIA ATN tests were conducted. BIS Router and COMSOFT AFTN/AMHS based AIDC Backbone BIS Router and AMHS implemented. Implemented between Brisbane and Melbourne, 64 kbps IPLC established with Fiji for basic Oakland, Nadi and AMHS will be migrated to CRV when successful Auckland; CRV pilot project is completed. Implemented between Connection with Singapore using AMHS was Melbourne and implemented October 2016; Johannesburg;

Another AMHS connections pending CRV pilot AIDC is also in use between project (target date for December 2017) including Melbourne and Mauritius; both connection with New Zealand and USA. Operational trial between Plan to upgrade AMHS support IWXXM traffic Brisbane and Ujung from Nov. 2020. Pandang since May 2013. Implementation in July 2017. LOA needs to be updated.

BANGLADESH In Q1/2013, Bangladesh installed ATN/AMHS COMSOFT Tentative date of The Bangladesh and BIS Router at Dhaka (VGHS) with User implementation of AIDC is ATM Upgrade Agents at Chittagong (VGEG) and Sylhet Q4 of 2018 with Kolkata Project (VGSY). and Myanmar. (BATMUP) under Public Private Partnership (PPP) in Dhaka is expected to be completed by 2018.

A - 1

ACSICG/5 Appendix A to the Report

As soon as the ATM upgradation is completed hopefully Bangladesh will be able to implement AIDC with Kolkata and Myanmar by the end of 2018.

BHUTAN ATN/AMHS circuits, using IP over VPN, with Currently not applicable. If Thailand (Bangkok) and India (Mumbai) required in the future, will be decided after CRV commissioned in June and July 2017 implementation (scheduled respectively. for mid-2019). AEROTHAI’S th IOT and POT with Mumbai completed on 27 AMHS System June 2017.

IOT and POT with Thailand completed on 2nd May 2017.

TMC signing with both countries at final stage.

BRUNEI DARUSSALAM ATN BIS Router planned for 2015 and AMHS planned for 2015

A - 2

ACSICG/5 Appendix A to the Report

CAMBODIA BIS Router and AMHS installed. AVITECH AIDC function and THALES which supports Cambodia (CATS) AMHS connected with capability made available. AIDC ICD Version 1. Bangkok via VSAT IP link since 10 December 2013 Ready for testing with neighbors ATS Facilities starting from 2017 and target date of implementation with Bangkok in 3Q2019

CHINA ATN Router and AMHS including NCC IN-HOUSE AIDC between some of deployed in 2008 which is being upgraded to (Aero-Info ACCs within China has support ATN/IPS with target date of completion Technologies been implemented. AIDC in December 2013. Co., Ltd) between several other ACCs are being implemented. ATN/AMHS circuit with Hong Kong China is completed POT, after sign the TMC will put into AIDC between Sanya and operation in 2018. Hong Kong put in to operational use since 8 Feb With Thailand is completed POT, after sign the 2007. TMC circuit will put into operation in 2018. AIDC between Dalian and AMHS/ATN technical tests with Macau Incheon implemented in completed in 2009. Plan for ATN/AMHS Nov. 2016; implementation with Macao China in 2019. Guangzhou with Nanning/Zhanjiang/Zhuhai ATN/AMHS circuit with ROK has been put into implemented; operation since June 2011. Nanning and ATN/AMHS tests with India has been put into Kunming/Guiyang/Zhanjian operation since 2016. g implemented in 2011; Zhanjiang/Haikou;

A - 3

ACSICG/5 Appendix A to the Report

State/Organization ATN G/G Boundary Intermediate System AMHS AIDC ATM System selected Remarks (BIS) Router/AMHS Vendors to support AIDC and Selected Associated ICD (Implementation Status of the Basic 5 message set supported) ATN and AMHS IOT with Mongolia is Chengdu and completed in May 2018. Chongqing/Guiyang implemented in 2011; Connection tests with Nepal is TBD. Guiyang and Chongqing/Kunming implemented in 2011;

For Beijing/Ulaanbaatar, planned date of testing in 2019.

HONG KONG, CHINA Hong Kong China had completed the COMSOFT AFTN-based AIDC with Raytheon ATM system Already support Interoperability Test (IOT) with Beijing Sanya put into operational Support AIDC ICD exchange of IWXXM successfully in April 2016. The leased line use in Feb 2007. AIDC Version 3 commissioned messages based on between Beijing and Hong Kong has also put in technical trial with Taibei in November 2016. FTBP place in June 2017. Hong Kong is now conducted in 2010 and coordinating with Beijing for another round of completed in 2012 and put IOT and Pre-operational Test (POT) through the into operational use in Nov. leased line. The planned implementation date of 2012 Beijing-Hong Kong AMHS link would be by the end of 2017. AIDC technical and interoperability tests with ATN/AMHS circuit with Bangkok put into Guangzhou conducted operation use in Sept 2014. successfully in April and June 2017 respectively. ATN/AMHS interoperability tests with other adjacent communications centres commenced in AIDC tests with Manila is late 2009, viz Taibei (2009), Japan (Planned under coordination for the Q2/2018 after implementation of CRV), new ATM system – on Philippines (Planned Q1/2018 after CRV) and going. Viet Nam (Planned 2018).

A - 4

ACSICG/5 Appendix A to the Report

MACAO, CHINA ATN/AMHS interoperability test with Beijing COMSOFT (Not applicable for using commenced in March 2009. AIDC, looking into the possible application (some ATN/AMHS circuit with Hong Kong put into way) between TWR and operational use in end Dec. 2009. ACC/APP). ATN/AMHS implementation with mainland China planned for 2018

COOK ISLANDS

DEMOCRATIC PEOPLE’S The ATN BIS Router and AMHS planned for in With neighboring ACCs to REPUBLIC OF KOREA 2011. be implemented

- Support and FIJI ISLANDS ATN BIS Router and AMHS implemented COMSOFT AFTN based AIDC implemented AIDC Connection with USA and Australia has been implemented between messaging: ABI, EST, implemented to support basic AMHS traffic. Nadi/ Brisbane, Auckland CPL, CDN, ACP, TOC, and Oakland. AOC with all three Plan to upgrade these connections using CRV and centers IP after the implementation of CRV pilot project. - AIDC ICD version 2.0 implemented with For connections with sub-regional centres: Auckland and Oakland. For New Caledonia using AMHS in 2017; For - AIDC ICD Version 1.0 connection with Kiribati using UA/AMHS implemented with implemented in 2015. Brisbane

A - 5

ACSICG/5 Appendix A to the Report

FRANCE Planned for implementation of AMHS in 2020. Implementation of AIDC THALES EUROCAT for Alternate routing for (French Polynesia Tahiti) (based on Version 3) with AIDC backup between Tahitti Planned for using IP to replace X.25 with New adjacent centres (Oakland and Christchurch via Zealand shortly. and Auckland) since 2009. Tahitti/New Caledonia IP link

INDIA Dual stack ATN/IP router and AMHS COMSOFT -15-May-2017, AIDC 1) Raytheon at New 1) Major Indian airports implemented at Mumbai in 2011. implemented between Delhi, Mumbai and and ATC centres have Operational AMHS connections with Bangkok, Chennai and Kuala Lumpur Chennai integrated ATS Dhaka, Singapore, Kathmandu, Karachi with ABI and EST Automation Systems implemented. messages. CDN is done 2) Selex at Hyderabad having AIDC capability. With Beijing implemented in 2016; with voice confirmation. and Bengaluru. Successful AIDC trials With Colombo planned for May 2017; TOC/AOC to be have been carried out With Bhutan and Nairobi planned for 2017. implemented; 3) INDRA at 39 locations amongst major ATSUs -Chennai-Colombo in within India. testing phase; 2) AIDC implemented - Chennai-Male test trials in between Chennai and progress; Mumbai. - Chennai-Yangon is in 3) AMHS implemented testing phase; and working between -Mumbai-Male test trials in A. BBIS: Mumbai- progress; Singapore, Bangkok -Trivandrum-Male test trials B: BIS: Mumbai, in progress. Kathmandu, Dhaka

A - 6

ACSICG/5 Appendix A to the Report

INDONESIA ATN BIS Router and AMHS with Singapore IDS Implementation Thales in Makassar able Between PNG – Ujung implemented Since February 2018; Jakarta (new ATM system to support ICD Version 3 Pandang, the in 1Q2019) The target date since December 2015 implementation are AMHS Trial (IOT) with Brisbane planned of AIDC implementation waiting for PNG’s ATM 4Q2018 over VPN; ELSA will commence testing in system upgraded. 4Q2019 including following Between Oakland – pairs: Ujung Pandang is not planned yet, due to Jakarta-Singapore; traffic volume Jakarta-Chennai; consideration (very Jakarta-Ujung Pandang; low). Jakarta-Melbourne; Jakarta – Kuala Lumpur

Ujung Pandang –Brisbane: implemented in July 2017 (LOA to be updated). Ujung Pandang – Manila - Successful testing conducted; - Target date of implementation in 4Q2018. Ujung Pandang - Kota Kinabalu - Implementation date TBC

JAPAN ATN BBIS router and AMHS installed at 2000. NEC AIDC implemented between Japan and USA Connection tests with USA 2000 - 2004 and put Fukuoka ATMC and conducting testing AIDC into operational use in 2005. Oakland ARTCC in 1998. over AMHS and cutover date is 5 May 2017. AIDC implemented between Fukuoka ATMC and

A - 7

ACSICG/5 Appendix A to the Report

State/Organization ATN G/G Boundary Intermediate System AMHS AIDC ATM System selected Remarks (BIS) Router/AMHS Vendors to support AIDC and Selected Associated ICD (Implementation Status of the Basic 5 message set supported) ATN BBIS router (to apply to Dual Stack) and Anchorage ARTCC in 2005. AMHS (to upgrade in 2015. The connection test with each country which is not currently AIDC implemented between connecting is started after update. Tokyo ACC/Fukuoka ACC and Incheon ACC in 2010. Upgrading connection with Hong Kong using VPN will be implemented in 2018 after Implemented between implementation of CRV; Fukuoka and Incheon since June 2009. Coordinating for all other circuits upgrading. AIDC implemented between Fukuoka ACC/Naha ACC and Taibei ACC implemented.

AIDC between Fukuoka ACC and Shanghai ACC under negotiation.

KIRIBATI Connection with Nadi using UA/AMHS implemented in 2015.

LAO PDR ATN BIS Router and AMHS completed, planned THALES AIDC testing with Bangkok THALES which is able to for operation with Bangkok since 4Q 2016. in 2017 and target for support ICD Version 2. implementation in 3Q2019.

Testing with Hanoi ongoing since 2017; with Cambodia operational test again in June 2018.

A - 8

ACSICG/5 Appendix A to the Report

MALAYSIA ATN BIS Router completed 2007. AMHS FREQUENTIS AIDC testing with Bangkok SELEX which is able to implementation planned for Q42017; ACC conducted since 2016. support ICD Version 3. Operational trial will commence 3Q2018.

AIDC Between Kuala Lumpur/ Chennai implemented in phases from May 2017 implementation for ABI, EST and MAC along with response messages LAM, LRM and ACP. Review on the CDN message implementation conducted in Aug. 2017.

AIDC testing with Singapore on going since 2016. Target date for operational trial from 2Q2018.

Planned testing with Ho Chi Minh ACC – 4Q2019;

AIDC between KK ACC and Philippines in 4Q2019 and technical testing with Ujung Pandang planned for 2Q2018;

AIDC between Kuching ACC and Singapore planned for 4Q2020;

A - 9

ACSICG/5 Appendix A to the Report

AIDC between Kota Kinabalu ACC and Singapore planned for 4Q2020;

AIDC between Kuala Lumpur and Jakarta planned for 4Q2019.

ATM system is AIDC MALDIVES Planned for 2019 as existing AFTN was upgraded ready. Implementation with SELEX which is able to recently to make it compatible with protocols of ACC’s (Planned trials in support ICD Version 3. interconnected AMHS systems. progress; target date for implementation with Chennai in 3Q2018; Planned testing with Mumbai in 3Q2018; with Colombo, Melbourne and Trivandrum planned for 2019)

MARSHALL ISLANDS

MICRONESIA (EDERATED STATES OF)

Chuuk

Kosrae

Pohnpei

Yap

A - 10

ACSICG/5 Appendix A to the Report

MONGOLIA AMHS/AFTN gateway implemented 2012. COMSOFT ATM automation system INDRA Aircon 2100 supports both AIDC and supporting AIDC ICD ATNBIS router implemented in 2014. OLDI. Version 2.

Coordinating with China using ATN/AMHS Coordinating with Russia on connection technical trials conducted in 2014. OLDI connection in target date 2016.

Coordinating with China on AIDC connection between Beijing/Ulaanbaatar technical trial in progress. Planned date of testing in 2019.

MYANMAR AMHS including ATFN/AMHS gateway THALES AIDC connection pre- THALES Automation implemented in Nov. 2011; operation test with Thailand system upgraded to Connection with Thailand implemented in conducted in 4Q2017 and Thales Topsky ATC 4Q2016; Target date of system in January 2017 Planned for AMHS connection with Beijing. implementation 3Q2019; which supports AIDC Target date TBC. AIDC testing with Kunming Ver. 2 and AMHS and Chennai conducted in connections 2017.

NAURU

AIDC between Kathmandu NEPAL BIS Router and AMHS commissioned with COMSOFT and Beijing and planned Kathmandu Mumbai circuit on 2 June 2014. testing between KTM-BBN and KTM-CCU for 3Q2018

NEW CALEDONIA New router and AMHS commissioned December COMSOFT 2016

A - 11

ACSICG/5 Appendix A to the Report

NEW ZEALAND IP based AMHS connections with USA June COMSOFT AIDC implemented between Supported the Basic 5 2016 and plan to upgrade the connections using New Zealand, Australia, message set. ATM CRV and IP after the implementation of CRV Fiji, Tahiti, Chile and USA. systems are LEIDOS and pilot project. ADACEL

PAKISTAN ATN/AMHS connections with Mumbai since COMSOFT Implemented between ATM system from Intra Existing Radar system 2015. Karachi and Lahore ACCs AIRCON 2100 being upgraded.

Planning for AMHS connection with Beijing and Further testing to be Kuwait after upgrading existing facilities between conducted between the Countries. Target dates for implementation Delhi/Karachi & TBC. Delhi/Lahore after system upgradation at Indian end; Mumbai/Karachi &AHM/Karachi on trial operation. For testing with Muscat planned for 4Q2019. Coordination for testing with Tehran is in progress.

PAPUA NEW GUINEA Plans to create a newly duplicated digital COMSOFT Plan to implement with all COMSOFT which is able communications line connecting with existing neighboring FIRs in 3Q to support ICD Version 3 and new sites and AMHS system implemented in 2018. Negotiation with 4Q2014 Indonesia for AIDC with Ujung Pandang in May 2018.

PHILIPPINES New ATN/AMHS was installed at the New COMSOFT Technical Trials on the THALES which is able to CNS/ATM Center in Manila. Site Acceptance interim system: support ICD Version 2. was successfully done on October 2015. The new On-going with Singapore, AMHS commissioned and operational in March Ujung Pandang and Taipei 2018. The international connection still using ACCs; AFTN. The AMHS Interoperability test with Planned technical trial over Hong Kong and Singapore is planned by end of new ATM system with

A - 12

ACSICG/5 Appendix A to the Report

State/Organization ATN G/G Boundary Intermediate System AMHS AIDC ATM System selected Remarks (BIS) Router/AMHS Vendors to support AIDC and Selected Associated ICD (Implementation Status of the Basic 5 message set supported) 2018. other ACCs from 4Q2017 to 4Q2018: Coordination is AMHS interoperability test with Oakland USA is underway for using AIDC planned for 4Q2018. function of the new ATM system with adjacent ACCs.

Planned implementation:: 4Q2018 – Singapore ACC; 4Q2018 – Ujung Pandang ACC; 4Q2018 – Taipei ACC;

REPUBLIC OF KOREA ATN/AMHS circuit with China put into SAMSUNG AIDC implemented between Rockheed Martin System operational use in June 2011. ACC and Fukuoka ATMC.

AIDC between Incheon and Dalian implemented in Nov. 2016.

SINGAPORE AMHS implemented. COMSOFT Operational with Ho Chi THALES currently Minh implemented July support ICD Version 1 ATN/AMHS circuit with India put into 2014. and to be upgraded to operational use in March 2011. Version 3 in 3Q 2018. Planned operational trial ATN/AMHS circuit with UK put into operational with Kuala Lumpur ATCC use in March 2012. in 2Q2018.

ATN/AMHS circuit with Thailand put into Technical trials with Manila operational use in December 2014. ACC ongoing since Dec. 2014. Revised planned ATN/AMHS circuit with Australia put into operational implementation operational use in October 2016. by 4Q 2018.

A - 13

ACSICG/5 Appendix A to the Report

ATN/AMHS circuit with Indonesia put into Technical trials with Jakarta operational use in February 2018. ACC will be initiated once Interoperability Test with Malaysia, Philippines, the Jakarta ACC ATMS renewal is completed. Sri Lanka and Vietnam planned for 2018. Interoperability Test with Bahrain, Brunei and Japan planned for 2019.

SRI LANKA ATN BIS Router Planned for 2013. IP based IDS Trials with Male’ planned INTELCAN which is AMHS implemented by Oct. 2017. for in 2017. able to support ICD - Mumbai tested May 2017 operational Version 3. planned for Q4 2017; Trial with Chennai on- - Singapore testing in Q4 2017 going. Plan for operational for 2018; implementation in 2018 and - Male testing and operational date with Melbourne plan for TBD. 1Q2018.

THAILAND BBIS/BIS Routers already implemented. AEROTHAI's AIDC Connection test with THALES which is being AMHS has been implemented since July 2011. AMHS System Lao PDR, Cambodia, implemented with and UBITECH Myanmar and Malaysia planned completion in Connection with Cambodia, India, Singapore, System underway since 2016; Early 2017. Hong Kong China implemented. Operation trial with these AIDC feature supports Pre-operational test (POT) with Bangladesh, Lao States from late 2017 to APAC AIDC ICD V.3. PDR, Malaysia, Myanmar, Bhutan and Beijing early 2019. Target date of China completed, implementation planned for implementation is around end of 2018. 3Q2019.

Interoperability Test; with Italy and Vietnam planned for end of 2018.

Connection with SITA (SITA AMHS Gateway inter-connections) implemented.

A - 14

ACSICG/5 Appendix A to the Report

TONGA AMHS planned for 2008. CPDLC and ADS-C is not considered for lower The provider is linked to the New Zealand airspace AFTN

UNITED STATES AMHS implemented. IN-HOUSE AFTN based AIDC IN-HOUSE which is able (Salt Lake City & Atlanta). Transition using implemented. to support APAC and AMHS when counter parts ready Planned for AIDC NAT ICDs currently Planned for AMHS implementation with implementation with Version 2. Philippines 4Q2018 Philippines 1Q2019

VANUATU

VIET NAM AMHS (basic) implemented. IN-HOUSE Operational with Singapore Support ICD Version 1.0 Trial phase from 4Q/2015 to 3Q/2018. IOT with since April 2014. Trial with with THALES at Ho Chi Thailand in progress from 4Q/2017 Singapore for additional Minh ATM system. Plan to use AMHS in 4Q/2018; messages sets in 2018. Support ICD Version 3.0 Planned for IOT with Hong Kong and Singapore Negotiating for with Selex at Hanoi ATM in 2018 implementation with System. Philippines in June 2017; For IOT with Laos PDR. TBC. Technical testing with Cambodia already done; Trials with Lao. PDR in progress and with Malaysia to be confirmed.

Testing with Cambodia on – going; For operation trial TBC.

A - 15

ACSICG/5 Appendix A to the Report

Wallis and Futuna (FRANCE) AMHS implementation planned for end of 2017 COMSOFT

______

A - 16 INTERNATIONAL CIVIL AVIATION ORGANIZATION

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN

Version 1.0

20 April 2018

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

Table of Contents

ABBREVIATIONS ...... 4 1.0 INTRODUCTION ...... 6 1.1 Purpose ...... 6 1.2 Overview of the CRV ...... 6 2.0 IMPLEMENTATION OVERVIEW AND PROCESSES ...... 7 2.1 General Description of Implementation ...... 7 2.2 Implementation Schedule/ Roadmap ...... 7 2.2.1 Work Processes ...... 7 2.2.2 Roadmap for CRV ...... 8 2.3 Application Transition Schemes ...... 8 2.3.1 AMHS ...... 8 2.3.2 AFTN ...... 8 2.3.3 ADS-B...... 9 2.3.4 Voice ...... 9 2.4 Technical Specifications of CRV (for applications reference) ...... 9 2.4.1 Service Level Agreement & Quality of Service ...... 10 2.4.2 IP Addressing ...... 10 2.4.3 Interface ...... 10 2.4.4 Routing Restrictions...... 11 2.4.5 Packet Loss Rate ...... 11 2.4.6 For VoIP Transport (ED-137) ...... 11 2.4.7 Standards used ...... 11 2.5 Use Cases ...... 11 3.0 IMPLEMENTATION SUPPORT ...... 13 3.1 Introduction ...... 13 3.2 Implementation Team ...... 15 3.2.1 CRV-OG ...... 15 3.2.2 National CRV Points of Contact ...... 15 3.2.3 Local CRV Points of Contact ...... 28 3.2.4 CRV Contractor ...... 43 4.0 BASIC SITE IMPLEMENTATION REQUIREMENTS ...... 44 4.1 Site/ Facilities Requirements ...... 44 4.1.1 CRV User Responsibility ...... 44 4.1.2 Contractor Responsibility ...... 44 4.2 Hardware and Software Requirements ...... 46 4.2.1 General Topics ...... 46 4.2.2 Hardware Requirements...... 47 4.2.3 Software Requirements ...... 47 5.0 TESTING AND EVALUATION...... 47 6.0 CONTINGENCY PLAN/ BACK-OFF PLAN ...... 49 6.1 Purpose ...... 49 6.2 Harmonized Contingency Plan...... 49 7.0 MIXED OPERATING ENVIRONMENT ...... 49 7.1 Routing of AFTN/ AMHS messages to non-CRV States/ Administrations ...... 49

Page 2 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

7.2 Inter-Region common network connectivity...... 49 Appendix A ...... 50 Appendix B ...... 55 Appendix C ...... 69

Page 3 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

ABBREVIATIONS

ABBREVIATION DESCRIPTION AFTN Aeronautical Fixed Telecommunication Network AIDC ATS Inter-facility Data Exchange AMHS Air Traffic Service Message Handling System ANSP Air Navigation Service Provider APANPIRG Asia/Pacific Air Navigation Planning and Implementation Regional Group APAC Asia/Pacific ATC Air Traffic Control ATM Air Traffic Management ATN Aeronautical Telecommunication Network ATS Air Traffic Services BBIS Backbone Boundary Intermediate System BIS Boundary Intermediate System CAA Civil Aviation Authority CAR Caribbean Region CBA Cost Benefit Analysis CNS Communications, Navigation and Surveillance ConOps Concept of Operations CRV Common aeRonautical Virtual Private Network DSCP Differentiated Services Code Point EUR European Region FIXM Flight Information Exchange Model FPL Flight Plan ICAO International Civil Aviation Organization IP Internet Protocol IPS Internet Protocol Suite IWXXM ICAO Weather Information Exchange Model MET Meteorological MPLS Multi-Protocol Label Switching NAT Network Address Translation NID Network Interface Device OH Operational Hazard OG Operation Group OSI Open Systems Interconnections PoC Point of Contact QoS Quality of Service RFI Request for Information RFP Request for Proposal SARP Standards and Recommended Practices SAT Site Acceptance Test SIP Session Initiation Protocol SME Subject Matter Expert SOP Standard Operating Procedures ST Sealed Tender

Page 4 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

ABBREVIATION DESCRIPTION SWIM System-Wide Information Management TF Task Force WXXM Weather Information Exchange Model (based on XML) UC Use Case VoIP Voice Over Internet Protocol VPN Virtual Private Network XML Extensible Markup Language

Page 5 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

1.0 INTRODUCTION

1.1 Purpose

The purpose of this Implementation Plan is to provide guidance for all States/ Administrations on the operation requirements for the upcoming Common aeRonautical Virtual Private Network (CRV) used in Asia/ Pacific (APAC) Region and the roadmap for implementation.

The details includes in Table 1, Table 2 and Appendix A, a list of all States/ Administrations concerned, and for each State/ Administration it includes the:

i. National Points of Contact and Local Points of Contact; and

ii. expected deployment date.

The information contained in this document was first adopted by the 1st Meeting of CRV Operations Group (CRV OG/1). It is intended that this Implementation Plan shall be used as the means to:

i. identify all actions required to implement CRV;

ii. ensure a harmonized approach for the APAC Region;

iii. monitor and report on progress; and

iv. identify any issues, risks or problems which may arise.

1.2 Overview of the CRV

Currently, aeronautical ground-ground communications in the ICAO Asia/Pacific Region, and in particular Aeronautical Fixed Telecommunication Network (AFTN) and AMHS services, operate over point-to-point international leased circuits. However, this network configuration exhibits a number of limitations such as the inability to switch to new protocols like Voice over IP (VoIP) or System Wide Information Management (SWIM) efficiently, high cost for every connection and limited flexibility for increase in bandwidth.

A CRV Task Force (TF) was formally established in accordance with APANPIRG Decision (24/32), (Bangkok, Thailand, 24-26 June 2013). The concept of CRV was taken from other common network that has already implemented in other regions such as Pan-European Network Services (PENS) and FAA Telecommunication Infrastructure (FTI).

The CRV is a dedicated multiprotocol label switching (MPLS) Internet Protocol (IP) based Virtual Private Network (VPN) communication network provided by a common network service provider and support all Aeronautical Fixed Service (AFS) in the APAC region. Telecommunication costs are reduced as States/ Administrations will only require minimal connections to a far reaching network instead of individual connections to each neighboring State/ Administration. The CRV service provider provides the service to allow CRV members to exchange voice and data information with each other.

Each CRV member should determine the amount of bandwidth require for each Quality of Service (QoS) sub queue. In addition, each CRV member should also determine the total access bandwidth that they need to subscribe.

Page 6 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

2.0 IMPLEMENTATION OVERVIEW AND PROCESSES

2.1 General Description of Implementation

States/ Administrations should refer to the implementation roadmap (see Appendix A) to take note of the estimated CRV implementation date provided by other States/ Administrations that they wish to exchange data/ voice via the CRV.

The implementation date, type of data, voice, bandwidth and QoS between the two States/ Administrations shall be negotiated and agreed bilaterally and supported by the CRV service provider.

CRV service provider is to put up individual service contracts for the two connecting States/ Administrations.

The work processes and CRV implementation roadmap in 2.2 provides a breakdown of the estimated schedule and serve as a guide.

2.2 Implementation Schedule/ Roadmap

The planned project timeline for each States/ Administrations to implement CRV could be based on the estimated work processes schedule and roadmap for CRV.

2.2.1 Work Processes

The projected activities and schedule to implement the services includes the following:

S/No. Subject Projected Activities Projected Schedule 1 Technical 1. Respective ANSPs develop their 6 to 9 months requirements and associated requirements and Statement of SOW Work (SOW) that specify performance, interface, conversion, operational procedure, acceptance test procedure 2. Present to Vendor for comment and response 3. To seek CRV-OG concurrence on deviation from CRV common package 4. Finalize requirements 2 Negotiation and 1. To decide the type of data or voice to be 6 to 9 months agreement exchanged via CRC, QoS for each type between two of applications and the required connecting bandwidth States/ 2. CRV Contractor to comment and Administrations response to the agreed requirements 3. Agree to implementation schedule 3 CRV Contractor 4. Contractual and Legal review 6 to 9 months proposes 5. Technical and operational review Contract to 6. Finalize contract ANSP 7. Establish contract and payment system 4 Site preparation Site preparation and 1 to 3 months implementation of the service 5 Test and 1. Perform acceptance test with associated 3 to 6 months

Page 7 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

S/No. Subject Projected Activities Projected Schedule evaluation applications 2. Perform acceptance test with respective ANSPs 6 Service Service acceptance 1 week acceptance

2.2.2 Roadmap for CRV

The roadmap for CRV implementation in the APAC Region is appended in Appendix A.

2.3 Application Transition Schemes

This paragraph provides States/ Administrations the recommended transition scheme for each application (e.g. AMHS, ATFM, ADS-B, Voice, etc.) targeted to be implemented or migrated from the existing communication link/ network.

2.3.1 AMHS

Being IP, it should be possible to reroute the existing connection at the IP layer either by an address translation or by pointing the LA at a new IP address in the AMHS system. However the recommended approach will be to setup a parallel connection using the CRV that can be thoroughly tested to the satisfaction of both ANPS’s. Once the stability of the CRV has been verified, the cutover would be conducted by the respective com-centers at the AMHS system level. The actual approach taken will require a negotiation between each pair of ANSP’s.

2.3.2 AFTN

Depending on the existing AFTN connection there are a number of migration strategies available. Option 1. Migration to AMHS Setting up a new AMHS link over the CRV as per ICAO grand master plan xyz.123 would be the preferred option for migration of AFTN. It would allow the new connection to be setup and tested independently. Option 2. Migrate from native X.25 to XoT Where the existing connection is a native X.25 connection end to end, and migration to AMHS is not possible, then XoT is the next preferred option. It is recommended that a new LA be setup that uses the XoT over CRV path. Once the XoT connection has been verified and tested by each ANSP then actual migration of AFTN would be performed by the respective com centers similar to AMHS in 2.3.1 above. If PCCW are not able to provide serial interfaces on their CE routers then it would be incumbent on the ANSP to deliver the AFTN traffic as a XoT connection. Option 3. Migrate from XoT to XoT Where the AFTN connection between two ANSP’s is already using XoT, and if the trust in the performance of the CRV is high, then the cutover from the legacy link to the CRV could be as simple as an X25 route change on each ANSP’s respective XoT routers. Alternatively, a new LA could be setup and tested before being cutover at the system level by the respective ANSP’s com- centers.

Page 8 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

2.3.3 ADS-B

To deliver their stream to the PCCW gateway, likewise at the other end it would be up to the partner ANSP to ensure that that there is a multicast path available from the CRV egress to their flight data management system. Being multicast it is possible for the same information to traverse the same two endpoints via multiple network paths simultaneously, however some ANSPs may decide to setup new multicast groups via the CRV so that the performance of the CRV can be measured against the legacy link. Alternatively, ANSPs may decide to replace the multicast stream with unicast data flows that operate via an ADS-B filter. PCCW could implement Generic Routing Encapsulation (GRE) tunnel solution (NID to NID) between States/ Administrations who are agreeable to have direct connection for routing control over the any to any MPLS layer 3 backbone.

2.3.4 Voice

The specific strategy used to migrate the voice services will vary depending on the existing setup, the proposed voice interface between the ANSP and PCCW (E&M / ISDN / VoIP), how the partner ANSP is setup and their intended connection to PCCW. Despite this there are two main options. Option 1 – New buttons on the operator consoles - Preferred This option involves setting up new buttons on the operator consoles at each end. The new buttons are configured from the outset to route via the CRV. This strategy allows the new service to be configured and tested with minimal disruption to operators and also allows for an almost seamless cutover (pressing a different button). Another great advantage of this strategy is to ability to do a practical test of the voice quality by allowing the same pair of controllers test both paths within a few seconds of each other. Option 2 – Reconfigure existing connections to use the CRV Where Option 1 is not possible, the only other alternative is to reconfigure the existing connection. This will involve increased coordination between the two ANSP’s and PCCW as well as potentially multiple technical groups within an ANSP as it is likely that multiple systems will need to be reconfigured at the same time. E.g. Voice switches, networking devices etc. This option would also involve a lengthy outage and interruption to operational staff.

2.4 Technical Specifications of CRV (for applications reference)

CRV envisaged in the ICAO CNS/ ATM concept via through two backbones (one Multiprotocol Label Switching (MPLS), based on a terrestrial, satellite, or both networks, and one based on a secured Virtual Private Network over the public internet.

i. It will be a homogeneous and generalized application of the IP protocol in the transport network for voice and data aeronautical communications;

ii. It will established an appropriate Quality of Service (QoS) quality requirements;

iii. It will have a centralized and common network management;

iv. It will have a homogeneous and standardized interface, consisting Network Interface Device(s) (NID(s)) linked to the existing local switches, satellite and/or terrestrial links based

Page 9 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

on the Multiprotocol Label Switching (MPLS) technology, as well as ground services, based on a Virtual Private Network (VPN) over the public internet; v. It will have voice and data gateway service by the Service Provider; and vi. For IT security, individual ANSPs may implement an authentication service based on a cooperative public key infrastructure (PKI) including IPSec for IPv4 and IPv6 and digital certificates management for public IP links between ANSPs.

Figure 1: High level system overview of CRV

2.4.1 Service Level Agreement & Quality of Service

i. QoS are implemented using guidance from IETF RFC 4594 Configuration Guidelines for Different Service Classes. The routing protocol, voice, voice signaling, real-time interactive and standard data types shall all be given separate QoS bandwidth; ii. Differentiated Services Code Point (DSCP) QoS markings to traffic will be used before it enters the network; and iii. SLAs are based on States/ Administrations’ requirements (i.e. Packages A, B, B+, C, C+ and D offered by CRV contractor).

2.4.2 IP Addressing

i. CRV supports IPv4 and IPv6 addressing. The overall IP addressing plan will be centrally managed by the CRV contractor and will be known as the CRV IP address plan; ii. An IPv4 plan, appended as Appendix B, was agreed in the APAC region and was concluded through Conclusion 21/22 - Asia/Pacific ATN Interim Addressing Plan; and iii. The Middle East Regional (MID) region IPv4 plan is appended as Appendix C of this document.

2.4.3 Interface

i. The interface type provided by the NID to the CRV User is the Ethernet IEEE 802.3ab (1000 Base-T).

Page 10 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

2.4.4 Routing Restrictions

i. Route advertisements will be restricted so that each CRV User which interacts with the CRV routing protocol can only advertise subnets which are allowed in the CRV IP Address Plan.

2.4.5 Packet Loss Rate:

i. Packet loss rate of less than 0.1% for all the SLA-Voice; and

ii. Packet loss rate of less than 0.5% for all the SLA-Data.

2.4.6 For VoIP Transport (ED-137)

i. The VoIP Transport shall provide a maximum jitter of 40ms;

ii. The VoIP Transport shall provide a maximum packet loss of 0.1%;

iii. The VoIP Transport shall provide an availability greater than 99.9%; and

iv. The CRV shall use the high priority tags in the VPN packet headers to ensure that VoIP traffic is given high priority and minimal delay. An appropriate level of priority will be given to ED-137 SIP signaling.

2.4.7 Standards used

i. SNMP and MIB-II management protocols, implemented in accordance with RFC 1157 and RFC 1213;

ii. Implementation of the RTP/RTCP and RTP “header compression” protocols, in accordance with RFC 2508;

iii. The multiservice IP network permit the creation of VPNs using MPLS, in accordance with RFC 2547 and RFC 3031, and QoS configuration over MPLS/VPN, in accordance with RFC 3270 and RFC 2983;

iv. QoS is implemented using guidance from IETF RFC 4594. (Covered under QoS); and

v. The CRV provide transport for the ED-137 VoIP.

*Note: If at the time of the publication of this document the specific rules and standards mentioned in any of the other Sections have been revoked, superseded or updated, the new rules or standards shall be deemed as applicable.

2.5 Use Cases

Use Case 1 – ANSPs Interconnect AMHS

Summary of Situation ANSP ‘A’ and ANSP ‘B’ wish to have a direct connection between their AMHS. Both ANSPs decide that the AMHS application shall be built upon the Aeronautical Telecommunication Network (ATN). The ATN will in turn use the CRV.

Page 11 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

User Response Each ANSP already has a connection to the CRV. Each ANSP: 1. Notifies the CRV-OG Coordinator of their intention to establish the new facility. 2. Determines if their existing access speed is sufficient. If it is not the ANSP will arrange with the CRV Service Provider to increase their bandwidth. 3. Negotiates bi-laterally with the other ANSP to determine what IT security arrangements are required. In this User Case they decide to implement an IPSec VPN. 4. Negotiates bi-laterally with the other ANSP to determine what testing, acceptance and commissioning procedures are required. 5. Notify CRV-OG on completion of the implementation to update records. Operational Needs

UC1.1 The CRV link must meet the reliability and availability needs of AMHS. UC1.2 The CRV link must provide IP version 4 transport for the ATN. UC1.3 The CRV link must provide IP version 6 transport for the ATN. UC1.4 The CRV link must allow the ANSPs to implement IPSec VPN tunnels. UC1.5 The CRV link must allow for bandwidth changes.

Use Case 2 – ANSPs Implement ATC Voice over Internet Protocol Circuits

Summary of Situation ANSPs ‘A’ and ‘B’ wish to build upon the success of their AMHS implementation and have identified four Voice over Internet Protocol (VoIP) voice circuits which should be moved to the CRV.

User Response Each ANSP already has a connection to the CRV. Each ANSP: 1. Notifies the CRV-OG Coordinator of their intention to establish the new facility. 2. Determines if their existing access bandwidth is sufficient. If it is not, the ANSP will arrange with the Service Provider to increase their bandwidth. 3. Negotiates bi-laterally with the other ANSP to determine what IT security arrangements are required. In this Case they decide to implement an IPSec VPN to provide secure end-to-end transport between ANSPs. 4. Negotiates bi-laterally with the other ANSP to determine what testing, acceptance and commissioning procedures are required. 5. Tags the VPN traffic containing the Voice over Internet Protocol (VoIP) Real-time Transport Protocol (RTP) and Session Initiation Protocol (SIP) data with appropriate priority markings to allow the CRV Service Provider to identify the voice traffic. Operational Needs

UC2.1 The CRV link must meet the reliability and availability needs of ATC voice. UC2.2 The CRV link must provide an IP version 4 VPN tunnel to transport IP version 4 VoIP and SIP signaling. UC2.3 The CRV link must provide an IP version 6 VPN tunnel to transport IP version 6 VoIP and SIP signaling. UC2.4 The CRV link will use the high priority tags in the VPN packet headers to ensure that VoIP traffic is given high priority and minimal delay.

Use Case 3 – ANSPs Implement Automatic Ring-down Circuits

Summary of Situation ANSPs ‘A’ and ‘B’ wish to build upon the success of their AMHS implementation and have identified an Automatic Ring-down (ARD) analog voice circuit which should be moved to the CRV.

User Response Each ANSP already has a connection to the CRV. Each ANSP:

Page 12 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

1. Notifies the CRV-OG Coordinator of their intention to establish the new facility. 2. Determines if their existing access bandwidth is sufficient. If it is not, the ANSP will arrange with the Service Provider to increase their bandwidth. 3. Negotiates bi-laterally with the other ANSP to determine what voice quality Mean Opinion Score (MOS) is required. Perceptual Evaluation of Speech Quality (PESQ) ITU-T Rec. P.862 may be used to measure the effects of distortions (e.g. errors, packet loss, delay, etc.) to provide the MOS score. 4. Negotiates bi-laterally with the other ANSP to determine what testing, acceptance and commissioning procedures are required.

UC3.1 The CRV link must meet the reliability and availability needs of ATC voice. UC3.2 The CRV link must provide conversion from analog voice to VoIP. UC3.3 The CRV link must provide appropriate SIP signaling to support the ARD functionality. UC3.4 The CRV link must provide IP version 4 transport for the VoIP. UC3.5 The CRV link must provide IP version 6 transport for the VoIP. UC3.6 The CRV link will use the high priority tags in the packet headers to ensure that VoIP traffic is given high priority and minimal delay. The CRV must give an appropriate level of priority to SIP. UC3.7 The CRV link must deliver voice so that it is clearly understood with minimal delay.

Use Case 4 – ANSPs Implement Analog Voice Circuits

Summary of Situation ANSPs ‘A’ and ‘B’ wish to build upon the success of their AMHS implementation and have identified four analog voice circuits which should be moved to the CRV.

User Response Each ANSP already has a connection to the CRV. Each ANSP: 1. Notifies the CRV-OG Coordinator of their intention to establish the new facility. 2. Determines if their existing access bandwidth is sufficient. If it is not, the ANSP will arrange with the Service Provider to increase their bandwidth. 3. Negotiates bi-laterally with the other ANSP to determine what voice quality Mean Opinion Score (MOS) is required. In this Case they decide a MOS of 4.0 is required so they select a CRV service level that provides the required voice quality. 4. Negotiates bi-laterally with the other ANSP to determine what testing, acceptance and commissioning procedures are required. Operational Needs

UC4.1 The CRV link must meet the reliability and availability needs of ATC voice. UC4.2 The CRV link must provide conversion from analog voice to VoIP. UC4.3 The CRV link must detect analog signaling and provide appropriate SIP signaling and vice versa. UC4.4 The CRV link must provide IP version 4 transport for the VoIP. UC4.5 The CRV link must provide IP version 6 transport for the VoIP. UC4.6 The CRV link will use the high priority tags in the packet headers to ensure that VoIP traffic is given high priority and minimal delay. The CRV must give an appropriate level of priority to SIP. UC4.7 The CRV link must deliver voice so that it is clearly understood with minimal delay.

3.0 IMPLEMENTATION SUPPORT

3.1 Introduction

The aim of the transition is to be interruption less. But as the services must migrate from the current network infrastructure to the CRV, an interruption time due to disconnection and reconnection, is

Page 13 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0 mandatory and the team involved (CRV-OG, CRV Members and Contractor) will be of utmost importance to the overall process.

This chapter comprises the basic teams involved in the implementation of the CRV infrastructure, the roles of each professional and the main coordination steps and stakeholders including the CRV-OG.

These responsibilities come in addition to those stated in the Terms and Conditions and Terms of Reference.

Figure 3 describes the relevant entities for the CRV implementation.

Figure 3: Relevant Entities to this Project. (Source: CRV Tender doc - Att II - Terms of Reference_v3)

Page 14 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

3.2 Implementation Team

The implementation team will be composed of the CRV-OG representatives, the National Points of Contact (NPOC), Local Points of Contact (LPOC) and the CRV Contractor Team, as described in the following sections.

3.2.1 CRV-OG

The CRV Operations Group (OG) will provide oversight of the function and performance of the network after the CRV is completely installed. Besides, it will be involved in the oversight of the implementation of the CRV post Contract Award.

The main activities and roles applied to the CRV-OG during the implementation of the CRV infrastructure are:

i. Develop close coordination with the National CRV POC and Contractor for the complete implementation of the CRV node;

ii. Provide the CRV IP Addressing Scheme (Plan) to the Contractor, in close coordination with the National CRV POC; and

iii. Provide the classification and marking scheme for the prioritization of traffic for the QoS to be used by the aeronautical applications in the CRV network.

Note: When applying QoS, the end-to-end configuration needs to be observed (LAN- layer 2 switches and WAN- Layer 3 routers devices). So, this activity will involve close coordination with the National CRV POC and Contractor, taking into consideration the tender document Att II - Annex b - Matrix of Flows for CRV services_v2), SLA, and the tender document Att II - Annex c - Mapping of services for quality management_v2.

3.2.2 National CRV Points of Contact

Table 1 contains the National CRV Points of Contact that will be in charge of the whole process in each CRV Member, independently if the State involved has more than one node.

The main activities and roles of the National CRV Points of Contact are:

Page 15 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

i. Develop close coordination with the CRV-OG representatives, Contractor and Local CRV POC for the complete implementation of the CRV node;

ii. Receive the requests for site surveys from the Contractor, coordinating the actions with the Local CRV POC;

iii. Participate and/or Coordinate the participation of the Local CRV POC and Local Staff in the implementation meetings with the Contractor;

iv. Participate and/or Coordinate the participation of the Local CRV POC and Local Staff in the training package (on line, on site, initial and refresh) as defined in the Section 3.12 (Training) of the Terms of Reference (TOR) document;

v. Coordinate the actions and instruct the Local CRV Points of Contact regarding all activities involved in the implementation phase;

vi. Review and approve the System Design Document (SDD), System Engineering plan (SEP) and other documents, part of the tender package, prepared by the Contractor upon the contract award and signature; vii. Review and approve the Validation Plan, including the Site Acceptance Test (SAT), prepared by the Contractor; viii. Oversee if the Contractor is following the national laws and procedures concerning the assignment of frequencies with the radio regulator authorities in each country (case of microwave and satellite equipment);

ix. Update the ICAO CNS Regional Officer (ICAO Asia and Pacific Regional Office) with regard to the timeframe, situation, difficulties and other topics deemed necessary for the implementation of the CRV node(s);

x. Provide the local CRV IP Addressing Scheme - Plan to the Contractor in close coordination with the CRV-OG representatives.

xi. Provide the current numbering plan for the ATS Switched Voice Circuits to the Contractor; xii. Provide the current direct hotline Voice Circuits configuration to the Contractor; xiii. Provide the classification and marking scheme for the prioritization of traffic for the QoS to be used by the aeronautical applications in the CRV network (See note in the paragraph 3.2.1.3); xiv. Receive the requests for site surveys from the Contractor and coordinate the activities with the Local CRV POC; and xv. Approve the implementation planning.

Page 16 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

Table 1: National CRV Points of Contact

Asia Pacific Region:

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC) Director of Technical Services Office Tele: +93 (0)20 Afghanistan Eng. Mohammad Director of CNS [email protected] Afghanistan 2311962 Kabul international airport Civil Aviation Shaker Popal om Mobile : +93 (0)799 601095 Authority (ACAA)

Airservice Australia Terence.palmer@ai Airservices Mr. Terence Team Leader 25 Constitution Avenue

Australia rservicesaustralia.c Tel:+61 (2) 6268 4960 Australia Palmer Networks Canberra 2600, ACT

om Australia

Communication Officer (ATM) Dhaka Hazrat Headquarters, Kurmitola Bangladesh Mr. S M A Civil Aviation [email protected] Tel +880 171 506 7502 Shahjalal Dhaka 1229 Gaffar Fakir Authority of d Fax +880 (2) 890 1411 BANGLADESH Bangladesh

Page 17 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC)

Air Navigation Services, Ministry of Mobile :+975 17622702 [email protected] Information & Superintendent, Office: +975 8 271347 Bhutan Mr. Pema Tashi Paro Airport Communicatio ANS (Ext.:107),

ns Fax.: +975 8 271944 Department of Civil Aviation"

Brunei

Darussalam

State Secretariat of Civil Aviation Chief of CNS #44 Phnom Penh State Secretariat neangto.ans@gmail Tel +855 (23) 224 258 Cambodia Mr. Neang To International Airport of Civil .com Fax +855 (23) 224 259 Russian Federation Blvd. Aviation Phnom Penh CAMBODIA

Page 18 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC)

Air Traffic Management Bureau of CAAC No.301 Weatern, Dongwei huangzheng@atnc. Tel:+86 58729977 China ATMB/CAAC Mr. Huang Zheng Engineer Rd, SunHe, Chao Yang

com.cn Fax:+86 (10) 67331459 District,

Beijing, China

Civil Aviation Department Civil Aviation Headquarters Chief Hong Kong, Department, Tel:+852 2910 6505 1 Tung Fai Road

Mr. MH Hui Electronics [email protected]

China Hong Kong, Fax:+852 2845 7160 Hong Kong International Engineer China Airport, Lantau HONG KONG, CHINA

Civil Aviation Authority of Macao, China Alameda Dr. Carlos D' ADA- samsonpun@aacm. Tel:+853 8796 4150 Assumpcao China, Macau Administration Mr. Samson Pun Safety Officer

gov.mo Fax:+853 2833 8089 336-342, Centro Comercial of Airports Cheng Feng 18 andar MACAO, CHINA

Page 19 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC) General Administration of Civil Aviation Democratic General Vice Chief, Tel:+850 (2) 181111 Ext. Pyongyang International People's Administration Communication [email protected]. Mr. Ri Sung II 8108 Airport

Republic of of Civil Section ATM kp

Fax:+850 (2) 381 4410 Sunan District, Pyongyang Korea Aviation Department DEMOCRATIC PEOPLE'S REPUBLIC OF KOREA Manager Air Airports Fiji Limited Tel:+679 673 1623 Airports Fiji Mr. Kelepi Navigation Private Mail Bag Fiji Mobile:+679 990 6110 Limited Dainaki Engineering [email protected] Nadi Airport

Fax:+679 673 1123 Services FIJI ISLANDS France (territories of French jean- Direction Aviation Civile Polynesia, Mr. Jean-Marc Tel:+687 352443 DSNA (France) ATM Expert marc.valentin@avi BP H1, 98800

New Valentin Fax:+687 265 206

ation-civile.gouv.fr NEW CALEDONIA Caledonia and Wallis and Futuna)

Airports Authority of India Airports Rajiv Gandhi Bhawan Mr. Anurag General Tel:+91 (11) 2461 0537

India Authority of [email protected] Saddurjung Airport

Sharma Manager (COM) Fax:+91 (11) 2463 2930 India New Delhi 110003 INDIA

Page 20 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC)

Airnav Indonesia Airnav Tel:+62 (21) 5591 5000 Ms. Arief Head, IT arief.agustama@air Support Building Indonesia Indonesia Mobile: +62 811936582 Agustama Division navindonesia.co.id Jl. Ir. Juanda, Tangerang Fax:+62 (21) 5591 5100 INDONESIA

Chief of Flight Information 1st 2-1-3 Kasumigaseki Section, katou- Tel:+81-3-5253-8751 Japan JCAB Mr. Kenichi Kato Chiyoda-ku Tokyo 100-

Operations and [email protected] Fax:+81-3-5253-1664 8918 JAPAN Flight Inspection Division

Kiribati

Director of Air Director of Air Traffic Traffic Technical Service Center Lao Air Traffic Tel:+856 (20) 585 777 94 Mr. Lamkeo Technical lamkeoattsc@hotm P.O. Box 2985 Lao Management Fax +856 (21) 512 216 Phouxay Service Center ail.com Wattay International

Lao Air Traffic Airport Management Vientiane Air Traffic Department of Civil Management Aviation Malaysia Department Of Sector No.27, Persiaran Perdana Mr. Sahrol Nizal [email protected] Tel:+603 8871 4278 Malaysia Civil Aviation for Director Level 4, Block Podium B,

Bin Ab Rashid y Fax:+603 8881 0530 Malaysia General of Civil Precinct 4 Aviation 62618 Putrajaya Malaysia MALAYSIA

Page 21 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC) Department of Civil Aviation ATC Operating Building Department Of winmawdca@gmai Tel:+95 92 5018 3029 Myanmar Mr. Win Maw Deputy Director Yangon International

Civil Aviation l.com Fax:+95 (1) 533 016 Airport Yangon 11021 MYANMAR Team Leader Airways New Zeland Mr. Vaughan Network 26 Sir William Pickering Hickford Development Tel:+64 (3) 358 1521 Airways New vaughan.hickford@ Drive New Zealand

Zealand airways.co.nz Russley, Christchurch, Mr. Dave Network Tel:+64 (3) 357 0346 Canterbury 8043 Pearson Support Team NEW ZELAND Leader

Pakistan Civil Aviation Senior Fasih-uz- Authority Mr. M. Fasih-uz- Additional Zaman.Khan@caap Headquarters, Terminal-I Pakistan Zaman Khan Director Com- akistan.com.pk Jinnah International Airport Ops Karachi 75200 PAKISTAN

Page 22 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC)

Civil Aviation Authority of the Philippines Air Navigation Service Civil Aviation ANS Technical Center Mr. Elmer E. elm_gomez@yaho Tel:+63 (2) 944 2192 Philippines of the Division Chief Building

Gomez o.com Fax:+63 (2) 879 9244 Philippines Old Mia Road, Pasay City 1300 Metro Manila, PHILIPPINES Ministry of Land, Ministry of Infrastructure and Transport Republic of Land, Mr. Kyung Joon, Assistant Tel:+82 (44) 201 4362 11, Doum-ro 6

[email protected]

Korea Infrastructure Jang Director Fax:+82 (44) 201 5637 Sejong Special self- and Transport governing City REPUBLIC OF KOREA Civil Aviation Authority of Engineer Singapore Air Singapore Mr. Augustine (Communication augustine_lau@caa Tel:+65 6422 7071 Singapore Traffic Control Singapore Changi Airport

Lau s/ Navaids s.gov.sg Fax:+65 6542 2447 Centre P.O. Box 1 Systems) SINGAPORE 918141 Airport & Aviation Services Airport & Head of head.eane@airport. (Sri Lanka) Ltd. Aviation Mr. Wipula Electronics and lk Mobile:+94 77 304 7653 Sri Lanka Colombo Airport Services (Sri Wimanshanthi Air Nav [email protected] Fax:94 (11) 263 3488 Ratmalana 10370 Lanka) Ltd. Engineering om SRI LANKA

Page 23 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State/ National CRV ANSP/ Administratio Point of Contact Job Title E-mail Telephone/FAX Address CAA n (POC) Aeronautical Radio of Chief, Policy chonlawit.ba@aero Thailand Ltd. Aeronautical Mr. Chonlawit Tel: +66 2285 9578 +66 6 and Strategy thai.co.th 102 Soi Ngamduplee Thailand Radio of Banphawatthanra 3265 3643 +66 8 6575 7901 Management [email protected] Tungmahamek, Sathon Thailand Ltd. k Fax:+66 (2) 285 9057 Bureau om Bangkok 10120 THAILAND Federal Aviation Administration Federal ATO, Programme International Aviation [email protected] Management Organization

United States Mr. Hoang Tran Telecommunicat Tel:+1 (202) 267 7142

Administration v 800 Independence Avenue, ion Lead (FAA) SW Washington, DC 20591 USA

Page 24 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

MID Region (CRV) Focal Points (updated in December 2017 at CRV OG/3 meeting):

State Name/Title Contact Details (Tel./Fax/Mobile/Email)

Bahrain Mohamed Ali Saleh Fax: +973 17329966 Chief Aeronautical Telecomm Tel: +973 17321187 Email: [email protected] Yaseen Hassan AlSayed Fax: +973 17329966 Head Aeronautical Telecomm Network Tel: +973 17321183 Email: [email protected] Egypt Mr. Mohamed Ramzy Mohamed Abdallah Tel: +202 22657981 Director of AFTN/AMHS Technical +201007736780 Department Email: [email protected] Eng. Haitham Mohamed Ahmed Eldosoki Tel: +202 22650781 Director of AIM Technical Department +201007810781 Email: [email protected] Iran Mr. AliAkbar SalehiValojerdi Fax: +98 21 66025101 Senior Expert of IRANAFTN/AMHS Tel: +98 21 6102337 Training Department Mobile: +989 124 202775 Email: [email protected] Mr. Alireza Mahdavisefat Fax: +98 21 66025101 Senior Expert of IRANAFTN/AMHS COM Tel: +98 21 6314 6432 Centre Mobile: +989 333510320 Email: [email protected] Iraq

Jordan Ms. Mona Ribhi AlNaddaf Tel: +9626 4881473 +96279 9876710 Email: [email protected] Kuwait Mr. Hassan Alattar Fax: +965-2 4721 279

Page 25 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State Name/Title Contact Details (Tel./Fax/Mobile/Email) Communication Engineer Tel: +965-2 4732 530 Mobile: +965 99449454 Email: [email protected] Lebanon Mr. Mohamad Abdallah Saad Fax: +961 1 629 031 Head of Telecommunication Equipment Tel: +961 1 628 151 Mobile: +961 3 280 299 Email: [email protected] Libya Oman Mr. Nasser Salim Al-Suleimani Email: [email protected] Chief ATM Systems [email protected] Mr. Ibrahim Said Al-Hajri ATM Systems Engineer Qatar Saudi Arabia Ibrahim bash Fax: +966 12 671 9041 Senior Systems Engineer Tel: +966 12 671 7717 Ext 1119 Automation Engineering Branch Mobile: +966 50 567 1231 Email: [email protected] Sudan Eng. Yasir Eltayeb Sidahmed Fax: +249 183 770001 Tel: +249 183 782701 Email: [email protected] Syria

UAE Greg Kurten Fax: +971 2 599 6872 A/Director CNS Tel: +971 2 599 6860 Communication, Navigation and Email: [email protected] Surveillance Shahzad Chaudhary Fax: +971 2 599 6872 Senior CNS Engineer Communication, Tel: +971 2 599 6865 Navigation and Surveillance Email: [email protected]

Page 26 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State Name/Title Contact Details (Tel./Fax/Mobile/Email)

Yemen

Page 27 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

3.2.3 Local CRV Points of Contact

Table 2 contains the Local Points of Contact. In fact, the professionals nominated and listed in the referred tables will really take part in the installation, on behalf of the States, and will be in charge of the oversight of the Contractor´s team in each site. They will report directly to the National Points of Contact of each CRV Member. The main activities and roles for the Local CRV Points of Contact are:

i. Instruct and coordinate the actions with all the local staff involved in the CRV implementation;

ii. Develop close coordination with the National CRV POC and the Contractor´s site staff for the complete implementation of the CRV node;

iii. Coordinate the actions for the site surveys with the National CRV POC;

iv. Participate in the implementation meetings with the Contractor (if decided by the National Point of Contact);

v. Participate to the elaboration of the implementation planning;

vi. Participate in the Training Package and nominate, to the National CRV POC, the Local staff there will participate in the referred events; vii. Report, give feedback and update the National CRV POC regarding all aspects concerning the implementation of the CRV node; viii. Assist the National POC in the revision and approval of the SDD, SEP and other implementation documents, prepared by the Contractor;

ix. Assist the National POC in the revision and approval of the Validation Plan including the SAT, prepared by the Contractor;

x. Oversee the installation in order to ensure that the Contractor team is keeping the working area clean and free from fire hazards and if after installation, all excess material is duly removed;

xi. Make sure that the local safety rules are observed by the Contractor in terms of intervention on operational systems; xii. Oversee the installation in order to ensure that the Contractor is following what is described in the TOR, item 3.3.2.9, concerning the Electromagnetic compatibility/ grounding; xiii. Oversee if the QoS configuration is duly performed by the Contractor, as defined by the CRV-OG representatives and the National CRV POC; xiv. Oversee if the CRV IP Addressing Scheme (Plan) is duly performed by the Contractor, as defined by the CRV-OG representatives and the National CRV POC; xv. Oversee if the configuration of current numbering plan for the ATS Switched Voice is duly performed by the Contractor, as defined by the CRV-OG representatives and the National CRV POC;

Page 28 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

xvi. Oversee if the configuration of the current Direct Circuits (DIR) is duly performed by the Contractor, as defined by the CRV-OG representatives and the National CRV POC; xvii. Coordinate the actions for the site surveys and assist the Contractor´s personnel during the visits; and xviii. Hold meetings with the Contractor as deemed necessary and report to National POC.

Page 29 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

Local CRV Points of Contact (installation and oversight of the Contractor´s team on each site)

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact

Afghanistan Afghanistan Kabul Eng. Mohd.Shaker Popal [email protected] Kabul International Airport Civil Aviation Authority (ACAA) American Pago Pago Tel.: Pago Pago International Samoa Fax : Airport Australia Airservices Brisbane Mr. Michael Earnes Michael.Eames@Airser +61 2 6268 5042 Australia Airservices

Australia vicesAustralia.com +61 409 357 965 Australia Brisbane Air Traffic Services Centre Airport Drive, Eagle Farm, Queensland 4009 Australia

Australia Airservices Melbourne Bibhuti Panda +61 2 6268 5169 Australia Airservices Australia +61 451 060 674 Australia Melbourne Air Traffic Services Centre Tower Road, Tullamarine, Victoria Australia Bangladesh Dhaka Tel 088-02- Hazrat Shahjalal 8920852, 088-02- International Airport - 8901465 Dhaka COM Center email [email protected] v.bd

Page 30 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Bhutan Air Paro Mr. Pema Tashi Paro Airport Navigation Mobile :+975 Services, 17622702 Office: Ministry of +975 8 271347 Information (Ext.:107), Fax.: & +975 8 271944 Communicati ons Department of Civil Aviation Air Paro Mr. Sangay [email protected] Tel: +97508 Paro Airport Navigation Senior Communication 271407, 272511 Services, Officer Mobile: Ministry of +97517342667 Information Fax.: & +97508271407 Communicati ons Department of Civil Aviation Brunei Brunei Tel.: Brunei International Airport Darussalam Fax :

Page 31 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Cambodia Phnom Penh Mr. Norngsao 85- Tel.: 855-23- Phnom Penh International 16771136, 890194, 855-23- Airport - Phnom Pehn Mr. Sivaluk 66-2502-6742 890262, Mr. COM center (Thailand number) Norngsao 85- 16771136, Mr. Sivaluk 66-2502- 6742 (Thailand number) Fax : China ATMB - Air Beijing Mr. Huang Zheng [email protected] Tel.:+86(10)58729 Beijing Network Control Traffic .cn 977 Center Management Fax No.301 Weatem, Dongwei Bureau,CAA :+86(10)67331459 Rd. Sunhe, Chao Yang C District, Beijing ,China

China ATMB - Air Guangzhou Tel.:+86-020- Guangzhou COM Network Traffic 86122850 Center Management Fax :+86-020- Bureau,CAA 86636200 No.3 Nanyun East Street, C Airport Road, Baiyun District Guangzhou, China China, Hong Hong Kong Mr. Gene Kwok [email protected] Tel: +852 2910 Civil Aviation Department Kong k 6523 Headquarters, 1 Tung Fai Fax: +852 2845 Road, Hong Kong 7160 International Airport, Lantau, Hong Kong China, ADA- Macau Tel.: Macau Administraito (+853)28861111 Macau International Airport n of Airports Fax: PAC on Talpa (+853)28862222 Macao, China Email: airportdirector@a da.com.mo

Page 32 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Cook Rarotonga Tel.: Rarotonga International Islands Fax : Airport Democratic ATC, Pyongyang Tel.: 850-2-381 Pyongyang City People's Pyongyang 5910 Republic of International Fax : 850-2-831 Korea Airport, 4410 SUNAN District, DPR Korea Fiji Airports Fiji Nadi Mr. Jioji Kinisi [email protected] Tel: +679 ATMC Equipment Room, Limited 6731603 ATMC Building Fax:+679 6731123 Ottawa Road, Nadi Airport, Fiji Islands French Service d'Etat Papeete Mr. Marc Deginther Marc.deginther@aviatio Tel: (689) 40 86 Service d'Etat de l'Aviation Polynesia de l'Aviation n-civile.gouv.fr 10 32 Civile Civile / Faa'a BP 6011 - 98702 Faa'a International Mobile: (689) 89 International Airport Airport 29 84 74

Fax: (689) 40 86 10 39

India Airports Mumbai Mr. Hemant Ramchandani [email protected] +91 (22) 2682 Authority of Joint General Manager 8123 India (CNS) Mobile: +91 92 CSI Airport 2331 4272 Mumbai India India Airports New Delhi Mr. K. S. Kathayat Authority of AGM (COM) India IGI Airport New Delhi 110037

Page 33 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact India

Indonesia Jakarta ATS Jakarta Tel.: Centre Fax : Soekarno-Hatta International Airport Jakarta, Tangerang, Banten 19120 Indonesia Indonesia Makassar Makassar Tel.: ATS Centre Fax : Sultan Hasanuddin International Airport Jalan Raya Airport No. 1 Makassar Sulawesi 90552, Indonesia Japan Tokyo Air Tokyo TBD Tel.: 1-2, Namiki, Tokorozawa Traffic Fax : city, Saitama pref. Control 359-0042 Japan Centre

Japan Air Traffic Fukuoka TBD Tel.: Management Fax : 1302-17 Nata Higashi-ku Center Fukuoka-city Fukuoka-Pref (ATMC) 811-0204 Japan

Kiribati Mr Tarawa Tel.: Bonriki International CARLIER Fax : Airport Yann of DGAC/DAC- New Caledonia

Page 34 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Lao People's Vientiane Tel.: 856-21- Democratic 520157, 856-21- Wattay International Republic 512090, Airport Ms. Pen 66- 802969631 (Thailand number). Mr. Somboon 856-20-5560-1638 Malaysia Kota Kota Kinabalu Mr. Mohd. Dahri Bin [email protected] Tel:+6 088 ATCC Building,

Kinabalu Air Munik y 224911 Jalan Kepayan Traffic Mobile: +6 019 88618 Kota Kinabalu, Control 8815780 Sabah. Centre Fax: +6 088 219170 Malaysia Kuala Selangor Mr. Mohd. Hamli Bin [email protected]. Tel: +6 03 7846 Kuala Lumpur Air Traffic

Lumpur Air Alias my 5233 Control Centre, Traffic Mobile: +6 012 Level 1, Block A, Complex Control 629 5405 of Air Traffic Control Centre (KL Fax: +6 03 7845 Centre, ATCC) 6590 47200 Subang, Selangor.

Malaysia Kuching Kuching Mr. Suzaiman bin Zaini [email protected] Tel: +6 082 Kuching Air Traffic Control Sub-Centre 616532 Centre, Kuching Air Mobile: +6 016 Kuching International Traffic 8881971 Airport, Control Fax: +6 082 93728 Kuching,Sarawak. Centre 454523 Maldives Maldives Male Tel.: 960-322071 Malé International Airport Airports Fax: 960-317202 Ibrahim Nasir International Company atcc @ Airport Limited airport.com.mv Hulhule 22000, Republic of Maldives

Page 35 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Marshall Majuro Tel.: Marshall Islands Islands Fax : International Airport Micronesia Chuuk/Kosrae/P Tel.: Pohnpei International (Federated onapei/Yap Fax : Airport States of) Mongolia Communicati Ulaanbaatar Tel.: +976 11 Khan-Uul district, 10th on 281603 khoroo, Buyant-Ukhaa, Navigation Fax : +976 Ulaanbaatar, Mongolia Surveillance 1170049785 section, Civil Aviation Authority of Mongolia Myanmar Department Yangon Mr. Kyaw Zay Ya [email protected] Tel:95-1-533030, ATC Tower Building, Of Civil om Ext:453 Yangon Int’l Airport, Aviation Airport Road, 11021, Mobile:95-9- Mingaladon Township, 974684449 Yangon, Myanmar.

Fax:95-1-533016 Nauru Nauru Tel.: Nauru International Airport Fax : – Yaren Nepal Kathmandu Tel.: Tribhuvan International Fax : Airport New Direction de Noumea Mr. Félicien TORRES felicien.torres@aviation Tel.: Nouméa Magenta Airport, Caledonia l'aviation -civile.gouv.fr 179, rue Roger Gervolino civile / BP H1 - 98849 Noumea Service de la Cedex Navigation Aerienne

Page 36 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact New Airways New Christchurch, Tel.: 20 Sir William Pickering Zealand Zealand Fax : Drive, Russley, Christchurch, New Zealand New Airways New Auckland, Tel.: Cyrill Kay Road, Auckland Zealand Zealand Fax : Airport, Auckland, New Zealand Niue Islands

Pakistan G.M. Karachi Mr. Fasih-uz-zaman aftnophq@caapakistan. Jinnah International Airport

Communicati com.pk +92 (21) 924-8732 on +92 (21) 924-8733 Headquarters (fax) Civil Aviation Authority, Technical Division, COM-OPS, Branch Terminal -1, JIAP, Karachi, Pakistan Palau Koror Tel.: Roman Tmetuchl Fax : International Airport

Page 37 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Papua New Port Moresby Tel.: Jacksons International Guinea Fax : Airport Morea-Tobo Rd Port Moresby 121 Papua New Guinea

Philippines Civil Pasay City Mr. Gilmar D. Tiro [email protected] Tel.: +63 (2) 944- Philippine Air Traffic Aviation of 2242, +63 (2) Management Center CAAp the 6727729, +63 (2) Compound, Old Mia Road, Philippines 6727728 Pasay City, 1300 Metro Fax : Manila, PHILIPPINES Republic of AFTN Center Seoul Tel.: + 823 62, Haneul-Gil Gangseo-Gu Korea 28800335 Seoul, 157-711, Korea Fax : Samoa Faleolo Tel.: Faleolo International Fax : Airport Singapore Singapore Singapore Tel.: 6214 LORADS II Building, 60, Air Traffic 8050/65 Biggin Hill Road, Control Fax : 6545 9370 Singapore Postal Code Centre 509950 Solomon Honiara Tel.: Honiara International Islands Fax : Airport Sri Lanka Colombo Tel.: Colombo Ratmalana Fax : Airport Thailand Aeronautical Bangkok Tel.: 0-2287- 102 Ngamduplee Radio Of 3531-41 Tungmahamek sathorn Thailand Fax : Bangkok Thailand 10120 LTD Timor Leste Dili Tel.: Presidente Nicolau Lobato Fax : International Airport

Page 38 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Tonga Tongatapu Tel.: Fuaʻamotu International Fax : Airport Tuvalu Funafuti Tel.: Funafuti International Fax : Airport United FAA Oakland Tel.: 510-745- 5125 Central Avenue States Oakland Air 3000 Fremont, CA 94536-6531 Route Traffic Fax : Control Center United FAA Salt Salt Lake City Mr. Tom Beschler Thomas.ctr.beschler@fa Tel.:(609) 485- 2150 W. 700 N. Salt Lake States Lake City a.gov 4818 City UT 84116 Network Fax : Enterprise Management Center Vanuatu Mr Port Vila Tel.: Bauerfield International CARLIER Fax : Airport Yann of DGAC/DAC- New Caledonia Viet Nam Ho Chin Tel.: Tan Son Nhat International Minh/Hanoi Fax : Airport Noi Bai International Airport

Page 39 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Wallis and Aviation Wallis Mr. Bernard Le Guillou bernard.le- Hihifo Airport Futuna Civile guillou@aviation- Tél: 00-681-72- Aviation Civile

civile.gouv.fr 12-02 BP1 Mata-Utu Fax: 00-681-72- 98600 WALLIS 29-54 mél: seac- [email protected]

ICAO MID Region Bahrain Bahrain Civil Manama Affairs Egypt NANSC Cairo Iran Civil Tehran Aviation Organization Iraq CAA Baghdad Jordan CARC Amman Kuwait Directorate Kuwait General of CA Lebanon CAA Beirut Libya CAA Tripoli Oman Public Muscat Authority for CA Qatar CAA Doha Saudi General Jeddah and Arabia Authoroity of Riyadh CA Sudan CAA Khartoum

Page 40 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact Syria CAA Damascus UAE General CA AbuDhabi Authoroity Yemen CA and Met Sanaa Authrority Interregion al connectivity Russia Interregional Khabarovsk China: Mr. Huang Zhang China: Mr. Huang China: connection Tel：0086-010-67318494 Zhang Address：No. 301 ，Qian for AFTN ,0086-010-58729977 Tel：0086-010- Wei Gou Cun，Sun He between FAX：0086-010- 67318494 ,0086- Xiang, Chaoyang District Beijing 67331459 010-58729977 Beijing 100122 China E- FAX：0086-010- and mail:[email protected] 67331459 Russia Far East Air m.cn E- Address: Branch “Far East Navigation” mail:huangzheng Air Navigation” 680031, 680031, POC Ms. Tatyana @atnc.com.cn Matveevskoye Shosse, 28a Matveevskoy Ivanovna Khvan Khabarovsk Russia e Shosse, 28a Tel: 007(4212)418-591 POC Ms. Tatyana Khabarovsk Email: Ivanovna Khvan Russia [email protected] Tel: 007(4212)418-591 Email: [email protected] kovd.ru

Page 41 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

State State/ANSP Site Local CRV Points of Email Telephone / Fax Service installation Contact UK Interconnecti Fareham Name: Stuart Dingle [email protected]. Name: Stuart

on with uk Dingle Physical Address: 4000 Singapore Email: Parkway, Whiteley, Stuart.Dingle@nat Fareham, Hants PO15 7FL s.co.uk D: 01489 612259 M: 07786 211975 South Africa Interconnecti Johannesburg on with India Italy Interconnecti Rome on with Thailand

Page 42 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

3.2.4 CRV Contractor

The Contractor shall nominate all the staff involved in the implementation of the CRV node, mainly the Program Manager for the CRV program. The Contractor will follow all the steps described in the tender documentation, specially the TOR and Instructions to Tenderers, for the implementation of the CRV node. The main activities to be carried out by the Contractor during the implementation are:

i. Submit the updated SDD and the SEP to the CRV-OG, to the CNS Officer for the Asia/Pacific Regional Office and to the National CRV POC;

ii. Submit the requests for site surveys to the National CRV POC following the procedures described in the paragraph 4.1.2.2;

iii. Update and submit the Installation Transition Plan to the CRV-OG, to the CNS Officer for the Asia/Pacific Regional Office and to the National CRV POC;

iv. Be responsible for the supply, transport, installation, start-up and operation of all CRV equipment especially designed for a given CRV node;

v. Be dealing with customs and transport company about shipping and introducing the equipment in the Country;

vi. The interconnection (to be provided by CRV users) of the Network Interface Device (NID) to the Local Area Network (LAN) switches and other local equipment, including Voice Communication System (VCS), will be confirmed during the site survey; vii. Demonstrate before the final validation of the SDD and through a test bed that the main characteristics of the intended design of the network will meet the performance requirements, SLA, safety, security and contingency requirements; viii. Implement the CRV IP Addressing Scheme (Plan), following the information provided by the CRV-OG and/or the National CRV POC;

ix. Implement the classification and marking scheme for the prioritization of the traffic and Quality of Services (QoS), as described in the document Att II - Annex c - Mapping of services for quality management_v2 and in coordination with the CRV-OG and the National and Local CRV POCs (See note in the paragraph 3.2.1.3);

x. The Contractor shall measure the established parameters during circuit implementation (in accordance with ITU-T), and shall also monitor them for 24 hours to show compliance with the established specifications;

xi. Implement the configuration of current numbering plan for the ATS Switched Voice, as defined by the CRV-OG representatives and the National CRV POC, and taking into account the tender document Att II - Annex b - Matrix of Flows for CRV services_v2; xii. Implement the configuration of the current Direct Circuits (DIR), as defined by the CRV-OG representatives and the National CRV POC and taking into account the tender document Att II - Annex b - Matrix of Flows for CRV services_v2;

Page 43 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

xiii. Submit, in details, the escalation process to be followed for the implementation in each CRV node;

xiv. Submit, to the CRV National POC, the documentation for the training of the CRV technicians;

xv. Contractor Representative shall record the minutes of the meeting and distribute the minutes within three (3) Business Days of the meeting date;

xvi. The Contractor shall propose a planning chart that includes all the actions, steps, milestones, meetings, after negotiations with CRV Local and National POC and respect it once approved by the CRV User Representative or amend it in coordination with CRV User representatives; and xvii. The Contractor shall help the CRV User in the uptake of responsibility before commissioning the equipment by accompanying the CRV User technicians in charge of the equipment.

4.0 BASIC SITE IMPLEMENTATION REQUIREMENTS

Chapter 4 describes the site and facilities requirements envisaged in the implementation phased for the CRV infrastructure, divided into CRV User´s and Contractor´s responsibilities, and also the main hardware and software for the proof of concept and implementation of the WAN links, LAN protocols, applications and main equipment.

These responsibilities come in addition to those stated in the Terms and Conditions and Terms of Reference.

4.1 Site/ Facilities Requirements

4.1.1 CRV User Responsibility

i. The CRV User shall provide the physical space for the installation of cabinets and equipment;

ii. The CRV User shall deliver to the premises the electric power required to feed the equipment to be provided by the Contractor;

iii. The CRV User shall provide access to the equipment to be connected to the CRV NID and to analog/ digital voice gateway;

iv. The CRV User shall accompany and assist the Contractor during the whole operation;

v. The CRV User shall provide room for storing the equipment, received before its installation; and

vi. The CRV User shall inform the Contractor about the local safety rules and procedures and produce suited documents as deemed necessary.

4.1.2 Contractor Responsibility

i. The Project Manager, on behalf of the Contractor, shall nominate and introduce all the staff involved in the site surveys and in the implementation of a CRV node. The list with the staff

Page 44 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

nominated will be submitted to the National and Local CRV POCs with the formal requests for the site survey and beginning of the very implementation of the CRV equipment and following the procedures described in the paragraph 4.1.2.4;

ii. The Contractor shall identify the exact locations of the equipment during the site survey; iii. The Contractor will be responsible for providing the accessories, switches, cables, connections between the main distribution panel and the NID; iv. The Contractor shall be responsible for the installation of the CRV network equipment, accessories and the provision of the tools, testing equipment and software for the Site Acceptance Tests (SAT);

v. The procedures to the Contractor for the site surveys aiming the installation of the equipment are as follows: a) Send a formal request to the national CRV POC, with an anticipation of 20 days for the required coordination with the local CRV POC, sending the names of the staff to be involved with the visit; b) If authorized, the Contractor shall proceed to the site survey in the date and time indicated by the national CRV POC; c) If the Contractor fails to comply with the survey in the exact date, the national POC will cancel the visit and the Contractor will have to restart the whole site survey process; and d) The Contractor will provide all of the instruments and tools deemed necessary for the site survey.

Page 45 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

vi. The Contractor shall be held liable for any damage to existing property in each CRV User facilities caused to the facilities by its staff and/or its sub-contractors’; vii. The Contractor shall comply with the site safety rules especially during critical phases such as commissioning or interferences with operational systems by following CRV User staff indications in charge of technical safety and not take personal initiatives that could have an impact on operational systems; viii. The Contractor shall be responsible for storing the equipment before its installation;

ix. The Contractor may be asked to sign additional documents in order to follow local safety rules;

x. The Contractor shall keep the working area clean and free from fire hazards. After installation, all excess material shall be removed;

xi. The Contractor shall identify the exact locations for the installation of cabinets and equipment during the site survey; xii. The Contractor shall provide the CRV equipment grounding in each node; xiii. If necessary, the Contractor shall install protection against atmospheric discharges for all the equipment to be implemented for the provision of the CRV infrastructure in each node;

Note: The Contractor will be responsible for reviewing the characteristics of any existing devices that might be available as long as it is allowed the usage by the CRV representative; xiv. The Contractor shall be responsible for the connection to the power supply in the installation site, including electrical wiring between the power outlet and the equipment rack of the Contractor, including the respective circuit breakers and devices to protect against surges and atmospheric discharges; xv. The Contractor shall be running simulations over a period that has to be determined before commissioning the equipment. CRV User representatives shall be involved in the setting and execution of these simulations; and xvi. The Contractor shall procure the results of the tests.

4.2 Hardware and Software Requirements

4.2.1 General Topics

i. For the installation of the equipment to be provided, the Contractor shall follow and consider all the tender documents, especially the TOR, the Att II - Annex e - CRV IRS_v2 and the Att II - Annex f - Additional Voice and Data Gateway Service_v3.

ii. Although the Contractor operates MPLS data transport solutions, it is fully committed to the perfect operations of the applications and shall follow the initial end-to-end applications trials.

Page 46 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

4.2.2 Hardware Requirements

i. For the satellite equipment, the Contractor shall install the indoor and outdoor units.

ii. Where Applicable, the basic satellite equipment to be provided and checked is: Block Up Converters (BUC), Low Noise Block (LNB) down converters and Satellite Modems and VSAT Network management sub-system.

iii. Where Applicable, the basic ground/terrestrial equipment to be provided will comprise: routing system of the IP VPN Internet (with the needed interfaces), the basic ground voice and data gateway (with the needed interfaces), the NID (with the needed interfaces), switches (with the needed interfaces), A/B baseband switch (with the needed interfaces), Multiprotocol Label Switching (MPLS) for the Wide Area Network (WAN) (optical and/or microwave) links equipment.

iv. Before connecting the NID and the analog/digital, if needed, the contractor´s team shall install the new racks and prepare the transition cables, such as junction coaxial cables, junction sub-d cables or RJ based cables.

v. All the test and measurement tools shall be provided by the Contractor. No testing and measurement equipment will be provided by the CRV User representatives.

vi. All the needed equipment must be shipped and acknowledge by the CRV-User before the installation phase with sufficient delay. The Provider have to take the customs procedure delay into account. vii. All the received items must be inventoried and tested before the beginning of installation in order to avoid dispute.

4.2.3 Software Requirements

Where applicable, the basic software to be provided and/or used in each site is: Network Management Systems (NMS) software, if the SDD indicates that one or more CRV nodes will be selected to manage the CRV network in parallel with the Contractor´s Network Operations Center (NOC), software for BUC, Satellite Modems, NID, Voice/Data Gateway and switches.

4.2.4 Documentation Requirements

The needed documentation for the uptake of the equipment shall be provided to CRV User on its demand as deemed necessary.

5.0 TESTING AND EVALUATION.

The tests for the acceptance of the implemented equipment in each CRV node will be performed using simulations of the applications and, eventually, the real application tests that will follow the operational requirements as described in the tender documents, mainly, but not restricted to:

Page 47 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

i. Att II - Annex a - CRV CONOPS_v2;

ii. Att II - Annex b - Matrix of Flows for CRV services_v2;

iii. CRV Implementation plan (Chapter 5); and

iv. Validation Plan including the Site Acceptance Test (SAT) protocols (prepared by the Contractor).

The main testing and measurement equipment and tools that shall be used by the Contractor are:

i. Spectrum Analyzer;

ii. cable analyzer;

iii. audio analyzer/generator;

iv. Multi-meters;

v. LAN/Network protocol analyzer; and

vi. Telephones.

Note: This paragraph doesn´t exhaust all the testing and measurement equipment to be used during the implementation phase, and the Contractor shall describe all of them in the documentation to be provided after the contract signature.

The Contractor shall test its backbone (end-to-end) and the connection to its Network Operating Center (NOC). The links will be tested using computers for asynchronous and IP flows for example, and analogical phones.

An example of asynchronous test is opening a HyperTerminal session and send characters and a Bit Error Rate Test using a software such as WinSSD.

The requirements for the test procedures will be reflected in the Chapter 5 (Testing and Evaluation). Notwithstanding this fact, the tests procedures will need some software for the applications as reflected in the following paragraphs. Note: The following paragraphs don´t exhaust all the software and the Contractor shall describe all of them in the documentation to be provided after the contract signature.

For AFTN simulation: The simulation will consist of connecting a PC to the AFTN port at the back of the rack (with the right rate described in the document Att II - Annex b - Matrix of Flows for CRV services_v2) and close the serial interface at the other end of the circuit (loop). With the PC launch the winssd program (or other similar) and start the Bit Error Rate (BER) test. Run the test for 5 minutes and check that there are only a few errors.

For AMHS simulation: AMHS service is over IP (see the document Att II - Annex b - Matrix of Flows for CRV services_v2. To simulate it:

i. ping any remote equipment in the network according to the following cross matrix; and

Page 48 of 69

COMMON AERONAUTICAL VPN (CRV) IMPLEMENTATION PLAN – V1.0

ii. Verify that the end user is exchanging information correctly.

IP based RADAR and Asterix: The simulation will consist in selecting two sites, configuring sufficient bandwidth and multicast an IP flow.

ATS/DS Circuits: All ATS/DS calls are auto-dialed. The communication is established after the user picks up the phone. The simulation will consist of connecting a telephone on the desired line at the back of the rack, pick-up the phone make the call to the other end of the circuit. For E1 based circuits, to be connected to a VCS, this cannot be simulated.

ATS Switched Circuits: ATS switched calls are dialed. The communication is established after the user picks up the phone and dials the remote dial number. The simulation will consist of connecting a telephone on the desired line at the back of the rack, pick-up the phone and dial a remote number in order to call the other end of the circuit. For E1 based circuits, connected to a VCS, this cannot simulated.

6.0 CONTINGENCY PLAN/ BACK-OFF PLAN

6.1 Purpose

States/ Administrations are to establish contingency plan, with the CRV contractor, in case of the following scenario:

i. CRV total failure;

ii. CRV partial failure (e.g. voice channel failure);

iii. Provider Edge (PE) to Customer Edge (CE) link failure (e.g. ANSP1 lose connectivity to CRV); and

iv. PE to PE failure (e.g. ANSP1 and ANSP2 unable to exchange data/ or voice).

6.2 Harmonized Contingency Plan

States/ Administrations could also bilaterally/ multilaterally setup additional IPLC(s) as a contingency. This contingency plan could be harmonized in the APAC region to reduce costs.

7.0 MIXED OPERATING ENVIRONMENT

7.1 Routing of AFTN/ AMHS messages to non-CRV States/ Administrations

During the initial phase of the CRV implementation, States/ Administrations who have joined CRV are to ensure the routing of AFTN/ AMHS messages to States/ Administrations who have not joined CRV.

7.2 Inter-Region common network connectivity

It is envisaged for common networks (e.g. PEN, FTI and CRV) in different Regions to be inter-connected.

Page 49 of 69

Appendix A - CRV Implementation Table

Appendix A

State/ Intended date for Applications Envisaged Migration Prerequisites/ Administration CRV cut-over targeted SLA scheme dependencies (peers) Australia Contract in May 2018 AFTN, ADS-B, AMHS, staged Termination of current COM and service readiness in voice approach contract 3Q 2018 with Singapore in June 2019; with Japan would be end of 2019. Bhutan Contract in 4Q2018, Data (AMHS, AFTN) and Administrative approval from service readiness in voice the management for the direct 2Q2019 contract and approval from BCAA Cambodia As early as convenient Internal decision making

China Contract in 3Q2018, Data (AMHS) staged service readiness in With Hong Kong 1Q2019; approach 4Q2018 With Japan 2Q2020; With Thailand 2Q2019; With India in end of 2019.

Democratic People's Contract in 3Q2018 and AFTN and VoIP Republic service readiness in of Korea 4Q2018

Page 50 of 69

Appendix A - CRV Implementation Table

State/ Intended date for Applications Envisaged Migration Prerequisites/ Administration CRV cut-over targeted SLA scheme dependencies (peers) Hong Kong, China Contract signed on 6 DATA (AMHS) and VoIP staged Need to coordinate with Apr.2018 With: approach relevant Service readiness by China 1Q2019; CAAs/ANSPs in joining 2Q2018 Manila 1Q2019; CRV in a harmonized manner, etc. Japan 4Q2019; Thailand 2Q2019;

Macao, China To be confirmed CBA migration from X25 to IP Fiji Contract in May 2018 Data (AMHS) and VoIP Staged approach CBA, safety case and service readiness in With: Australia and USA 3Q 2018 3Q2018

France (New 2019 is target for New ATS Voice , AMHS with CBA, cost must be affordable Caledonia and Caledonia to sign Fiji & AIDC, AMHS and Wallis and Futuna: no French Polynesia) contract subject to ATS voice with USA dedicated connection to CRV internal security assessment India Contract in 4Q2018 and BBIS first, then BIS States staged CBA, safety case service readiness in approach 1Q2019. Indonesia ContractAvailable in 2Q2019 and AFTN, AMHS, ADS-B and CBA Service readiness in voice 3Q2019

Page 51 of 69

Appendix A - CRV Implementation Table

State/ Intended date for Applications Envisaged Migration Prerequisites/ Administration CRV cut-over targeted SLA scheme dependencies (peers) Japan Contract signed in Data first: staged Nov.2017 and service With: Hong Kong 4Q2019 approach readiness in USA 3Q2018; 1Q 2018 for Fukuoka Singapore 3Q2019; China 2Q2020 Malaysia Contract to be signed 1Q AFTN, AMHS, ADS-B and staged New ATC center operational 2019 and service ATS voice approach in 2020 readiness in 4Q2019

Myanmar As early as convenient AFTN, AMHS, ADS-B and CBA voice

New Zealand Contract in May2018 AFTN, AMHS and voice CBA attractive if all and service readiness in counterparts join in 3Q 2018 Philippines Contract signed in March Data (AMHS) and staged approach Success transition to the New 2018 and service voice ATM centre in 4Q2018 readiness in 2Q2018 Republic of Korea Contract in 2Q2019 and Data (AMHS), AIDC and staged service readiness in 4Q VoIP approach 2019 Singapore Contract in 1/ AFTN/AMHS staged CBA attractive if all 3Q2018 and 2/ Voice/AIDC/ADS-B approach counterparts join in service readiness With: Australia June2019; in 4Q2018 Japan 3Q2019 Thailand 2Q2019; India 2019.

Page 52 of 69

Appendix A - CRV Implementation Table

State/ Intended date for Applications Envisaged Migration Prerequisites/ Administration CRV cut-over targeted SLA scheme dependencies (peers) Sri Lanka As soon as CRV is AMHS connectivity Phased approach CBA available with Mumbai, with the Singapore and Male. implementation of CRV Direct Speech facilities with Chennai, Trivendrum, Mumbai, Male, Jakarta, Melbourne, Singapore Thailand Contract in 3Q 2018 and Data first Staged approach service readiness in Then voice, subject to 4Q2018 safety case: China 2Q2019 Hong Kong 2Q2019; Singapore 2Q2019; India 2019

Page 53 of 69

Appendix A - CRV Implementation Table

State/ Intended date for Applications Envisaged Migration Prerequisites/ Administration CRV cut-over targeted SLA scheme dependencies (peers) United States Contract in May 2018 1/ AFTN to AMHS over IP Staged approach and service readiness in with Australia 3Q 2018 2/ other FIRs as opportune (French Pol., Samoa, Philippines, Indonesia, PNG etc) 3/ ATFM, AMHS with attachment 4/ AMHS with Japan, Fiji and New Zealand

5/ BBIS with Fiji, Australia and Japan 3Q2018 (for only AMHS)

Page 54 of 69

Appendix B – APAC IPv4 Address Plan

Appendix B

1 Introduction

1.1 Objective

This document is meant to describe the addressing plan for IPv4 addresses throughout the Asia/Pacific Region. This document defines the recommended address format for IPv4 addresses. The IPv4 network is to be used within region.

1.2 References

[1] ICAO Doc 9705- Manual of Technical Provisions for the ATN AN/956 [2] ICAO Doc 9896 Manual for the ATN using IPS Standards and Protocols [3] ICAO Doc 7910 ICAO Location Indicators [4] RFC 1518 An Architecture for IP Address Allocation with CIDR [5] RFC 1918 Address Allocation for Private Internets [6] RFC 2050 BGP-4 Internet Registry IP Allocation Guidelines [7] RFC 3330 Special-Use IPv4 Addresses [8] RFC 4271 BGP-4 Specification

1.3 Terms Used

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. 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.

Page 55 of 69

Intra-domain (interior – Protocols for exchanging routing information between gateway) routing protocol routers within an AS. Inter-domain (exterior – Protocols for exchanging routing information between gateway) routing protocol Autonomous Systems. They may in some cases be used between routers within an AS, but they primarily deal with exchanging information between Autonomous Systems. Local Internet Registry – A Local Internet Registry (LIR) is an IR that primarily assigns address space to users of the network services it provides. LIRs are generally ISPs, whose customers are primarily end users and possibly other ISPs. [LACNIC]

1.4 Acronyms

AMHS – ATN Message Handling System ARP – Address Resolution Protocol ATN – Aeronautical Telecommunications Network BGP – Border Gateway Protocol DNS – Domain Name Service IANA – Internet Assigned Numbers Authority ICS – ATN Internet Communication Service IP – Internet Protocol IPv4 – Internet Protocol Version 4 IPv6 – Internet Protocol Version 6 IPS – Internet Protocol suite LACNIC – Latin American and Caribbean Internet Address Registry LIR – Local Internet Registry OSPF – Open Shortest Path First RIR – Regional Internet Registry

Page 56 of 69

1.5 Overview of Addressing Issues

The following subsections present issues that affect the completion of the addressing plan for operating the IPS-based AMHS network.

1.5.1 Public or Private Address

An important decision for the region is whether to use private or public addresses. Private addresses can be used if coordinated by all participating States and Organization; however, it is possible that existing networks already use addresses in the private block ranges. Public addresses must be obtained from a Regional Internet Registry (RIR). The Internet Assigned Numbers Authority (IANA) has delegated responsibility for administration of Internet numbering to the Latin American and Caribbean Internet Address Registry (LACNIC).

1.5.2 Address of Systems in External Regions

Systems in external regions could be assigned an address from the APAC address space rather than use an address in their regional address block. Note however that this must be coordinated with private addresses so as to avoid collisions.

2 IPv4 Addressing Overview and Fundamentals

In the Internet Protocol a distinction is made between names, addresses, and routes. A name indicates what we seek. An address indicates where it is. A route indicates how to get there. The Internet protocol deals primarily with addresses. Its main task is to forward data to a particular destination address. It is the task of higher-level protocols to make the mapping from names to addresses, for example using a domain name service (DNS). The Internet protocol forwards packet data units (PDU) to a destination address using routing tables maintained by a routing protocol. The routing tables contain the address of the next hop along the route to the destination. There are in general two classes of routing protocols: inter-domain or exterior routing protocols such as the Border Gateway Protocol (BGP) and intra-domain or interior routing protocols such as the Open Shortest Path First (OSPF) protocol. In order to forward PDUs to the next hop address, there must be a mapping from this address to the link level address, for example, an Ethernet address. This mapping is maintained by an address discovery protocol such as the Address Resolution Protocol (ARP). An IPv4 address consists of four bytes (32 bits). These bytes are also known as octets. For readability purposes, humans typically work with IP addresses in a notation called dotted decimal. This notation places periods between each of the four numbers (octets) that comprise an IP address. For example, an IP address that a computer sees as 00001010 00000000 00000000 00000001

Page 57 of 69

is written in dotted decimal as 10.0.0.1 Because each byte contains 8 bits, each octet in an IP address ranges in value from a minimum of 0 to a maximum of 255. Therefore, the full range of IP addresses is from 0.0.0.0 through 255.255.255.255. That represents a total of 4,294,967,296 possible IP addresses. A network may be set up with IP addresses to form a private or public network. On a private network a single organization controls address assignment for all nodes. On a public network there must be some conventions to assure that organizations do not use overlapping addresses. In the Internet this function is performed by the Internet Assigned Numbers Authority (IANA), which delegates authority to Regional Internet Registries (RIR). For the CAR/SAM Region the RIR is the Latin American and Caribbean Internet Address Registry (LACNIC). IPv4 Addresses are a fixed length of four octets (32 bits). An address begins with a Network ID, followed by a Host ID as depicted in Figure 2-1.

32 bits

Network ID Host ID

Figure 2-1. IPv4 Address Format

The original IP addressing scheme divided the Network ID from the Host ID is in a several octet boundaries. In this scheme the main classes of addresses were differentiated based on how many octets were used for the Network ID. This method is called classful addressing. Classful addressing was by convention further modified so that the Host ID could be split into subnet ID and sub host ID. This is typically accomplished using a subnet mask and is called classful addressing with subnetting. This eventually evolved into classless addressing where the division between the Network ID and Host ID can occur at an arbitrary point, not just on octet boundaries. With classless addressing the dividing point is indicated by a slash (/) followed the number of bits used for the Network ID. This value is called the prefix length of the address and the address value up to that point is called the network prefix. Private Addressing is defined in RFC 1918. IANA has reserved the following three blocks of the IP address space for private Internets: 10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) 192.168.0.0 - 192.168.255.255 (192.168/16 prefix) Because of the number of bits available to users, these blocks are referred to as a "24-bit block", a "20-bit block", and a "16-bit" block. An enterprise that decides to use IP addresses out of the private address space defined by RFC 1918, can do so without any

Page 58 of 69

coordination with IANA or an Internet registry. Addresses within this private address space will only be unique within an enterprise or a group of enterprises (e.g., an ICAO region), which chose to cooperate over this space so they may communicate with each other in their own private Internet.

3 IPv4 Addressing

3.1 Overview CAR/SAM

3.1.1 During the fourth meeting of ATN/TF4 (Santo Domingo, Dominican Republic, 27 to 28 June 2008) the group analyzed different alternatives for the implementation of the TCP/IP in the CAR/SAM Regions identifying the available options that would facilitate this implementation in the AMHS Service and future applications. This was reviewed in accordance with Document 9880 Part IIB of the ICAO. In this respect the Meeting decided two viable options for the implantation the TCP/IP: a) AMHS using the RFC1006 on Guiders TCP/IP (IPv4) to allow AMHS to directly interface with IPv4 Guiders for the intra-regional connections. b) Configurating AMHS, as specified in a) with capacity for IPv4 conversion to IPv6 through the implementation of a function of IP router as gateway for the interregional connections.

3.1.2 The Sixth Meeting of Committee ATM/CNS (ATM/CNS/6) (Santo Domingo, Dominican Republic, 30 June to the 04 July 2008) analyzed this Plan of IP Addressing for CAR/SAM Regions and considered that such a plan would be sent to the ICAO for revision.

3.1.3 During the ACP/WG/I/8 (Montreal, Canada, 25 to 29 August 2008) it was concluded that it is possible to consider a regional scheme of IPv4 addressing. Taking into consideration that the private sector would be using the propose addressing scheme in other applications, the Meeting considered nonviable to apply the IP addressing scheme at a global level.

3.1.4 The Third Meeting of the Group of Regional Implementation SAM/IG/3 (Lima, Peru, 20 to 24 April 2009) considered that, taking into account specified in Table CNS 1Bb from the FASID, the AMHS system to be installed in the SAM Region will use IP protocol and will initially use the IPv4 version. The block of used IPv4 addresses will follow the format established during the ATM/CNS/SG/6 Meeting.

3.2 IP Addressing Plan

When we began to work on the plan of IP addressing, we once again reviewed the scheme that was originally proposed, analyzed the amount of States/Territories by

Page 59 of 69

Region, the amount of addressing that each State/Territory could use and the amount of addressing reserved for the interconnection between States/Territories. The result of this study concluded that:

3.2.1 1 bit would be reduced to State/Territory level. This means the transfer of 256 States to 128 States by region. In the EUR/NAT Region, which is most numerous, has 53 States/Territories, means that there are many vacant numbers. 3.2.2 1 bit at Host's level would be added. This would allow the transfer from 4096 to 8190 hosts per State/Territory. This was considered due to the amount of future applications that would be implemented, mainly in the more developed States, and could cause the amount of directions not to be sufficient. The structure is shown below:

3.2.3 It should be noted the networks assigned to each State are private networks (RFC 1918). The first Bytes that integrate the assigned address will always maintain a decimal value of 10. Whereas the other three Bytes are used to distribute, in hierarchic form, the blocks of directions corresponding to each State. 3.2.4 The first four bits of the second Byte (4 bits) will be used to identify the regions in around which the States/Territories of the world are grouped: o 0000 => SAM: South American Office. o 0001 =>. NACC: North American, American Power station and Caribbean Office. o 0010 => APAC: Asia and Pacific Office. o 0011 => MID: Middle East Office. o 0100 => WACAF: Western and Central African Office. o 0101 => ESAF: Eastern and Southern African Office. o 0110 => EUR/NAT: European and North Atlantic Office.

3.2.5 On the other hand, the last four bits of the second Byte, and the first three bits of the third Byte (7 bits) will be used to identify the States/Territories of each region.

3.2.6 Whereas the last five bits of the third Byte and the eight bits that compose the fourth Byte (13 bits) will be used by each one of the States/Territories to assign addressing to their terminals/servers 3.2.7 The IPv4 address allocation scheme will be able to cover: o 16 Regions.

Page 60 of 69

o 128 States/Territories by each Region. o 8190 Host' s for each State/Territory 3.2.8 The IPv4 addressing plan would allow each State/Territory to be able to make use of the block of directions assigned as needed. a) Each State has been assigned 8190 usable Network addresses, which seem to be sufficient to cover existing needs. b) In the development of the mentioned scheme, a flexible margin has been designated so that it will allow the future growth or change in the network in the future. For example, if a region were subdivided in two or more regions, or the emerging of a new State/Territory. c) Argentina has already implemented its ATN network with a scheme of addresses different from the proposed one, prior to the publication of this document, has placed a border devise with the intention that this devise will make the address translation between the outer directions.

Page 61 of 69

3.3.1 Network Assignment for ASIA/PACIFIC

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used 1 Australia 10 . 32 .0.0 / 19 First 10 . 32. 0 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 32. 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

2 Bangladesh 10. 32. 32 .0 / 19 First 10 . 32. 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 32. 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

3 Bhutan 10. 32. 64.0 / 19 First 10 . 32. 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 32. 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Brunei 4 10. 32. 96.0 / 19 First 10 . 32. 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Darussalam Last 10 . 32. 127 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

5 Cambodia 10. 32. 128. 0 / 19 First 10 . 32. 128 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 32. 159 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

6 China 10. 32. 160. 0 / 19 First 10 . 32. 160 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 32. 191 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Hong Kong, 7 10. 32 . 192. 0 / 19 First 10 . 32 . 192 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 China Last 10 . 32 . 223 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

8 Macao, China 10. 32 . 224. 0 / 19 First 10 . 32 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 32 . 255 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 0 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Democratic people’s 9 10. 33 . 0 . 0 / 19 First 10 . 33 . 0 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Republic of Korea Last 10 . 33 . 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

10 Fiji 10. 33 . 32 . 0 / 19 First 10 . 33 . 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1

Page 62 of 69

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used Last 10 . 33 . 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

11 India 10. 33 . 64 . 0 / 19 First 10 . 33 . 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 33 . 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

12 Indonesia 10. 33 . 96 . 0 / 19 First 10 . 33 . 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 33 . 96 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

13 Japan 10. 33 . 128 . 0 / 19 First 10 . 33 . 128 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 33 . 159 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

14 Kiribati 10. 33 . 160 . 0 / 19 First 10 . 33 . 160 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 33 . 191 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Lao People’s 15 Democratic 10. 33 . 192 . 0 / 19 First 10 . 33 . 192 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Republic Last 10 . 33 . 223 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

16 Malaysia 10. 33 . 224 . 0 / 19 First 10 . 33 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 33 . 255 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 0 1 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

17 Maldives 10. 34 . 0 . 0 / 19 First 10 . 34 . 00 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Marshall 18 10. 34 . 32 . 0 / 19 First 10 . 34 . 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Islands Last 10 . 34 . 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

19 Micronesia 10. 34 . 64 . 0 / 19 First 10 . 34 . 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

20 Mongolia 10. 34 . 96 . 0 / 19 First 10 . 34 . 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 127 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

21 Myanmar 10. 34 . 128 . 0 / 19 First 10 . 34 . 128 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 159 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Page 63 of 69

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used 22 Nauru 10. 34 . 160 . 0 / 19 First 10 . 34 . 160 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 191 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

23 Nepal 10. 34 . 192 . 0 / 19 First 10 . 34 . 192 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 223 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

24 New Zealand 10. 34 . 224 . 0 / 19 First 10 . 34 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 34 . 255. 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 0 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

25 Pakistan 10. 35 . 0 . 0 / 19 First 10 . 35 . 0 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 35 . 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Papua New 26 10. 35 . 32 . 0 / 19 First 10 . 35 . 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Guinea Last 10 . 35 . 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

27 Philippines 10. 35 . 64 . 0 / 19 First 10 . 35 . 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 35 . 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Republic of 28 10. 35 . 96 . 0 / 19 First 10 . 35 . 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Korea Last 10 . 35 . 127 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

29 Samoa 10. 35 . 128 . 0 / 19 First 10 . 35 . 128 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 35 . 159 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

30 Singapore 10. 35 . 160 . 0 / 19 First 10 . 35 . 160 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 35 . 191 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Solomon 31 10. 35 . 192 . 0 / 19 First 10 . 35 . 192 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Islands Last 10 . 35 . 223 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

32 Sri Lanka 10. 35. 224 . 0 / 19 First 10 . 35 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 35 . 255 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 0 1 1 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

33 Thailand 10. 36 . 0 . 0 / 19 First 10 . 36 . 00 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1

Page 64 of 69

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used Last 10 . 36 . 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

34 Timor Leste 10. 36. 32 . 0 / 19 First 10 . 36. 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 36. 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

35 Tonga 10. 36 . 64 . 0 / 19 First 10 . 36 . 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 36 . 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

36 Vanuatu 10. 36 . 96 . 0 / 19 First 10 . 36 . 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 36 . 127 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

37 Vietnam 10. 36 . 128 . 0 / 19 First 10 . 36 . 128 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 36 . 159 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

38 Afghanistan 10. 36 . 160 . 0 / 19 First 10 . 36 . 160 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 36 . 191 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

French 39 Polynesia, 10. 36 . 192 . 0 / 19 First 10 . 36 . 192 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 France Last 10 . 36 . 223 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

New 40 Caledonia, 10. 36 . 224 . 0 / 19 First 10 . 36 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 France Last 10 . 36 . 255 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 0 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Wallis & 41 Futuna Islands, 10. 37 . 0 . 0 / 19 First 10 . 37 . 0 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 France Last 10 . 37 . 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Niue Islands, 42 10. 37 . 32 . 0 / 19 First 10 . 37 . 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 New Zealand Last 10 . 37 . 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Pecan Island, 43 United 10. 37 . 64 . 0 / 19 First 10 . 37 . 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Kingdom Page 65 of 69

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used Last 10 . 37. 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

American 44 Samoa , United 10. 37 . 96 . 0 / 19 First 10 . 37. 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 States Last 10 . 37. 127 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Guam, United 45 10. 37 . 128 . 0 / 19 First 10 . 37. 128 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 States Last 10 . 37. 159 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Johnson Island 46 Kingman Reef, 10. 37 . 160 . 0 / 19 First 10 . 37. 160 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 United States Last 10 . 37. 191 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Midway, 47 10. 37 . 192 . 0 / 19 First 10 . 37. 192 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 United States Last 10 . 37. 223 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Northern Mariana 48 10 . 37 .224. 0 / 19 First 10 . 37 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Islands, United States Last 10 . 37 . 255 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 0 1 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Palmyra, 49 10 . 38 . 0 . 0 / 19 First 10 . 38 . 0 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 0 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 United States Last 10 . 38 . 31 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 0 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Wake Islands, 50 10. 38. 32 . 0 / 19 First 10 . 38 . 32 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 United States Last 10 . 38 . 63 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

51 Cook Islands 10.38. 64 .0 / 19 First 10 . 38 . 64 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 1 0 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 38 . 95 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 1 0 1 1 1 1 1 . 1 1 1 1 1 1 1 0

52 Palau 10. 38 . 96 . 0 / 19 First 10 . 38. 96 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 38. 127 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 0 1 1 0 . 0 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Page 66 of 69

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used 53 VACANT

128 RESERVED 10. 47 . 224 . 0 / 19 First 10 . 47 . 224 . 1 0 0 0 0 1 0 1 0 . 0 0 1 0 1 1 1 1 . 1 1 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1 Last 10 . 47 . 255 . 254 0 0 0 0 1 0 1 0 . 0 0 1 0 1 1 1 1 . 1 1 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

3.3.2 Network Assignment for USA

State/Administrat Direction Ref Network Decimal notation Binary Notation Region State/Territory Host’s ion used

1 United States 10.19.160.0/19 First 10 . 19 .160 . 1 0 0 0 0 1 0 1 0. 0 0 0 1 0 0 1 1 . 1 0 1 0 0 0 0 0 . 0 0 0 0 0 0 0 1

Last 10 . 19. 191 254 0 0 0 0 1 0 1 0. 0 0 0 1 0 0 1 1 . 1 0 1 1 1 1 1 1 . 1 1 1 1 1 1 1 0

Page 67 of 69

3.4 Using IPv4-Compatible Address Formats

In many instances, you can represent a 32-bit IPv4 address as a 128-bit IPv6 address. The transition mechanism defines the following two formats.

IPv4-compatible address

000 ... 000 IPv4 Address

IPv4-mapped address

000 ... 000 0xffff IPv4 Address

The mapped address format is used to represent an IPv4 node. The only currently defined use of this address format is part of the socket API. An application can have a common address format for both IPv6 addresses and IPv4 addresses. The common address format can represent an IPv4 address as a 128-bit mapped address. However, IPv4-to-IPv6 protocol translators also allow these addresses to be used.

Page 68 of 69

Appendix C – MID IPv4 Address Plan

Appendix C

No. State Network IP Hosts IP addresses Address Decimal Notation Binary Notation 1st Byte Region State Hosts 1 Bahrain 10.48.0.0/19 First 10.48.0.1 00001010. 0011 0000.000 00000.00000001 Last 10.48.31.254 00001010. 0011 0000.000 11111.11111110 2 Egypt 10.48.32.0/19 First 10.48.32.1 00001010. 0011 0000.001 00000.00000001 Last 10.48.63.254 00001010. 0011 0000.001 11111.11111110 3 Iran 10.48.64.0/19 First 10.48.64.1 00001010. 0011 0000.010 00000.00000001 Last 10.48.95.254 00001010. 0011 0000.010 11111.11111110 4 Iraq 10.48.96.0/19 First 10.48.96.1 00001010. 0011 0000.011 00000.00000001 Last 10.48.127.254 00001010. 0011 0000.011 11111.11111110 5 Jordan 10.48.0.0/19 First 10.48.128.1 00001010. 0011 0000.100 00000.00000001 Last 10.48.159.254 00001010. 0011 0000.100 11111.11111110 6 Kuwait 10.48.0.0/19 First 10.48.160.1 00001010. 0011 0000.101 00000.00000001 Last 10.48.195.254 00001010. 0011 0000.101 11111.11111110 7 Lebanon 10.48.0.0/19 First 10.48.196.1 00001010. 0011 0000.110 00000.00000001 Last 10.48.223.254 00001010. 0011 0000.110 11111.11111110 8 Libya 10.48.0.0/19 First 10.48.224.1 00001010. 0011 0000.111 00000.00000001 Last 10.48.255.254 00001010. 0011 0000.111 11111.11111110 9 Oman 10.48.0.0/19 First 10.49.0.1 00001010. 0011 0001.000 00000.00000001 Last 10.49.31.254 00001010. 0011 0001.000 11111.11111110 10 Qatar 10.48.0.0/19 First 10.49.32.1 00001010. 0011 0001.001 00000.00000001 Last 10.49.63.254 00001010. 0011 0001.001 11111.11111110 11 Saudi 10.48.0.0/19 First 10.49.64.1 00001010. 0011 0001.010 00000.00000001 Arabia Last 10.49.95.254 00001010. 0011 0001.010 11111.11111110 12 Sudan 10.48.0.0/19 First 10.49.96.1 00001010. 0011 0001.011 00000.00000001 Last 10.49.127.254 00001010. 0011 0001.011 11111.11111110 13 Syria 10.48.0.0/19 First 10.49.128.1 00001010. 0011 0001.100 00000.00000001 Last 10.49.159.254 00001010. 0011 0001.100 11111.11111110 14 UAE 10.48.0.0/19 First 10.49.160.1 00001010. 0011 0001.101 00000.00000001 Last 10.49.127.254 00001010. 0011 0001.101 11111.11111110 15 Yemen 10.48.0.0/19 First 10.49.128.1 00001010. 0011 0001.110 00000.00000001 Last 10.49.223.254 00001010. 0011 0001.110 11111.11111110

Page 69 of 69

INTERNATIONAL CIVIL AVIATION ORGANIZATION

VOICE OVER INTERNET PROTOCOL (VOIP) AND ANALOG VOICE INTERFACE CONTROL DOCUMENT FOR THE ASIA-PACIFIC COMMON AERONAUTICAL VIRTUAL PRIVATE NETWORK

VERSION 1.0

C - 1

EXECUTIVE SUMMARY

Under the guidance of the International Civil Aviation Organization (ICAO) a number of States/Administrations in the Asia/Pacific region have created a data and voice communications network to allow for the exchange of air traffic control information. This network is delivered by the Service Provider.

This Interface Control Document (ICD) defines the Voice over Internet Protocol (VoIP) service and Analog Voice service interfaces between the Service Provider and each of the States/Administrations.

C - 2

CONTENTS 1.0 PURPOSE AND SCOPE ...... 5

2.0 SYSTEM OVERVIEW ...... 5

3.0 INTERFACE LOCATIONS ...... 5

4.0 INTERFACE TYPES ...... 6 4.1.1 Voice over Internet Protocol ...... 6 4.1.2 VoIP Gateway ...... 6 4.1.3 Analog Voice ...... 7 4.1.4 Redundant Analog Voice ...... 8 5.0 VOIP INTERFACE CONTROLS ...... 8 5.1 INTRODUCTION ...... 8 5.2 INTERFACE: ETHERNET-SINGLE...... 8 5.2.1 Physical layer ...... 8 5.2.2 Data link layer ...... 9 5.2.3 Network layer ...... 9 5.2.4 Transport Layer ...... 9 5.2.5 Upper Layers ...... 10 5.2.6 Quality of Service Markings ...... 10 5.3 INTERFACE: ETHERNET-MULTI ...... 10 5.3.1 Physical layer ...... 10 5.3.2 Data link layer ...... 10 5.3.3 Network layer ...... 10 5.3.4 Transport Layer ...... 10 5.3.5 Upper Layers ...... 11 5.3.6 Quality of Service Markings ...... 11 6.0 ANALOG VOICE INTERFACE CONTROLS ...... 11 6.1 INTRODUCTION ...... 11 6.2 INTERFACE: E&M TYPE I ...... 11 6.3 INTERFACE: E&M TYPE V ...... 12 6.4 INTERFACE: FXS ...... 12 6.5 INTERFACE: FXO ...... 12 7.0 DIAL PLAN ...... 12

APPENDIX A - ACRONYMS ...... 14

C - 3

LIST OF FIGURES FIGURE PAGE FIGURE 1: HIGH LEVEL SYSTEM OVERVIEW ...... 5 FIGURE 2: LOCATION OF INTERFACE ...... 6 FIGURE 3: VOICE OVER INTERNET PROTOCOL INTERFACE ...... 6 FIGURE 4: VOIP GATEWAY INTERFACE ...... 7 FIGURE 5: ANALOG VOICE INTERFACE ...... 7 FIGURE 6: REDUNDANT ANALOG VOICE INTERFACE ...... 8 FIGURE 7 : 8P8C MODULAR SOCKET ...... 9

LIST OF TABLES TABLE PAGE TABLE 1: VOIP INTERFACE DEFINITIONS ...... 8 TABLE 2: ANALOG VOICE INTERFACE DEFINITIONS ...... 11

C - 4

1.0 Purpose and Scope This Interface Control Document (ICD) defines the interface between the Service Provider and each of the States/Administrations of the Voice over Internet Protocol (VoIP) service and Analog Voice service for Ground to Ground voice communications and forms part of the Specification for the Asia-Pacific Common aeRonautical Virtual Private Network (CRV).

The purpose of this ICD is to clearly communicate all possible voice inputs and outputs with the CRV. This ICD helps understanding and is to ensure compatibility between system, sub-systems and components. This ICD only addresses the first four layers of the OSI model, that being the Physical, Data Link, Network and Transport layers and Analog Voice interfaces. Information specific analog switching system is outside the scope of this ICD.

The intended audience of this ICD is the Service Provider, States/Administrations and the Operations Group (OG).

2.0 System Overview The CRV is to consist of a network which facilitates telecommunications between the States/Administrations.

State/ State/ Administration Administration

Service Provider State/ State/ Administration Administration Figure 1: High level system overview

The various VoIP and Analog Voice interfaces have not been shown on this diagram, as they will be detailed below.

3.0 Interface Locations The Service Provider will place a Network Interface Device (NID) into the State/Administration’s premises, as shown in Figure 2.

C - 5

State/Administration’s Premises

Location of interface defined in this ICD

State/Administrations’s Network Service Providers’ Service Provider Network Interface Device (NID)

Figure 2: Location of Interface The interface point defined in this ICD is the customer facing socket on the Service Providers’ Network Interface Device (NID).

The OG maintains a list of State/Administrations which have a connection to the Service Provider and the street address of each location.

4.0 Interface Types Several VoIP and Analog Voice interfaces are available. These are diagrammed below.

4.1.1 Voice over Internet Protocol

State/Administration’s Premises

Ethernet

Ethernet Ethernet VoIP ATC Voice Positions State/Administrations’s VoIP Network Service Providers’ Network Interface Device (NID)

Figure 3: Voice over Internet Protocol Interface

4.1.2 VoIP Gateway

C - 6

State/Administration’s Premises

Analog Voice

VoIP Ethernet Ethernet Analog Gateway Voice Switch Analog Voice ATC Voice Positions State/Administrations’s IP Network Service Providers’ Network Interface Device (NID)

Figure 4: VoIP Gateway Interface

4.1.3 Analog Voice

State/Administration’s Premises

Analog Voice

Analog Analog Voice Voice Switch ATC Voice Positions Service Providers’ Network Interface Device (NID) Voice Gateway

Figure 5: Analog Voice Interface

C - 7

4.1.4 Redundant Analog Voice

State/Administration’s Premises

Analog Voice

Service Providers’ Network Interface Device (NID) Voice Gateway Patch Panel Analog Analog Voice Voice Switch ATC Voice Positions

Analog Voice

Service Providers’ Network Interface Device (NID) Voice Gateway

Figure 6: Redundant Analog Voice Interface

5.0 VoIP Interface Controls

5.1 Introduction The CRV Ethernet interfaces are summarised in Table 1. These interfaces may be used for VoIP or VoIP Gateway Interface types.

Table 1: VoIP Interface Definitions

Interface Type Version Interface Type Paragraph Reference

Ethernet-single 1 Single Ethernet connection with no 5.2 redundancy

Ethernet-multi 1 Two or more Ethernet connections 5.3 which failover

5.2 Interface: Ethernet-single This interface type is for a State/Administration that has only a single connection to the Service Provider.

5.2.1 Physical layer Each local access interface is presented via a standard RJ45 (female) Ethernet (IEEE 802.3) socket.

This Ethernet port is an IEC 60603-7 8P8C modular connector as shown in Figure 7.

C - 8

The Ethernet port shall support cable terminations as specified by EIA/TIA 568A.

Figure 7 : 8P8C modular socket

For cases where both the Service Provider equipment and the State/Administration equipment can operate at 1Gbps, then: . electrical signaling shall meet the 1000BASE-T standard, as defined by IEEE 802.ab; . the Service Provider equipment and the State/Administration equipment shall use auto negotiation for speed and duplex. For all other instances, then: . electrical signaling shall meet the 100BASE-TX, as defined by IEEE 802.3u; and . the Service Provider equipment and the State/Administration equipment shall both be statically set to 100 Mbps/Full-Duplex, so as to avoid speed/duplex negotiation mismatch and compatibility issues.

5.2.2 Data link layer The data link protocol is IEEE-802.3 Ethernet (MAC and 802.2 LLC) and ARP in compliance with: RFC 826 An Ethernet Address Resolution Protocol, November 1982.

5.2.3 Network layer The Network layer will use Internet Protocol version 4 in compliance with: RFC 791 Internet Protocol, September 1981, and RFC 792 Internet Control Message Protocol, September 1981, as updated by RFCs 950, 4884, and 6633, and RFC 796 Address Mappings, September 1981, and RFC 894 Standard for the Transmission of IP Datagrams over Ethernet Networks, April 1984.

The OG maintains the CRV IP Address and Routing Plan. This Plan contains a list of all the subnets used by the network.

The State/Administration shall make an IP address on its connecting equipment responsive to ICMP echo (PING) packets to assist in maintenance and fault finding.

The Service Provider shall make an IP address on its connecting equipment responsive to ICMP echo (PING) packets to assist in maintenance and fault finding.

Note that while IPv4 is used in the initial implementation, IPv6 will be supported in the future.

5.2.4 Transport Layer The Transport layer may use TCP and/or UDP in compliance with: RFC 793 Transmission Control Protocol, September 1981, as updated by RFC 3168, and RFC 768 User Datagram Protocol, August 1980.

C - 9

5.2.5 Upper Layers The Session, Presentation, and Application layers are combined in the TCP/IP model and will use SIP, SDP, and RTP in compliance with: RFC 3261 SIP: Session Initiation Protocol, June 2002, and RFC 3550 RTP: A Transport Protocol for Real-Time Applications, July 2003, and RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control, July 2003, and RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples, December 2003, and RFC 3666 Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows, December 2003, and RFC 4566 SDP: Session Description Protocol, July 2006.

The CRV OG maintains a SIP Dial Plan. The initial SIP Dial Plan is presented below (see 7.0).

5.2.6 Quality of Service Markings The OG maintains the CRV Quality of Service Plan for the CRV. Packets traversing this interface shall comply with this plan.

5.3 Interface: Ethernet-multi This interface type is for a State/Administration that has more than one connection to the Service Provider.

5.3.1 Physical layer This is identical to the Ethernet-single interface (see 5.2.1).

5.3.2 Data link layer This is identical to the Ethernet-single interface (see 5.2.2).

5.3.3 Network layer This is identical to the Ethernet-single interface (see 5.2.3).

5.3.4 Transport Layer The Transport layer may use TCP and/or UDP in compliance with: RFC 793 Transmission Control Protocol, September 1981, as updated by RFC 3168, and RFC 768 User Datagram Protocol, August 1980, and RFC 2439 BGP Route Flap Damping, November 1998, and RFC 4271 A Border Gateway Protocol 4 (BGP-4), January 2001, as updated by RFC 6286, and RFC 6286 Autonomous-System-Wide Unique BGP Identifier for BGP-4, June 2011.

Border Gateway Protocol version 4 (BGP-4) shall be used to exchange routing information between the Service Provider and the State/Administration. The BGP implementation shall use the BGP peers, Autonomous System (AS) numbers and route preference details contained in the CRV IP Address and Routing Plan.

A password shall be used to secure BGP sessions and enable Message Digest 5 authentication on the TCP/IP connections between BGP peers. BGP route filters should be used so that only authorized subnets are accepted by the BGP peers.

C - 10

5.3.5 Upper Layers The Session, Presentation, and Application layers are combined in the TCP/IP model and will use SIP, SDP, and RTP in compliance with: RFC 3261 SIP: Session Initiation Protocol, June 2002, and RFC 3550 RTP: A Transport Protocol for Real-Time Applications, July 2003, and RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control, July 2003, and RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples, December 2003, and RFC 3666 Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows, December 2003, and RFC 4566 SDP: Session Description Protocol, July 2006.

The CRV OG maintains a SIP Dial Plan. The initial SIP Dial Plan is presented below (see 7.0).

5.3.6 Quality of Service Markings This is identical to the Ethernet-single interface (see 5.2.6).

6.0 Analog Voice Interface Controls

6.1 Introduction The CRV Analog Voice interfaces are summarised in Table 2. These interfaces may be used for Analog Voice Interface types, either single or redundant with an A/B Switch.

Table 2: Analog Voice Interface Definitions

Interface Type Interface Type Paragraph Reference

E&M Type I 2 or 4 wire audio with E and M 6.2 signals

E&M Type V 2 or 4 wire audio with E and M 6.3 signals

FXS Foreign eXchange Station 6.4

FXO Foreign eXchange Office 6.5

6.2 Interface: E&M Type I This is the most common E&M interface in North America. Type I uses two leads for supervisor signaling: E, and M. During inactivity, the E-lead is open and the M-lead is connected to the ground. The PBX (that acts as trunk circuit side) connects the M-lead to the battery in order to indicate the off- hook condition. The Cisco router/gateway (signaling unit) connects the E-lead to the ground in order to indicate the off-hook condition.

Each local access interface is presented via a standard RJ48S (female) socket.

This E&M port is an IEC 60603-7 8P8C modular connector as shown in Figure 7.

C - 11

The E&M port supports 2 or 4 wire audio.

6.3 Interface: E&M Type V Type V is symmetrical and allows two signaling nodes to be connected back-to-back. This is the most common interface type used outside of North America. Type V uses two leads for supervisor signaling: E, and M. During inactivity the E-lead and M-lead are open. The PBX (that acts as trunk circuit side) connects the M-lead to the ground in order to indicate the off- hook condition. The Cisco router / gateway (signaling unit) connects the E-lead to the ground in order to indicate off- hook condition.

Each local access interface is presented via a standard RJ48S (female) socket.

This E&M port is an IEC 60603-7 8P8C modular connector as shown in Figure 7.

The E&M port supports 2 or 4 wire audio.

6.4 Interface: FXS A Foreign eXchange Station interface is the port that provides dial tone and ring voltage. Historically, it is the jack in the wall into which you would plug an analog telephone. An FXS interface would connect to an FXO interface on the CRV Voice Gateway. Because the FXS interface is “facing” a station or telephone, the interface is not used to dial digits. When the FXS interface detects a ground start or loop start condition, as configured, it should provide dial tone and, possibly, collect digits. When an FXS interface is used to place a call, it provides ring voltage to alert the station.

FXO/FXS circuits use standard telephone wiring with RJ-11 connectors.

6.5 Interface: FXO A Foreign eXchange Office interface is the interface “facing” the office. Historically, it is the plug on the analog telephone or the plug(s) on your analog phone system. An FXO interface connects to an FXS interface on the CRV Voice Gateway. When placing a call, the FXO interface closes the loop to the FXS interface, receives dial tone, and provides digits, like dialing from aa analog telephone.

FXO/FXS circuits use standard telephone wiring with RJ-11 connectors.

7.0 Dial Plan In compliance with ICAO 9804, an initial dial plan was developed using an 8 digit numbering plan consisting of the following:  1-3 digits for the Country Code/Area Identifier (AA) – E.164  4-2 digits for the ANSP Centre code (CC) – ANSP provided  3 digits for the operator position (OO) – ANSP provided

The initial dial plan includes Airservices Australia, Airways New Zealand, Fiji Airports and USA FAA and joining CRV members would be added in a similar fashion.

C - 12

ANSP Operator Position AA CC OO Airservices Australia Brisbane - Coral 61 400 001 Brisbane - Lord Howe 61 400 002 Brisbane - Nauru 61 400 003

Papua New Brisbane - PNG 675 121 01 Guinea (via Australia)

Airways New Zealand Auckland 64 202 001 Auckland 64 202 002

Fiji Airports Nadi-CWP 1 679 44 001 Nadi -CWP 2 679 44 002

USA FAA Oakland D5 (80) 1 5170 080 Oakland D9 (83) 1 5170 083 Oakland D3 (84) 1 5170 084 Oakland D6 (86) 1 5170 086

C - 13

APPENDIX A - ACRONYMS

A.0 Acronyms This appendix defines the acronyms used in this document.

BGP Border Gateway Protocol ICAO International Civil Aviation Organization ICD Interface Control Document ICMP Internet Control Message Protocol ISO International Organization for Standardization IP Internet Protocol ITU International Telecommunications Union ITU-T ITU Telecommunications Sector OSI Open Systems Interconnection QOS Quality of Service TBD to be Determined TCP Transmission Control Protocol

C - 14 ACSICG/5 Appendix D to the Report

TERMS OF REFERENCE

SWIM Task Force

Objectives: In order to achieve B1-SWIM and the Seamless ATM Plan objectives, ATM and AIM systems - in compliance with global standards for the conceptualisation and exchange of aeronautical, flight and meteorological information - should be implemented in the high density FIRs and high density international aerodromes by November 2022 (PASL Phase III) and in all FIRs and international aerodromes by November 2025 (PASL Phase IV). To that end, the SWIM Task Force will: a) Benchmark the various successful implementations of SWIM in States and regions to adopt best practices; b) Develop and maintain a regional roadmap for SWIM services (ATM, AIM, MET, other), dependencies and enablers; c) Liaise with relevant regional contributory bodies to refine operational and communications requirements (example: ATFM/SG, AIS AAITF, MET IE/WG, AMHS ACSICG, CRV/OG, etc.); d) Complement global SWIM governance with regional procedures as needed and define how it can be implemented in APAC, with a particular focus on version management of concept and exchange models, architecture models, cyber-security, data quality management and maintenance of a trusted environment; e) Provide guidance and training to APAC member States and APANPIRG contributory bodies involved in SWIM-related work; f) Develop guidance/requirements for publishers/service providers and subscribers/service consumers; g) Promote enablement of ATM services as SWIM Application Services (SAS); h) Define how SWIM Registry/Registries and services will be implemented in the APAC region and what the minimum level of information a service needs to provide to the Registry/Registries; i) Support APANPIRG WG/TF regarding data exchange models of AIXM, FIXM, and IWXXM and examine if any extension is required for the operational use in APAC; j) Monitor developments by the IMP and escalate issues as required; k) Implement the APAC Regional SWIM; and l) Undertake any other tasks related to SWIM implementation that may arise in the future.

Considering the cross-disciplinary nature of SWIM, the Task Force will ensure proper coordination with relevant regional contributory bodies under APANPIRG.

D - 1 ACSICG/5 Appendix D to the Report

Composition

The SWIM TF will consist of experts from ATM, AIM, MET and CNS from Asia/Pacific States (ANS Providers), and from IATA and ICCAIA.

Conduct of the work

The task force will conduct its work through Web Conferences, teleconferences, other electronic means of communications and Face-to-Face meetings.

Reporting:

The group will report to CNS SG through ACSICG.

______

D - 2

INTERNATIONAL CIVIL AVIATION ORGANIZATION

ASIA AND PACIFIC OFFICE

AFTN ROUTING DIRECTORY

ASIA AND PACIFIC REGIONS

TWENTY – EIGHTH EDITION

JUNE 2018

PREPARED BY THE ICAO ASIA AND PACIFIC REGIONAL OFFICE

EXPLANATORY NOTES

The Routing Directory is based on the existing AFTN circuits in the Asia and Pacific Regions.

I. Explanation of columns:

a) Column A contains destination AFTN routing indicators. These indicators employ the minimum number of characters to preclude ambiguity.

b) Columns 1, 2, 3 etc. contain the location indicators of the originating/relaying AFTN COM centres/stations in the heading and the AFTN routing indicators in conjunction with the destination indicators.

c) Primary Routing is indicated in the left-hand subdivision under each origin, in upper case letters.

d) Alternate routing is indicated in the right-hand subdivision under each origin, in lower case letters.

e) National and/or non-AFTN routing is indicated by the letter (N). Local arrangement for alternate routing is indicated by the letter n.

II. Explanation of Symbols:

A stations - stations in the "A" Aeronautical Fixed Service Routing Area (AFSRA) - Solomon Is., Nauru, and Papua New Guinea. AG stations - stations in Solomon Is. AN stations - stations in Nauru AY stations - stations in Papua New Guinea

B stations - stations in the "B" AFSRA - (Greenland, Iceland) C stations - stations in the "C" AFSRA - (Canada) D stations - stations in the "D" AFSRA - (West Africa) E stations - stations in the "E" AFSRA - (Europe) F stations - stations in the "F" AFSRA - (Central and South Africa) G stations - stations in the "G" AFSRA - (Coastal West Africa)

H stations - stations in the "H" AFSRA - (Coastal East Africa) HE stations - stations in the Arab Republic of Egypt

K stations - stations in the "K" AFSRA - (U.S.A.) L stations - stations in the "L" AFSRA - (Europe, Mediterranean) M stations - stations in the "M" AFSRA - (Caribbean, Central America)

28th Edition 10-06-18

N stations - stations in the "N" AFSRA (South Pacific) NC stations - stations in Cook Is. NF stations - stations in Fiji NFT stations - stations in Tonga NG stations - stations in Kiribati NGF stations - stations in Tuvalu NI stations - stations in Niue Island NL stations - stations in Futuna and Wallis Islands NS stations - stations in Samoa NST stations - stations in American Samoa NT stations - stations in French Polynesia NV stations - stations in Vanuatu NW stations - stations in New Caledonia NZ stations - stations in New Zealand

O stations - stations in the "O" AFSRA - (Middle East) OA stations - stations in Afghanistan OB stations - stations in Bahrain OE stations - stations in Saudi Arabia OI stations - stations in Iran, Islamic Rep. of OJ stations - stations in Jordan OK stations - stations in Kuwait OL stations - stations in Lebanon OM stations - stations in United Arab Emirates OO stations - stations in Oman OP stations - stations in Pakistan OR stations - stations in Iraq OS stations - stations in Syria OT stations - stations in Qatar OY stations - stations in Yemen

P stations - stations in the "P" AFSRA - (North Pacific) PA stations - stations in Alaska PB stations - stations in Baker Is. PC stations - stations in Phoenix Is. PG stations - stations in Mariana Is. Guam PH stations - stations in Hawaii PJ stations - stations in Johnston Is. PK stations - stations in Marshall Is. PL stations - stations in Line Is. PM stations - stations in Midway Is. PT stations - stations in Federated State of Micronesia PW stations - stations in Wake Is.

R stations - stations in the "R" AFSRA - (West Pacific) RC stations - stations in China RJ stations - stations in Japan RK stations - stations in Republic of Korea RO stations - stations in Japan (Ryukyu Is.) RP stations - stations in the Philippines

28th Edition 10-06-18 3.

S stations - stations in the "S" AFSRA - (South America) SA stations - stations in Argentina SC stations - stations in Chile

T stations - stations in the "T" AFSRA - (North East Caribbean)

U stations - stations in the "U" AFSRA - (Russian Federation) UT stations - stations in Uzebekistan

V stations - stations in the "V" AFSRA - (East and West Asia) VA stations - stations in India (West) VC stations - stations in Sri Lanka VD stations - stations in Cambodia VE stations - stations in India (East) VG stations - stations in Bangladesh VH stations - stations in Hong Kong VI stations - stations in India (North) VL stations - stations in Lao People's Democratic Republic VM stations - stations in Macau VN stations - stations in Nepal VO stations - stations in India (South) VQ stations - stations in Bhutan VR stations - stations in Maldives VT stations - stations in Thailand VV stations - stations in Viet Nam VY stations - stations in Myanmar

W stations - stations in the "W" AFSRA (Brunei, Indonesia, Malaysia, Singapore, Southern South East Asia) WA stations - stations in Indonesia (Eastern part of Indonesia) WB stations - stations in Malaysia (East) WBA stations - stations in Brunei WBS stations - stations in Brunei WI stations - stations in Indonesia (Western part of Indonesia) WM stations - stations in Malaysia (West) WP stations - stations in Timor Leste WR stations - stations in Indonesia (Middle part of Indonesia) WS stations - stations in Singapore

Y stations - stations in "Y" AFSRA (Australia)

Z stations - stations in the "Z" AFSRA (China, Dem. People's Rep. of Korea, Mongolia) Z stations (except ZK and ZM) - stations in China ZK stations - stations in Democratic People's Republic of Korea ZM stations - stations in Mongolia

Note 1: The names of the continents, areas and countries appearing in parentheses indicate broadly the geographical location of the AFSRAs. The chart contained in Doc 7910, shows the delineation of these AFSRAs.

28th Edition 10-06-18

AMENDMENTS

RECORD OF AMENDMENTS AND CORRIGENDA RELATING TO AFTN ROUTING DIRECTORY, ASIA AND PACIFIC REGIONS, TWENTY-SEVENTH EDITION

AMENDMENTS CORRIGENDA No. Date Date Entered No. Date Date Entered Applicable entered by of issue entered by

28th Edition 10-06-18 5.

A 1 2 3 4 5 6 ORIGIN AGGG ANAU AYPM KSLC NCRG NFFN DESTINATION AG (N) n YB YB YB nf NZ YB ks AN YB (N) n YB YB nf NZ YB ks AY YB YB (N) n YB nf NZ YB ks B YB YB YB (N) n NZ KS yb C YB YB YB (N) n NZ KS yb D YB YB YB (N) n NZ YB ks E YB YB YB (N) n NZ YB ks F YB YB YB (N) n NZ YB ks G YB YB YB (N) n NZ YB ks H YB YB YB (N) n NZ YB ks K YB YB YB (N) n NZ KS yb L YB YB YB (N) n NZ YB ks M YB YB YB (N) n NZ KS yb NC YB YB YB NZ yb (N) n YB ks NF (EX. NFT) YB YB YB NF yb NZ (N) n NFT YB YB YB NZ yb NZ YB ks NG (EX. NGF) YB YB YB NF yb NZ NGT n NGF YB YB YB NF yb NZ NGF n NI YB YB YB NZ yb NZ YB ks NL YB YB YB NF yb NZ NW n NS (EX. NST) YB YB YB NZ yb NZ YB ks NST YB YB YB NST n NZ KS yb NT YB YB YB NZ yb NZ YB ks NV YB YB YB YB nf NZ YB ks NW YB YB YB NF yb NZ NW yb NZ YB YB YB NZ yb NZ YB ks OA YB YB YB (N) n NZ YB ks OB YB YB YB (N) n NZ YB ks OE YB YB YB (N) n NZ YB ks OI YB YB YB (N) n NZ YB ks OJ YB YB YB (N) n NZ YB ks OK YB YB YB (N) n NZ YB ks OL YB YB YB (N) n NZ YB ks OM YB YB YB (N) n NZ YB ks OO YB YB YB (N) n NZ YB ks OP YB YB YB RJ yb NZ YB ks OR YB YB YB (N) n NZ YB ks OS YB YB YB (N) n NZ YB ks OT YB YB YB (N) n NZ YB ks OY YB YB YB (N) n NZ YB ks P YB YB YB (N) n NZ KS yb RC YB YB YB RJ yb NZ YB ks RJ,RO YB YB YB RJ yb NZ YB ks RK YB YB YB RJ yb NZ YB ks RP YB YB YB RJ yb NZ YB ks S YB YB YB (N) n NZ KS yb T YB YB YB (N) n NZ KS yb

Routing Directrory 29/06/2018 6.

A 1 2 3 4 5 6 ORIGIN AGGG ANAU AYPM KSLC NCRG NFFN DESTINATION U (EX. UH UI UT UE UN) YB YB YB RJ yb NZ YB ks UH,UE,UN YB YB YB RJ yb NZ YB ks UI YB YB YB RJ yb NZ YB ks UT YB YB YB RJ yb NZ YB ks VA YB YB YB RJ yb NZ YB ks VC YB YB YB RJ yb NZ YB ks VD YB YB YB RJ yb NZ YB ks VE YB YB YB RJ yb NZ YB ks VG YB YB YB RJ yb NZ YB ks VH YB YB YB RJ yb NZ YB ks VI YB YB YB RJ yb NZ YB ks VL YB YB YB RJ yb NZ YB ks VM YB YB YB RJ yb NZ YB ks VN YB YB YB RJ yb NZ YB ks VO YB YB YB RJ yb NZ YB ks VQ YB YB YB RJ yb NZ YB ks VR YB YB YB RJ yb NZ YB ks VT YB YB YB RJ yb NZ YB ks VV (EX. VVT) YB YB YB RJ yb NZ YB ks VVT YB YB YB RJ yb NZ YB ks VY YB YB YB RJ yb NZ YB ks WA YB YB YB RJ yb NZ YB ks WB (EX. WBA WBS) YB YB YB RJ yb NZ YB ks WBA WBS YB YB YB RJ yb NZ YB ks WI YB YB YB YB rj NZ YB ks WM YB YB YB RJ yb NZ YB ks WP YB YB YB RJ yb NZ YB ks WR YB YB YB RJ yb NZ YB ks WS YB YB YB RJ yb NZ YB ks Y YB YB YB YB nf NZ YB ks Z (EX. ZG ZJ ZK ZM) YB YB YB RJ yb NZ YB ks ZG YB YB YB RJ yb NZ YB ks ZJ YB YB YB RJ yb NZ YB ks ZK YB YB YB RJ yb NZ YB ks ZM YB YB YB RJ yb NZ YB ks

Routing Directrory 29/06/2018 7.

A 1 2 3 4 5 6 ORIGIN NFTF NGFU NGTT NIUE NSFA NSTU DESTINATION AG NZ NF NF NZ NZ KS AN NZ NF NF NZ NZ KS AY NZ NF NF NZ NZ KS B NZ NF NF NZ NZ KS C NZ NF NF NZ NZ KS D NZ NF NF NZ NZ KS E NZ NF NF NZ NZ KS F NZ NF NF NZ NZ KS G NZ NF NF NZ NZ KS H NZ NF NF NZ NZ KS K NZ NF NF NZ NZ KS L NZ NF NF NZ NZ KS M NZ NF NF NZ NZ KS NC NZ NF NF NZ NZ KS NF (EX. NFT) NZ NF NF NZ NZ KS NFT (N) n NF NF NZ NZ KS NG (EX. NGF) NZ NF (N) n NZ NZ KS NGF NZ (N) n NF NZ NZ KS NI NZ NF NF (N) n NZ KS NL NZ NF NF NZ NZ KS NS (EX. NST) NZ NF NF NZ (N) n KS NST NZ NF NF NZ NZ (N) n NT NZ NF NF NZ NZ KS NV NZ NF NF NZ NZ KS NW NZ NF NF NZ NZ KS NZ NZ NF NF NZ NZ KS OA NZ NF NF NZ NZ KS OB NZ NF NF NZ NZ KS OE NZ NF NF NZ NZ KS OI NZ NF NF NZ NZ KS OJ NZ NF NF NZ NZ KS OK NZ NF NF NZ NZ KS OL NZ NF NF NZ NZ KS OM NZ NF NF NZ NZ KS OO NZ NF NF NZ NZ KS OP NZ NF NF NZ NZ KS OR NZ NF NF NZ NZ KS OS NZ NF NF NZ NZ KS OT NZ NF NF NZ NZ KS OY NZ NF NF NZ NZ KS P NZ NF NF NZ NZ KS RC NZ NF NF NZ NZ KS RJ,RO NZ NF NF NZ NZ KS RK NZ NF NF NZ NZ KS RP NZ NF NF NZ NZ KS S NZ NF NF NZ NZ KS T NZ NF NF NZ NZ KS

Routing Directrory 29/06/2018 8.

A 1 2 3 4 5 6 ORIGIN NFTF NGFU NGTT NIUE NSFA NSTU DESTINATION U (EX. UH UI UT UE UN) NZ NF NF NZ NZ KS UH,UE,UN NZ NF NF NZ NZ KS UI NZ NF NF NZ NZ KS UT NZ NF NF NZ NZ KS VA NZ NF NF NZ NZ KS VC NZ NF NF NZ NZ KS VD NZ NF NF NZ NZ KS VE NZ NF NF NZ NZ KS VG NZ NF NF NZ NZ KS VH NZ NF NF NZ NZ KS VI NZ NF NF NZ NZ KS VL NZ NF NF NZ NZ KS VM NZ NF NF NZ NZ KS VN NZ NF NF NZ NZ KS VO NZ NF NF NZ NZ KS VQ NZ NF NF NZ NZ KS VR NZ NF NF NZ NZ KS VT NZ NF NF NZ NZ KS VV (EX. VVT) NZ NF NF NZ NZ KS VVT NZ NF NF NZ NZ KS VY NZ NF NF NZ NZ KS WA NZ NF NF NZ NZ KS WB (EX. WBA WBS) NZ NF NF NZ NZ KS WBA WBS NZ NF NF NZ NZ KS WI NZ NF NF NZ NZ KS WM NZ NF NF NZ NZ KS WP NZ NF NF NZ NZ KS WR NZ NF NF NZ NZ KS WS NZ NF NF NZ NZ KS Y NZ NF NF NZ NZ KS Z (EX. ZG ZJ ZK ZM) NZ NF NF NZ NZ KS ZG NZ NF NF NZ NZ KS ZJ NZ NF NF NZ NZ KS ZK NZ NF NF NZ NZ KS ZM NZ NF NF NZ NZ KS

Routing Directrory 29/06/2018 9.

A 1 2 3 4 5 6 ORIGIN NTAA NVVV NWWW NZCH OPKC PKMJ DESTINATION AG NZ YB NF YB ks VA zb KS AN NZ YB NF YB ks VA zb KS AY NZ YB NF YB ks VA zb KS B NZ YB NF KS yb OK oi KS C NZ YB NF KS yb OK oi KS D NZ YB NF YB ks OK oi KS E NZ YB NF YB ks OK oi KS F NZ YB NF YB ks OK oi KS G NZ YB NF YB ks OK oi KS H NZ YB NF YB ks OK oi KS K NZ YB NF KS yb OK oi KS L NZ YB NF YB ks OK oi KS M NZ YB NF KS yb OK zb KS NC NZ YB NF NC n VA zb KS NF (EX. NFT) NZ YB NF YB ks VA zb KS NFT NZ YB NF NFT n VA zb KS NG (EX. NGF) NZ YB NF YB ks VA zb KS NGF NZ YB NF YB ks VA zb KS NI NZ YB NF NI n VA zb KS NL NZ YB NL YB ks VA zb KS NS (EX. NST) NZ YB NF NS n VA zb KS NST NZ YB NF KS yb VA zb KS NT (N) n YB NF nt NT n VA zb KS NV NZ (N) n NF YB ks VA zb KS NW NZ nw YB (N) n YB ks VA zb KS NZ NZ YB NF (N) n VA zb KS OA NZ YB NF YB ks OA oi KS OB NZ YB NF YB ks OK oi KS OE NZ YB NF YB ks OK oi KS OI NZ YB NF YB ks OI ok KS OJ NZ YB NF YB ks OK oi KS OK NZ YB NF YB ks OK oi KS OL NZ YB NF YB ks OK oi KS OM NZ YB NF YB ks OK oi KS OO NZ YB NF YB ks OK oi KS OP NZ YB NF YB ks (N) n KS OR NZ YB NF YB ks OI ok KS OS NZ YB NF YB ks OI ok KS OT NZ YB NF YB ks OK oi KS OY NZ YB NF YB ks OK oi KS P NZ YB NF KS yb VA zb (N) n RC NZ YB NF YB ks VA zb KS RJ,RO NZ YB NF YB ks VA zb KS RK NZ YB NF YB ks VA zb KS RP NZ YB NF YB ks VA zb KS S NZ YB NF KS yb OK oi KS T NZ YB NF KS yb OK oi KS

Routing Directrory 29/06/2018 10.

A 1 2 3 4 5 6 ORIGIN NTAA NVVV NWWW NZCH OPKC PKMJ DESTINATION U (EX. UH UI UT UE UN) NZ YB NF YB ks OI ok KS UH,UE,UN NZ YB NF YB ks OI ok KS UI NZ YB NF YB ks OI ok KS UT NZ YB NF YB ks VA oi KS VA NZ YB NF YB ks VA zb KS VC NZ YB NF YB ks VA zb KS VD NZ YB NF YB ks VA zb KS VE NZ YB NF YB ks VA zb KS VG NZ YB NF YB ks VA zb KS VH NZ YB NF YB ks VA zb KS VI NZ YB NF YB ks VA zb KS VL NZ YB NF YB ks VA zb KS VM NZ YB NF YB ks VA zb KS VN NZ YB NF YB ks ZB va KS VO NZ YB NF YB ks VA zb KS VQ NZ YB NF YB ks VA zb KS VR NZ YB NF YB ks VA zb KS VT NZ YB NF YB ks VA zb KS VV (EX. VVT) NZ YB NF YB ks VA zb KS VVT NZ YB NF YB ks VA zb KS VY NZ YB NF YB ks VA zb KS WA NZ YB NF YB ks VA zb KS WB (EX. WBA WBS) NZ YB NF YB ks VA zb KS WBA WBS NZ YB NF YB ks VA zb KS WI NZ YB NF YB ks VA zb KS WM NZ YB NF YB ks VA zb KS WP NZ YB NF YB ks VA zb KS WR NZ YB NF YB ks VA zb KS WS NZ YB NF YB ks VA zb KS Y NZ YB NF YB ks VA zb KS Z (EX. ZG ZJ ZK ZM) NZ YB NF YB ks ZB va KS ZG NZ YB NF YB ks ZB va KS ZJ NZ YB NF YB ks ZB va KS ZK NZ YB NF YB ks ZB va KS ZM NZ YB NF YB ks ZB va KS

Routing Directrory 29/06/2018 11.

A 1 2 3 4 5 6 ORIGIN PTKK PTPN PTRO PTSA PTYA RCTP DESTINATION AG KS KS KS KS KS RP vh AN KS KS KS KS KS RP vh AY KS KS KS KS KS RP vh B KS KS KS KS KS VH rp C KS KS KS KS KS VH rp D KS KS KS KS KS RP vh E KS KS KS KS KS VH rp F KS KS KS KS KS RP vh G KS KS KS KS KS RP vh H KS KS KS KS KS RP vh K KS KS KS KS KS VH rp L KS KS KS KS KS VH rp M KS KS KS KS KS VH rp NC KS KS KS KS KS RP vh NF (EX. NFT) KS KS KS KS KS RP vh NFT KS KS KS KS KS RP vh NG (EX. NGF) KS KS KS KS KS RP vh NGF KS KS KS KS KS RP vh NI KS KS KS KS KS RP vh NL KS KS KS KS KS RP vh NS (EX. NST) KS KS KS KS KS RP vh NST KS KS KS KS KS RP vh NT KS KS KS KS KS RP vh NV KS KS KS KS KS RP vh NW KS KS KS KS KS RP vh NZ KS KS KS KS KS RP vh OA KS KS KS KS KS RP vh OB KS KS KS KS KS RP vh OE KS KS KS KS KS RP vh OI KS KS KS KS KS RP vh OJ KS KS KS KS KS RP vh OK KS KS KS KS KS RP vh OL KS KS KS KS KS RP vh OM KS KS KS KS KS RP vh OO KS KS KS KS KS RP vh OP KS KS KS KS KS RP vh OR KS KS KS KS KS RP vh OS KS KS KS KS KS RP vh OT KS KS KS KS KS RP vh OY KS KS KS KS KS RP vh P (N) (N) (N) (N) (N) VH rp RC KS KS KS KS KS (N) n RJ,RO KS KS KS KS KS RJ vh RK KS KS KS KS KS RJ vh RP KS KS KS KS KS RP vh S KS KS KS KS KS VH rp T KS KS KS KS KS VH rp

Routing Directrory 29/06/2018 12.

A 1 2 3 4 5 6 ORIGIN PTKK PTPN PTRO PTSA PTYA RCTP DESTINATION U (EX. UH UI UT UE UN) KS KS KS KS KS RJ vh UH,UE,UN KS KS KS KS KS RJ vh UI KS KS KS KS KS RJ vh UT KS KS KS KS KS RJ vh VA KS KS KS KS KS VH rp VC KS KS KS KS KS RP vh VD KS KS KS KS KS VH rp VE KS KS KS KS KS VH rp VG KS KS KS KS KS VH rp VH KS KS KS KS KS VH rp VI KS KS KS KS KS VH rp VL KS KS KS KS KS VH rp VM KS KS KS KS KS VH rp VN KS KS KS KS KS VH rp VO KS KS KS KS KS VH rp VQ KS KS KS KS KS VH rp VR KS KS KS KS KS RP vh VT KS KS KS KS KS VH rp VV (EX. VVT) KS KS KS KS KS VH rp VVT KS KS KS KS KS VH rp VY KS KS KS KS KS VH rp WA KS KS KS KS KS RP vh WB (EX. WBA WBS) KS KS KS KS KS RP vh WBA WBS KS KS KS KS KS RP vh WI KS KS KS KS KS RP vh WM KS KS KS KS KS RP vh WP KS KS KS KS KS RP vh WR KS KS KS KS KS RP vh WS KS KS KS KS KS RP vh Y KS KS KS KS KS RP vh Z (EX. ZG ZJ ZK ZM) KS KS KS KS KS VH rp ZG KS KS KS KS KS VH rp ZJ KS KS KS KS KS VH rp ZK KS KS KS KS KS VH rp ZM KS KS KS KS KS VH rp

Routing Directrory 29/06/2018 13.

A 1 2 3 4 5 6 ORIGIN RJJJ RKSS RPLL UHHH UUUU VABB DESTINATION AG WS vh RJ WS vh UU zb RJ n VT vc AN WS vh RJ WS vh UU zb RJ n VT vc AY WS vh RJ WS vh UU zb RJ n VT vc B KS ws RJ VH ws UU zb BI n VT vc C KS ws RJ VH ws UU zb EG n VT vc D WS vh RJ WS vh UU zb LF n HK vt E WS vh RJ VH ws UU zb (N) n VT vc F WS vh RJ WS vh UU zb LF n HK vt G WS vh RJ WS vh UU zb LE n HK vt H WS vh RJ WS vh UU zb LG n HK vt K KS ws RJ zb VH ws UU zb RJ n VT vc L WS vh RJ VH ws UU zb (N) n VT vc M KS ws RJ VH ws UU zb EG n VT vc NC KS ws RJ WS vh UU zb RJ n VT vc NF (EX. NFT) KS ws RJ WS vh UU zb RJ n VT vc NFT KS ws RJ WS vh UU zb RJ n VT vc NG (EX. NGF) KS ws RJ WS vh UU zb RJ n VT vc NGF KS ws RJ WS vh UU zb RJ n VT vc NI KS ws RJ WS vh UU zb RJ n VT vc NL KS ws RJ WS vh UU zb RJ n VT vc NS (EX. NST) KS ws RJ WS vh UU zb RJ n VT vc NST KS ws RJ WS vh UU zb RJ n VT vc NT KS ws RJ WS vh UU zb RJ n VT vc NV KS ws RJ WS vh UU zb RJ n VT vc NW KS ws RJ WS vh UU zb RJ n VT vc NZ KS ws RJ WS vh UU zb RJ n VT vc OA WS vh RJ WS vh UU n LC n OP vn OB WS vh RJ WS vh UU n LC n OO op OE WS vh RJ WS vh UU n LC n OO op OI WS vh RJ WS vh UU n LC n OP oo OJ WS vh RJ WS vh UU n LC n OO op OK WS vh RJ WS vh UU n LC n OO op OL WS vh RJ WS vh UU n LC n OO op OM WS vh RJ WS vh UU n LC n OO op OO WS vh RJ WS vh UU n LC n OO op OP WS vh RJ WS vh UU n LC n OP oo OR WS vh RJ WS vh UU n LC n OO op OS WS vh RJ WS vh UU n LC n OO op OT WS vh RJ WS vh UU n LC n OO op OY WS vh RJ WS vh UU n LC n OO op P KS ws RJ VH ws UU zb EG n VT vc RC RC vh RJ RC vh UU zb RJ n VT vc RJ,RO (N) n RJ zb VH rc UU zb RJ n VT vc RK RK zb (N) n VH rc UU zb RJ n VT vc RP WS vh RJ (N) n UU zb RJ n VT vc S KS ws RJ VH ws UU zb LE n VT vc T KS ws RJ VH ws UU zb EG n VT vc

Routing Directrory 29/06/2018 14.

A 1 2 3 4 5 6 ORIGIN RJJJ RKSS RPLL UHHH UUUU VABB DESTINATION U (EX. UH UI UT UE UN) UU zb RJ VH rc (N) n (N) n ZB op UH,UE,UN UU zb RJ VH rc (N) n (N) n ZB op UI UU zb RJ VH rc (N) n (N) n ZB op UT UU zb RJ VH rc (N) n UA un ZB op VA WS vh RJ WS vh ZB n RJ uh (N) n VC WS vh RJ WS vh ZB n RJ uh VC vt VD VH ws RJ VH rc ZB n RJ uh VT vc VE WS vh RJ VH rc ZB n RJ uh VE n VG VH ws RJ VH rc ZB n RJ uh VG vt VH VH ws RJ VH rc ZB n RJ uh VT vc VI WS vh RJ WS vh ZB n RJ uh VI n VL VH ws RJ VH rc ZB n RJ uh VT vc VM VH ws RJ VH rc ZB n RJ uh VT vc VN ZB ws RJ VH ws ZB n RJ uh VN zb VO WS vh RJ WS vh ZB n RJ uh VO n VQ WS vh RJ WS vh ZB n RJ uh VQ vt VR WS vh RJ WS vh ZB n RJ uh VC vt VT VH ws RJ VH rc ZB n RJ uh VT vc VV (EX. VVT) VH ws RJ VV vh ZB n RJ uh WS vt VVT VH ws RJ VV vh ZB n RJ uh WS vt VY VH ws RJ VH rc ZB n RJ uh WS vt WA WS vh RJ WS vh UU zb RJ n WS vt WB (EX. WBA WBS) WS vh RJ WS vh UU zb RJ n WS vt WBA WBS WS vh RJ WS vh UU zb RJ n WS vt WI WS vh RJ WS vh UU zb RJ n WS vt WM WS vh RJ WS vh UU zb RJ n WS vt WP WS vh RJ WS vh UU zb RJ n WS vt WR WS vh RJ WS vh UU zb RJ n WS vt WS WS vh RJ WS vh UU zb RJ n WS vt Y WS vh RJ WS vh UU zb RJ n VT vc Z (EX. ZG ZJ ZK ZM) ZB vh ZB rj VH ws ZB n RJ uh ZB op ZG ZB vh ZB rj VH ws ZB n RJ uh ZB op ZJ ZB vh ZB rj VH ws ZB n RJ uh ZB op ZK RK zb ZK zb VH ws ZB n RJ uh ZB op ZM ZB vh ZB rj VH ws UI zb UI uh ZB op

Routing Directrory 29/06/2018 15.

A 1 2 3 4 5 6 ORIGIN VCCC VDPP VECC VGZR VHHH VIDD DESTINATION AG WS va VT VA vg VT va VT rp VA n AN WS va VT VA vg VT va VT rp VA n AY WS va VT VA vg VT va VT rp VA n B WS va VT VA vg VT va RJ vt VA n C WS va VT VA vg VT va RJ vt VA n D WS va VT VA n VT va VT vvt VA n E WS va VT VA n VT va VT rj VA n F WS va VT VA vo VT va VT rp VA ve G WS va VT VA n VT va VT vvt VA n H WS va VT VA n VT va VT vvt VA n K WS va VT VA vg VT va RJ vt VA n L WS va VT VA n VT va VT rj VA n M WS va VT VA vg VT va RJ vt VA n NC WS va VT VA vg VT va VT rp VA n NF (EX. NFT) WS va VT VA vg VT va VT rp VA n NFT WS va VT VA vg VT va VT rp VA n NG (EX. NGF) WS va VT VA vg VT va VT rp VA n NGF WS va VT VA vg VT va VT rp VA n NI WS va VT VA vg VT va VT rp VA n NL WS va VT VA vg VT va VT rp VA n NS (EX. NST) WS va VT VA vg VT va VT rp VA n NST WS va VT VA vg VT va VT rp VA n NT WS va VT VA vg VT va VT rp VA n NV WS va VT VA vg VT va VT rp VA n NW WS va VT VA vg VT va VT rp VA n NZ WS va VT VA vg VT va VT rp VA n OA VA ws VT VA n VT va VT rp VA n OB WS va VT VA n VT va VT rp VA n OE WS va VT VA n VT va VT rp VA n OI WS va VT VA n VT va VT rp VA n OJ WS va VT VA n VT va VT rp VA n OK WS va VT VA n VT va VT rp VA n OL WS va VT VA n VT va VT rp VA n OM WS va VT VA n VT va VT rp VA n OO WS va VT VA n VT va VT rp VA n OP VA ws VT VA n VT va ZB vt VA n OR WS va VT VA n VT va VT rp VA n OS WS va VT VA n VT va VT rp VA n OT WS va VT VA n VT va VT rp VA n OY WS va VT VA n VT va VT rp VA n P WS va VT VA vg VT va RJ vt VA n RC WS va VT VA vg VT va RC rp VA n RJ,RO WS va VT VA vg VT va RJ rc VA n RK WS va VT VA vg VT va RJ zg VA n RP WS va VT VA vg VT va RP rc VA n S WS va VT VA vg VT va RJ vt VA n T WS va VT VA vg VT va RJ vt VA n

Routing Directrory 29/06/2018 16.

A 1 2 3 4 5 6 ORIGIN VCCC VDPP VECC VGZR VHHH VIDD DESTINATION U (EX. UH UI UT UE UN) WS va VT VI n VT va RJ zb UT n UH,UE,UN WS va VT VI n VT va RJ zb UT n UI WS va VT VI n VT va RJ zb UT n UT WS va VT (N) n VT va RJ zb UT n VA VA ws VT VA n VA vt VT vvt VA n VC (N) n VT VA n VA vt VT rp VA n VD WS va (N) n VA n VA va VT vvt (N) n VE VA ws VT (N) n VA vt VT vvt VA n VG VA ws VT VA n (N) n VT vvt VA n VH WS va VT (N) n VT va (N) n VA n VI VA ws VT (N) n VE vt VT vvt (N) n VL WS va VT VA vg VT vt VT vvt VA n VM WS va VT VA n VT vt VM zg VA ve VN VA ws VT VA n VA vt ZB zg VA n VO VA ws VT (N) n VA vt VT vvt VA n VQ VA ws VT VA n VA vt VT vvt VA n VR VR n VT VA vg VA vt VT rp VA n VT WS va VT VA vg VT va VT vvt VA n VV (EX. VVT) WS va VT VA vg VT va VVT vt VA n VVT WS va VT VA vg VT va VVT vt VA n VY WS va VT VA vg VT va VT vvt VA n WA WS va VT VA vg VT va VT rp VA n WB (EX. WBA WBS) WS va VT VA vg VT va VT rp VA n WBA WBS WS va VT VA vg VT va VT rp VA n WI WS va VT VA vg VT va VT rp VA n WM WS va VT VA vg VT va VT rp VA n WP WS va VT VA vg VT va VT rp VA n WR WS va VT VA vg VT va VT rp VA n WS WS va VT VA vg VT va VT rp VA n Y WS va VT VA vg VT va VT rp VA n Z (EX. ZG ZJ ZK ZM) VA ws VT VA n VT va ZB zg VA n ZG VA ws VT VA n VT va ZG zb VA n ZJ VA ws VT VA n VT va ZJ zg VA n ZK VA ws VT VA n VT va ZB zg VA n ZM VA ws VT VA n VT va ZB zg VA n

Routing Directrory 29/06/2018 17.

A 1 2 3 4 5 6 ORIGIN VLVT VMMC VNKT VOMM VQPR VRMM DESTINATION AG VT vv VH zg VA zb WM va VA VC AN VT vv VH zg VA zb WM va VA VC AY VT vv VH zg VA zb WM va VA VC B VT vv VH zg ZB va WM va VA VC C VT vv VH zg ZB va WM va VA VC D VT vv VH zg ZB va VA wm VA VC E VT vv VH zg VA zb VA wm VA VC F VT vv VH zg ZB va VA wm VA VC G VT vv VH zg ZB va VA wm VA VC H VT vv VH zg ZB va VA wm VA VC K VT vv VH zg ZB va WM va VA VC L VT vv VH zg VA zb VA wm VA VC M VT vv VH zg ZB va WM va VA VC NC VT vv VH zg VA zb WM va VA VC NF (EX. NFT) VT vv VH zg VA zb WM va VA VC NFT VT vv VH zg VA zb WM va VA VC NG (EX. NGF) VT vv VH zg VA zb WM va VA VC NGF VT vv VH zg VA zb WM va VA VC NI VT vv VH zg VA zb WM va VA VC NL VT vv VH zg VA zb WM va VA VC NS (EX. NST) VT vv VH zg VA zb WM va VA VC NST VT vv VH zg VA zb WM va VA VC NT VT vv VH zg VA zb WM va VA VC NV VT vv VH zg VA zb WM va VA VC NW VT vv VH zg VA zb WM va VA VC NZ VT vv VH zg VA zb WM va VA VC OA VT vv VH zg VA zb VA n VA VC OB VT vv VH zg VA zb VA wm VA VC OE VT vv VH zg VA zb VA wm VA VC OI VT vv VH zg VA zb VA wm VA VC OJ VT vv VH zg VA zb VA wm VA VC OK VT vv VH zg VA zb VA wm VA VC OL VT vv VH zg VA zb VA wm VA VC OM VT vv VH zg VA zb VA wm VA VC OO VT vv VH zg VA zb VA wm VA VC OP VT vv VH zg ZB va VA wm VA VC OR VT vv VH zg VA zb VA wm VA VC OS VT vv VH zg VA zb VA wm VA VC OT VT vv VH zg VA zb VA wm VA VC OY VT vv VH zg VA zb VA wm VA VC P VT vv VH zg ZB va WM va VA VC RC VT vv VH zg ZB va WM va VA VC RJ,RO VT vv VH zg ZB va WM va VA VC RK VT vv VH zg ZB va WM va VA VC RP VT vv VH zg ZB va WM va VA VC S VT vv VH zg ZB va WM va VA VC T VT vv VH zg ZB va WM va VA VC

Routing Directrory 29/06/2018 18.

A 1 2 3 4 5 6 ORIGIN VLVT VMMC VNKT VOMM VQPR VRMM DESTINATION U (EX. UH UI UT UE UN) VT vv VH zg ZB va VA wm VA VC UH,UE,UN VT vv VH zg ZB va VA wm VA VC UI VT vv VH zg ZB va VA wm VA VC UT VT vv VH zg ZB va VA wm VA VC VA VT vv VH zg VA zb (N) n VA VC VC VT vv VH zg VA zb VA wm VA VC VD VT vv VH zg VA zb VA wm VA VC VE VT vv VH zg VA zb (N) n VA VC VG VT vv VH zg VA zb VA n VA VC VH VT vv VH zg ZB va VA wm VA VC VI VT vv VH zg VA zb (N) n VA VC VL (N) n VH zg VA zb VA wm VA VC VM VT vv (N) n ZB va VA wm VA VC VN VT vv ZG vh (N) va VA wm VA VC VO VT vv VH zg VA zb (N) n VA VC VQ VT vv VH zg VA zb VA wm (N) n VC VR VT vv VH zg VA zb VA wm VA (N) n VT VT vv VH zg VA zb VA wm VA VC VV (EX. VVT) VV vt VH zg VA zb VA wm VA VC VVT VV vt VH zg VA zb VA wm VA VC VY VT vv VH zg VA zb VA wm VA VC WA VT vv VH zg VA zb WM va VA VC WB (EX. WBA WBS) VT vv VH zg VA zb WM va VA VC WBA WBS VT vv VH zg VA zb WM va VA VC WI VT vv VH zg VA zb WM va VA VC WM VT vv VH zg VA zb WM va VA VC WP VT vv VH zg VA zb WM va VA VC WR VT vv VH zg VA zb WM va VA VC WS VT vv VH zg VA zb WM va VA VC Y VT vv VH zg VA zb WM va VA VC Z (EX. ZG ZJ ZK ZM) VT vv ZG vh ZB va VA n VA VC ZG VV vt ZG vh ZB va VA n VA VC ZJ VV vt ZG vh ZB va VA n VA VC ZK VT vv ZG vh ZB va VA n VA VC ZM VT vv ZG vh ZB va VA n VA VC

Routing Directrory 29/06/2018 19.

A 1 2 3 4 5 6 ORIGIN VTBB VVTS VVVV VYYY WBKK WBSB DESTINATION AG WS wm VT vh VVT VT WM WS wm AN WS wm VT vh VVT VT WM WS wm AY WS wm VT vh VVT VT WM WS wm B VH ws VH vt VVT VT WM WS wm C VH ws VH vt VVT VT WM WS wm D WS va VT vh VVT VT WM WS wm E LI ws VH vt VVT VT WM WS wm F WS va VT vh VVT VT WM WS wm G WS va VT vh VVT VT WM WS wm H WS va VT vh VVT VT WM WS wm K VH ws VH vt VVT VT WM WS wm L LI ws VH vt VVT VT WM WS wm M VH ws VH vt VVT VT WM WS wm NC WS wm VT vh VVT VT WM WS wm NF (EX. NFT) WS wm VT vh VVT VT WM WS wm NFT WS wm VT vh VVT VT WM WS wm NG (EX. NGF) WS wm VT vh VVT VT WM WS wm NGF WS wm VT vh VVT VT WM WS wm NI WS wm VT vh VVT VT WM WS wm NL WS wm VT vh VVT VT WM WS wm NS (EX. NST) WS wm VT vh VVT VT WM WS wm NST WS wm VT vh VVT VT WM WS wm NT WS wm VT vh VVT VT WM WS wm NV WS wm VT vh VVT VT WM WS wm NW WS wm VT vh VVT VT WM WS wm NZ WS wm VT vh VVT VT WM WS wm OA VA ws VT vh VVT VT WM WS wm OB WS va VT vh VVT VT WM WS wm OE WS wm VT vh VVT VT WM WS wm OI WS wm VT vh VVT VT WM WS wm OJ WS wm VT vh VVT VT WM WS wm OK WS wm VT vh VVT VT WM WS wm OL WS wm VT vh VVT VT WM WS wm OM WS wm VT vh VVT VT WM WS wm OO WS wm VT vh VVT VT WM WS wm OP VA ws VT vh VVT VT WM WS wm OR WS wm VT vh VVT VT WM WS wm OS WS wm VT vh VVT VT WM WS wm OT WS wm VT vh VVT VT WM WS wm OY WS wm VT vh VVT VT WM WS wm P VH ws VH vt VVT VT WM WS wm RC VH ws VH vt VVT VT WM WS wm RJ,RO VH ws VH vt VVT VT WM WS wm RK VH ws VH vt VVT VT WM WS wm RP VH ws RP vh VVT VT WM WS wm S VH ws VH vt VVT VT WM WS wm T VH ws VH vt VVT VT WM WS wm

Routing Directrory 29/06/2018 20.

A 1 2 3 4 5 6 ORIGIN VTBB VVTS VVVV VYYY WBKK WBSB DESTINATION U (EX. UH UI UT UE UN) VH va VH vt VVT VT WM WS wm UH,UE,UN VH va VH vt VVT VT WM WS wm UI VH va VH vt VVT VT WM WS wm UT VH va VH vt VVT VT WM WS wm VA VA ws VT vh VVT VT WM WS wm VC WS wm VT vh VVT VT WM WS wm VD VD n VT vh VVT VT WM WS wm VE VA ws VT vh VVT VT WM WS wm VG VG n VT vh VVT VT WM WS wm VH VH ws VH vt VVT VT WM WS wm VI VA ws VT vh VVT VT WM WS wm VL VL vvt VV vt VL vvt VT WM WS wm VM VH ws VV vh ZG vvt VT WM WS wm VN VA vh VV vh ZG vvt VT WM WS wm VO WM ws VT vh VVT VT WM WS wm VQ VA ws VT vh VVT VT WM WS wm VR WS wm VT vh VVT VT WM WS wm VT (N) n VT vh VVT VT WM WS wm VV (EX. VVT) VVT vh VV n (N) n VT WM WS wm VVT VVT vh (N) n VVT VT WM WS wm VY VY vh VT vh VVT (N) n WM WS wm WA WS wm VT vh VVT VT WM WS wm WB (EX. WBA WBS) WM ws VT vh VVT VT (N) n WM ws WBA WBS WS wm VT vh VVT VT WM (N) n WI WS wm VT vh VVT VT WM WS wm WM WM ws VT vh VVT VT WM WS wm WP WS wm VT vh VVT VT WM WS wm WR WS wm VT vh VVT VT WM WS wm WS WS wm VT vh VVT VT WM WS wm Y WS wm VT vh VVT VT WM WS wm Z (EX. ZG ZJ ZK ZM) ZB vh VV vh ZG vvt ZB vt WM WS wm ZG ZB vh VV vh ZG vvt ZB vt WM WS wm ZJ ZB vh VV vh ZG vvt ZB vt WM WS wm ZK ZB vh VV vh ZG vvt ZB vt WM WS wm ZM ZB vh VV vh ZG vvt ZB vt WM WS wm

Routing Directrory 29/06/2018 21.

A 1 2 3 4 5 6 ORIGIN WIII WMKK WPDL WSSS YBBB ZBBB DESTINATION AG YB ws WS vt Y YB wi AG n RJ zg AN YB ws WS vt Y YB wi AN n RJ zg AY YB ws WS vt Y YB wi AY n RJ zg B YB ws WS vt Y RJ yb KS nf RJ zg C YB ws WS vt Y RJ yb KS nf RJ zg D YB ws WS vt Y YB vt FA ws RJ op E WS yb WS vt Y EG vt WS wi RJ zg F YB ws WS vt Y YB vt FA ws RJ op G YB ws WS vt Y YB vt FA ws RJ op H YB ws WS vt Y YB vt FA ws RJ op K YB ws WS vt Y RJ yb KS nf RJ zg L WS yb WS vt Y EG vt WS wi RJ zg M YB ws WS vt Y RJ yb KS nf RJ zg NC YB ws WS vt Y YB wi NZ ks RJ zg NF (EX. NFT) YB ws WS vt Y YB wi NF nz RJ zg NFT YB ws WS vt Y YB wi NZ ks RJ zg NG (EX. NGF) YB ws WS vt Y YB wi NF nz RJ zg NGF YB ws WS vt Y YB wi NF nz RJ zg NI YB ws WS vt Y YB wi NZ ks RJ zg NL YB ws WS vt Y YB wi NF nz RJ zg NS (EX. NST) YB ws WS vt Y YB wi NZ ks RJ zg NST YB ws WS vt Y YB wi KS nf RJ zg NT YB ws WS vt Y YB wi NZ ks RJ zg NV YB ws WS vt Y YB wi NV n RJ zg NW YB ws WS vt Y YB wi NF nz RJ zg NZ YB ws WS vt Y YB wi NZ ks RJ zg OA WS yb VO vt Y VC vt WS wi OP vn OB WS yb WS vt Y OB vt WS wi OP zg OE WS yb WS vt Y OB vt WS wi OP zg OI WS yb WS vt Y OB vt WS wi OP zg OJ WS yb WS vt Y OB vt WS wi OP zg OK WS yb WS vt Y OB vt WS wi OP zg OL WS yb WS vt Y OB vt WS wi OP zg OM WS yb WS vt Y OB vt WS wi OP zg OO WS yb WS vt Y OB vt WS wi OP zg OP WS yb VT ws Y VT oo WS wi OP zg OR WS yb WS vt Y OB vt WS wi OP zg OS WS yb WS vt Y OB vt WS wi OP zg OT WS yb WS vt Y OB vt WS wi OP zg OY WS yb WS vt Y OB vt WS wi OP zg P YB ws WS vt Y RJ yb KS nf RJ zg RC WS yb WS vt Y RJ vt WS wi RJ zg RJ,RO WS yb WS vt Y RJ vt WS wi RJ zg RK WS yb WS vt Y RJ vt WS wi RK rj RP WS yb WS vt Y RP vt WS wi VH zg S YB ws WS vt Y RJ yb KS nf RJ zg T WS yb WS vt Y RJ yb KS nf RJ zg

Routing Directrory 29/06/2018 22.

A 1 2 3 4 5 6 ORIGIN WIII WMKK WPDL WSSS YBBB ZBBB DESTINATION U (EX. UH UI UT UE UN) WS yb WS vt Y RJ vt WS wi UH rj UH,UE,UN WS yb WS vt Y RJ vt WS wi UH rj UI WS yb WS vt Y RJ vt WS wi UH rj UT WS yb WS vt Y RJ vt WS wi UH rj VA WS yb VT ws Y VC vt WS wi VA zg VC WS yb WS vt Y VC vt WS wi VA rj VD WS yb VT ws Y VT wm WS wi VT zg VE WS yb VT ws Y VC vt WS wi VA zg VG WS yb VT ws Y VT wm WS wi ZG rj VH WS yb WS vt Y RJ vt WS wi VH zg VI WS yb VT ws Y VC vt WS wi VA zg VL WS yb VT ws Y VT wm WS wi VT zg VM WS yb WS vt Y VT rj WS wi ZG rj VN WS yb VT ws Y VC vt WS wi VN zg VO WS yb VO ws Y WM vt WS wi VA zg VQ WS yb VT ws Y VC vt WS wi VA zg VR WS yb WS vt Y VC vt WS wi VA zg VT WS yb VT ws Y VT wm WS wi VT zg VV (EX. VVT) WS yb VT ws Y VVT vt WS wi VT zg VVT WS yb VT ws Y VVT vt WS wi VT zg VY WS yb VT ws Y VT wm WS wi VY zg WA (N) n WS vt Y WI yb WI ws RJ zg WB (EX. WBA WBS) WS yb WB n Y WM vt WS wi RJ zg WBA WBS WS yb WBS ws Y WBS wm WS wi RJ zg WI (N) n WS vt Y WI yb WI ws RJ zg WM WS yb (N) n Y WM vt WS wi RJ zg WP YB ws WS vt (N) (n) YB wi WP n RJ zg WR (N) n WS vt Y WI yb WI ws RJ zg WS WS yb WS vt Y (N) n WS wi RJ zg Y YB ws WS vt Y YB wi (N) n RJ zg Z (EX. ZG ZJ ZK ZM) WS yb VT ws Y RJ vt WS wi (N) n ZG WS yb VT ws Y VT rj WS wi ZG n ZJ WS yb VT ws Y VT rj WS wi ZG vh ZK WS yb VT ws Y RJ vt WS wi ZK rk ZM WS yb VT ws Y RJ vt WS wi ZM uh

Routing Directrory 29/06/2018 23.

A 1 2 3 4 5 6 ORIGIN ZGGG ZJHK ZKKK ZMUB DESTINATION AG VH zb VH zg ZB n ZB AN VH zb VH zg ZB n ZB AY VH zb VH zg ZB n ZB B ZB vh ZG vh ZB n ZB C ZB vh ZG vh ZB n ZB D ZB vh ZG vh ZB n ZB E VH zb VH zg ZB n ZB F ZB vh VH zg ZB n ZB G ZB vh ZG vh ZB n ZB H ZB vh ZG vh ZB n ZB K ZB vh ZG vh RK zb ZB L VH zb VH zg ZB n ZB M ZB vh ZG vh ZB n ZB NC VH zb VH zg ZB n ZB NF (EX. NFT) VH zb VH zg ZB n ZB NFT VH zb VH zg ZB n ZB NG (EX. NGF) VH zb VH zg ZB n ZB NGF VH zb VH zg ZB n ZB NI VH zb VH zg ZB n ZB NL VH zb VH zg ZB n ZB NS (EX. NST) VH zb VH zg ZB n ZB NST VH zb VH zg ZB n ZB NT VH zb VH zg ZB n ZB NV VH zb VH zg ZB n ZB NW VH zb VH zg ZB n ZB NZ VH zb VH zg ZB n ZB OA ZB vh ZG vh ZB n ZB OB ZB vh ZG vh ZB n ZB OE ZB vh ZG vh ZB n ZB OI ZB vh ZG vh ZB n ZB OJ ZB vh ZG vh ZB n ZB OK ZB vh ZG vh ZB n ZB OL ZB vh ZG vh ZB n ZB OM ZB vh ZG vh ZB n ZB OO ZB vh ZG vh ZB n ZB OP ZB vh ZG vh ZB n ZB OR ZB vh ZG vh ZB n ZB OS ZB vh ZG vh ZB n ZB OT ZB vh ZG vh ZB n ZB OY ZB vh ZG vh ZB n ZB P ZB vh ZG vh ZB n ZB RC ZB vh VH zg ZB n ZB RJ,RO ZB vh ZG vh RK zb ZB RK ZB vh ZG vh RK zb ZB RP VH zb VH zg ZB n ZB S ZB vh ZG vh ZB n ZB T ZB n ZG vh ZB n ZB

Routing Directrory 29/06/2018 24.

A 1 2 3 4 5 6 ORIGIN ZGGG ZJHK ZKKK ZMUB DESTINATION U (EX. UH UI UT UE UN) ZB n ZG vh ZB n ZB UH,UE,UN ZB n ZG vh ZB uh ZB UI ZB n ZG vh ZB uh UI zb UT ZB n ZG vh ZB uh ZB VA VH zb VH zg ZB n ZB VC VH zb VH zg ZB n ZB VD VH zb VH zg ZB n ZB VE VH zb VH zg ZB n ZB VG VH zb VH zg ZB n ZB VH VH zb VH zg ZB n ZB VI VH zb VH zg ZB n ZB VL VH zb VH zg ZB n ZB VM VM vh ZG vh ZB n ZB VN ZB vh ZG vh ZB n ZB VO VH zb VH zg ZB n ZB VQ VH zb VH zg ZB n ZB VR VH zb VH zg ZB n ZB VT VH zb VH zg ZB n ZB VV (EX. VVT) VV vh ZG vh ZB n ZB VVT VV vh ZG vh ZB n ZB VY VH zb VH zg ZB n ZB WA VH zb VH zg ZB n ZB WB (EX. WBA WBS) VH zb VH zg ZB n ZB WBA WBS VH zb VH zg ZB n ZB WI VH zb VH zg ZB n ZB WM VH zb VH zg ZB n ZB WP VH zb VH zg ZB n ZB WR VH zb VH zg ZB n ZB WS VH zb VH zg ZB n ZB Y VH zb VH zg ZB n ZB Z (EX. ZG ZJ ZK ZM) ZB n ZG n ZB rk ZB ZG (N) n ZG n ZB rk ZB ZJ ZJ vh (N) n ZB rk ZB ZK ZB n ZG n (N) n ZB ZM ZB n ZG n ZB rk (N) n

Routing Directrory 29/06/2018 25.

AFTN CIRCUITS - ASIA/PAC ROUTING DIRECTORY

Terminal 1 Terminal II ATSMHS or AFTN Over CRV (Y/N)

Apia/Faleolo Christchurch AMHS/UA

Bangkok Beijing AMHS Mumbai AMHS Dhaka AMHS Ho-Chi-Minh AFTN Hong Kong AMHS Kuala Lumpur AFTN Phnom Penh AMHS Rome AFTN Yangon AMHS Singapore AMHS Vientiane AMHS Paro AMHS

Beijing Bangkok AMHS Fukuoka AFTN Guangzhou AFTN Hong Kong AMHS Karachi AFTN Khavarosk AFTN Kathmandu AFTN Mumbai AMHS Pyongyang AFTN Seoul AMHS Ulaan Baatar AFTN Yangon AFTN

Brisbane Christchurch AMHS Timor Leste Jakarta AFTN Johannesburg AFTN Honiara Nadi AMHS Nauru Port Moresby Port Vila USA AMHS

Brunei Kuala Lumpur Singapore AFTN

Chennai Mumbai AFTN Kolkata AFTN Kuala Lumpur AFTN

Christchurch Apia/Faleolo AMHS/UA Niue AMHS/UA Rarotonga AMHS/UA

28th Edition 10-06-18 26.

Terminal 1 Terminal II ATSMHS or AFTN Over CRV (Y/N)

Brisbane AMHS Papeete/Tahiti AFTN Tonga/Fua’Amotu AMHS/UA USA AMHS

Chuuk USA AMHS/UA

Colombo Mumbai AMHS Male AFTN Singapore AFTN

Delhi Mumbai AFTN Kolkata AFTN

Dhaka Bangkok AMHS

Fukuoka Beijing AFTN Hong Kong AFTN Moscow AFTN Seoul AFTN Singapore AFTN Taibei AFTN USA AMHS

Guangzhou Beijing AFTN Hong Kong AFTN Macau AFTN Haikou AFTN Hanoi AFTN

Hanoi Ho-Chi-Minh AFTN Vientiane AFTN Guangzhou AFTN

Haikou Guangzhou AFTN Hong Kong AFTN

Ho-Chi-Minh Bangkok AFTN Hanoi AFTN Hong Kong AFTN Singapore AFTN

Hong Kong Bangkok AMHS Beijing AMHS Guangzhou AFTN Ho-Chi-Minh AFTN Macau AMHS Manila AFTN Haikou AFTN Taibei AFTN Fukuoka AFTN

28th Edition 10-06-18 27.

Terminal 1 Terminal II ATSMHS or AFTN Over CRV (Y/N)

Honiara Brisbane AMHS/UA

Jakarta Brisbane AFTN Singapore AMHS

Karachi Beijing AFTN Mumbai AMHS Kabul AFTN Kuwait AMHS Tehran*

* Not listed in the ANP AFTN Planning Table

Kathmandu Beijing AFTN Mumbai AMHS

Kolkata Mumbai AFTN Delhi AFTN Chennai AFTN

Koro USA AMHS/UA

Kosrae USA AMHS/UA

Kuala Lumpur Bangkok AFTN Brunei Singapore AFTN Chennai AFTN

Macau Guangzhou AFTN Hong Kong AMHS

Majuro USA AMHS/UA

Male Colombo AFTN

Manila Hong Kong AFTN Ho Chi Minh AFTN Singapore AFTN Taibei AFTN

Mumbai Bangkok AMHS Dhaka AMHS Kolkata AFTN Colombo AMHS Delhi AFTN Karachi AMHS Kathmandu AMHS Chennai AFTN Muscat/Seeb AFTN (No connection) Nairobi AFTN

28th Edition 10-06-18 28.

Terminal 1 Terminal II ATSMHS or AFTN Over CRV (Y/N)

Paro AMHS Singapore AMHS

Nadi Brisbane AMHS Funafuti Noumea AMHS Tarawa AMHS/UA USA AMHS Wallis Is.

Nauru Brisbane AMHS/UA

Niue Christchurch AMHS/UA

Noumea Nadi AMHS

Pago Pago USA AMHS/UA

Papeete/Tahiti Christchurch AFTN

Paro Mumbai AMHS Bangkok AMHS

Phnom Penh Bangkok AMHS Ho Chi Minh AMHS

Pohnpei USA AMHS/UA

Port Moresby Brisbane AFTN

Port Vila Brisbane AMHS/UA

Pyongyang Beijing AFTN

Rarotonga Christchurch AFTN

Seoul Beijing AMHS Fukuoka AFTN

Singapore Bangkok AMHS Bahrain AFTN Brisbane AMHS Brunei AFTN Colombo AFTN Ho-Chi-Minh AFTN Jakarta AMHS Kuala Lumpur AFTN London AMHS Manila AFTN Mumbai AMHS Fukuoka AFTN

28th Edition 10-06-18 29.

Terminal 1 Terminal II ATSMHS or AFTN Over CRV (Y/N)

Taibei Hong Kong AFTN Manila AFTN Fukuoka AFTN

Tarawa Nadi AMHS/UA

Timor Leste Brisbane AMHS

Tonga/Fua’Amotu Christchurch AMHS/UA

Ulaan Baatar Beijing AFTN

Vientiane Bangkok AMHS Hanoi AFTN

Wallist Is. Nadi (planning)

Yangon Bangkok AMHS Beijing AFTN

Yap USA AMHS/UA

______

28th Edition 10-06-18

ACSICG/5 Appendix G to the Report

STRATEGY FOR IMPLEMENTATION OF COMMUNICATION SYSTEMS TO SUPPORT AIR NAVIGATIONSERVICE IN THE ASIA/PACIFIC REGION

Considering that:

1) legacy AFTN circuits are required until the ground systems of ATM Service Providers (ASP) and Airspace Users (AU) in reliant states are compatible with ATS Message Handling Service (AMHS), the successor implementation of the Aeronautical Fixed Service (AFS); 2) the Aeronautical Telecommunication Network (ATN) is specified in ICAO SARPs and technical manuals as the network supporting AFS—implemented using either OSI protocols (ATN/OSI) or the Internet Protocol Suite (ATN/IPS)—for both ground-ground and ground-air services; 3) many states have implemented ATN and AMHS in accordance with ICAO guidance (regional BBIS providing dual OSI/IPS stack routing at the AMHS level); 4) AN Conf/12 endorsed the Global Air Navigation Plan version 4including the Aviation System Block Upgrades of the Globally Interoperable Services and Data improvement area based on System-Wide Information Management (SWIM) message exchange patterns (specified in the SWIM Operational Concept as IP-based web services); 5) APANPIRG adopted the Seamless ATM Plan (Version 2) in 2016 which includes the regional objective for SWIM and Common aeRonautical VPN (CRV) implementation; and 6) operational precedents of slightly different implementations of this SWIM concept exist in North America and Europe.

THE GENERAL STRATEGY FOR THE IMPLEMENTATION OF THE NECESSARY INTER-STATE COMMUNICATION SERVICES TO SUPPORT THE GLOBAL AIR NAVIGATION PLAN IN THE ASIA/PACIFIC REGION IS AS FOLLOWS: a) Initiate transition ATSMHS and other applications to Internet Protocol Suite (IPS) based CRV. This would allow ATSMHS to be compatible to other regions using either CRV or other IP based networks. b) continue deploying the ground-ground ATN backbone network of AMHS Message Transfer Agents (MTA) needed to support operational ground-ground services (as the infrastructure supporting AFTN such as X.25 becomes obsolete) and the air-ground services expected to migrate to ATN/IPS. c) acknowledge ICAO’s acceptance of IP sub-networking and the precedent of PENS in Europe and FTI in North America and consider the consequent potential for superior approaches to APAC’s ATN which is deployed as an aggregation of private leased point-to-point and other circuits including the Public Internet; d) apply guidance from ICAO technical panels—primarily the Information Management and Communications panels—in progressing regional planning and co-ordination in terms of inter- state exchange of aeronautical, meteorological, flight information, voice communication services and surveillance data;

G - 1

ACSICG/5 Appendix G to the Report e) permit BBIS and BIS and non-backbone States, and States in other regions with connections to the Asia/Pacific region, to connect their Message Transfer Agents (MTA) to backbone BBIS States using either the OSI-based ATN Internet Communications Services (ICS) or the ATN IPS on a bilateral basis; f) permit States with limited traffic to operate only UA terminals connected to the MTA of another State, subject to bilateral agreement. Such connections should use the CRV’s IP VPN. In cases where is not practical, use of the public Internet subject to appropriate security provisions and access control is acceptable; g) complete migration from AFTN to AMHS within the time frame specified in the Regional Air Navigation Plan; h) once a robust ATN has been established, transition from the OSI-based ATN ICS to the AMHS MTA network using the ATN/IPS as specified in ICAO Doc 9896; i) consider options for augmenting the operational regional ATN to meet future operational requirements(including virtualizing the ATN over generic sub-networking infrastructure/services capable of supporting other higher-level communication services in addition to the ATN).

IN ORDER TO ACHIEVE THE ABOVE STRATEGY THE FOLLOWING ACTIONS ARE REQUIRED: i) Enhance AMHS to include the File Transfer Body Part (FTBP) sub-set of extended AMHS in order to support the exchange of IWXXM data using FTBP; j) Australia, Fiji, New Zealand and USA to replace their obsolete South Pacific AFS Network equipment with a subscription to the CRV managed service. In addition to sustaining operational voice and ground-ground data services, validate the 10 key points of the CRV proof-of-concept; k) Remaining APAC states to monitor outcomes of the proof of concept andconsider subscription to the CRV service if it is beneficial given their particular circumstance; l) When CRV pilot is completed and service is accepted, BBIS States should prioritize the transition of AMHS MTA to CRV as well as coordinate with BIS States to join. Conversion of legacy interfaces (X.25, X.25 SNDCF, and IP SNDCF) to IPS should be utilized to support the AMHS transition to CRV. m) States and ASP/AU to participate in the SWIM Task Force and nominate subject matter experts to implement Phases 2 and Phase 3 of the Seamless ATM plan Version 2 adopted by APANPIRG in 2016.Three phases are identified in the SWIM Task Force’s work plan:

a. Definition phase b. Implementation phase 1 - expansion of services and preparation of phase 2 c. Implementation phase 2 – generalization. n) Support the transition to FIXM with initial focus on the regional ATFM. ______

G - 2