cti-taxii — archive

Re: [cti-taxii] Manifest Resource

From: John Wunder <[email protected]>
To: [email protected]
Date: Fri, 05 Oct 2018 14:43:00 -0000

I agree, we should make this change. I would guess the reason version isn t required is that we wanted to be able to transport other content types, besides STIX, that might not have a version property. I m not particularly concerned about that, though could always use a placeholder. We should optimize for STIX. John From: [email protected] <[email protected]> On Behalf Of Allan Thomson Sent: Friday, October 5, 2018 10:38 AM To: Bret Jordan <[email protected]>; [email protected] Subject: Re: [cti-taxii] Manifest Resource Bret I tried to think any case where they might not be available or generated. I couldn t think of any reasonable use case where the taxii server could not provide these, so I m supportive of the change. Allan From: < [email protected] > on behalf of Bret Jordan < [email protected] > Date: Friday, October 5, 2018 at 7:00 AM To: " [email protected] " < [email protected] > Subject: [cti-taxii] Manifest Resource All, In looking at the Manifest Resource and its purpose, I am thinking we need to make the date added and version properties required. I believe this was an oversight in 2.0. Currently we have the following properties Property Name Type Description id (required) string The identifier of the object that this manifest entry describes. For STIX objects the id MUST be the STIX Object id . For object types that do not have their own identifier, the server MAY use any value as the id . date_added (optional) timestamp The date and time this object was added. version (optional) string The version of this object. For objects in STIX format, the STIX modified property is the version. media_type (optional) string The media type that this specific version of the object can be requested in. This value MUST be one of the media types listed on the collection resource. I propose that we change this to: Property Name Type Description id (required) string The identifier of the object that this manifest entry describes. For STIX objects the id MUST be the STIX Object id . For object types that do not have their own identifier, the server MAY use any value as the id . date_added (required) timestamp The date and time this object was added. version (required) string The version of this object. For objects in STIX format, the STIX modified property is the version. media_type (optional) string The media type that this specific version of the object can be requested in. This value MUST be one of the media types listed on the collection resource. Is there anyone that would be against this change? If no, I will create a Github issue and make the change in Working Draft 04. Bret