Comments (7)
F2F consensus was to rename to taxii2
from cti-taxii2.
If we do this, we should probably drop the concept of DNS SRV records for discovery since that would be two ways of doing the same thing.
from cti-taxii2.
As there was some objection to /taxii/ I'll point out that there is /.well-know/ defined by https://tools.ietf.org/html/rfc5785 that helps address this.
Not sure that NAPTR is the correct solution as it is targeted to SIP internet telephony. Unless more definition is provided around usage of NAPTR, I can't see it being a viable option.
from cti-taxii2.
We talked about this briefly on the working call on 2018-01-23 and we agreed that we need to look in to this and that we will discuss again on a future working call.
from cti-taxii2.
During interoperability testing, the CTI TC learned that the /taxii/ URL conflicts with existing product URLs. The conflict prevents effective implementation of TAXII2 for existing products, which is undesirable.
The proposed solution is to change the DiscoveryURL from /taxii/ to /taxii2/. While this change breaks backward compatibility, the estimated impact is small. Servers supporting both TAXII 2.0 and TAXII 2.1 can easily support both URLs through aliasing. Servers that can not use the /taxii/ URL can now use the /taxii2/ URL. Clients that support both TAXII 2.0 and TAXII 2.1 may have to try multiple URLs for discovery to succeed.
This change will also help distinguish TAXII 2.
from cti-taxii2.
Suggested changes have been added to the document.
from cti-taxii2.
These changes were made in the following sections:
3.1
4
4.1
4.1.1
8.2.1
from cti-taxii2.
Related Issues (20)
- Rename the spec_versions url filter parameter to be singular HOT 1
- Make the TAXII Envelope contain a list of objects not a bundle HOT 2
- Add text to explain status counts when server has yet to start processing request HOT 1
- Consider renaming the status value of pending to processing HOT 1
- What is the purpose of Discovery API roots having different domains in the list of api_roots ? HOT 2
- API Root Resource does not define the URL of the resource? HOT 2
- Typo in url prop of section 5.4 HOT 2
- Change integer to be 54 bits in size per RFC 7493 HOT 1
- If collections permission has false for CanRead and CanWrite, does user have permissions to see existence of Collection?
- RFE: Add additional Supported Fields to TAXII Filtering HOT 1
- Potential confusion with errors when adding duplicate objects
- Potential Confusion on Get Object Manifests
- Potentially misleading table in TAXII spec
- Typos in the TAXII spec
- Manifest & Versions Resource missing `next` Property HOT 1
- Additional URL query parameters
- Match field formatting
- "Incorrect" Spelling
- TAXII filtering is ambiguous when handling spec_version and version match fields
- Advanced filtering capability
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cti-taxii2.