-
Notifications
You must be signed in to change notification settings - Fork 19
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
Post 1.0 - WD02 Comment - Regex target #38
Comments
Deferred to post 1.0 or until a use case appears |
The need for 'regex' targets is going to apply to a subset of actuators. The ability to import targets is documented in the current specification, therefore agree with the comment to defer until use cases are identified |
This issue is over a year old. Given that we have a means to extend the target space in the profiles and to date, no additional comments, use case nor actuator profile has been provided, suggest we close this issue |
Given that (i) the original source of the comment is no longer a TC member and (ii) no use cases have been presented, I recommend closing this issue. The subject can be revisited in the future if a use case is presented. |
Discussed at triage session, leave for future and await a use case and a proposal. |
Jason Webb made the comment to table 2-2 "I would suggest adding a new target type to this list.
I would like to be able to base my target on regular expression matching of packet content.
For example, I may want to define a target based on whether or not a packet contains a specific sequence of bytes.". This issue requires discussion as several alternatives on how to solve were suggested. Used cases are sought.
The text was updated successfully, but these errors were encountered: