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

Re: Fw: Reserved characters for a LDAP URI

To: Michael Ströder <michael@stroeder.com>
Subject: Re: Fw: Reserved characters for a LDAP URI
From: "Wen-Cheng Wang" <wcwang@cht.com.tw>
Date: Wed, 25 Dec 2002 00:28:45 +0800
Cc: <ietf-ldapbis@OpenLDAP.org>, <ietf-pkix@imc.org>
References: <OFF91A436E.B001E5FE-ON86256C98.0060DA4C-86256C98.0062317F@us.ibm.com> <015b01c2ab28$edd53650$4f85900a@wcwang> <3E0870F7.8070800@stroeder.com>

Michael wrote:
>
> This and all the URL-escaping examples show clearly that implementations
> should be prepared to handle all sorts of DN- and URL-escaping. Therefore
> the debate about the one and only right way will be endless.
>

I totally agree with you. What I argued with Japan PKI IWG members is that

ou=PKI%20IWG,o=Chunghwa%20Telecom%20Co.%5C,%20Ltd.,c=TW

is "one of the correct encodings". Unfortunately, they do not think so. That
is
why I asked for some comments from LDAPbis and PKIX mailing list.

Wen-Cheng Wang
Telecommunication Labs,
Chunghwa Telecom Co., Ltd.

References:
- Re: Fw: Reserved characters for a LDAP URI
  - From: John McMeeking <jmcmeek@us.ibm.com>
- Re: Fw: Reserved characters for a LDAP URI
  - From: "Wen-Cheng Wang" <wcwang@cht.com.tw>
- Re: Fw: Reserved characters for a LDAP URI
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: Re: Fw: Reserved characters for a LDAP URI
Next by Date: Re: Fw: Reserved characters for a LDAP URI
Index(es):
- Chronological
- Thread