Draft Report as at Feb 3 - International Civil Aviation … WG-I 19/Draft Report of... · Web viewSecretariat draft State Letter asking for (i) support from personnel with IPS skills

Summary

This document is the ACP WG-I/19 Meeting Report.

ACP WG-I/19MEETING REPORT

20-22 January 2016

AERONAUTICAL COMMUNICATIONS PANEL (ACP)

WG-I – Internet Protocol Suite – 19th Meeting

Montreal, Canada, 20th - 22th January 2016

Report of ACP WG-I/19 Meeting

Presented by the Rapporteur and the Secretary

Report of ACP, WG-I/19 Meeting(Montreal, 20-22 January, 2016)

Table of Contents

AGENDA ITEM 1: MEETING ORGANIZATIONAL ISSUES.........................................3

AGENDA ITEM 2: APPROVAL OF THE AGENDA AND REVIEW OF WG-I/18 MEETING REPORT...........................................................................................................3

AGENDA ITEM 3: REVIEW OF ACTION ITEMS AND ITEMS FOR FOLLOW-UP. 3

AGENDA ITEM 4: COMPLETION/EVOLUTION OF THE ATN/IPS WORK..............6

Agenda Item 4.1: IPS Implementation Guidance Development.......................................7Agenda Item 4.2: IPS Security.............................................................................................8Agenda Item 4.4: Mobility.................................................................................................10Agenda Item 4.8: Integration with other Systems...........................................................13

AGENDA ITEM 7: A/G SECURITY STANDARDS UPDATES/ SDS SUB-GROUP REPORT.............................................................................................................................14

AGENDA ITEM 8: ANY OTHER BUSINESS....................................................................14

AGENDA ITEM 9: NEXT MEETING.................................................................................14

APPENDIX A - ACP WG-I AGENDA.................................................................................15

APPENDIX B - LIST OF ATTENDEES..............................................................................16

APPENDIX C – TABLE OF NEW ACTION ITEMS FROM WG-I/18...........................17

APPENDIX D – TABLE OF WORKING AND INFORMATION PAPERS...................18

document.docx Page2


AGENDA ITEM 1: MEETING ORGANIZATIONAL ISSUES

1.1 The meeting was opened by the Rapporteur, Mr. Liviu Popescu who welcomed all participants to the meeting.

1.2 The meeting was attended by ## experts and the Panel Secretary, Mr. Vaughn Maiolla. The list of participants is in Appendix B of this report.

AGENDA ITEM 2: APPROVAL OF THE AGENDA AND REVIEW OF WG-I/18 MEETING REPORT

2.1 A draft agenda was presented by the Rapporteur, who then explained the allocation of Working/Information Papers to the agenda items. The agenda and order of proceedings were accepted by the meeting. The agenda and allocation of WPs/IPs is given in Appendix A of this report. A list of all WPs is given in Appendix D. Discussion was limited to those items for which papers had been submitted. Hence items 4.3, 4.6, 4.7 5 and 6 were not covered.

AGENDA ITEM 3: REVIEW OF ACTION ITEMS AND ITEMS FOR FOLLOW-UP

Action items were not dealt with as a single discussion item. The following table has been updated based on relevant discussion under other agenda items.

Action Item

Description Status

13-8 ICAO Secretariat will work to obtain IPV6 address blocks for the Regions. – Still in progress.

Efforts on-going to obtain necessary resources.

OPEN – In progress.

14-4: Secretariat draft State Letter asking for (i) support from personnel with IPS skills and (ii) an extension to the schedule for the work programme based on the various reasons given above. In order to be effective State Letter must ask for experts to be nominated by name with details of expertise.

Letter not distributed as funding to make use of personnel not yet available. Secondee with the skills being sought now.

OPEN – In progress as at Jan. 2016

14-5: ICAO to develop a justification for a /16 address block and make an application to ARIN or IANA based on expediency.

As above.

OPEN

14-6: Hoang Tran to draft guidance material for Doc 9896 on IPV4-IPV6 transition.

OPEN

14- 8: ICAO to apply for new TLD and draft appropriate guidance material on the allocation of lower level domain names.

As per 13-8, 14-4, 14-5

OPEN

