Re: I-D ACTION:draft-ietf-pkix-pi-08.txt

["Anders Rundgren" <[e-mail]>]

>It is my hope that PI will become an RFC in the near future, so
>that certificates (from an un-named large PKI :-) that currently
>handle PIs by munging them into Common Name (e.g.,
>CN="Kemp.David.P.0514101404") will have a saner alternative.

The de-facto standard, already engraved in *millions* of certs is
putting 0514101404 in serialNumber. 

This is almost as de-facto standard as putting e-mail addresses in DNs
which in turn is almost as de-facto standard as using URIs for naming
globally unique objects.

C:\Internet-Drafts>del draft-ietf-pkix-pi-*.txt

:-)

Pardon my complaints, let there be an RFC!  But don't expect
this scheme to become the trend.

There is a slight problem with the whole idea.  Either RPs require
and act upon the PI-data or they don't care about it.  This in my
opinion makes the extension redundant or is just another way
to screw up validation.

If you on top of this add policy extensions I believe a real disaster
is in the making.

Anders