International Civil Aviation Organization
ACPWGW03/AI-5
2010-01-22
REPORT
AERONAUTICAL COMMUNICATIONS PANEL (ACP)
WORKING GROUP OF THE WHOLE
THIRD MEETING
Montreal, 18 to 22 January 2010
REPORT OF THE THIRD MEETING
5.
AGENDA ITEM 5:
FUTURE WORK
5.1
Introduction
5.1.1
#3 and #11.
Under this agenda item, the meeting reviewed WPs #2, #3, #8, #11 and #12 as well as IPs
5.1.2
WP#2 discusses long term frequency spectrum planning considerations, WP#8 discusses
necessary updates to the ICAO provisions on VDL Mode 4, WP#11 and IP#11 discuss the status and
completion of Doc 9880 and IP#3 gives an update on the Wireless Aircraft Intra-Communications
(WAIC) study.
5.1.3
Updates to the ACP Work Programme are captured under the discussion on WP#3. The
agreed updates to the work program of individual working groups are captured in Attachment A and the
updates to the work program of the Panel as a whole are captured in Attachment B.
5.2
Status and completion of Doc 9880 the ATN/OSI manual
5.2.1
IP#11 was presented by the Secretary, providing a summary status of the various chapters
of Document 9705, which chapters have been tagged for update and transfer to Doc 9880, which chapters
have been tagged for deletion and which chapters have already been transferred. The secretary clarified
that the following parts of Doc 9880 have already been finalized, approved by the Secretary General, and
pending final editing and publication, published on the ICAO-NET.

Part I
(10 pages)
684077409
Air-Ground Applications

Part IIA

Part IIB

Part III

