Re: [cti-taxii] Last Call

[Matt Pladna <mpladna@lookingglasscyber.com>]

1. Approve; date_added to me is one of the major points of requesting a manifest.  Version makes sense too. 
   1. Iâd argue though at this point the client should just be request the objects endpoint but I might be missing the point/use case.  If someone can clarify just email me privately please
2. Approve (I like this a lot)

 

-- Matt Pladna

 

From: <cti-taxii@lists.oasis-open.org> on behalf of Bret Jordan <Bret_Jordan@symantec.com>
Date: Monday, October 8, 2018 at 10:28
To: "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org>
Subject: [cti-taxii] Last Call

 

All,

 

I would like to ask for a last call for comments and feedback on the following two issues.  The current expressed consensus is that we should accept these changes. Please review as soon as possible and voice your feedback.

 

1) Make the date added and version properties required on the Manifest resource section 5.3.1.

https://github.com/oasis-tcs/cti-taxii2/issues/93

 

 

2) Add an optional alias property to the Collection resource in section 5.2.1

https://github.com/oasis-tcs/cti-taxii2/issues/90

alias (optional)

string

A human readable collection name that can be used on systems to alias a collection ID. This could be used by organizations that want to preconfigure a known collection of data, regardless of the underlying collection ID that is configured on a specific implementations. The alias value MUST use URL safe characters.   If defined, the alias MUST be unique within a single api-root on a single TAXII server. There is no guarantee that an alias is globally unique across api-roots or TAXII server instances. Example: /{api-root}/collections/critical-high-value-indicators/

 

If you approve, disapprove, or have additional editorial suggestions, please comment on the email list. 

 

 

Thanks,

Bret