16-2: Hoang Tran to update the contents of WP04 (IPV6 OPEN

document.docx Page3


Action Item

Description Status

Implementation Issues for Fixed Network) and provide more details in the next WG-I/18 meeting.See link: http://www.icao.int/safety/acp/ACPWGF/ACP-WG-I-16/ACP%20WG%20I-6%20WP04%20Network%20Planning.doc

16-4: Focal points to list existing implementation guidance documents available at regional level and to report them to the next WG-I meeting.

OPEN

17-1 Secretary to have the ACP web-site modified to provide a protected area for sensitive documents.

CLOSED and superseded by Action 18-1

17-3 All members to provide comments on the questions raised by IP01 (SWIM concept of operation and implementation) and also provide any concerns that they may have. These will be forwarded to the Secretary of the ATMRPP and the newly-formed Information Panel by the Secretary (ACP).

CLOSED and superseded by action to form joint-group.

18-1: Secretary to transfer CP web-site to sharepoint, in which case it would be wholly secure.

OPEN – In progress

18-2: WG-I members to provide feedback by the end of July, on ATN/IPS Job Card, especially with respect to key items for inclusion.

CLOSED – job card now approved.

18-3: WG-I to consider unambiguous terminology for applications and communications media.

OPEN

18-4: WG-I to consider network (i.e. OSI/IPS) transition issues, with emphasis on ground-based solutions to accommodate different aircraft architectures. These will be developed for consideration by the CP, who many need to consider institutional issues also.

18-5: Secretary to work with Terry Davis to prepared a “strawman” discussion paper dealing with the above. Through Web Meetings and other means, WG-I will determine the best way to deal with these. The resulting plan would then be given to the CP for consideration.

OPEN

18-6: WG-I to appoint a sub-group to review internet standards and propose a suitable set of Internet standards to meet the needs of civil aviation.

OPEN

18-7: WG-I to elaborate upon the impact of multi-homing on network mobility in Doc 9896.

OPEN

18-8: Secretary to incorporate the proposed changes given in WP11 in a log of proposed changes for consideration in the Edition 3 of Doc 9896. (Note: this may be published as early as end-2016)

CLOSED – WP12

document.docx Page4


Action Item

Description Status

submitted

18-9: WG-I to consider the following actions. Update the mobility specification in Doc 9896 to the

current RFC 6275, Remove the restrictions on MIPv6 Route Optimization and

explore additional techniques to improve the robustness, routing table updates and routing efficiency