Part IVA
Ground-Ground Applications ATS Interfacility Data
Communications (AIDC)
Ground-Ground Applications ATS Message Handling Service
(ATSMHS)
Internet Communication Service, Including Upper Layer
Communications Service
Directory Services
5.2.1.1
It was clarified that the above parts, have already been approved in principle by the
Secretary General, and that this material can be considered stable. The editorial process the document is
undergoing, while it may change paragraph numbering and rectify editorial errors such as erroneous
references, it will, in principle, not touch the technical content of the document. Therefore, the document
in its already approved but pre-published state, should be sufficiently mature for use.
5.2.1.2
Mr. Nikos Fistas added to the information given in IP11 by mentioning that Part IV –
Security and Part C – Registration were still not available. In addition to this, Part III was incomplete as
Chapter 3 was also not available.
5.2.1.3
WP#11, presented by Mr. Jean Yves Piram, highlights the urgency to complete the work
on Doc 9880. During the presentation it was noted that the program, as presented in IP#11, and with the
additional clarifications on the current status of the completed parts of Doc 9880, is on-track. In addition
the following issues were also highlighted:
1)
Decision on how to proceed for completion/referencing of technical specifications for
A/G applications in “Protected Mode”, including PM-FIS and PM-ADS.
2)
Decision on publication or withdrawal of Part IIA (AIDC).
5.2.1.4
As per item 1), the meeting referred further discussions on this item to the next meeting
of ACP WG-M. On item 2), the meeting noted that WG-M has already identified Part IIA for potential
deletion, as it has been strongly indicated that the AIDC implementation method as originally described in
Doc 9705 and later transferred into Part IIA of Doc 9880 is not compatible with the AIDC messaging as
developed by the OPLINKP, and that current or planned implementations will not make use of this
method. The ACP WG-W agreed that Part IIA should be withdrawn.
5.3
Long Term Frequency Spectrum Considerations
5.3.1
WP#2, presented by the Secretary, discusses the current ICAO Strategy for establishing
and promoting the ICAO position for future ITU World Radiocommunication Conferences, and the
potential need for a far ranging long term Frequency Spectrum Strategy for aviation.
5.3.1.1
The current long-term ICAO Strategy for establishing and promoting the ICAO position
for future ITU World Radiocommunication Conferences (WRC) was developed by the Air Navigation
Commission, approved by Council and included in the third edition of the Frequency Spectrum Handbook
(Doc 9718) in 2003. This strategy, assisted by the Assembly Resolution A36-25 (2007), provides the
basis for the ICAO Position, guidance for the development of the ICAO Position and guidance for the
promotion of the ICAO Position. The strategy also defines the development and maintenance of the
ICAO policy on all radio frequency spectrum requirements, a policy which has official status as it is
approved by Council. The policy is contained in Appendix E to the Handbook on Radio Frequency
Spectrum Requirements (Doc 9718).
5.3.1.1.1
To date, this strategy has served aviation well and seems to provide sufficient leverage in
the WRC-12 process for aviation, given that Aviation Authorities and Industry take heed of the recent
updates (2007) made to the Assembly Resolution A36-25, and ensure that their voice be heard in the
process of their States’ Frequency Spectrum Authorities’ actions to develop their National and Regional
Position for the upcoming WRC.
5.3.1.2
On the other hand, in order to develop a long term (25+ years) spectrum strategy, a long
term CNS equipage strategy and technology roadmap would need to be available in accurate detail. Over
the last decades experience has shown that CNS equipage strategies developed by aviation (such as those
laid out by the 10th and the 11th Air Navigation Conference), while useful to provide guidance and
direction to planning activities, tend to be fairly inaccurate as indicators of the actual outcome of States’
implementation activities. This is mainly due to the fact that airspace users and service providers are
driven primarily by short or immediate term operational and/or commercial requirements and need the
flexibility to meet such requirements in a dynamically changing environment.
5.3.1.2.1
A long term planning by aviation in a scenario where an uncertain future would be
mapped out in inaccurate detail, appears to be a distraction at best and a disadvantage at worst, as it may
ultimately be something that aviation is held accountable to. Furthermore, trying to predict or define a
CNS architecture for a period of decades may only serve to constrain aviation technology to
obsolescence, especially when considering the more tactical and opportunity oriented mode of other
services when seeking new allocations through the WRC
5.3.1.2.2
These considerations should not be interpreted as negating the need for constant vigilance
and/or potential further development of the ICAO spectrum strategy. Rather, they indicate that detailed
long-term equipage forecasts are not a sound basis for a spectrum strategy, given their inherent
unreliability, and that a higher-level approach should be selected instead.
5.3.1.3
Starting at WRC-2003 (No. 5.197A) and then at WRC-2007 (No. 5.197A, 5.327A,
5.444B), a number of ARNS bands were allocated to the AM(R)S as well under certain conditions. The
WRCs acknowledged (through the accompanying Resolutions) that ICAO could manage the introduction
of mixed services in the bands, as long as all the systems affected were ICAO standardized.
5.3.1.4
The paper suggests that the focus of any proposed long term strategy be placed on
leveraging and enhancing the flexibility inherent in the new “mixed” aeronautical allocations through
system design and planning.
5.3.2
In the discussion that ensued, the logistics of exploiting the recently granted flexibility in
the Aviation Spectrum were discussed. The main concerns voiced were:
5.4
1)
A cohesive CNS strategy is needed, to reduce rather than increase the number of systems
a modern aircraft has to carry. This strategy should be ATM requirements driven rather than
technology driven.
2)
Panels and Working Groups need to be aware that spectral efficiency is a general
requirement. Any new technologies need to be explored in the context of increased spectrum
efficiency, and steps need also to be taken to explore the possibility of recovering spectrum.
Update of ICAO Provisions for VDL Mode 4
5.4.1
WP#8 presented by Larry Johnsson requested WG-M to undertake work to update the
VDL Mode-4 SARPS and Manual. It was pointed out that this request could have been taken to WG-M
directly. Although this is technically correct, the Secretary expressed the view that it is helpful from a
planning perspective for new or revived tasks such as these, to be brought to the ACP and included in the
work programme. The point was made that the inclusion of items in the work programme would not
preclude working groups from dealing with issues being addressed to them as they arise, however SARPs
cannot be developed or maintained without expressly being part of the agreed work program of the panel.
5.5
Update on Wireless Aircraft Intra-Communications (WAIC)
5.5.1
IP#3 was presented by Marcella Ost, representing the Aerospace Vehicle System Institute
(AVSI). The presentation provided a status update on recent activities within ITU-R WP 5B and ACP
WG-F with regard to Wireless Avionics Intra-Communications (WAIC), requesting WG-W's continued
guidance on the subject, particularly in considering other relevant ICAO activities which may be required
for the development of these systems. In this regard, the issue of equipment certification was highlighted.
The view was expressed that ICAO could assist greatly by providing guidance on certification.
5.5.2
WAIC systems are expected to offer aircraft designers and operators unique opportunities
to improve flight safety and operational efficiency while reducing costs to the aviation industry. Work
related to WAIC is being conducted in close coordination among the AVSI membership, ICAO, the ITUR, as well as national and international organizations involved in aviation and radiocommunications.
5.5.3
WAIC systems will provide communications over short distances between points on a
single aircraft. In all cases communication is assumed to be part of a closed, exclusive network required
for operation of the aircraft. WAIC systems are not intended to provide communications, in any
direction, between points on an aircraft and another aircraft, terrestrial systems or satellites. Only safety
related applications are being contemplated for WAIC systems. That is, it is not anticipated that spectrum
utilized for WAIC systems will be used for non-safety-related aircraft applications such as in-flight
entertainment (IFE) communications or include communications with consumer devices, such as radio
local area network (RLAN) devices that are brought on board the aircraft by passengers.
5.5.4
One great concern with the use of WAIC is the need to streamline the certification
process. At the present time it is theoretically necessary to obtain certification approval and a radio
licence in order to support this capability in each state. This is clearly not practical for an aircraft system
with general application.
5.6
Future Guidance Material
5.6.1
WP12 was presented by the Secretary. This paper proposed that additional guidance
material be added to Doc 9896 to deal with transition and interfacing issues between OSI and IPS
implementations. It also pointed out that VDL Mode-2 is an OSI based system yet the upcoming airport
surface and satellite datalinks will be IP-based, hence some guidance on their co-existence would also be
needed. The paper went on to make this point that this material, if supplemented with information on
avionics equipage, could form the basis of a useful communications roadmap which could guide states in
their implementation decisions.
5.6.2
In the ensuing discussion, it was pointed out that the term “gateway” was too generic and
could cause confusion, especially since some of the solutions implemented (ie; dual-stacks) were not
necessarily gateways. This was noted by the secretary and an assurance given that this would be taken
into consideration when developing the guidance material.
5.6.3
The meeting endorsed the proposal and hence it will be added to the scope of the WG-M
work programme task – Implementation of ATN/IPS.
5.7
Future ACP Work Programme
5.7.1
The Secretary outlined a proposal, as contained in WP#3, to develop a new working
group to develop standards for the new Airport Surface datalink. It was explained that the proposed
working group, WG-S would rely as much as possible on existing material developed by industry
standards-making bodies. The anticipated work package would be fairly small, mainly consisting of
SARPs as needed to specify the necessary radio frequency characteristics to satisfy ITU-R requirements
and with appropriate references to industry standards. It was pointed out that although the work will be
dependent on the development of a Common Aviation Profile by RTCA SC-223 and EUROCAE WG-82,
which will take a number of months to prepare, it is still necessary to begin action to obtain approval for
the establishment of the new Working Group now. It was also mentioned that Airport Surface Datalink
was required by both the NextGen and SESAR programmes sometime in the 2014 timeframe, thus adding
more urgency to the need for standards development.

