[CSS] Fwd: ARINC CSS Media Independent Messaging Status

Tue Mar 5 15:39:34 EST 2019

Good day,

The AEEC Cabin Systems Subcommittee (CSS) requests your review of an input from Safran (formerly Zodiac Interior Innovations).

If there is anything you might need, please do not hesitate to ask.

Cheers,

Smitty
443-221-8372

Scott Smith
Sr. Principal Engineer
SAE ITC, ARINC Industry Activities

Begin forwarded message:

From: Steven Rines <Steven.Rines at zii.aero<mailto:Steven.Rines at zii.aero>>
Date: March 4, 2019 at 15:58:35 GMT-7
To: Scott Smith <Scott.Smith at sae-itc.org<mailto:Scott.Smith at sae-itc.org>>
Subject: ARINC CSS Media Independent Messaging Status

Smitty, please forward this email to the CSS mailing list.  Thanks, --Steve

All,

At our last CSS meeting in St. Augustine I presented the draft APIM and whitepaper on Media Independent Network Messaging that I intended to present at the SAI Subcommittee in Coral Gables.  It’s been several weeks now since the SAI Subcommittee meeting.  Sorry for my delay in reporting back to you; it’s been a bit busy.

First, I screwed up at our CSS meeting.  We should have reviewed the APIM and made final edits before I carried it to Coral Gables.  As was, the APIM I delivered still listed Boeing and Airbus as “TBD” which caused the Boeing and Airbus representatives to step back and refuse to approve until they had checked with their internal engineering teams.  Second, I screwed up the presentation in Coral Gables.  The Subcommittee members ended up conflating security requirements for WAIC safety and regularity of flight and requirements for a messaging system for cabin systems and scaring themselves.  The end result is that the SAI Subcommittee did not approve the APIM for Media Independent Network Messaging.  However, they did agree to give Boeing and Airbus representatives time to review the topic internally and asked me to re-present the APIM at the June SAI meeting in Toulouse.  The Subcommittee went on to say that, until we get APIM approval in June, the ad hoc Messaging working group cannot represent itself as an ARINC CSS working group.

There is still a lot of work to do hit our target of completing the ARINC Messaging characteristic in first quarter 2021 so it is my intention to continue the ad hoc Messaging working group with bi-weekly WebEx meetings.  I’ll see if Smitty can set-up a WebEx for us through ARINC.  If not I will set up the meeting through Zodiac’s WebEx.

Anyone interested in participating in the ad hoc messaging working group please let me know and I’ll add you to the mailing list for upcoming meetings.

I spoke with Ethan Owyang (Boeing) and explained the above situation regarding ad hoc meetings.  Ethan said Boeing is willing and able to support.  Ethan suggested changing the name for our proposed messaging service to “Secure Media Independent Messaging.”  I agreed and all of my work since the Subcommittee meeting reflects that new name.

Week before last I was in Germany and took that opportunity to meet with Fritz Urban and several engineers at Airbus to provide a briefing on where we are at with messaging.  Fritz and company agreed to talk internally about how to move the APIM forward and also to see if they could support our ad hoc meetings.

On 22 February EASA published Notice of Proposed Amendment (NPA) 2019-01, Aircraft Cyber Security, for comment by 22 May.  The proposed amendments introduce changes to certification standards based on recommendations from RTCA SC-216 to DO-356A/ED-204A. The FAA is in the process of releasing an AC that will introduce similar changes to their cert documentation.  The reason this is interesting to our messaging topic is that our messaging solution will now be expected to adhere to the security requirements in DO-356A.

In discussions with the FAA over the last few weeks regarding Wireless Avionics Intra-Communications (WAIC), we determined that, while comprehensive, DO-356A security requirements did not take into account any security risks for aircraft functions that utilized wireless communications.  SWG-3, the WAIC Security Special Working Group is now in the process of defining the specific requirements associated with wireless communications for aircraft functions (not limited to WAIC).  Those requirements will be used to either incorporate wireless communications security requirements into DO-356A or define a dedicated wireless communications AC.  In either case, SMIM will have to meet WAIC MOPS security requirements if we intend it to support aircraft functions over wireless communications.

I have been talking with the FAA as well as management at RTCA and ARINC to figure out what the documents should look like for the various elements of SMIM.  The WAIC MOPS will define a clear demarcation between the transport layer and messaging at the PHY/MAC/Link Layer.  It looks like that demarcation will end up as a TSO –not just for WAIC, but for any device that wants to be SMIM compliant.  This is *great* as it provides a test suite that suppliers can use to verify compliance and a clear statement of compliance that system integrators can use for procurement of SMIM devices.

Network security requires certain capabilities to be available in every equipment and a specific configuration of that equipment, therefore, compliance to DO-356A security requirements must be demonstrated at the equipment supplier and the integrator.  That makes the documents and dependencies for SMIM look something like this:

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. This email, and any attachments, may contain confidential and/or proprietary material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited. If you received this message in error, please contact the sender and permanently delete any printout of the message, the original and any copy of the e-mail and its attachments from your computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 48517 bytes
Desc: image008.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0007.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0008.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1523 bytes
Desc: image001.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0008.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0009.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1525 bytes
Desc: image002.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0009.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0010.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 561 bytes
Desc: image003.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0010.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0011.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1436 bytes
Desc: image004.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0011.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0012.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1402 bytes
Desc: image005.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0012.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0013.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1436 bytes
Desc: image006.png
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0013.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0014.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Semantic Ontology Notes 190304.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 56973 bytes
Desc: Semantic Ontology Notes 190304.docx
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0001.docx>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/css/attachments/20190305/20fa3571/attachment-0015.htm>