GDDI 1.0b2 FTF Avatar
  1. OMG Issue

GDDI — Consider changing Total Length from 3 to 4 octets or add "trimmed" wording

  • Key: GDDI-4
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Eric Ogren)
  • Summary:

    Comment from Matteo Vescovi:
    8.1.2.4 Total Length
    "This integer PIM attribute maps to a CORBA unsigned long whose most significant 8-bits are unused, resulting in a 24-bit (3 octet) field as shown in the above figure."

    I'm curious why the standard CDR rules were not followed, and it was decided to encode an unsigned long as 3 octets instead of 4? To save one octet? To limit max message size?

    Also, figure 17 has "CORBA unsigned long" next to the Total Length field, which might be misleading. Perhaps it should say "CORBA unsigned long (trimmed)" or similar, to alert the reader to the fact that the usual CORBA unsigned long CDR marshalling does not apply to this field.

  • Reported: GDDI 1.0a1 — Fri, 8 Nov 2024 16:47 GMT
  • Disposition: Resolved — GDDI 1.0b2
  • Disposition Summary:

    Change the encoded size of the "Total Length" field from 3 to 4 octets

    During the GDDI FTF 1.0 session in San Francisco 2024, the group agreed that the size of the "Total Length" field should be changed from 3 to 4 octets. This allows standard CDR rules to be followed for all encoded fields. It also provides for a larger payload field size, i.e. for cases with a large number of Type Blocks and many TLVs per block.

  • Updated: Tue, 1 Jul 2025 14:58 GMT