Home' RTCA Documents for Review : ED-ABC_DO-XYZ_OC_FRAC_Profiles_SC223_WG108 Contents 11
© 2019 RTCA, Inc.
Scope and References
The objective of the Profile document is to identify a minimum set of IETF RFCs that must
be implemented by airborne and ground nodes supporting aeronautical safety
communications to fulfil the functional requirements specified in Section 3.3. The Profile
document covers the transport and network protocol layer functions, including security,
naming, address discovery and resolution, routing, mobility, multilink and network
The current scope of IPS Profiles is the air/ground (A/G) communication supporting B1,
B2, FANS, and AOC services.
The high-level functional part of the profile was developed initially based on the IETF RFC
6434, “IPv6 Node Requirements” and the NIST Special Publication 500-267, “A Profile
for IPv6 in the US Government – Version 1.0”. Subsequently, the Profile was further
refined by referencing “US DoD Standards Profiles for IPv6 Capable Products – Version
5”. Existing ICAO Document 9896, Edition 2 was also consulted to identify additional
functional RFCs that were mandated for aeronautical use. Finally, the resulting list of
functional RFCs were updated to incorporate IETF updates and mitigate obsolescence.
Detailed IPS concept of operations and requirements are specified in the
RTCA/EUROCAE Minimum Aviation Systems Performance Standard (MASPS) for IPS.
A limited set of high-level requirement statements are included in this Profile document to
establish the context and to improve readability.
This document contains detailed profiles of the RFCs that are required by at least one of
the IPS device classes to support the air/ground communication services specified in
Section 3.1. Any functional RFC that is deemed ‘optional’ is not a minimum requirement
for IPS to assure interoperability and deterministic performance supporting aeronautical
The desire of the aviation community is to leverage commercial industry standards and
commercial-off-the-shelf (COTS) products to support future communication needs. As
such, deviation from IETF RFCs are only mandated on a case by case basis to improve
performance and safety of operation.
For future IPS systems supporting “Data Primary” operations, multi-level security will be
required to protect IPS systems from malicious attacks. It is assumed that the Secure
Dialog Service (SDS), specified in the ICAO Document 9896, will provide end-to-end
application security. In addition, each access subnetwork under IPS will offer cyber
security capabilities within their operating domain. Cyber security functions of the
subnetwork and SDS are outside the scope of this Profile document. However, security
function will be required for IPS to protect the IPS network control flows. This Profile
document addresses the security requirements for the network control flows. The specified
mechanisms can also be applied to protect IPS network data flows, if necessary.
The global mobility solution for IPS is under development by ICAO Communications
Panel Working Group I. Global mobility Profiles will be defined in the subsequent update
to this document after ICAO finalizes the mobility solution.
Links Archive DO-253D_Change1_FRAC Navigation Previous Page Next Page