Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / taxiiproject/taxii-specifications issues and pull requests

#92 - taxii/stix2.0 open servers

Issue - State: closed - Opened by Ari-Roda over 6 years ago

#91 - Update README.md

Pull Request - State: closed - Opened by rroberge about 9 years ago

#90 - trademarks need to be reviewed

Issue - State: closed - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#89 - [Content Binding] Acknowledgements needs to be updated

Issue - State: closed - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#88 - [Content Binding] Should be version 4 (not version 3)

Issue - State: closed - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#87 - [Content Binding] Should be updated to include STIX 1.2 and STIX 1.2.1

Issue - State: open - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#86 - [Services Spec] Version ID should end in “:1.1.1” instead of “-1.1.1”

Issue - State: closed - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#85 - Copyright statement need to be updated

Issue - State: closed - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#84 - Need to update acknowledgements

Issue - State: closed - Opened by MarkDavidson over 9 years ago
Labels: TAXII 1.1.1

#83 - Version 2.0 Requirements - Add Security

Issue - State: closed - Opened by packet-rat over 9 years ago - 1 comment

#82 - Document Requirements

Issue - State: open - Opened by MarkDavidson over 9 years ago - 1 comment

#80 - Content_Binding fields need to be made a required field

Issue - State: open - Opened by jordan2175 over 9 years ago - 3 comments

#79 - Remove designation of TAXII headers

Issue - State: open - Opened by jordan2175 over 9 years ago

#78 - Rename query to supported_queries in section 3.7

Issue - State: open - Opened by jordan2175 over 9 years ago

#77 - Proposal - Create New Message Types

Issue - State: open - Opened by jordan2175 over 9 years ago

#76 - Message Binding issues in Collection Information Response

Issue - State: open - Opened by jordan2175 over 9 years ago

#75 - Proposal - Build TAXII Certification Levels

Issue - State: open - Opened by jordan2175 over 9 years ago

#73 - Specify a maximum size for TAXII Messages

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 2 comments

#72 - ambiguity of the available attribute

Issue - State: open - Opened by walters301 almost 10 years ago - 2 comments

#71 - Services specification content block references "Section 0"

Issue - State: open - Opened by jordan2175 almost 10 years ago

#70 - new X-TAXII-Content-Types header for automatic version negotiation

Issue - State: open - Opened by traut almost 10 years ago - 5 comments

#70 - new X-TAXII-Content-Types header for automatic version negotiation

Issue - State: open - Opened by traut almost 10 years ago - 5 comments

#69 - Add Time Zone requirements to Services Spec

Issue - State: open - Opened by MarkDavidson almost 10 years ago

#68 - Inconsistant naming in services spec and xml spec

Issue - State: open - Opened by jordan2175 almost 10 years ago - 1 comment

#67 - Remove "message" field intended for human eyes from the specification

Issue - State: open - Opened by traut almost 10 years ago - 4 comments

#66 - Proposal: Reconsider the use of URI formatting

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 1 comment

#65 - Proposal: Modify Extended Headers

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 6 comments

#64 - Proposal: Desired Polling Interval

Issue - State: open - Opened by MarkDavidson almost 10 years ago

#63 - Digital Signatures

Issue - State: open - Opened by MarkDavidson almost 10 years ago

#62 - Discussion: Format Changes/Additions

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 2 comments

#61 - Typeo in 3.9 XML Message Binding

Issue - State: open - Opened by jordan2175 almost 10 years ago

#60 - Address TAXII FAQ Items

Issue - State: open - Opened by MarkDavidson almost 10 years ago

#59 - Proposal: Revise TAXII Query

Issue - State: open - Opened by MarkDavidson almost 10 years ago

#58 - Proposal: Make TAXII more discoverable

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 6 comments

#57 - Proposal: Identify a core set of required functionality (use cases)

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 1 comment

#56 - Proposal: Data Model and Naming Changes

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 22 comments

#55 - Proposal: Remove Content Binding IDs for MIME Types

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 15 comments

