Format of errata statements in KMIP V1.1 Errata

["Griffin, Robert" <robert.griffin@rsa.com>]

Hi –

 

I’m thinking to use the same format for the KMIP V1.1 Errata as SAML used (http://docs.oasis-open.org/security/saml/v2.0/sstc-saml-approved-errata-2.0.html) . See below for an example (for discussion in our call today).

 

Thanks!

Bob

 

 

2       Approved Errata

Following are the approved errata to the SAML V2.0 OASIS Standard.

E0: Incorrect Section Reference

Change [SAMLCore] at line 2660 to refer to section 3.7.3 rather than 3.6.3 for Reason codes. This was a typographical error.

E1: Relay State for HTTP Redirect

Change [SAMLBind] Section 3.4.3 at lines 551-553 to reflect the fact that, indeed, the RelayState parameter is covered by the query string signature described in Section 3.4.4.1 (DEFLATE encoding). Note that Section 3.5.3, which has similar original wording, remains correct for its case.

Original:

RelayState data MAY be included with a SAML protocol message transmitted with this binding. The value MUST NOT exceed 80 bytes in length and SHOULD be integrity protected by the entity creating the message. Signing is not realistic given the space limitation, but because the value is exposed to third-party tampering, the entity SHOULD insure that the value has not been tampered with by using a checksum, a pseudo-random value, or similar means.

New:

RelayState data MAY be included with a SAML protocol message transmitted with this binding. The value MUST NOT exceed 80 bytes in length and SHOULD be integrity protected by the entity creating the message, either via a digital signature (see Section 3.4.4.1) or by some independent means.