Proposal - Create New Message Types

[jordan2175]

After spending a lot of time working through the logic, and discussing similar things on the github issue tracker, I would like to propose the creation of two new TAXII message and then the future deprecation of the following 4 TAXII messages. As this will not result in a breaking change, as systems today would just ignore the new message, I propose that we do this for TAXII 1.2.

The reason for this change is the discovery messages and collection information messages are really two sides of the same coin, and you really need both to do anything with TAXII as everything is done by a collection name.

Two New Messages

info_request
    id
    options

info_response
    id
    in_response_to
    options
    version         // TAXII Version
    supported_queries
    collections
        name
        description
        available       // TRUE / FALSE
        type            // FEED / SET
        volume
        delivery_parameters
            protocol
            encodings
            content_encodings
            message
        poll_services
            protocol
            address
            encodings
            content_encodings
            message
        inbox_services
            protocol
            address
            encodings
            content_encodings
            message
        subscription_services
            protocol
            address
            encodings
            message
        message
    signature

Messages to Deprecate in TAXII 2.0
discovery_request
discovery_response
collection_information_request
collection_information_response