DDS Security 1.0 FTF 2 — Open Issues - OMG Issue Tracker

Key: DDSSEC_-103

Status: closed

Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)

Summary:

In view of http://issues.omg.org/browse/DDSSEC_-80 it would be clearer if the CryptoTransform operation encode_serialized_data was called encode_serialized_payload. And similarly the decode_serialized_data was renamed decode_serialized_payload

Reported: DDS-Security 1.0b1 — Tue, 1 Dec 2015 18:05 GMT

Disposition: Resolved — DDS-Security 1.0

Disposition Summary:

Rename encode_serialized_data and decode_serialized_data with encode_serialized_payload and decode_serialized_payload, respectively

Per the issue description rename the CryptoTransform operation encode_serialized_data to encode_serialized_payload

Also rename the CryptoTransform operation decode_serialized_data to decode_serialized_payload

This replacement shall occur both in the text and the figures. In addition Figures 13 and 20 still reference a RTPS submessage element called "SerializedData" per the resolution of DDSSEC-80 the correct name is "SerializedPayload". Therefore this changed figures 5, 7, 13, and 20 attached to this issue resolution should also have the "SerializedData" changed to "SerializedPayload".

Updated: Tue, 12 Jul 2016 14:45 GMT

Attachments:

Figure12_Cryptographic.emf 119 kB ()
Figure13_i80_i103.png 148 kB (image/png)
Figure20_i80_i103.png 148 kB (image/png)
Figure31_DDSSecurity-Xform-Writer.emf 93 kB ()
Figure32_DDSSecurity-Xform-Multiwriter.emf 118 kB ()
Figure34_DDSSecurity-Xform-Multi-Reader-Writer.emf 156 kB ()
Figure5_i80_i103.png 151 kB (image/png)
Figure7_i80_i103.png 249 kB (image/png)