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.

Sign up for GitHub

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

Jump to bottom

A normative statement concerning the order of protocols in the network-traffic object is not enforced #151

Open

rpiazza opened this issue Jun 24, 2020 · 0 comments

Contributor

rpiazza commented Jun 24, 2020

Protocols MUST be listed in low to high order, from outer to inner in terms of packet encapsulation. That is, the protocols in the outer level of the packet, such as IP, MUST be listed first.

This should be checked - although it would be difficult for the following reasons:

protocols is a list of strings, which SHOULD come from IANA registry but may not. So I suppose we could enforce it for a few most-used protocols, but certainly not all...
Also, lowercase is suggested but not required either, increasing complexity of any validation.
The statement seems to be contradictory about what order to enforce (see Protocol normative statement seems to be contradictory oasis-tcs/cti-stix2#231)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment