support for X509 V1 certificates

[Ron Monzillo <Ronald.Monzillo@Sun.COM>]

Does the x509 token profile standardize an interoperable
encapsulation of  an X.509 V1 certificate in a BinarySecurityToken?

It appears that support for the Certificate Path and PKCS7 token types is
not required, so it would appear that there is no required support for 
V1 certificates;
either by themselves, or in one of the multiple certificate forms. Is 
this true?

Standard identifiers for V1 certificates can be included in STRs but
the profile does not appear to standardize a token type to identify a V1
certificate encapsulated in a Binary Security token.

Thus, it doesn't seem like the profile defines an interopable way to send a
V1 cert in a wsse:security header, only how to reference one.

Can someone provide the rational for leaving out V1 certificates from the
token types (that can be encapuslated in a binary security token)?

Thanks