OASIS Open

QuintessenceLabs Pty Ltd.

No

This proposal has several design flaws that must be addressed before accepting into the standard. The major flaws are:
1. Requires that the server maintain state between client requests using undefined, non-interoperable, and vendor-dependent mechanisms;
2. Severely limits streaming performance by requiring the client to manage sequential delivery of each streaming part. Full round-trip network delays are necessary between each message part; and
3. Builds on the flawed crypto proposal of 1.2; i.e. allows a client to override the server in how to use a managed key (e.g. mode, or padding). This is inconsistent with the key wrapping specification which clearly disallows this, and requires the server to return an error when a client attempts to do this.