PKIX-3 Extensibility

[Russ Housley <housley@xxxxxxxxxx>]

I think that there are messages that are specific to particular
environments, and I cannot find a place for such messages in PKIX-3.  For
example, a particular community might use hardware tokens, and they might
need messages to transfer PINs associated with those tokens.  I am sure
that there are many, many more such examples.  The PKIX working group
cannot add a message type for every environment. Yet, the current CHOICE is
hopeless for extensibility.

I propose that an additional  branch be added to the CHOICE.  The
additional branch would be:

	other [48] SEQUENCE {
			oid	OBJECT IDENTIFIER,
			value	ANY DEFINED BY oid  }

In this way, particular communities can extend PKIX-3 to handle their
specific needs without having to annoy the working group to add brances to
the choice that are usefult to a small set of users.

Russ