Report of ACP, WG-M/14 Meeting

(Montreal, 2-5 June 2008)

ACP WG-M/17 REPORT
Jan 31 - Feb 1, 2011

AERONAUTICAL COMMUNICATIONS PANEL (ACP)

WG M – Maintenance of A/G and G/G Communication Systems

17th Meeting

Bangkok, Thailand, Jan 31st-Feb 1st, 2011

DRAFT - Report of ACP WGM-17 Meeting

Drafted by the Secretary

WG M Meeting 17 Draft Report V1.docPage1

Report of ACP, WG-M/17 Meeting

(Bangkok, Jan 31st – Feb 1st, 2011)

TABLE OF CONTENTS

1. OPENING OF MEETING

2. AGENDA ITEM 1(b): STATUS OF ACTION ITEMS

3. Agenda Item 2(a) – Status of FAA DataComm Programme

4. Agenda Item 2(b) – Status of LINK 2000+/ SESAR

5. Agenda Item 2 (c) - Status of Surface Wireless Communications

6. Agenda Item 3(b) – AMHS and Directory Updates.

7. Agenda Item 3(a) – Security Updates (Doc 9705 Baseline).

8. Agenda Item 6: Other Business

9. Agenda Item 3(c): PM-FIS and PM-ADS-C Status.

10. Agenda Item 4(a) – IPS Implementation Status

11.Agenda Item 4(c) – Discussion on how to proceed with Air-Ground Security.

12.Agenda Item 4(d) – Doc 9896 VOIP Development Status.

13.Agenda Item 5 – Maintenance of VDL Documents.

14.Agenda Item 6 – Maintenance of UAT Documents.

15.AGENDA ITEM 8: Next Meeting

16.APPENDIX 1 – LIST OF ATTENDEES

17.APPENDIX 2 – Proposed Agenda and Schedule

18.APPENDIX 3 – List of Action Items

WG M Meeting 17 Draft Report V1.docPage1

Report of ACP, WG-M/17 Meeting

(Bangkok, Jan 31st – Feb 1st, 2011)

1.OPENING OF MEETING

1.1The Working Group Rapporteur, Brent Phillips opened the 17th meeting of WG-M. Following which, the meeting participants introduced themselves to the meeting.

1.2This was followed by a review of the meeting agenda and schedule, following which it was approved by the meeting. It was also pointed out a number of working papers had been incorrectly posted on the meeting web-site. The secretary took an action to remedy this problem.

Action Item 17-1: Secretary to post correct working papers to Meeting Web-Site.

1.3 The meeting report presents the agenda items in numeric order, although for practical reasons the meeting, not all items were dealt with in this order. Many items, particularly those dealing with programme updates were dealt with at the WG-I/13 meeting, immediately preceding this meeting. Hence it was not necessary to deal with these at WG-M/17.

1.4Thanks were expressed to the AEORTHAI for their sponsorship of the meeting and to the ICAO ASIA-PAC staff for their organisation of the meeting.

2.AGENDA ITEM 1(b): STATUS OF ACTION ITEMS

2.1The Secretary introduced WP-2, “Status of Action Items Assigned to Secretary”. Regarding Action Item 16-2, the comment was made that the (EUROCONTROL) AMC could be used as an alternative to the GIS Portal. It was also pointed out that Action Item 16-7 should be assigned to Vidyut Patel and not Mike Olive. The status of the action items as given in WP-2 was accepted by the meeting.

2.3Against Action Item 16-8, Greg Saccone (Boeing) expressed concern that actual implementation did not reflect the current provisions of Document 9880. This led to the following action item;

Action Item 17-2: Where appropriate, Secretary to take steps to ensure alignment between actual implementation and provisions of Doc 9880.

2.4The current disposition of all action items following the meeting is given in Appendix 3.

3.AGENDA ITEM 2(A) – STATUS OF FAA DATACOMM PROGRAMME

3.1Gregg Anderson (FAA) presented IP-3 providing an overview and status report on the FAA Data Comm programme. The salient points from this paper were as follows. The programme portfolio covers; automation systems in towers and ATSUs; avionics; network infrastructure and will support a number of automated ATS Services. Two programme segments have been defined.

3.2Segment 1 provides Tower service beginning in 2014 with Departure Clearances. Followed by En-Route services in 2016, including automating routine clearances, transfer of communications to the next sector, and the ability to provide better routes around weather.

3.3Segment 2will introduce data messaging for non time-critical communications in the Approach Control environment, as well as implementing trajectory based flight in designated airspace. This is expected to begin in 2018.

