Re: [cti] [cti-taxii] TAXII Materials Submission - TAXII Pre-Draft spec

["Jordan, Bret" <bret.jordan@bluecoat.com>]

I want to also re-state what Mark said.  Mark and I have worked hard on the document thus far, and have received several great submissions of content and lots of feedback.  We personally thank all of you that have helped thus far and request that everyone take a look and give us your feedback.

The document is not perfect, and some parts are more rough around the edges than others.  But I hope you will be able to see where we are going, and how we have taken all of your feedback over the past 2 years and are trying to forge a better solution for TAXII.

As you read through this document if you think, "I could word this better", please, please, send us your text. Writing normative text is HARD.  You will also notice that the document is currently in three different and distinct voices.  That will be fixed before we make an official draft.  It is just an outgrowth of contributions and massive editing.  

We welcome and highly encourage your feedback.  For those attending the F2F, we would love to spend some time during BoF time, Dinner, or even after discussing your ideas and feedback.  

One point of note...  As you read the document, please understand the audiences that we have defined.  Section 1 is really targeted at a Product Manager.  It should give just enough information for them to know what TAXII is all about and what it will mean to them to implement it, it should also work as a good primer for any average technical person wanting to know more about what TAXII is.  Section 2 - X will target actual product architects and developers. 

Lets all make TAXII the single best solution for communicating threat intelligence and lets get this done and out the door by late Spring!!!!

Thanks,

Bret

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." 

On Jan 7, 2016, at 21:59, Mark Davidson <mdavidson@soltra.com> wrote:

I had meant for this to go to the CTI list, and I got bit by autocomplete.

-Mark

From: <cti-taxii@lists.oasis-open.org> on behalf of Mark Davidson <mdavidson@soltra.com>
Date: Thursday, January 7, 2016 at 11:28 PM
To: "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org>
Subject: [cti-taxii] TAXII Materials Submission - TAXII Pre-Draft spec

All,

Please find attached the TAXII 2.0 pre-draft specification. As noted on the TAXII SC list and within the document itself, this document is intended to be a discussion platform and help drive consensus. The quality of the document is a bit uneven – we’d like to kindly request that readers attempt to get the “big picture” first and comment on specific wordings/phrasings second. Notably, if you think “Channels and Collections” are the wrong way to go, that would be a great thing to raise at the F2F.

Thank you and we look forward to seeing you at the F2F!

Mark and Bret

<TAXII2Spec.pdf>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail