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

Recursive Payload - preamble #9

Open
reisub-de opened this issue Sep 18, 2017 · 1 comment
Open

Recursive Payload - preamble #9

reisub-de opened this issue Sep 18, 2017 · 1 comment
Assignees

Comments

@reisub-de
Copy link
Contributor

When we have a recursive payload (e.g. fragmentation) the result of the "defragmentation" should be another valid packet. Does this packet include the Magic bits or not? If we use the reserved bits for flags these may be required for further processing so my vote for this is yes, include the magic (first) byte.

@hgn
Copy link
Member

hgn commented Sep 18, 2017

Yes, as in ipv4 and IPv6 the common header is a requirement

@reisub-de reisub-de self-assigned this Sep 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants