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

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

To: IETF-PKIX@xxxxxxxxxxxxxxxx
Subject: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
From: "Jim Schaad (Exchange)" <jimsch@xxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 28 Feb 1998 21:16:56 -0800
Approved-by: jean.pawluk@TANDEM.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>

> A question was recently asked of me which I though I knew the answer
> for but cannot find any backup on this information.
>
> When an RFC822 name is encoded in SubjectAltName (or one of its
> equivalents), is a display name allowed as well as the base address?
> So can I encode "Jim Schaad [jimsch@microsoft.com]", or can I just
> encode jimsch@microsoft.com?   I have always assumed until I was asked
> that only the latter was permitted.
>
> jim schaad
>
>

Follow-Ups:
- Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
  - From: Paul Hoffman / IMC

Prev by Date: [IETF-PKIX] CMP Progression
Next by Date: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
Previous by thread: [IETF-PKIX] CMP Progression
Next by thread: Re: [IETF-PKIX] RFC 822 names in SubjectAltName and other extensions
Index(es):
- Date
- Thread