WG-M is expected to finalize the development of Document 9880 in the second quarter
of 2010, including the following identified work items:

Proposed Defect Reports (PDRs) for various aspects of AMHS will be compiled,
reviewed and changes made as required.


Provisions for PM-ADS-C and PM-FIS will be added.
The security provisions for ATN/OSI are undergoing validation and any resulting PDRs
will need to be incorporated into Doc 9880.
5.7.2
The meeting was advised that WG-M will continue work on Doc 9776 to accommodate
multi-frequency operations, a stated requirement of the LINK 2000+ and Data Com programmes. The
proposed inclusions to Doc 9776 will have undergone technical validation, thus providing confidence that
the amendments will be final. Once all of the provisions for multi-frequency operation have been
compiled, Edition 2 of Doc 9776 will be released.
5.7.3
The meeting was then advised that recent UAT developments have made it necessary to
reconvene the UAT Sub-Group which will work under WG-M. This group will compile a change package
for Doc 9861 with completion expected in mid-2010.
5.7.4
Given that the two validation initiatives (VDL Mode-2 and ATN/OSI Security) along
with the ongoing implementation of AMHS, will result in a high number of PDRs, the meeting was
advised that WG-M is considering methods to deal with these expeditiously. Among the proposals being
considered are (i) the use of the ICAO Regional Officers to collect PDRs as they are generated and (ii) the
re-establishment of the configuration control board (CCB). Both of these will allow PDRs to be dealt with
effectively between meetings. The Working Group meetings would then simply approve their inclusion in
the appropriate documents. Other work on Doc. 9896 includes an investigation into the need for DNS
Root Servers. Two proposals will be reviewed during 2010.
5.7.5
Regarding ATN/IPS it was explained that a number of implementation issues had been
brought to the attention of WG-I and that these will need to be addressed in order to ensure global
interoperability. These will most likely be incorporated into the Guidance Material section of Doc 9896.
The items are as follows:

