OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Notes from working call


We had 15 people on the working call today and we were able to get through the following open TAXII issues.  The Github issue tracker has been updated to reflect the consensus from the call. Also, I am attaching the slides that I used today as there are some topics that we did not get to, that I will want to discuss next week.  If I captured any of the notes incorrectly in the Github Issue Tracker, please make changes to the issue in question.

1) I put out another request for a volunteer to help me be an editor on the TAXII 2.1 specification document. 

2) Update JSON Reference #43

The consensus on the call was to do this and mandate that JSON based encoding must use UTF-8. We recognized that we need to verify this will not break things for our members from APAC and I will do that.

3) Returning the number of results is not explicitly clear #42

The consensus on the call was that it probably should be the number of objects that match the query or filter that was provided. However, we need to do some more investigation on this once we redo our pagination style. I think if we do keep this, with our pagination changes, then we should probably make it optional for the server to implement.

4) Trailing-slash normative requirement for resource identifiers is missing #41

There was no objection to adding a normative statement that says all resource endpoints MUST have a trailing slash.

5) Trey asked Terry to talk a bit about the Request for Information object that he and Jason worked on.  There were a few comments about making sure this does not explode in to a complete table regex query. So we might need to start small and add.  We also might need to do something immediately for the TAXII collections via a URL parameters and then look at adding this more robust solution once we do channels.  We need to have further discussions about this.  There were two comments made that we need to make sure we have working prototypes and implementations to test this, both from a basic dataset perspective and a large dataset perspective, before we get to far down the path. 

6) Add Delete Capability to Object Endpoints #38

There were several comments made by Terry and JMG, but all in all, it seems like everyone is generally in agreement with doing this. However, we decided that we would bring it up again for further discussion.


Attachment: 2018-02-20_working call.key.pdf
Description: 2018-02-20_working call.key.pdf

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]