OASIS Cyber Threat Intelligence (CTI) TC

 View Only
  • 1.  Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products

    Posted 10-06-2015 18:56







    I would like to formally make a motion that we make no decisions on default or MTI serialization bindings for CTI TC work products until we have consensus
    on requirements and evaluation criteria, identification and understanding of potential options and understanding of how each option does or does not meet the consensus requirements and evaluation criteria.




    Sean Barnum
    OASIS CTI TC / STIX SC Co-chair










  • 2.  Re: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products

    Posted 10-06-2015 19:02
    I second the motion. Patrick Maroney President Integrated Networking Technologies, Inc. Desk: (856)983-0001 Cell: (609)841-5104 Email: pmaroney@specere.org On Tue, Oct 6, 2015 at 11:56 AM -0700, "Barnum, Sean D." < sbarnum@mitre.org > wrote: I would like to formally make a motion that we make no decisions on default or MTI serialization bindings for CTI TC work products until we have consensus on requirements and evaluation criteria, identification and understanding of potential options and understanding of how each option does or does not meet the consensus requirements and evaluation criteria. Sean Barnum OASIS CTI TC / STIX SC Co-chair


  • 3.  RE: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products

    Posted 10-06-2015 19:08
    Thank you Sean / Patrick.  I will await Chet and OASIS’s feedback on the period of debate / discussion required, but we will take a vote on this motion ASAP.   Alex   From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org] On Behalf Of Patrick Maroney Sent: Tuesday, October 06, 2015 3:02 PM To: cti@lists.oasis-open.org; Barnum, Sean D. Subject: Re: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products   I second the motion. Patrick Maroney President Integrated Networking Technologies, Inc. Desk: (856)983-0001 Cell: (609)841-5104 Email: pmaroney@specere.org   On Tue, Oct 6, 2015 at 11:56 AM -0700, "Barnum, Sean D." < sbarnum@mitre.org > wrote:   I would like to formally make a motion that we make no decisions on default or MTI serialization bindings for CTI TC work products until we have consensus on requirements and evaluation criteria, identification and understanding of potential options and understanding of how each option does or does not meet the consensus requirements and evaluation criteria.     Sean Barnum OASIS CTI TC / STIX SC Co-chair This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.


  • 4.  RE: Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products

    Posted 10-06-2015 21:38




    I agree with this 110%… but do we really need to make a motion to
    not do something?  I would hate to waste time on a voting process for that sort of thing.
     


    From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org]
    On Behalf Of Barnum, Sean D.
    Sent: Tuesday, October 06, 2015 2:56 PM
    To: cti@lists.oasis-open.org
    Subject: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products


     



     


    I would like to formally make a motion that we make no decisions on default or MTI serialization bindings for CTI TC work products until we have consensus on requirements and evaluation criteria,
    identification and understanding of potential options and understanding of how each option does or does not meet the consensus requirements and evaluation criteria.


     


     


    Sean Barnum


    OASIS CTI TC / STIX SC Co-chair




    DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses.  The company accepts no liability for any damage caused by any virus transmitted by this email.




  • 5.  Re: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products

    Posted 10-07-2015 09:11
    If we promise not to vote for  an MTI at this time , then that is a good enough ‘vote’. BTW, I will eventually insist we have an MTI, whatever it will be. Otherwise, all we are doing is a branding effort for vendors to call their proprietary implementations “standard and not  interoperable. On Oct 6, 2015, at 5:35 PM, Bush, Jonathan < jbush@DTCC.COM > wrote: I agree with this 110%… but do we really need to make a motion to not do something?  I would hate to waste time on a voting process for that sort of thing.   From: cti@lists.oasis-open.org [ mailto:cti@lists.oasis-open.org ] On Behalf Of Barnum, Sean D. Sent: Tuesday, October 06, 2015 2:56 PM To: cti@lists.oasis-open.org Subject: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products     I would like to formally make a motion that we make no decisions on default or MTI serialization bindings for CTI TC work products until we have consensus on requirements and evaluation criteria, identification and understanding of potential options and understanding of how each option does or does not meet the consensus requirements and evaluation criteria.     Sean Barnum OASIS CTI TC / STIX SC Co-chair DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses.  The company accepts no liability for any damage caused by any virus transmitted by this email. Attachment: smime.p7s Description: S/MIME cryptographic signature


  • 6.  Re: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products

    Posted 10-07-2015 21:08
    Completely agree. Cheers Terry MacDonald On 7/10/2015 8:10 pm, "Eric Burger" < Eric.Burger@georgetown.edu > wrote: If we promise not to vote for  an MTI at this time , then that is a good enough ‘vote’. BTW, I will eventually insist we have an MTI, whatever it will be. Otherwise, all we are doing is a branding effort for vendors to call their proprietary implementations “standard and not  interoperable." On Oct 6, 2015, at 5:35 PM, Bush, Jonathan < jbush@DTCC.COM > wrote: I agree with this 110%… but do we really need to make a motion to not do something?  I would hate to waste time on a voting process for that sort of thing.   From: cti@lists.oasis-open.org [ mailto:cti@lists.oasis-open.org ] On Behalf Of Barnum, Sean D. Sent: Tuesday, October 06, 2015 2:56 PM To: cti@lists.oasis-open.org Subject: [cti] Formal motion regarding selection of default or MTI serialization bindings for CTI TC work products     I would like to formally make a motion that we make no decisions on default or MTI serialization bindings for CTI TC work products until we have consensus on requirements and evaluation criteria, identification and understanding of potential options and understanding of how each option does or does not meet the consensus requirements and evaluation criteria.     Sean Barnum OASIS CTI TC / STIX SC Co-chair DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses.  The company accepts no liability for any damage caused by any virus transmitted by this email.