Currently, YETI prohibits Destination_Collection_Name and instead uses URLs to allow clients to indicate which Data Collection they are pushing to. This is a holdover from TAXII 1.0, and YETI should probably be updated to use the Destination Collection Name concept.
Currently, YETI prohibits Destination_Collection_Name and instead uses URLs to allow clients to indicate which Data Collection they are pushing to. This is a holdover from TAXII 1.0, and YETI should probably be updated to use the Destination Collection Name concept.