Acquisition of a large IPV6 address allocation from the “Internet Corporation for
Assigned Names and Numbers”, (ICANN) to allow consistency in address allocation by ANSPs
and Regions.

Network Architecture Design Guidance for the IPS (IPv6) network, including regional
addressing assignment, subnet addressing, aircraft addressing, routing infrastructure, routing
protocol, network segmentations, regional interconnect designs, etc.

PKI and IPSec Implementation Guidance to insure that the key fields are formatted and
used consistently which is necessary for the interoperability of authentication and security
services between ANSP’s and regions.

The definition of a consistent Aircraft and Ground System Naming/Identity for PKI use
as the authentication identifier.

The definition of an Aircraft and Ground System IPS Domain Name System structure for
both the aircraft and ground systems. This should also include the required design guidance for
“ATN Root Name Server” infrastructure to be setup between the ANSPs.

IPS DNS Implementation Guidance for interfacing the “ATN Root Name Servers”, for
implementing DNSSec both within and between ANSPs, the creation of “service names”, and
IPv4/IPv6 resolution services.

IPv4 – IPv6 Transition Guidance to ensure that a minimal set of transition services are
supported to minimize interoperability and to ensure that supported transition services are
implemented similarly between ANSPs/regions.
5.7.6
The ACP WG-W discussed the proposals provided in WP#3 and developed updates to
the work program of the Panel as a whole and the individual working groups. The updates as captured in
Attachments B and Attachment A respectively, will now be subject to review by the Air Navigation
Commission. The Secretary will communicate any eventual amendments to the proposed work plan to
the ACP members.
APPENDIX A – PROPOSED UPDATE OF ACTIVITIES FOR ACP WORKING GROUPS
WORKING GROUP F (FREQUENCIES)
The terms of reference for the Working Group F (Frequency) concentrate on the preparatory activities for
the ITU world Radiocommunication Conference in 2012 as well as for relevant meetings of the ITU
Radiocommunication Sector (in particular ITU-R Study Group 4 and 5 and Working Parties 4C and 5B)
and those of the Regional Telecommunication Organizations.
This work programme is on track and
no amendments are proposed at this time. The main items of interest on the ITU WRC-2012 agenda are
agenda items 1.3 (Unmanned Aerial Systems (UAS)), 1.4 (AM(R)S) and 1.7 (AMS(R)S). However there
is a number of other items as well on the WRC-2012 agenda which may adversely affect access to
frequency spectrum by Civil Aviation. The ICAO Position contains detailed description of all WRC2012 agenda items of interest to aviation.
WORKING GROUP M (MAINTENANCE)
WG-M will take the necessary action to make the COSPAS/SARSAT Guard Bands between 121.4 and
121.6 MHz for the provision of air traffic control services. This shall include consultation with WG-F and
possible changes to Annex 10, Vol. V.
In consultation with WG-F review Annex 10 Vol. 5 and perform the following; remove time-limited
clauses which have passed their sunset date; remove other redundant text and add clarifying text where
required.
Review Annex 10 Vol. 3 in consultation with other panels and working groups if/as appropriate and
perform the following; remove time-limited clauses which have passed their sunset date; remove other
redundant text and add clarifying text where required.
Update document 9880 with the following:

Inclusion of requirements resulting from AMHS PDRs.

Provisions for PM-ADS-C and PM-FIS (subsequent to initial work to be done by RTCA SC-214
and WG-78).

Inclusion of requirements resulting from PDRs related to ATN/OSI Security Validation activities.
Continue with validation activities and when complete, incorporate all of the necessary provisions for
VDL Mode-2 support for multi-frequency operations into Edition 2 of Document 9776. (Input required
from RTCA and EURCAR to compile final provisions).
Based on changes to industry standards for UATs, the UAT Sub-Group will compile a change package
for Doc 9861.
On-going maintenance of SARPS and Manuals for VDL Mode 4.
WORKING GROUP I (IPS)
Finalise the provisions for VOIP in Doc 9896 and re-issue this document as Edition 2.
Evaluate options for the provision of DNS service with inclusion of chosen option in Doc. 9896.
Develop additional Guidance Material for ATN/IPS to ensure global interoperability. Work to support
this includes the following:

