Closed maybe-sybr closed 3 years ago
We talked about this on an editors call and seem to agree. We will discuss this on a TC call.
This is the proposed text and has been made in the master document.
If this property and the start property are both defined, then this property MUST be greater than or equal to the timestamp in the start property.
Sounds great to me and matches the assumption I've been making in some staged patches for my own projects, @jordan2175 - thanks for the update.
I have an implementation capturing and describing network traffic and have noticed that the STIX 2.1 spec specifically states that
network-traffic
observables'end
property must be strictly greater than thestart
property if both are defined.-- ref the table in section 6.12.1
This causes issues for me describing single packet UDP flows which get timed out because I then set the end time to the start time. It would be incorrect IMO to set the end time to anything else since there was no activity associated with it after the start time, and I'd prefer to include the end time to be explicit rather than relying on a downstream system to interpret what the absence of an end datestamp and
is_active: False
means.I can also see an issue with systems which have limited clock resolution which observe flows which complete within a single tick. I've not seen this behaviour personally but it seems like a thing which might reasonably occur, e.g. if observations were being made by software without access to a high resolution timer.
What would you suggest the expected behaviour here should be? Is there any particular reason why the
start
andend
property cannot have the same value?