Re: [EXT] [cti-taxii] Errata in TAXII spec around allowed collection ID formats.

[Bret Jordan <Bret_Jordan@symantec.com>]

Jason,

The intent is that all collections have a UUIDv4 address. We tried to catch all of the examples that had place-holders and fix them.  But apparently there was more than one in 2.0 that we missed.  I just checked and this problem does not exist in the 2.1 WD04 document. 

Now with that said, if you want to write some text that talks about aliasing a collection ID with some sort of vanity name, please do so.  I would just suggest that if we do this, we should require that the UUIDv4 be added as an x-header so that a client would know from which collection it actually came from.

Bret

---

From: cti-taxii@lists.oasis-open.org <cti-taxii@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Sent: Tuesday, September 25, 2018 7:11:56 AM
To: cti-taxii@lists.oasis-open.org
Subject: [EXT] [cti-taxii] Errata in TAXII spec around allowed collection ID formats.

 

I have found errata in the TAXII spec

The TAXII spec defines the ID of the collection resource to be of type "identifier", which, at the start of the document, is defined as having to be a UUID. However, numerous examples throughout the specification show a collection ID having a common string name such as "my-collection".

Is it allowed for a TAXII collection to have a common name as an ID? Or do they all have to be UUIDS

This has ramifications for people wanting to create special read-only or write-only collections that serve as things like an Inbox.


-
Jason Keirstead
Lead Architect - IBM.Security
www.ibm.com/security

"Things may come to those who wait, but only the things left by those who hustle." - Unknown