Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
erik4711 opened this issue Nov 22, 2016 · 0 comments
Labels
pcapv3 aka pcapng

Comments

@erik4711
Copy link

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.

@erik4711 erik4711 changed the title Comments on 4.3. Enhanced Packet Block - Specify timestamps as a 64 bit vaule Comments on 4.3. Enhanced Packet Block - specify timestamps as a 64 bit vaule Nov 22, 2016
@mcr mcr added the pcapv3 aka pcapng label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pcapv3 aka pcapng
Projects
None yet
Development

No branches or pull requests

2 participants