TAXII SC Meeting 8/11/2015

What do you think about Channels? We described the concept on the last TAXII SC Call. You’ve had time to digest the idea (hopefully). Is the Channel concept a good top level architecture? What do you think? Should we continue to move forward? Note that other proposals can be raised at any time! Ref: https://github.com/TAXIIProject/TAXII-Specifications/wiki/Possible-TAXII-2.0:-Channel-based-TAXII

If we move forward, part 1 This means “continue to explore further”, not “will 100% follow this to the end no matter what” Define requirements What things must stay from TAXII 1.x? Must go? Other requirements? Define use cases (Some very light use cases already exist on the wiki) Define Roles/Goals Define high level features based on Use cases and Requirements

If we move forward, part 2 These will be decided later, but are mentioned here for awareness Pick a transport method Nominees: RabbitMQ, HTTP (w/ Long polling), Web Sockets, ZeroMQ, others? Pick a format Nominees: JSON, XML, ProtoBuf, others? Start constructing a spec outline The fun part: prototyping

If we don’t move forward We figured somebody would ask You can have the rest of the hour back

Participation Brainstorm: Roles/Goals, Use Cases, Requirements Volunteer to create or modify use cases Looking for: Title, 1-2 sentence description, Role(s)/Goal(s), 5-7 step “main success scenario” Who wants to prototype things? Can be a “TAXII Server”, or integration of a product you might be working on, or something else Documentation goes on wiki for now

Open Discussion