Darren (and friends),
I believe the intent of using MAX as a size limit is to encourage dynamic
allocation of these fields. If the group decides that setting hard-coded
max values is more advantageous than using MAX, then I would recommend the
following limits (these are guestimates of upper limits; the guessing part
is the disadvantage of setting hard-coded maximiums):
ContentHints ::= SEQUENCE {
contentDescription UTF8String SIZE (1..128) OPTIONAL,
contentType ContentType }
ESSPrivacyMark ::= CHOICE {
pString PrintableString SIZE (1..ub-privacy-mark-length),
utf8String UTF8String SIZE (1..128)
}
MLReceiptPolicy ::= CHOICE {
none [0] NULL,
insteadOf [1] SEQUENCE SIZE (1..64) OF GeneralNames,
inAdditionTo [2] SEQUENCE SIZE (1..64) OF GeneralNames }
- John Pawling