Develop and publish profiles for use of the internet standards specified in the IPS manual (or as alternate, encourage non-ICAO groups such as RTCA or EUROCAE to standardize some of the options listed in the IPS manual,

Consider different IPv6 addressing structure and address discovery mechanisms to permit simultaneous multilink operations over multiple IP air/ground networks offered by separate MSPs,

Develop requirements for mobility and multi-link, and Consider the list of alternatives described in this paper to

develop standards to address the deficiencies in the existing IPS Manual.

OPEN – to be incorporated into

18-10: Secretary to forward SWIM CONOPS to WG-I. CLOSED – WP## describes this and CONOPS posted on web-site.

18-11: Secretary to maintain a log of options/issues raised during meetings for further discussion if needed. This action will apply to all WPs/IPs presented during WG-I/18.

CLOSED –WP12 submitted

18-12: Secretary to propose meeting dates in the Sept/October timeframe. One of the objectives of this meeting would be to determine methods to resolve the issues raised in the (options/issues) log.

CLOSED – meeting held Jan 2016

18-13: Secretary to inform the CP of the decision to make the SDS SG a sub-group of WG-I.

CLOSED – done at CWG/1

document.docx Page5


AGENDA ITEM 4: COMPLETION/EVOLUTION OF THE ATN/IPS WORK

4.1 Liviu Popescu presented WP03 – WG-I IPS Work Programme. This paper began by introducing the final work programme items, developed at CP/1 and refined by the Communication Panel CWG at their first meeting, which were then allocated to WG-I.

4.2 WP03 then proposed the formation of two sub-groups (to WG-I) and provided a justification. The two sub-groups are to be as follows; an IPS Security sub-group and an IPS Mobility sub-group.

4.3 On the IPS Security sub-group, WP03 proposed that all SDS-SG tasks will be incorporated into the IPS Security SG. The scope of the IPS Security SG will be enlarged to cover all IPS Security, without affecting the current SDS SG agreed list of deliverables and activities timeline. As a result, the IPS Security SG would also work on a security technical framework and the material required for the coordination on security policy and security operational issues with the other Panels (AVSEC, RPASP, IMP).

4.4 On the IPS Mobility sub-group, it was explained that at WG-I/18 there were five action items related to mobility and multilink operation, that need to be addressed in Doc 9896 Ed. 3. It was proposed that this group be established with priority and commence coordination with industry groups also working on ATN/IPS standards.

4.5 It was further proposed that these sub-groups, work and meet as needed making used of web-meetings and face-to-face meetings when justified and report to WG-I. WG-I in addition would continue working on the other aspects of ATN/IPS development identified in the work programme. The proposal was supported by the group.

4.6 Vic Patel was identified as the Rapporteur for the IPS Security sub-group however a Rapporteur for the IPS Mobility sub-group was needed. The (WG-I) Rapporteur asked the group to consider nominations for the IPS Mobility sub-group Rapporteur.

ACTION ITEM 19-1: WG-I members consider nominations for the IPS Mobility sub-group Rapporteur.

4.7 The Secretary presented WP04 – Log of Proposals. This working paper was developed in response to an action item from WG-I/18. The meeting was asked to consider the Working Paper and identify errors, shortcomings and improvements.

4.8 The Rapporteur then presented a spreadsheet, which provided a suitable way to record proposals and their disposition as well as the status of all action items and other tasks. It was agreed by the group that this would be a suitable template for providing traceability of the WG’s activities. This spreadsheet has become IP03. This spreadsheet contains:

working /information paper references;

document.docx Page6


identified work program items;

related actions assigned to members;

proposals for future integration into Doc 9896 Ed. 3.

The Secretary was tasked with populating this spreadsheet based on this and past meetings. This resulted in the following action item.

ACTION ITEM 19-2: Secretary to populate the spreadsheet of tasks related to the development of the ATN/IPS. This would include deliverables assigned to members and proposals for future consideration.

4.9 Greg Saccone presented IP-4, AEEC IPS Update. The AEEC had voted on and approved an ARINC Project Initiation/Modification (APIM) in September 2015 that was tasked with developing an ARINC project paper for IPS for Aeronautical Safety Services. This will include producing an industry roadmap and a development plan for defining IPS for Aeronautical Safety Services, including airborne, ground-based and space-based communication systems, coordinating with aviation Standards Development Organizations (SDOs), Air Navigation Service Providers (ANSPs) and others with an interest. This will be done in two steps:

Step 1: Develop a roadmap document and development plan, scheduled completion Apr 2017

Step 2: Execute the development plan and produce ARINC Project Paper 8XX, Internet Protocol Suite (IPS) for Aeronautical Safety Services, anticipated completion Apr 2019

4.10 The group will be co-chaired by Airbus (Luc Emberger) and Boeing (Greg Saccone), with participation from Airtel ATN, GE Aviation, Honeywell, Rockwell Collins, Thales, ARINC (RC-IMS), FAA, SITA, Inmarsat, Panasonic and others. The kickoff meeting for the group was held on December 10, 2015 and the first face-face meeting is scheduled to be at RTCA in Washington DC on 23-25 February. The group intends to define its scope, to identify deployment roadmaps and how those coincide with the IPS solution, and examine aircraft and ground system architectures and requirements. Coordination with other industry groups must also be maintained in order to ensure no overlap or conflicts in specifications. A first draft of the report is expected by Q42016.

4.11 The notional schedule was given for Step 1, including high-level detail of the first steps. The meeting was invited to note the information, and encouraged to attend the first meeting in February and bring whitepapers describing areas of interest and considerations for the IPS roadmap and development plan.

ACTION ITEM 19-3: WG-I members consider attending AEEC February meeting and contribute to development of IPS roadmap and development plan.

Agenda Item 4.1: IPS Implementation Guidance Development

document.docx Page7


4.12 Mike Olive presented IP01 - IPS over VDL Mode-2 Feasibility Demonstration, this described a series of test performed to test the feasibility of transporting IPS packets over VDL Mode-2. This test was a collaborative effort between Honeywell, Boeing and SITA with each providing facilities and equipment.

4.13 The salient points from this were as follows: The test involved LINK2000 applications (CM and CPDLC) supported by the IPS

dialogue service. The IPS stack had been adapted to use VDL Mode 2. Tests did not include addressing, mobility/handovers (as only one ground station

was used) or security. Tests were done using a connectionless, broadcast mode for downlinks. Tests only used IPV4. Laboratory and live communication environments were used. The avionics equipment used was a B737 avionics test bench using production

equipment.

4.14 It was also pointed out that the objective of the tests was simply to prove functional feasibility and that performance was not evaluated. Of interest was the fact that the tests used the Boeing Cert. Plan testing script.

4.15 The adaptation to make IPS compatible with VDL Mode 2, was to use a “protocol identifier” to advertise that the VHF ground station supports IPS. This was in compliance with ISO 9577. It is worth mentioning that IP05, IPS over VDL (FAA), which focussed on IPS Mobility and is hence dealt with under Agenda Item 4.4, also proposed the use of the same AVLC protocol extensions.

4.16 Given the protocol overheads expected, Datagram service with unnumbered frames was used, which is supported by the VDL Mode 2 standards. This would allow broadcast mode to be used in a live environment. This may have the benefit of improved communications reliability and may be investigated further.

4.17 Additional functional test cases are anticipated including:

Message size boundary conditions. Packet loss simulations Message retransmission Link loss and recovery.

4.18 Flight tests are planned for later in 2016.

Agenda Item 4.2: IPS Security

4.19 The Rapporteur presented IP02 – IPS Security Guidance. This paper did two things, a) it presented a list of current and planned documents related to IPS Security and b) it raised a number of assumptions/questions to be answered in order to progress this work.

