OASIS Cyber Threat Intelligence (CTI) TC

All, Drew and I have finished resolving all of the comments and suggestions that came in for Working Draft 02 and today are releasing Working Draft 03. Please see the attached Word and PDF versions.  As editors we believe this version, Working Draft 03, is ready to advanced to Committee Specification Draft 01 (CSD 01).   MOTION: I motion that the TC accept TAXII 2.1 Working Draft 03 to be the version that we advance to Committee Specification Draft 01 and that the TC open a ballot to approve TAXII 2.1 Working Draft 03 as Committee Specification Draft 01.   TIMING: If this motion gets a second, the timing of the ballot will coincide as much as possible with the upcoming STIX 2.1 CSD01 ballot. NOTES: The permission for the Google Doc version of Working Draft 03 ( https://docs.google.com/document/d/1EsiWY7TGqt9yH6QUXv4c-opXSr3wR0TDMt8Q0yJjpoo/edit# ) have been locked down, as this version moves towards a CSD.  If you have further comments or suggestions on this Working Draft, please send them to the list.  If this motion passes, I will create a new Working Draft 04 document in the coming days and set permissions on it as we begin work on CSD02.  Thanks Bret Attachment: TAXII Version 2.1 - WD03.pdf Description: TAXII Version 2.1 - WD03.pdf Attachment: TAXII Version 2.1 - WD03.docx Description: TAXII Version 2.1 - WD03.docx

I second this Motion. On Jul 12, 2018, at 12:25 PM, Bret Jordan < Bret_Jordan@symantec.com > wrote: All, Drew and I have finished resolving all of the comments and suggestions that came in for Working Draft 02 and today are releasing Working Draft 03. Please see the attached Word and PDF versions.  As editors we believe this version, Working Draft 03, is ready to advanced to Committee Specification Draft 01 (CSD 01).   MOTION: I motion that the TC accept TAXII 2.1 Working Draft 03 to be the version that we advance to Committee Specification Draft 01 and that the TC open a ballot to approve TAXII 2.1 Working Draft 03 as Committee Specification Draft 01.   TIMING: If this motion gets a second, the timing of the ballot will coincide as much as possible with the upcoming STIX 2.1 CSD01 ballot. NOTES: The permission for the Google Doc version of Working Draft 03 ( https://docs.google.com/document/d/1EsiWY7TGqt9yH6QUXv4c-opXSr3wR0TDMt8Q0yJjpoo/edit# ) have been locked down, as this version moves towards a CSD.  If you have further comments or suggestions on this Working Draft, please send them to the list.  If this motion passes, I will create a new Working Draft 04 document in the coming days and set permissions on it as we begin work on CSD02.  Thanks Bret <TAXII Version 2.1 - WD03.pdf> <TAXII Version 2.1 - WD03.docx> --------------------------------------------------------------------- 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

Are there any objections to moving forward with TAXII 2.1 Working Draft 03 as Committee Specification Draft 01?  Please let us know over the next week if you do have an objection.


If you have not yet done so, I would encourage you to read through Working Draft 03. If there is any language we can improve, if there is a better way to present the information, please let me or Drew know. 


Thanks
Bret 

Sent from my Commodore 128D


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


On Jul 12, 2018, at 12:27 PM, " drew.varner@ninefx.com " < drew.varner@ninefx.com > wrote:



I second this Motion.

On Jul 12, 2018, at 12:25 PM, Bret Jordan < Bret_Jordan@symantec.com > wrote:





All,


Drew and I have finished resolving all of the comments and suggestions that came in for Working Draft 02 and today are releasing Working Draft 03. Please see the attached Word and PDF versions.  As editors we believe
this version, Working Draft 03, is ready to advanced to Committee Specification Draft 01 (CSD 01).  


MOTION:
I motion that the TC accept TAXII 2.1 Working Draft 03 to be the version that we advance to Committee Specification Draft 01 and that the TC open a ballot to approve TAXII 2.1 Working Draft 03 as Committee Specification
Draft 01.  


TIMING:
If this motion gets a second, the timing of the ballot will coincide as much as possible with the upcoming STIX 2.1 CSD01 ballot.


NOTES:
The permission for the Google Doc version of Working Draft 03 ( https://docs.google.com/document/d/1EsiWY7TGqt9yH6QUXv4c-opXSr3wR0TDMt8Q0yJjpoo/edit# )
have been locked down, as this version moves towards a CSD.  If you have further comments or suggestions on this Working Draft, please send them to the list.  If this motion passes, I will create a new Working Draft 04 document in the coming days and set permissions
on it as we begin work on CSD02. 


Thanks
Bret






<TAXII Version 2.1 - WD03.pdf>


<TAXII Version 2.1 - WD03.docx>



---------------------------------------------------------------------
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

Hi Bret,   I thought the TAXII spec called out the ability for TAXII Clients to include their implementation and version within the http user-agent but I don’t see it now. Is that within the spec?   If not I think this is something we should include and will include a GITHUB ticket to support. This is generally a light lift for the TAXII clients and would provide huge support for TAXII servers admins when trying to troubleshoot between various TAXII clients.   Let me know whether this is within the spec or not and I will provide something if needed.   Thanks,   -Marlon     From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org] On Behalf Of Bret Jordan Sent: Thursday, July 12, 2018 12:25 PM To: cti@lists.oasis-open.org Subject: [cti] TAXII 2.1 WD03 - CSD01 - Ballot   All,   Drew and I have finished resolving all of the comments and suggestions that came in for Working Draft 02 and today are releasing Working Draft 03. Please see the attached Word and PDF versions.  As editors we believe this version, Working Draft 03, is ready to advanced to Committee Specification Draft 01 (CSD 01).     MOTION: I motion that the TC accept TAXII 2.1 Working Draft 03 to be the version that we advance to Committee Specification Draft 01 and that the TC open a ballot to approve TAXII 2.1 Working Draft 03 as Committee Specification Draft 01.     TIMING: If this motion gets a second, the timing of the ballot will coincide as much as possible with the upcoming STIX 2.1 CSD01 ballot.   NOTES: The permission for the Google Doc version of Working Draft 03 ( https://docs.google.com/document/d/1EsiWY7TGqt9yH6QUXv4c-opXSr3wR0TDMt8Q0yJjpoo/edit# ) have been locked down, as this version moves towards a CSD.  If you have further comments or suggestions on this Working Draft, please send them to the list.  If this motion passes, I will create a new Working Draft 04 document in the coming days and set permissions on it as we begin work on CSD02.    Thanks Bret  

Marlon,


We do not currently define a user-agent string.  Please feel free to add an issue to the GitHub issue tracker for TAXII.  We can plan on addressing this on an upcoming working call.


Thanks 
Bret 

Sent from my Commodore 128D


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


On Jul 19, 2018, at 9:45 AM, Taylor, Marlon < Marlon.Taylor@hq.dhs.gov > wrote:







Hi Bret,
 
I thought the TAXII spec called out the ability for TAXII Clients to include their implementation and version within the http user-agent but I don t see it now.
Is that within the spec?
 
If not I think this is something we should include and will include a GITHUB ticket to support. This is generally a light lift for the TAXII clients and would
provide huge support for TAXII servers admins when trying to troubleshoot between various TAXII clients.
 
Let me know whether this is within the spec or not and I will provide something if needed.
 
Thanks,
 
-Marlon
 
 


From:
cti@lists.oasis-open.org [ mailto:cti@lists.oasis-open.org ]
On Behalf Of Bret Jordan
Sent: Thursday, July 12, 2018 12:25 PM
To: cti@lists.oasis-open.org
Subject: [cti] TAXII 2.1 WD03 - CSD01 - Ballot


 

All,
 
Drew and I have finished resolving all of the comments and suggestions that came in for Working Draft 02 and today are releasing Working Draft 03. Please see the attached Word and PDF versions. 
As editors we believe this version, Working Draft 03, is ready to advanced to Committee Specification Draft 01 (CSD 01).  
 
MOTION:
I motion that the TC accept TAXII 2.1 Working Draft 03 to be the version that we advance to Committee Specification Draft 01 and that the TC open a ballot to approve TAXII 2.1 Working Draft 03 as
Committee Specification Draft 01.  
 
TIMING:
If this motion gets a second, the timing of the ballot will coincide as much as possible with the upcoming STIX 2.1 CSD01 ballot.
 
NOTES:
The permission for the Google Doc version of Working Draft 03 ( https://docs.google.com/document/d/1EsiWY7TGqt9yH6QUXv4c-opXSr3wR0TDMt8Q0yJjpoo/edit# )
have been locked down, as this version moves towards a CSD.  If you have further comments or suggestions on this Working Draft, please send them to the list.  If this motion passes, I will create a new Working Draft 04 document in the coming days and set permissions
on it as we begin work on CSD02. 
 
Thanks
Bret
 

I added an item in GITHUB ( https://github.com/oasis-tcs/cti-taxii2/issues/86 ).   -Marlon   From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org] On Behalf Of Taylor, Marlon Sent: Thursday, July 19, 2018 9:45 AM To: Bret Jordan <Bret_Jordan@symantec.com>; cti@lists.oasis-open.org Subject: [SENDER UNVERIFIED][cti] RE: TAXII 2.1 WD03 - CSD01 - Ballot   Hi Bret,   I thought the TAXII spec called out the ability for TAXII Clients to include their implementation and version within the http user-agent but I don’t see it now. Is that within the spec?   If not I think this is something we should include and will include a GITHUB ticket to support. This is generally a light lift for the TAXII clients and would provide huge support for TAXII servers admins when trying to troubleshoot between various TAXII clients.   Let me know whether this is within the spec or not and I will provide something if needed.   Thanks,   -Marlon     From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org] On Behalf Of Bret Jordan Sent: Thursday, July 12, 2018 12:25 PM To: cti@lists.oasis-open.org Subject: [cti] TAXII 2.1 WD03 - CSD01 - Ballot   All,   Drew and I have finished resolving all of the comments and suggestions that came in for Working Draft 02 and today are releasing Working Draft 03. Please see the attached Word and PDF versions.  As editors we believe this version, Working Draft 03, is ready to advanced to Committee Specification Draft 01 (CSD 01).     MOTION: I motion that the TC accept TAXII 2.1 Working Draft 03 to be the version that we advance to Committee Specification Draft 01 and that the TC open a ballot to approve TAXII 2.1 Working Draft 03 as Committee Specification Draft 01.     TIMING: If this motion gets a second, the timing of the ballot will coincide as much as possible with the upcoming STIX 2.1 CSD01 ballot.   NOTES: The permission for the Google Doc version of Working Draft 03 ( https://docs.google.com/document/d/1EsiWY7TGqt9yH6QUXv4c-opXSr3wR0TDMt8Q0yJjpoo/edit# ) have been locked down, as this version moves towards a CSD.  If you have further comments or suggestions on this Working Draft, please send them to the list.  If this motion passes, I will create a new Working Draft 04 document in the coming days and set permissions on it as we begin work on CSD02.    Thanks Bret