Re: [cti-taxii] Two outstanding issues for TAXII 2.1 WD02

My opinion is already in the tracker. Agree that it’s fine to leave mandatory in interop for all but the TXF persona (the one where the server is just providing data, not accepting
  it).
Commented in Github.
From:
<> on behalf of "Bret Jordan (CS)" <>
Date:  Thursday, May 17, 2018 at 12:22 PM
To:  "" <>
Subject:  [cti-taxii] Two outstanding issues for TAXII 2.1 WD02



All,



As I mentioned on the full TC call today, we have two outstanding issues we would like to try and get included in working draft 2 (WD02).  This working draft would be
  the one we will hopefully submit for a CSD ballot..  Please respond to this email with your views on these topics, so we can understand what the TC would like the Editors to do.





1) Relaxing the TAXII authentication requirement to a SHOULD instead of a MUST for implementing basic authentication. On the last working call we had
  a slight preference for doing this. However, there was no consensus.  Would it help to get consensus to do this if we said that the interpretability documents still required it for nearly all personas?



I personally do not have a pony in this race, so I do not care either way. I am just trying to help find a solution that works for this TC. This issue
  can be found here: https://github.com/oasis-tcs/cti-taxii2/issues/58





2) Allow TAXII to process records in synchronous mode instead of just asynchronous.  This means, that we would allow HTTP status code of 200 (OK) for
  POSTs not just 202 (Accepted). We talked about this on the last working call and there was no consensus either way, it was about 50/50.  It was pointed out on the call that technically you could process all of the content synchronously and return a 202(Accepted)
  with a Status resource that showed everything was added.  However, this feels a bit ugly when the HTTP 200(OK) response was designed just for that purpose.



This issue can be found here:
https://github.com/oasis-tcs/cti-taxii2/issues/71



Thanks

Bret