document.docx Page8


4.20 This paper made the point that, the PKI implementation may affect interoperability hence a strategy is needed for deployment.

4.21 The bibliography of IPS Security documents covered a number of key areas; AMHS, EDS, VOIP, SDS, FCI and a number of operational concepts. The latter related to the handling of cyber-security events and the response to them and also the efficient management of PKIs. On VOIP security, the WG was advised that the EUROCONTROL VoIP Implementation Support (VOTE) group is soon to begin work on this with completion expected in approx. 18 months. FCI security was addressed by SESAR P 15.2.4 and project related deliverables are expected to become available to WG-I.

4.22 CP Work Programme Item 8 (Job-Card CP007.001 WG-S/I/T) calls for the development of a security technical framework identifying policy issues by the end of 2016. Taking into account the close deadline, in order to initiate the work in this direction the minimum set of assumptions/questions raised by this paper, were as follow;

a) is PKI the agreed security solution?;

b) if so, do we need a global architecture? and

c) if so, who will address the implementation requirements?;

d) what elements need coordination with other Panels and

e) who will be the responsible authority?

4.23 The meeting discussed the issues raised. The following points were made:

PKI is the agreed technical security solution for safety critical applications.

The Global Policy Authority is needed. ICAO can fulfil this role.

A global PKI architecture should consider an integration of local, regional and bridge based technical solutions able to provide the appropriate liability.

There will most likely be a two-tiered solution, ie: with regional and local certificate authorities. Hence there would be a hierarchy.

4.24 WP10 – PKI Management Considerations was presented by the Secretary. This paper described use of a central server to the support the cross-certification of PKIs. It was requested that any provisions (such as those, taken from Doc 9705 Ed. 3to be used in Doc 9896) be amended, so that an integrated approach was not precluded.

4.25 It was proposed that to effectively analyse the advantages and disadvantages of the options for local, regional and global PKI support, a series of block diagrams showing each scenario would be needed. It was agreed that these would be discussed at the scheduled May meeting. This led to an action item:

ACTION ITEM 19-4: All WG-I members to consider block diagrams dealing with PKI management scenarios and bring these to WG-I/21 (May 16-20).

document.docx Page9


4.26 The role of the AVSEC Panel was raised without conclusion. Although the Secretary expressed doubts about their ability to initiate this work, they would be responsible for high level policy development. In effect, acting as a PKI “Policy Authority”. This led to the following action item:

