A String Representation of General Name
draft-ietf-pkix-generalname-00
| Document | Type |
Expired Internet-Draft
(pkix WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Amit Kapoor , Ronald Tschalar | ||
| Last updated | 1999-11-16 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The PKIX working group has created the GeneralName [RFC2459] to support more name types than just the distinguished name specified by OSI. GeneralName is encoded in ASN.1. When a GeneralName is communicated not using a ASN.1 encoded protocol (e.g., in a configuration file), there is a need to have a string representation of GeneralName. This document specifies a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any GeneralName. This specification also recognizes that GeneralName needs to be communicated to humans, in which case the encoding has to be user friendly for display purposes, for e.g. on a business card or in an email message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)