Support Negotiations

["Jordan, Bret" <bret.jordan@bluecoat.com>]

Eric posted this request for TAXII on the STIX list...

#BEGIN

I would also strongly suggest that we adopt (in TAXII) a negotiation mechanism. For examples, see HTTP (the accept and 

require headers), SMTP (the server listing out everything optional it supports and leaving it up to the client to pick from the list), and SIP (offer / answer, where the client offers capabilities, the server picks what it supports from the list, and the client agrees (or not)). If we have a negotiation mechanism, then people’s code gets a lot less complicated. You know up front what you will and will not do. Anything outside the boundaries then gets gracefully handled.

#END

Thanks,

Bret

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail