[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] STIX Subcommittee Nomination
So, the typical way of doing this would be to have a single STIX SC with multiple work product efforts (e.g. STIX 1.x & STIX 2.0) underway with different editors and contributors.
This provides the coordination and communication Aharon describes as well as the separate focus that Bret, et al, describe.
This is true of almost all SDOs and I think still meets the objectives you are all conveying here.
sean
From: Joep Gommers <joep@intelworks.com>
Date: Thursday, June 18, 2015 at 3:33 PM To: "Jordan, Bret" <bret.jordan@bluecoat.com>, Aharon Chernin <achernin@soltra.com> Cc: "tony@yaanatech.com" <tony@yaanatech.com>, "mona.magathan@usbank.com" <mona.magathan@usbank.com>, "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] STIX Subcommittee Nomination I can also see some advantage with regards to focus. Separate work stream with separate cadence, leadership expertise, etc might be helpful. J-
From: "Jordan, Bret" <bret.jordan@bluecoat.com>
Date: Thursday, June 18, 2015 at 9:26 PM To: Aharon Chernin <achernin@soltra.com> Cc: "tony@yaanatech.com" <tony@yaanatech.com>, "mona.magathan@usbank.com" <mona.magathan@usbank.com>, "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] STIX Subcommittee Nomination
The same people may be on both subcommittees. By breaking them up this allows each subcommittee to focus on different things. There are some people that will not care about STIX 1.3 and some that will not care about STIX 2.0
Thanks,
Bret
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
Blue Coat Systems
PGP Fingerprint: 62A6 5999 0F7D 0D61 4C66 D59C 2DB5 111D 63BC A303
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]