[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAPDN and AuthMeth/DIGEST-MD5

To: Kurt@openldap.org
Subject: Re: LDAPDN and AuthMeth/DIGEST-MD5
From: Mark Wahl <M.Wahl@INNOSOFT.COM>
Date: Tue, 23 Nov 1999 13:18:52 -0600
Cc: ietf-ldapext@netscape.com
Cc: Mark Wahl <M.Wahl@INNOSOFT.COM>
Resent-date: Tue, 23 Nov 1999 11:20:07 -0800 (PST)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"8kbZ-.A.CP.YjuO4"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

> Great.  All we then need is to include in AuthMeth a specification
> for generating canonical LDAPDN string encoding of the user
> specified DN.  

RFC 2253 describes a procedure for turning a DN into a string format.  What 
I would like for section 2.2 is a way to describe how the the Attribute Type 
and Value components of an RDN can be ordered in the same way as if the DN 
was DER encoded.  Once we have that, the only additional statement that needs
to be made is about quoting and spacing behavior.

Mark Wahl, Directory Product Architect
Innosoft International, Inc.

Follow-Ups:
- Re: LDAPDN and AuthMeth/DIGEST-MD5
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>

Prev by Date: Get online today accepting credit cards. Our company even allows you to accept government cards.
Next by Date: Re: LDAPDN and AuthMeth/DIGEST-MD5
Index(es):
- Chronological
- Thread