header file contents

[Tim Hudson <tjh@cryptsoft.com>]

What I was trying (clearly rather unsuccessfully) to figure on the call
today was where we should be going to look for items to determine how to
fill in the identified gaps are and that depends on what your view point
is on what the definitive source (normative) text is when there is
missing content.

Other than the OASIS specification documents for v2.40 we have as source
material the original v2.30 draft documents contributed by RSA/EMC in
March 2013 *and *the v2.30 draft header files also contributed by
RSA/EMC which Bob uploaded way back in June 2013 at
https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/49510/latest/PKCS11_v2.40_header_files_wd01.zip

I've gone through all the items noted by Stef at
https://wiki.oasis-open.org/pkcs11/Definitions and updated them having
looked at each to see where the items first appeared in the various
specification versions and/or header files and included notes on that
information and a suggestion as to the path forward.

I've only processed the missing values in the last section to look for
clashes and haven't updated those noting where they are defined in
previous versions as yet (i.e. that information was only extracted for
the list against each document not for the missing items list at the
end).  Where items would qualify for an errata I've noted that for
reference.

I have also included the two items from Jaroslav Imrich that included a
suggestion to include both the correct and incorrect names for two
constants in the header files (added at the end).

It appears that none of the proposed header file versions (Stef, Oscar,
Dina) were produced by working forward from the v2.30 header files for
various reasons and for at least a few items we have directly clashing
numeric values being proposed.

My assumptions going forward are:
1) where there is content missing from the specification that needs to
go into the header files for actual use that any values defined already
in the v2.30 header files Bob uploaded should be seen as the "correct"
value to use
2) if we find an issue with any of the v2.30 header file contents then
we should step back to the v2.20 header files and resolve using those
given that RSA did not publish a version of the v2.30 header files on
the RSA web site back during the original v2.30 specification work
3) for the final header files where we have information that is not in
the specification text then we need to update the specification text so
that there is no clash of content for a subsequent version

Our previous TC discussions were about getting out header files rapidly
and also quickly getting out an v2.41 update that sorts out the issues
identified with relatively minimal other changes.

Tim.