Re: [cti-taxii] Backwards compatibility with TAXII 1.1 in discovery

Subject: Re: [cti-taxii] Backwards compatibility with TAXII 1.1 in discovery

I think we just support TAXII 2.0. There are already software packages people can use to interact using TAXII 1.x. If someone needs to use TAXII 1.x then it's easiest for everyone if we make that system independent of the TAXII 2.0/STIX 2.0 eco system.

The fact is that if someone is interacting with a TAXII 2.0 server, then they will support STIX 2.0, and won't want to access less descriptive STIX 1.x content over a TAXII 1.x connection.

There only time someone will need to access TAXII 1.x content is when they don't support TAXII 2/STIX 2, which means they won't need the ability to be redirected to TAXII 1.x during discovery. It's functionality that's not required.

On 10 Oct. 2016 23:51, "Eric Burger" <Eric.Burger@georgetown.edu> wrote:

Does anyone use TAXII 1.x? If the answer is No, you have your answer. If the answer is Yes, but only for experimental use, then you have an indication of an answer. If the answer is Yes, then we have to ask if our reputation of ripping out everything you think works right when you start using it will be yet again reinforced, to the point that sensible people will stop hitting their head against the wall and use RID instead.

On Oct 9, 2016, at 5:59 PM, Bret Jordan (CS) <Bret_Jordan@symantec.com> wrote:

Should TAXII 2.0 provide support for advertising TAXII 1.1.1 services via the new TAXII 2.0 Discovery API? If it should, then we need to try and figure out what that would look like and how that would work.

Personally I question the value of this for an MVP release of TAXII 2.0. I also question the need of a TAXII 2.0 implementer to advertise services that are running under TAXII 1.1.1...

I am curious to know your thoughts.

Bret

cti-taxii message