3.4It was pointed out that the programme has been harmonized with SESAR with Segment 1 corresponding to LINK 2000+ and Segment 2 corresponding to (SESAR) Implementation Package 2.

3.5 Users would be encouraged to equip through a strategy comprised of financial benefits, followed by operational incentives and finally regulatory action. Aircraft equipped with FANS-1/A would be supported due to the current large fleet of equipped aircraft.

4.AGENDA ITEM 2(B) – EUROCONTROL, LINK 2000+ AND SESAR.

4.1Liviu Popescu introduced WP 20, providing an update on the LINK 2000+ programme,.

4.2Key points from this were as follows. Financial incentives have been provided to encourage equipage. 500 aircraft are expected to be equipped as a result. Lab test and initial flight trials have been conducted on Multi-Frequency VDL Mode-2 (needed to support SESAR). Various anomalies have been detected with both the ground equipment and avionics. These will be resolved and a further round of flight tests will take place later in 2011. The following time-frame was outlined:

Implementation Package 1 (IP1) using Initial CPDLC (now – 2015)

Implementation Package 2 (IP2) using Initial 4D message set (2015 -2020)

Implementation Package 3 (IP3) using Full 4D message set (2020+)

on behalf of Mr Martin Adnams EUROCONTROL Link2000+ Programme Manager.

The presentation provided updates on the following; progress on incentives schemes; update on the VDL M2 multi-frequency validation led by EUROCONTROL and Link 2000+ Programme Coordination.

In the introduction key dates of the Programme had been reminded as follows:

1 January 2011 – After this date all new aircraft operating above FL 285 must be delivered with a compliant system.

7 February 2013 – By this date all LINK Region ANSPs must have implemented an operational compliant system.

7 February 2015 – By this date all aircraft operating above FL 285 must have been retrofitted with a compliant system.

7 February 2015 – By this date all EU Region ANSPs must have implemented an operational compliant system.

More information is available on the Link2000+ website:

On the subject of incentives, these were supported through the EC Trans-European Transport Network Executive Agency (TENT-EA) European Economic Recovery Plan (EERP) where EUROCONTROL was requested to bid on behalf of the Airspace Users. The final decision was reached on 22nd December 2009. The fleet shall be equipped in 2011 and 2012.The funding to Airspace Users covers 20% of the actual airline cost. 3 calls for tender had been launched in 2010. As a result, more than 500 aircraft will be equipped through the incentive scheme, however not all the Grant money will be used. Currently, no more applications will be accepted.

The Multi-frequency VDL M2 validation of AEEC 631-6 Specification is carried out by EUROCONTROL in a phased approach. The phases are as follows: Phase 1 – laboratory testing, Phase 2 – Flight trails in a limited VDL M2 Multi-Frequency ground implementation and Phase 3 – Airline Flights in a limited VDL M2 Multi-Frequency ground implementation.

SITA was contracted to support the validation via EUROCONTROL Maastricht UAC. PM-CPDLC Pioneer avionics had been also contracted to support the MF validation.

Phase 1 – Laboratory testing started on 27th September 2010 in Montreal. Minor ambiguities, non critical, had been identified in the specification. Additional laboratory tests with other avionics are planned for Q1-Q2 2011.

Phase 2 – 3 DFS/SITA VDL Ground stations had been upgraded with MF capability. 1st flight trial was performed on 26 November 2010. Preliminary results supported the successful demonstration of a number of MF operation aspects. Overall, no critical impact on the specification is expected. Additional flights are scheduled during Q3 2011.

Phase 3 – Will start Q3 2011. Mandated forward fit on 1st January 2011 will provide the opportunity to exercise MF with operational aircraft. MF transitions will cover a wider range of conditions than in Phase 2 within a similar ground scenario as in Phase 2. The aircraft recruited to Phase 3 will be selected by the 24 bits address.

On the subject of Programme coordination a series of activities are addressing short, medium and long term datalink evolution as follows: formal EUROCONTROL-FAA coordination in place, OPLINK Panel work on Datalink Harmonisation Plan for ANC 2012, SESAR and NEXTGEN R&D validation underway. In particular for medium term, the convergence is addressed through the development of Safety & Performance Requirements (SPR) and Interoperability standards by EUROCAE WG-78/RTCA SC-214.

In the discussion following the presentation it was clarified that the ANSPs ground deployment will follow a phased approach with two distinct mandate dates: 7 February 2013 for Link Region and 7 February 2015 for all EU States.

5.AGENDA ITEM 2(C) AEROMACS STANDARDS DEVELOPMENT