ACTION ITEM 19-5: Secretary to obtain the TORs for the AVSECP and make available to WG-I.

4.27 The Secretary presented WP5 – WiMAX Certificate Requirements. This paper provided a list of subscriber (certificate requester) requirements from the AeroMACS PKI Certificate Policy developed by the WiMAX Forum Aviation Working Group. It was futher explained that this paper was a follow on to the proposed PKI policy presented by the WiMAX Forum at WG-I/18.

4.28 The group was asked to consider these requirements. This paper generated significant discussion regarding the role of the WiMAX Forum Aviation Working Group. Although the Secretary stressed that the PKI policy to be adopted for AeroMACS would be decided by WG-I and WG-S, there were still concerns, hence two courses of action were agreed:

The secretary would find out more about the role of the WiMAX AWG and report to WG-I.

WG-S and WG-I would have a joint meeting on this at their next meeting. .

This led to the following action items:

ACTION ITEM 19-6: Secretary to report to WG-I on the role of the WiMAX AWG.

ACTION ITEM 19-7: Secretary to coordinate a joint meeting between WG-S and WG-I during the Feb. – Mar. meeting. Most likely on Wednesday.

Agenda Item 4.4: Mobility

4.29 Three papers on this subject were presented beginning with IP05 – VDL-2 for the ATN/IPS, presented by Tom McParland.

4.30 IP05 first proposed a framework for the ATN/IPS Mobile Network Architecture. The proposed framework consists of terrestrial and satellite based air/ground access networks connected to the ATN/IPS internetwork. For terrestrial air/ground access networks it is proposed that an air/ground access network be partitioned into one or more air/ground access sub-networks which may be operated by the same or different Air/Ground Communications Service Providers (ACSPs).

4.31 Mr. McParland explained that the terrestrial air/ground network architecture is modeled after the WiMAX network architecture where a Connectivity Service Network (CSN) may contract with multiple Access Service Network (ASN) providers.

4.32 IP05 next gave a description of Proxy Mobile IPv6 (PMIPv6). The motivation for PMIPv6 was to offload mobility from the aircraft to the network. Mr. McParland noted that PMIPv6 is now a Standards Tracked RFC and has become a part of both WiMAX and LTE standards.

document.docx Page10


4.33 Next a description of the VDL-2 extensions needed for to allow the AVLC protocol to carry IP traffic was provided. Mr. McParland noted that the VDL-2 frame extensions to AVLC were the same as those presented in IP 01 however, in this paper AVLC is connection-oriented and handoff is performed by the aircraft. Mr. McParland noted that having handoff across different access sub-networks appeared to be simpler than exchanging information between different provider ground stations to support ground controlled handover.

4.34 Mr. McParland next described the interaction between the extended AVLC and PMIPv6 as an instance of the ATN/IPS Mobile Network Architecture.

4.35 Mr. McParland described the ongoing investigation into multilink operation over multiple air/ground access networks. He stated that given the SDS/IP Dialogue Service support for different types of applications, he believed that multilink operation should be below this level. The investigation into several candidate protocols including Host Identity Protocol, SHIM 6, SCTP, and MultiPath TCP, was described. Of these MutiPath TCP was the most promising. It was noted that this mobility protocol only supported mobile hosts and not mobile networks. Mr. McParland noted that the use of TCP made this proposal different to what was described in IP01.

4.36 It was commented that in the interest of simpler avionics design and support, network mobility should be ground-based, as supported by this and other proposals. This prompted the comment that an ATN/IPS Mobile Network Architecture supporting this approach would be beneficial.

4.37 Bernhard Haindl commented that investigation had shown that PMIPv6 did not support NEMO. Hence PMIPv6 would only support aircraft hosts and not networks. The response to this was that the IETF PMIPv6 group was investigating extending PMIPv6 to NEMO. Many in the meeting commented that it was not clear that aircraft networks, as supported by NEMO, were required.

4.38 Bernhard Haindl then presented WP07 – Ground-Based LISP for Multilink Operations. This paper provided an IPv6 mobility and multi-link solution defined in SESAR project P15.02.04. It is based on LISP with the goal of minimizing the complexity in the aircraft and the overhead in the A/G datalinks. This solution proposes a ground based solution, where all the routing and mobility functionalities are only required in the ground network. Hence it is fully transparent to all end systems and aircraft complexity is reduced.

