[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [cti] TAXII 2.1 CS Motion
Hi Bret, Yes, there have been several proposals submitted to address these concerns however the TC has not evaluated them. The has made great progress while in the others areas and now has the opportunity to refocus on this area. During previous
meetings including Face-to-Face sessions, the TC agreed to include these use-cases within TAXII 2.1. While you may see no convergence in sight, TC members are actively at work (providing proposals, software implementations, etc.) to resolve this this concern within TAXII 2.1 so I wouldnât agree there is a TC wide-census to send TAXII 2.1
as is. It would be an injustice to the TC and TAXII community to move toward as a CS knowing the current situation and not trying to evaluate and resolve them within the TC before going release. -Marlon From: cti@lists.oasis-open.org <cti@lists.oasis-open.org>
On Behalf Of Bret Jordan Marlon, Thank you for your comments. However, to level set, right now we have three competing ideas / proposals for adding this type of functionality to TAXII and no convergence in sight. In order to get a solution that works for all parties,
my best guess is that it would be 5-6 months of work and testing. While I personally would have liked to see this get done 12 months ago, we did not then, nor do we now have consensus in the TC to add anything else to TAXII. What we do have is TC wide consensus to ship TAXII 2.1 as is. Keep in mind we
have done 4 CSDs and 3 public reviews, and the TC as a whole is not saying that TAXII 2.1 needs anything else. This is also why I proposed that we work on a solution that we could release as a standalone specification after TAXII 2.1 ships. Maybe call it TAXII 2.1 Query or something like that. To do this we would need to find a solution that works
for all parties so we can have TC wide consensus on the solution. If we went this route, then we can release TAXII 2.1 now, release the TAXII 2.1 Query specification whenever it gets done, and then fold that Query specification in to TAXII 2.2 whenever we
start that work. Thanks, Bret 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 Thu, Jan 9, 2020 at 12:06 PM Taylor, Marlon <Marlon.Taylor@cisa.dhs.gov> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]