5.1Brent Phillips introduced WP03, “AeroMACS Status Briefing”. WP03 discussed the evaluation trials being conducted at Cleveland Airport. Key findings from this were:

  • Satisfactory data rates and throughput were being observed.
  • Out-of-band (OOB) interference into adjacent aeronautical band (5030-5091 MHz) had been observed. The solution may require coordination through ICAO.
  • Further trials are planned for 2011 to: optimise antenna configuration, spectrum usage and performance.

5.3The meeting then entered into a general discussion on the practical aspects of airport surface datalink. One of the items discussed was the transition between surface and air-ground datalink. It was pointed out that aircraft would revert to air-ground datalink following “wheels-up”. This could either be triggered by mechanical means now or handled by software-defined radios in the future.

5.2The briefing then covered industry standards development activities. Key points from this were that the draft AeroMACS profile had been completed by RTCA SC-223 and EUROCAE WG-82 and was being distributed for Final Review and Comment (FRAC). Work on MOPS development is expected to commence in February 2011.

6.AGENDA ITEM 2(D) OTHERS

6.1Katsuya Inoguchi introduced IP2, “Long-Term Vision of Future Air Traffic Systems in Japan”.This described efforts to develop the Japanese plan for ATM modernisation. This plan is termed “CARATS: Collaborative Actions for Renovation of Air Traffic Systems” since it required the following collaborative works with various aviation stakeholders:

(a)Collaboration with industry, academia and government

(b)Collaboration between operators and Air Navigation Service Provider (ANSP)

(c)International Collaboration to realize seamless air traffic operations

(d)Collaboration among co-users of airspace (Civil, Japan Self-Defence Forces, US Forces)

(e)Collaboration with local communities

6.2In order to systematically establish the future air traffic system, CARATS a detailed road map with the cooperation of the parties concerned will first be drawn. This roadmap is near completion and undergoing final review.

7.AGENDA ITEM 3(A): ATN/OSI DOCUMENT 9880 UPDATE STATUS - SECURITY UPDATES (9705 BASELINE).

7.1Michael Olive, Honeywell, presented aworking paper (WP07)titled “ATN Certificate and CRL Analysis.” This paper uses a presentation format to summarize the subject full report, which is made available in its entirety in WP06. The analysis was performed by the Aerospace Advanced Technology organization of Honeywell International Inc. under contract to the FAA and in support of the FAA Data Comm Program Office. As background, WGM16-WP08 recommended that the detailed ATN Certificate and Certificate Revocation List (CRL) provisions in Doc. 9880 Part IV-B be replaced with references to industry standards, consistent with the Public Key Infrastructure (PKI) provisions in Section 2/5 of Doc. 9896 (ATN/IPS). The purpose of this analysis was to conduct a field-by-field examination of the elements of an ATN Certificate and an ATN CRL, as defined in Doc. 9705 Edition 3 Sub-Volume VIII, with respect to the industry specifications IETF RFC 5280 and ATA Spec 42. The analysis results show that the ATN certificate/CRL provisions align well with the industry standards, and the report recommends that many of the requirements in Doc 9705 Edition 3 Sub-Volume VIII could be replaced with references to RFC 5280 and Spec 42, as well as RFC 5480, which defines syntax and object identifiers for elliptic curve public keys. Where differences exist, the analysis report recommends that select ATN/OSI certificate/CRL provisions be maintained to supplement the industry standard references and provide specificity relevant to ATN (e.g., entity naming). Mr. Liviu Popescu, EUROCONTROL, commented that the recommendations to align the Doc. 9880 PKI provisions with the PKI provisions in Doc. 9896 was “on the right track.”

In the discussions that followed EUROCONTROL indicated that alignments with ATN/IPS provisions are a desirable target.

7.2Michael Olive, Honeywell, presented information paper (IP01) titled “ATN/OSI Security References in ARINC Specification 823.” This paper describes parallel industry standardization efforts within the Airlines Electronic Engineering Committee (AEEC) to update ATN/OSI security references contained in ARINC Specification 823, ACARS Message Security (AMS), from ICAO Doc. 9705 Sub-Volume VIII to ICAO Doc. 9880 Part IV-B. AMS security requirements are based on the ATN/OSI security provisions which, facilitates use of common security controls and infrastructure for datalink security, both ATN/OSI and ACARS. WG-M was invited to offer expected timing for availability of Doc. 9880 Part IV-B (e.g., advance version); this timing information may be a useful input for the AEEC since the ARINC Specification 823 updates will be considered for adoption during the upcoming AEEC General Session (18-21 April 2011).

Item for Follow-Up 17-1: WG-M to determine likely availability of advance version of Doc 9880 Part IVB.

