Comments on 4.3. Enhanced Packet Block - specify timestamps as a 64 bit vaule

[erik4711]

4.3. Enhanced Packet Block

Is there any valid reason for splitting the 64 bit timestamp into two separate 32 bit values? Several 64 bit fields already exist in the spec, such as the Section Length field of SHB and epb_dropcount option. Also, please note that if we would require the pcapng spec to be big-endian only then we wouldn't need to make this type of differentiation.

My recommendation is that the timestamp should be serialized as a single 64 bit value rather than as two 32 bit values.