#54 - Proposal: HTTP Protocol Simplification

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 1 comment

#53 - Error in XML message binding spec

Issue - State: closed - Opened by jordan2175 almost 10 years ago - 4 comments

#52 - Error in documentation for sample messages

Issue - State: closed - Opened by jordan2175 almost 10 years ago - 1 comment

#51 - TAXII Message IDs

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 1 comment

#50 - Evolve Generic MessageBinding Template

Issue - State: open - Opened by MarkDavidson almost 10 years ago

#49 - Clarify certain HTTP error conditions

Issue - State: open - Opened by MarkDavidson almost 10 years ago - 1 comment

#48 - Need consistant pluralization

Issue - State: open - Opened by jordan2175 almost 10 years ago

#47 - Look into signature options

Issue - State: open - Opened by MarkDavidson about 10 years ago - 1 comment

#46 - Query XML Schema does not enforce all Criteria must come before all Criterion

Issue - State: open - Opened by jasenj1 over 10 years ago
Labels: bug

#45 - TAXII Query negate operator definition is circular

Issue - State: open - Opened by MarkDavidson over 10 years ago

#44 - It doesn't always make sense to specify in_response_to in a Status Message

Issue - State: open - Opened by MarkDavidson over 10 years ago - 1 comment

#43 - Data Sets

Issue - State: closed - Opened by MarkDavidson about 11 years ago - 1 comment
Labels: services specification, xml specification, implementation consensus

#42 - Feed Volume Awareness

Issue - State: closed - Opened by MarkDavidson about 11 years ago - 1 comment
Labels: services specification, xml specification, implementation consensus

#41 - Content Binding ID Subtypes

Issue - State: closed - Opened by MarkDavidson about 11 years ago - 1 comment
Labels: services specification, xml specification, implementation consensus

#40 - Message Field in Content Blocks

Issue - State: closed - Opened by MarkDavidson about 11 years ago - 1 comment

#39 - Asynchronous Polling

Issue - State: closed - Opened by MarkDavidson about 11 years ago - 1 comment
Labels: services specification, xml specification, implementation consensus

#38 - Control of Result Types

Issue - State: closed - Opened by MarkDavidson about 11 years ago - 1 comment
Labels: services specification, xml specification, implementation consensus

#37 - Consider changing 'Timestamp Label' to 'Sequence ID'

Issue - State: open - Opened by terrymacdonald about 11 years ago - 5 comments

#36 - Update 1.1 specs per the 1.0 errata

Issue - State: closed - Opened by MarkDavidson over 11 years ago - 1 comment
Labels: http specification, xml specification

#35 - Python lxml validation issue

Issue - State: closed - Opened by scottquint over 11 years ago - 7 comments

#34 - Consider adding more role-focused information regarding Subscriptions

Issue - State: open - Opened by bworrell over 11 years ago - 1 comment
Labels: enhancement, services specification

#33 - Poll Request's timestamps required by Services spec but optional in XML spec

Issue - State: closed - Opened by bworrell over 11 years ago - 2 comments
Labels: bug, services specification, xml specification

#32 - Clarify an Inbox getting unsupported content

Issue - State: open - Opened by MarkDavidson over 11 years ago
Labels: enhancement, services specification

#31 - Clarify contract that TAXII Binding specifications need to meet

Issue - State: open - Opened by cmschmidt over 11 years ago - 1 comment
Labels: enhancement, services specification

#30 - Dedicated error type for Protocol Errors

Issue - State: closed - Opened by cmschmidt over 11 years ago - 1 comment
Labels: enhancement, services specification, xml specification

#29 - Add CAP 1.2 to the Content Binding Reference

Issue - State: closed - Opened by MarkDavidson over 11 years ago - 1 comment
Labels: content binding ref

#28 - Add a field to allow a data sender to designate a targeted data feed on the recipient

Issue - State: closed - Opened by cmschmidt over 11 years ago - 4 comments
Labels: enhancement, services specification, xml specification, implementation consensus

#27 - Make the <Content_Block> mandatory in Inbox Messages

