Reverting to "new" for disposition by working group.

Agreed that the text will be updated to describe the order of precedence.

Added text to CertificateList indicating that the ValidationOptions are ORed together in RC 1.02.10.

Reviewed text in telecon – agreed to this, but Nate should review before closing.

CMPWG 5/10/2012:

We reviewed the text and have several requests/suggestions:

1. The text in D6 should (when the text has been finalized) be copied to D5.
2. The numbers for CertificationValidationOptions should be padded to look like 32-bit values (currently resembles 16-bit).

We are also unsure of the proposed logic. When you review D6 we have 2 categories of options, the top-3 are for suppressing messages, whereas the bottom-2 are for configuring behavior. Therefore, we think that there should be a difference in how they are administered and have 3 possible suggestions for consideration:

a) top-3 items should be AND'ed, whereas bottom-2 should be OR'ed.
b) In addition with (a), change the bottom-2 bits to be in the high-word.
c) break-apart these value into 2 different bitmasks.

Added a UseDefaultOptions to ValidationOptions enum.

Added text that indicates that the CertificateList options only apply to Certifictates with the UseDefaultOptions bit set.

The data type is clearly an Int32. There is no need to pad with extra zeros.

Changed ValidationOptions to use bit number instead of numeric value to be consistent with how other bit masks are described in Part 4.

Reviewed and made online edits in 1.02.13 and agreed to changes.