[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions

To: IETF-PKIX@xxxxxxxxxxxxxxxx
Subject: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
From: Michael Myers <mmyers@xxxxxxxxxxxx>
Date: Sun, 15 Mar 1998 22:21:32 -0800
Approved-by: Michael Myers <mmyers@VERISIGN.COM>
Reply-to: "IETF X.509-based public key infrastructure mailing list" <IETF-PKIX@xxxxxxxxxxxxxxxx>
Sender: "IETF X.509-based public key infrastructure mailing list" <IETF-PKIX@xxxxxxxxxxxxxxxx>

Paul,

-----Original Message-----
From: Paul Hoffman / IMC <paulh@imc.org>
To: IETF-PKIX@LISTS.TANDEM.COM <IETF-PKIX@LISTS.TANDEM.COM>
Date: Sunday, March 15, 1998 1:05 PM
Subject: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other
extensions

>Steve:
>I think you are thinking too
>much in the Verisign online enrollment model, which is only one way certs
>will be generated.

Actually, we have several enrollment models.  You may be most familiar with
the Internet variety.  We also enable enterprise-level local registration
authorities who, with appropriate a priori arrangments, are held to be
authoritative for well-defined jurisdictions.

Mike

Prev by Date: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
Next by Date: Re: [IETF-PKIX] Comments on Malpani and PKIX OCSP drafts
Previous by thread: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
Next by thread: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
Index(es):
- Date
- Thread