4.39 The paper provided the high level system architecture of the FCI and described the different elements of Ground based LISP Mobility concept and how they interact in the different base station procedures like, registration, location announcement, and end-to-end connectivity. Selected multilink scenarios showing the communication from an ATS end system on ground to an end system on the aircraft network were also provided.

4.40 Other salient points from the presentation were as follows:

LISP was one of two candidate IP mobility protocols still under consideration by SESAR project 15.2.4. The other being NEMO.

LISP can accommodate the ICAO 24-bit address. In accordance with Doc 9896 LISP minimizes the overhead traffic on the A/G datalinks through;

o No encapsulation overhead on the A/G linko No routing or mobility overhead on the A/G link



o Location announcement only when the aircraft leaves/enters the access network

LISP takes into account QOS for path selection. LISP uses a “pull” model and hence provides scalability. LISP provides better multilink handling than NEMO. It can be provided over existing infrastructure and will ease IPV4 to IPV6 transition. It is also based on COTS solutions.

4.41 Furthermore LISP could support airborne hosts and networks. Static routing was shown in the examples given in WP7. Dynamic routing could also be hosted on the aircraft however this could also affect the air-ground link as there would be additional communication to support the exchange of routing information.

4.42 As there were a range of mobility solutions available, each with advantages, the question was raised as to whether a single choice should be made and if so, how???

4.43 It was pointed out that further choices were available, as Boeing was working on Asymmetric Extended Route Optimisation (AERO). Greg Saccone offered to provide a paper on this at the next meeting of WG-I.

ACTION ITEM 19-8: Greg Saccone to provide a paper on Asymmetric Extended Route Optimisation (AERO) at the WG-I/20.

4.44 Stephane Tamalet proposed that the process of selecting a mobility solution should begin with a set of high level requirements.

4.45 This generated significant discussion as the method for determining such requirements was not clear. Among the options discussed were, i) ATM-related projects and ii) consultation with Panels.

4.46 The point was re-iterated that minimizing the impact on the aircraft should clearly be a requirement.

4.47 Stephane Tamalet then pointed at that as many of the mobility solutions were still to be fully validated, it would be wise to consider a number of candidate solutions until validation was complete.

4.48 Liviu Popescu then proposed the following approach, which was accepted by the group:

WG-I should identify potential solutions, using the results of various studies as guidance.

To make an evaluation based on proposed solutions starting with the available material, eg: SESAR Project 15.2.4. outcomes (this example does not cover all candidate solutions) .

Develop high-level requirements in collaboration with ICAO operational panels.

The IPS Mobility sub-group should evaluate these using a methodology, which includes; the high-level requirements complemented by functional and performance-



based technical requirements; security requirements and others as agreed. (Development of the selection methodology to be within the scope of the IPS mobility sub-group)

4.49 WP12 – Mobility Issues observed during the ESA Antares Project was presented by Bernhard Haindl. This paper summarized the issues raised in WP8, WP9 and WP13. Overall these papers described activities within the (ESA) Iris program, which is aimed at designing a new A/G data link as a part of the Future Radio System (FRS). In the course of the design exercise, some issues have been identified that could be traced-back to the ICAO ATN/IPS Manual Ed.1.0. ESA recently tasked FREQUENTIS to compile these issues. Fourteen issues were identified and these were grouped according to the following:

Address Auto-Configuration Issues IPv6 Transport Layer and QoS Issues VoIP, Security and Robust Header Compression (ROHC) Issues

4.50 Although WP12 did suggest appropriate action to resolve these, these were not specific enough to be considered proposals for document amendments. In response to a request for these, the point was made that the issues required discussion by WG-I and certain actions such as a safety analysis, before a decision could be made and that many of the comments were specific to solutions currently under consideration for the ATN/IPS.

4.51 In response to this, the following action item was allocated:

ACTION ITEM 19-9: Bernhard Haindl to indicate protocol/solution specific shortcomings Identified in WP 12.

Agenda Item 4.8: Integration with other Systems.

