Re: SCVP 16 comments deadline

[Peter Sylvester <Peter.Sylvester@xxxxxxxxxx>]

There are several boolean values like

  ValidationPolicy ::= SEQUENCE { 
    ...
    inhibitPolicyMapping  [2] BOOLEAN OPTIONAL, 

and a policy definition. 

  ValidationPolValues ::=SEQUENCE  { 
    ...
    inhibitPolMap            BOOLEAN, 


- It would be nice to use the same field names.

- I suggest BOOLEAN DEFAULT FALSE for the inhibitPolMap together
  with some apppropriate tagging, it doesn't make much sense to
  me to code useless values. 

Would it be possible to add some statement about the intended
meaning of the 6 possible combination:


inhibitPolMap = FALSE 

inhibitPolicyMapping absent  1
                     FALSE   2
                     TRUE    3

inhibitPolMap = TRUE 

inhibitPolicyMapping absent  4
                     FALSE   5
                     TRUE    6


Does it mean that when the client value takes preceedence over the
server value? 

1 = FALSE
2 = FALSE
3 = TRUE
4 = TRUE
5 = FALSE
6 = TRUE


It had been said some time ago (as far as I remember) that these
inputs are not global ones but in principle for each of the
certs to be asked for. what was the conclusion why they stay global
for all certs?