Consideration of a consistent addressing scheme and if needed, the acquisition of a large IPV6
address allocation from the “Internet Corporation for Assigned Names and Numbers”, (ICANN)
to allow consistency in address allocation by ANSPs and Regions.

Development of Network Architecture Design Guidance for the IPS (IPv6) network, including
regional addressing assignment, subnet addressing, aircraft addressing, routing infrastructure,
routing protocol, network segmentations, regional interconnect designs, etc.

Development of PKI and IPSec Implementation Guidance to insure that the key fields are
formatted and used consistently which is necessary for the interoperability of authentication and
security services between ANSP’s and regions.

The definition of a consistent Aircraft and Ground System Naming/Identity for PKI use as the
authentication identifier.

The definition of an Aircraft and Ground System IPS Domain Name System structure for both the
aircraft and ground systems. This should also include the required design guidance for “ATN
Root Name Server” infrastructure to be setup between the ANSPs.

Development of IPS DNS Implementation Guidance for interfacing the “ATN Root Name
Servers”, for implementing DNSSec both within and between ANSPs, the creation of “service
names”, and IPv4/IPv6 resolution services.

Development of IPv4 – IPv6 Transition Guidance to ensure that a minimal set of transition
services are supported to minimize interoperability and to ensure that supported transition
services are implemented similarly between ANSPs/regions.
NEW WORKING GROUP S (airport Surface)
Commence work on SARPS and detailed technical material if/as required, for the IEEE 802.16e based
Airport Surface Communication link component of the Future Communication Infrastructure, once a
common Aviation Profile has been developed by RTCA SC-223 and EUROCAE WG-82. The SARPs,
while extensively referencing (through notes) the existing IEEE 202.16e standard as well as the material
being developed by RTCA and EUROCAE, would specify high level requirements such as RCP and the
frequency spectrum interface.
APPENDIX B
PROPOSED UPDATE TO THE ACP WORK PROGRAMME
Major task 1: Expected outcome -- Implementation of ATN/IPS
Output:
Implementation manual (guidance material)
a.
Autonomous System numbering
b.
IPv6 addressing plan
c.
Security protocols
Policy management
Key exchange
d.
Transition guidance
Q4 2011
WG-I
ICAO material on Voice over Internet Protocol (VoIP)
a.
VoIP additions to ATN/IPS Manual
Q3 2010
WG-I
Major task 2: Development of Standards for Future Communication Infrastructure.
Output:
SARPS/Guidance Material Development
New WG-S
Establish new WG for the development of SARPS for Airport Surface Communication
Major task 3: Expected outcome:
Maintenance of SARPs and guidance material for
communication systems.
Output:
Output:
Manual on detailed technical specifications for AMS(R)S
a.
Complete Part III (classic Aero) of Manual
Q2 2010
INMARSAT/MTSAT.
Manual on detailed technical specifications for ATN/OSI
a.
Finalise transition of Doc. 9705 to Doc. 98801 Q2 2010
b.
Complete protected mode FIS/ADS-C
c.
Security Provisions
Q3 2011
WG-M
WG-M
WG-M
SARPS and Manuals on VDL-2, 4 and UAT
WG-M
On-Going
Search for redundant or outdated SARPs and material in manuals
a. Update Annex 10 Vol.III/V provisions
Q4 2010
WG-M
1 With exception of Doc 9705 Sub-Volume II, Ch II (ADS-C) which is dependent on input from the OPLINKP.
ACP-WGW02/AI-4
Major task4: Expected outcome:
Output:
-2-
Spectrum allocation satisfying aviation needs.
ICAO position for WRC-12
a.
Technical material to support ICAO position
January 2012
b.
Regulatory material to support ICAO position January 2012
c.
Technical/Regulatory material for submission to regional
telecommunication organizations (ongoing until WRC-12)
September 2011
Updating RF policy handbook (Doc. 9718)
a. Develop Part II of RF Policy Handbook
Ongoing
Q3 2012
Increasing support and awareness for international
civil aviation requirements for WRC-12 (ongoing)
November 2011
WG-F
WG-F
WG-F
WG-F
WG-F
Studies related to harmful interference from non-aeronautical services (ITU, RTO)
Ongoing
WG-F
Note. — Dates identified in this section indicate foreseen completion of activities for
ACP, unless otherwise specified (e.g. applicability dates of SARPs).
— END —