4.52 The Secretary presented WP11 – Integration with SWIM. This paper presented the SWIM Interoperability Framework from the SWIM Concept document. It further asked the WG-I form a task force to coordinate with the Information Management Panel (IMP), to ensure the interoperability between SWIM and the ATN and also explore possibilities to simplify or streamline the framework.

4.53 In the ensuing discussion a number of points were made mainly considering transition towards the SWIM environment. It was pointed out that the supported SWIM (application) systems could have a significant impact over the deployed IP networks and other supported applications (eg: AMHS, VOIP), hence it would be important to identify these. Of special interest was the advent of air-ground SWIM, especially as each Region could have different expectations in terms of its use and capability.

4.54 The importance or early coordination was clearly recognised and this led to an action item.

ACTION ITEM 19-10: Secretary to make contents of SWIM Concept document available.

ACTION ITEM 19-11: WG-I members to consider nominations for a joint sub-group to work with the IMP on SWIM integration with the ATN/IPS



AGENDA ITEM 7: A/G SECURITY STANDARDS UPDATES/ SDS SUB-GROUP REPORT

7.1 Vic Patel presented WP14 – Report of SDS SG Meeting No. 4. This report was well received and understood by the group. The points raised reinforced the need for a joint meeting on security with WG-S as covered by Action Item 19-7.

AGENDA ITEM 8: ANY OTHER BUSINESS.

8.1 The Secretary presented IP06 and IP07, the latter provided details of the working method to be employed by the Data Communication Infrastructure Working Group (DCIWG) to be made up of former ACP members and the Operational Datalink Working Group (OPDLWG) to be made up of former OPLINKP members. Members of both groups would be eligible to become members of the Communication Panel which would among other things approve the work programme, approve and monitor joint (DCIWG and OPDLWG) activities and generally review the work of the DCIWG and OPDLWG.

8.2 It was further explained that the DCIWG could report directly to the ANC on purely technical issues, while the OPDLWG could report directly to the ANC on purely operational issues. It was further explained that the full “Panel” would most likely meet every two years to coincide with the (ANC) amendment cycle in order to approve Annex Amendments and amended/new Manuals.

8.3 IP06 provided details of the DCIWG work programme and “joint” activities. Of the former only a few key items such as ATN/IPS and cyber-security had job cards at this time. The other items, such as the development of the future terrestrial communication system (LDACS) were prospective at this time, however job cards were expected to be approved following the next “full” CP meeting scheduled in October.

8.4 The DCIWG and “joint” activities had been presented to and agreed by the OPDLWG at their last meeting in Langen, Germany, held in October 2015.

AGENDA ITEM 9: NEXT MEETING

9.1 WG-I/20 will be held 2 – 4 March, 2016 following WG-S/9 which will be held 29 Feb – 2 March, 2016. As with past practice, all WG-S and WG-I members are invited to attend both meetings.



APPENDIX A - ACP WG-I AGENDA

AERONAUTICAL COMMUNICATIONS PANEL (ACP)

NINETHEENTH MEETING OF WORKING GROUP - IMontreal, Canada 20 – 22 January, 2016

WG-I Proposed Agenda:

1. Meeting Organisational Issues

2. Approval of the Agenda & Review of WG-I/18 Meeting Report

3. Review of Action Items and Items for Follow-Up.

4. Completion/evolution of the ATN/IPS work (both for air/ground and ground/ground segments) -

Work Programme Items (CP-2 outcome) (WP03, WP04, IP04)

4.1. IPS implementation guidance development (IP1)

4.2. IPS security (IP2, WP5, WP10, IP6)

4.3. DNS

4.4. Mobility (WP6, IP4, IP7)

4.5. Naming and Addressing (IP08)

4.6. Consideration of transition aspects from existing/legacy systems (IPS – OSI transition)

4.7. Configuration Management

4.8. Integration with different systems (WP11)

4.9. QOS, COS issues (IP05)

5. IPv6 implementation papers (Mobile and Fixed)

6. Regional IP implementations (input from ICAO regional secretariats)

7. A/G security standards updates/ SDS sub-group report (Review of SDS meeting report) (WP14)

8. Any Other Business (IP06, IP07)

9. Next meeting


APPENDIX B - LIST OF ATTENDEES

