[IPS_Aero] FW: A858s1 Parts1&2 pre-M26

[Sam Buckwalter]

Hello All:

See the below email and drafts for the upcoming IPS Subcommittee meeting.


Sam Buckwalter
AEEC Executive Secretary
Lead Principal Engineer

ARINC Industry Activities an SAE ITC Program

m 1+443.454.0584
sam.buckwalter at sae-itc.org<mailto:sam.buckwalter at sae-itc.org>



From: Olive, Michael L <mike.olive at honeywell.com>
Sent: Sunday, February 12, 2023 6:38 PM
To: Sam Buckwalter <Sam.Buckwalter at sae-itc.org>
Cc: luc.emberger <luc.emberger at airbus.com>; Saccone (US), Gregory T <Gregory.T.Saccone at boeing.com>
Subject: A858s1 Parts1&2 pre-M26


Sam,
Attached are the latest draft versions of A858s1 Part 1 (d1-03) and Part 2 (d1-03) with additional input for discussion during Meeting 26 in PHX.  These files and the latest action item list are posted on the AEEC IPS Teams site as well.
As previously requested by AEEC, these supplement documents retain all redline changes, and the most recent redline changes are shown using yellow-highlighting.  For Parts 1 and 2, the following tables summarize the changes in this version, which include updates per discussions during Meeting 25 as well updates to address open action items.

858P1s1d1-03_20230208 (DRAFT - pre-M26).pdf - Part 1, Airborne IPS System Technical Requirements

Section
Action Item
Change
1.3.3
--
New section with proposed requirement statement conventions (same text in Parts 2 and 3), based on discussion with Sam regarding similar section in other AEEC standards.
4.4.1.1.5
P1-M17-02
P1-S01-17
Updated Trust Anchor and Certificate Validation section with new text provided by Rob Segers (FAA) that was reviewed jointly during the joint AEEC - RTCA/EUROCAE discussions.
Attachment 3 -
3.1.1.1,
3.2 Figure 3-4, 3.2.3.2,
3.3 Figure 3-5, 3.3.3.2
P1-M24-01
Changes to text/figures to reflect the AEEC IPS decision on action P2-M23-02 to include both FlightID and Tail Number in the Peer IDs for ACARS-based messages.
Attachment 3 -
3.1.2.2 Figure 3-2
--
Uncompressed Application Data Format figure updated to correctly reflect inclusion of MSN in downlink messages.  MSN was added previously (prior to publishing A858p1) to the User Data, but this figure was not updated accordingly.
Appendix A -
Figures A-2 thru A-14,
A-8
P1-M24-02
All example ATNPKT diagrams updated to reflect ICAO WG-I agreement to expand N(R) and N(S) to 8 bits each; AND the AEEC IPS decision on action P2-M23-02 to include both FlightID and Tail Number in the Peer IDs for ACARS-based messages.


858P2s1d1-03_20230208 (DRAFT - pre-M26).pdf - Part 2, IPS gateway Air-Ground Interoperability

Section
Action Item
Change
1.3.3
--
New section with proposed requirement statement conventions (same text in Parts 1 and 3), based on discussion with Sam regarding similar section in other AEEC standards.
4.3.1, Table 4-1, Figure 4-2,
4.3.2, Table 4-2, Figure 4-3
4.4.1, Table 4-3
4.4.2, Tables 4-4, 4-5
P2-M22-02
Example downlink/uplink messages and associated text/tables updated to reflect ICAO WG-I agreement to expand N(R) and N(S) to 8 bits each; AND the AEEC IPS decision on action P2-M23-02 to include both FlightID and Tail Number in the Peer IDs for ACARS-based messages.
(Thanks Fryderyk!)
4.x
P2-M23-02
AEEC IPS decision to include both FlightID and Tail Number in the Peer IDs for ACARS-based messages.  This change is addressed in Part 1 (P1-M24-01, P1-M24-02) and in Part 2 (P2-M22-02).

I will be sending PP858 Part 3 via separate email.
Thanks for distributing this information to the AEEC IPS participants.
Mike




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/ips_aero/attachments/20230214/187796db/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 858P1s1d1-03_20230208 (DRAFT - pre-M26).pdf
Type: application/pdf
Size: 7307050 bytes
Desc: 858P1s1d1-03_20230208 (DRAFT - pre-M26).pdf
URL: <http://mailman.sae-itc.org/pipermail/ips_aero/attachments/20230214/187796db/attachment-0002.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 858P2s1d1-03_20230208 (DRAFT - pre-M26).pdf
Type: application/pdf
Size: 4397337 bytes
Desc: 858P2s1d1-03_20230208 (DRAFT - pre-M26).pdf
URL: <http://mailman.sae-itc.org/pipermail/ips_aero/attachments/20230214/187796db/attachment-0003.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: _AEEC A858 Supp1 RAIL.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 163144 bytes
Desc: _AEEC A858 Supp1 RAIL.xlsx
URL: <http://mailman.sae-itc.org/pipermail/ips_aero/attachments/20230214/187796db/attachment-0001.xlsx>