[LP1]

7.3Michael Olive, Honeywell, also presented information paper (IP03) titled “Industry Standardization in the area of Security.” This paper summarizes Air Transport Association (ATA) Digital Security Working Group (DSWG) and Airlines Electronic Engineering Committee (AEEC) industry standardization activities relevant to ICAO Doc. 9880 Part IV-B. A graphic illustrates cross-reference linkages among the ICAO, ATA, and AEEC documents, and provides context for the recommendations presented previously in WP07.

7.4Vic Patel, FAA, presented a working paper (WP23) which is anAmendment Proposal to the Draft Doc 9880 Part IV B. The AP is to refer to RFC 5280,5480 and Spec 42 Certificate/CRL Profiles and remove the requirements in Part IV B which are covered by these references.

7.5Vic Patel, FAA, also presented working paper (WP22) which updates the draft version of Doc 9880 Part IV B with the Amendment Proposals which had been presented through Meeting 16.

7.6Tom McParland, BCI (supporting FAA), presented working paper (WP21) which contains draft requirements for the Secure Dialogue Service. The concept of the Secure Dialogue Service was presented in Meeting 16 in Working Paper 16. The Secure Dialogue Service is an alternative to implementing the Security ASO defined in the ULCS. By using the Secure Dialogue Service the complexities of implementing the SESE within the Security ASO and of implementing security in the ACSE can be avoided. The Secure Dialogue service is compatible with the Dialogue Service assumed by CPDLC and CM as defined in Doc 9880. The use of the Security Parameter as a matter of local policy is specified throughout the Doc 9880 versions of CPDLC and CM. It was noted that the ULCS defined in Doc 9880 refers to the System Security Object and so without having Part IV B of Doc 9980 the Doc 9880 ULCS has unresolved references and thus the Security ASO would be impossible to implement. The Secure Dialogue Service would fix this problem by permitting the Doc 9880 ULCS to be implemented without the Security ASO. Alternatively the Secure Dialogue Service could be implemented with the Doc 9705 Edition 2 ULCS. The Secure Dialogue Service could also provide support to ATN Air-Ground applications which use the IP Dialogue Service defined in Doc 9896.

7.7There was an ensuing discussion on the general issue of Doc 9880 Part IV B. It was pointed out that up to this point Part IV B was not an approved chapter of Doc 9880 and not posted on the ICAO Repository. The FAA stated that this was a problem for their Data Comm program while EUROCONTROL maintained that Link 2000+ did not require security and that SESAR had not yet determined the need for security or heir preferred approach. SESAR Work Package 16 will deal with security however it will be completed in two years. The FAA reported that they could not wait for this work to be completed. The FAA is initiating the next phase of their outreach program with avionics vendors and wants to include air-ground security, and thus needs a specification that can be referenced. The FAA noted that their Data Comm program and an independent organization had conducted risk assessments and had determined that the FAA has a requirement for air-ground security.

7.8After considerable discussion the following compromise was put forward. ICAO will place a draft version of Doc 9880 Part IV B on the Repository asas an “Advance unedited Manual on detailed technical specifications for the ATN/OSI - Part IV B ATN Security Provisions”. The FAA will provide this document as [LP2]a translation of ICAO Doc 9705 Edition 3. It was noted that Doc 9705 Edition 3 is a validated and approved document and that this is essentially following the same approach as was followed for CM, CPDLC, and the ULCS. The FAA will re-introduce the Amendment Proposals to Part IV B proposed during the previous Working Group M meetings following a CCB approach that includes participation by EUROCONTROL. It was acknowledged by the FAA that this does not address the overall issue of whether or not to do security. This discussion needs to occur in ACP WG-W and SC-214.

Action Item 17-3: Secretary to place a draft version of Doc 9880 Part IV B on the Repository as an “Advance unedited Manual on detailed technical specifications for the ATN/OSI - Part IV B ATN Security Provisions”.[LP3]

Action Item 17-4: FAA to submit an amendment proposal, containing the changes called for in WPs 11 through WP15, submitted at WG-M/16 in Paris. Amendment proposal to be processed by CCB. Secretary to update the draft Doc.9880 Part IVB accordingly.

Action Item 17-5: FAA to submit an amendment proposal, containing the changes called for in WPs 6 and 7, submitted at WG-M/17 in Bangkok. Amendment proposal to be processed by CCB. Secretary to update the draft Doc. 9880 Part IVB accordingly.

7.9The subject of security then led to an open discussion on the nature of the CCB. A number of points were agreed, a) one person should be in charge of the CCB process and that a responsible individual should be appointed for each volume of Doc 9880.