Re: [cti-taxii] TAXII per Chapter 5 of Fielding

[Trey Darley <trey@soltra.com>]

"...near infinite code-paths...This is the very problem we have with TAXII and STIX today - too much complexity."

+100, Jason, I'm having that printed on a t-shirt! ^_^

Cheers,

Trey

--

Trey Darley

Senior Security Engineer

Soltra | An FS-ISAC & DTCC Company

www.soltra.com

---

From: cti-taxii@lists.oasis-open.org <cti-taxii@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Sent: Thursday, September 10, 2015 16:40
To: John Anderson
Cc: cti-taxii@lists.oasis-open.org
Subject: Re: [cti-taxii] TAXII per Chapter 5 of Fielding

 

My $0.02 - While I really prefer REST principles for APIs, I also think that REST is whatever people want it to be.

There are hardly any (perhaps zero?) high traffic REST APIs in the wild that are purist REST and HATEOAS. The main one that hardly anyone follows is the concept of discoverability -, because it is somewhat idealistic, unnecessary in practice, and just complicates the API. As a developer I would much rather have a stringent REST spec with documented endpoints that I can consume, than a widely flexable one based on discovery that results in near infinite code-paths.

This is the very problem we have with TAXII and STIX today - too much complexity. We don't need to solve world hunger with this API. My challenge would be this - if simple REST is good enough for Google and Twitter and Facebook and Amazon, why is it not good enough for TAXII. We can only hope in our wildest dreams that our API gets consumed as much as those APIs do.

-
Jason Keirstead
Product Architect, Security Intelligence, IBM Security Systems
www.ibm.com/security | www.securityintelligence.com

Without data, all you are is just another person with an opinion - Unknown