Issue - State: closed - Opened by cmschmidt over 11 years ago - 2 comments
Labels: wontfix

#26 - Make the <Inclusive_End_Timestamp> field optional in Poll Response messages

Issue - State: closed - Opened by cmschmidt over 11 years ago - 3 comments
Labels: enhancement, wontfix, xml specification

#25 - Have all Begin Timestamp fields be inclusive or exclusive (instead of a mix)

Issue - State: closed - Opened by cmschmidt over 11 years ago - 3 comments
Labels: enhancement, services specification, xml specification, implementation consensus

#24 - Re-add PAUSE and RESUME actions for subscription management

Issue - State: closed - Opened by cmschmidt over 11 years ago - 5 comments
Labels: enhancement, services specification, xml specification, implementation consensus

#23 - Expand characters allowed in Message ID and Subscription ID fields

Issue - State: closed - Opened by cmschmidt over 11 years ago - 4 comments
Labels: enhancement, services specification, xml specification, implementation consensus

#22 - Possibly change TAXII Error Message to TAXII Status Message

Issue - State: closed - Opened by MarkDavidson almost 12 years ago - 1 comment
Labels: enhancement, services specification, http specification, xml specification

#21 - GET requests should not require Content-Type or X-TAXII-Content-Type

Issue - State: closed - Opened by MarkDavidson almost 12 years ago - 2 comments
Labels: bug, http specification

#20 - HTTP Protocol Binding - Possibly change 5.1.4 to GET instead of POST

Issue - State: closed - Opened by MarkDavidson almost 12 years ago - 9 comments
Labels: http specification

#19 - Standard Discovery Service location

Issue - State: closed - Opened by cmschmidt about 12 years ago - 2 comments
Labels: enhancement, services specification, http specification

#18 - PENDING Error Messages

Issue - State: closed - Opened by cmschmidt about 12 years ago - 1 comment
Labels: bug, services specification

#17 - Allow clients to dictate rate-limiting of responses

Issue - State: open - Opened by cmschmidt about 12 years ago - 7 comments
Labels: enhancement, services specification, http specification

#16 - Multiple issues surrounding timestamp labels

Issue - State: closed - Opened by cmschmidt about 12 years ago - 1 comment
Labels: bug, enhancement, services specification, xml specification

#15 - Expand payload types in TAXII messages

Issue - State: closed - Opened by cmschmidt about 12 years ago - 2 comments
Labels: enhancement, services specification

#14 - HTTP Protocol Binding - Proposal to remove X-TAXII-Accept header

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment
Labels: enhancement

#13 - Query

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment
Labels: enhancement, services specification, xml specification

#12 - TAXII Inbox Message

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 2 comments
Labels: question, services specification

#11 - Message Manifests

Issue - State: open - Opened by MarkDavidson about 12 years ago - 1 comment
Labels: services specification

#10 - XML Message Binding - XML DSIG / Encryption

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 2 comments
Labels: enhancement, xml specification

#9 - Services Specification - Timestamps

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment
Labels: bug, services specification

#8 - Feed information and management must use same protocol

Issue - State: closed - Opened by cmschmidt about 12 years ago - 1 comment
Labels: bug

#7 - No automated way to identify desired poll service

Issue - State: closed - Opened by cmschmidt about 12 years ago - 2 comments
Labels: bug, services specification

#6 - HTTP Protocol Binding - Discuss Section 7

Issue - State: closed - Opened by MarkDavidson about 12 years ago
Labels: question

#5 - HTTP Protocol Binding - Changes to Section 5

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment

#4 - HTTP Protocol Binding - Change 'get parameters' to 'query parameters'

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment

#3 - HTTP Protocol Binding - Changes to Accept header

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment

#2 - HTTP Protocol Binding - Change name of 'TAXII Media Type'

Issue - State: closed - Opened by MarkDavidson about 12 years ago - 1 comment

#1 - Wording change in Services Spec Section 4.2.5

Issue - State: closed - Opened by MarkDavidson about 12 years ago
Labels: services specification