[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Next batch of TAXII issues
All,
Here are seven low hanging issues I would like to see if we can resolve over email. If we do not hear any objections by the end of next week, we will proceed with the currently proposed solutions. Please respond with your approval, disapproval, or additional
feedback/suggestions/improvements either over email or in the Github issue tracker. BTW, here is the link to the current
TAXII 2.1 Document for your reference.
In section 3.4.1, change the version description text to:
In section 3.4, add the following text to the added after description:
In section 3.1, the following normative statement and examples were added:
For this one, I am not sure where we should put this information
In section 3.3, a paragraph remains about the old object search endpoint. This endpoint was removed before TAXII 2.0 was finished, however, this paragraph did not also get removed. Proposal, remove this paragraph.
In section 1.4.7 I have tried to address the above two issues, by making sure the references are correct and that we provide a way to advertise a version that is still at a CSD level. So an example version, in the Content-type header would be: "version=2.1.csd01"
In section 4.3.1 we define the versions to be "taxii-2.1" instead of the value that matches the media type version. I propose that for 2.1, we change this to be the same at the media type version. This will also allow us to advertise at the API root
level the CSD version as well.
Thanks
Bret
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]