Network Infrastructure and Security (NIS) Subcommittee
Last Updated:
July 12, 2010
Co-Chairman: Jean-Paul Moreaux – Airbus
Co-Chairman: Stephen Arentz- United Airlines
APIM: 05-021, 05-22, 08-007, 10-002, 10-004
Goal: Coordinate the standardization of IP connectivity and security to the aircraft. Enable fleet-wide solutions based on open standards for lower development cost, increased flexibility, higher reliability, reduced complexity, longer lifespan, and ease of configurability and maintenance.
Scope: NIS is to harmonize network-related and security-related activities of the various AEEC subcommittees working in related areas. NIS will serve as AEEC focal point for liaison to groups external to AEEC in order to coordinate work in these areas. NIS will focus on the interfaces and not on the hardware or software applications. NIS will provide support to AEEC by providing operational assessments of networking and security issues.
Benefit: By providing a forum for the discussion of networking- and security-related issues, all AEEC subcommittees can better coordinate their work with other aspects of aircraft and non-aircraft systems. This should reduce redundant activities, implement better more consistent, flexible, and interoperable solutions, and provide for better configuration control and ease maintenance.
AEEC General Session (March 2010) Update:
Adoption Items:
Supplement 1 to ARINC Specification 825: General
Standardization of CAN (Controller Area Network) Bus Protocol for Airborne Use
which
includes CAN gateway considerations, design guidelines, data upload and
download service, a sample Data Object Code (DOC) list, and cross-reference
information to AC120-156 Aviation Data Bus Assurance.
APIM Approvals:
AEEC approved the following new projects:
- APIM 10-002: Digital Certificate Usage in the Aircraft
Environment.
The result of this work will be ARINC Project Paper 8xx:
Guidance for Usage of Digital Certificates. This document will provide guidance
to aircraft manufacturers and operators on such subjects as the use of Public
Key Infrastructure (PKI) standards in the context of actual aircraft deployment,
unique aircraft avionics implementations, maintenance procedures and the
constraints of the aircraft environment. Coordination with the ATA Digital Security
Working Group (DSWG) continues to avoid duplicate provisions as they are
updating security provisions in ATA Spec 42.
- APIM 10-004: Supplement 2 to ARINC Specification 825:
General Standardization of CAN (Controller Area Network) for Airborne Use. The
updates will include new material such a timing model, common latency
methodology, bus loading (bandwidth) metrics, gateway definitions, and data
load examples. This will be a joint activity with the Software Data Loading (SDL)
Subcommittee.
Current Drafts:
Draft 1 of Supplement 1 to ARINC Specification 664: Aircraft Data Network, Part 8, Interoperation with Non-IP Protocols and Services
Next Meeting Announcement:
Air Ground Information Exchange/ Manager of Air Ground Interface Connections (AGIE/MAGIC) Subcommittee
Network Infrastructure and Security (NIS) Subcommittee
(pdf, 168K)
September 27-October 1, 2010; in Annapolis, Maryland
Register On Line
Working Papers:
Last Meeting Report:
Air Ground Information Exchange/ Manager of Air Ground Interface Connections (AGIE/MAGIC) Subcommittee
June 14-16, 2010; in Hamburg, Germany
Network Infrastructure and Security (NIS)
June 16-18, 2010; in Hamburg Germany
Associated Technical Application Bulletins:
| IP Addresses Used Onboard Aircraft |
| |
Staff: |
Roy Oishi |
| Reference: |
08-199/ABN-024 |
| Effective: |
December 2008 Until Superceded |
Summary:
ARINC 664 Aircraft Data Network Part 4: Internet-based Address Structure and Assigned Numbers, identifies IP address ranges for various domains onboard the aircraft. This TAB collects known IP address assignments for various aircraft and ground system implementations in order to reduce conflicts among the various systems connected to the onboard IP network. |
| Submit Feedback for this bulletin |
Controller Area Network (CAN) TWG
APIM 10-004: Supplement 2 to ARINC Specification 825:
General Standardization of CAN (Controller Area Network) for Airborne Use.
Goal: Updated ARINC Specification 825-1 to include new material such a timing model, common latency
methodology, bus loading (bandwidth) metrics, gateway definitions, and data
load examples. This will be a joint activity with the Software Data Loading (SDL)
Subcommittee.
Current Drafts:
Next Meeting Announcement:
Working Papers:
Last Meeting Report:
Click here for information regarding Ku-Band.
