Content_Binding fields need to be made a required field

[jordan2175]

We need to make the content_binding fields a required field for at least the discovery and collection information response messages.

[terrymacdonald]

Hi Bret,

Do you mean that we need to have a content_binding field for each of the
services listed in the responses for the discovery and collection response
messages (e.g. Supported_Content/Subtype field on Collection Information
Response), or that there needs to be a content_binding field in the TAXII
Header?

Cheers
Terry MacDonald

On 23 May 2015 at 04:48, jordan2175 notifications@github.com wrote:

We need to make the content_binding fields a required field for at least
the discovery and collection information response messages.

—
Reply to this email directly or view it on GitHub
#80.

[jordan2175]

@terrymacdonald I think the content_binding fields that we have are good for now, we just need to make them required.

[terrymacdonald]

@jordan2175 thanks for the clarification. I would agree that they should be
required.

Cheers
Terry MacDonald

On 23 May 2015 at 10:37, jordan2175 notifications@github.com wrote:

@terrymacdonald https://github.com/terrymacdonald I think the
content_binding fields that we have are good for now, we just need to make
them required.

—
Reply to this email directly or view it on GitHub
#80 (comment)
.