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

Re: Double quotes in DNs

To: Martin Lindström <martin@xxxxxxx>
Subject: Re: Double quotes in DNs
From: Mark Wahl <M.Wahl@xxxxxxxxxxxx>
Date: Wed, 14 Apr 1999 10:01:20 -0500
Cc: ietf-pkix@xxxxxxx, daniel@xxxxxxx, dpn@xxxxxxx, rmasters@xxxxxxx
In-reply-to: "Your message of Wed, 14 Apr 1999 11:03:13 +0200."<>
List-archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
Sender: owner-ietf-pkix@xxxxxxx

RFC 2253, which obsoletes RFC 1779, describes in section 2.4 the procedure
by which an ASN.1 attribute value is converted to a string.  You do not need
to have a double quote as part of the _attribute_value_ for your O.  The 
double quote is automatically added by the process of converting an X.500
DN encoding (BER) to an LDAP DN encoding (BNF).  Thesefore the PrintableString 
character set is suitable, just use  

Martin Lindstrom, Creative Computing

as the value.

Mark Wahl, Directory Product Architect
Innosoft International, Inc.

References:
- Double quotes in DNs
  - From: Martin Lindström

Prev by Date: RE: CA vs. EE cert processing
Next by Date: RE: New proposed solution to the QC biometric issue
Previous by thread: Double quotes in DNs
Next by thread: New proposed solution to the QC biometric issue
Index(es):
- Date
- Thread