ACP WG-I/18 – Montreal, Canada: 24th – 25th June 2015

LIST OF ATTENDEES

Name Organization Name E-mail Address

States

Jean-Marc Vacher Regis (DGAC) [email protected]

Frederic Picard THALES (on behalf of DSNA/DTI). [email protected]

Michel Solery DSNA/DTI [email protected]

Santi Ibarz AIRTEL [email protected]

Madhu Niraula Rockwell-Collins [email protected]

Brent W. Phillips FAA [email protected]

Vidyut Patel FAA [email protected]

Joe Knecht FAA [email protected]

Tom McParland BCI [email protected]

Aloke Roy Honeywell [email protected]

Mike Olive Honeywell [email protected]

International Organisations

Liviu Popescu EUROCONTROL [email protected]

Noppadol Pringvanich IATA [email protected]

Vaughn Maiolla ICAO [email protected]

Stephane Tamalet ICCAIA (Airbus) [email protected]

Greg Saccone ICCAIA (Boeing) [email protected]

Bernhard Haindl ESA (Frequentis) [email protected]

REMOTE ATTENDEES

17 participants

Page 16 of 19

APPENDIX C – TABLE OF NEW ACTION ITEMS FROM WG-I/18

Action Item

Description Status

19-1 WG-I members consider nominations for the IPS Mobility sub-group Rapporteur.

Open

19-2 Secretary to populate the spreadsheet of tasks related to the development of the ATN/IPS. This would include deliverables assigned to members and proposals for future consideration.

Open

19-3 WG-I members consider attending AEEC February meeting and contribute to development of IPS roadmap and development plan.

Open

19-4 All WG-I members to consider block diagrams dealing with PKI management scenarios and bring these to WG-I/21 (May 16-20).

Open

19-5 Secretary to obtain the TORs for the AVSECP and make available to WG-I.

Open

19-6 Secretary to report to WG-I on the role of the WiMAX AWG. Open

19-7 Secretary to coordinate a joint meeting between WG-S and WG-I during the Feb. – Mar. meeting. Most likely on Wednesday.

Open

19-8 Greg Saccone to provide a paper on Asymmetric Extended Route Optimisation (AERO) at the WG-I/20.

Open

19-9 Bernhard Haindl to indicate protocol/solution specific shortcomings Identified in WP 12.

Open

19-10 Secretary to make contents of SWIM Concept document available. Open

19-11 WG-I members to consider nominations for a joint sub-group to work with the IMP on SWIM integration with the ATN/IPS.

Open

Page 17 of 19

APPENDIX D – TABLE OF WORKING AND INFORMATION PAPERS

WP Title Contributor

1 SDS SG/4 - Proposed Agenda Rapporteur/Secretary

2 Meeting Logistics Secretary

3 WG-I Work Programme Rapporteur

4 Log of Proposals Secretary

6 Ground-Based LISP Frequentis on behalf of ESA

7 Ground-Based LISP for Multilink Operations Frequentis on behalf of ESA

8 IPV6 Transport Layer and QOS Issues Frequentis on behalf of ESA

9 VoIP, Security and ROHC Issues defined in Doc. 9896Frequentis on behalf of

ESA

10 PKI Management Considerations Secretary

11 Integration with SWIM Secretary

12 Mobility Issues identified during ANTARES Project Frequentis on behalf of ESA

13 IPv6 Auto-Configuration Issues Frequentis on behalf of ESA

14 SDS SG/4 Draft Report Rapporteur/Secretary

IP Title Contributor

1 IPv6 over VDL Mode 2 Testing Honeywell

2 IPS Security Status Rapporteur

3 IPS Repository Template Rapporteur

4 AEEC IPS Update Boeing on behalf of ICCAIA

5 IPS over VDL BCI on behalf of FAA

6 Current and Proposed Panel Work Programme Secretary

Page 18 of 19

WP Title Contributor

7 Working Arrangement for merged ACP and OPLINKP Secretary

Misc. Title Contributor

1 Manual of the SWIM Operational Concept IMP

Page 19 of 19

Documents

Draft Report as at Feb 3 - International Civil Aviation … WG-I 19/Draft Report of... · Web viewSecretariat draft State Letter asking for (i) support from personnel with IPS skills