RE: ;binary migration solution

["Ramsay, Ron" <Ron.Ramsay@ca.com>]

With userCertificate, it doesn't matter how you ask for it, there is only
one encoding possible, the raw BER. The presence of ;binary on either
request or response is purely cosmetic.

-----Original Message-----
From: Hallvard B Furuseth [mailto:h.b.furuseth@usit.uio.no]
Sent: Monday, 18 November 2002 00:50
To: Jim Sermersheim
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: ;binary migration solution


Jim Sermersheim writes:
> Unless some problem can  be shown, this is what I would prefer.
> 
>>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 11/15/02 02:58AM >>>
> How about defining ;binary to do nothing, except that if the client
> requests ;binary on an attribute, it receives it with ;binary (whether
> or not the attribute was added with a ;binary option)?

Well, the second suggestion has one problem, so I don't know if that
should be implemented:

> Also, maybe if an attribute was added with ;binary but the client
> requests the attribute without ;binary, it receives it without ;binary.

If the client asks for userCertificate but wants userCertificate;binary,
it would get the wrong value even if the certificate was added with
;binary.

Are there clients like that?

-- 
Hallvard