AW: LDAP Certificate transfer syntax

[Fantou Patrick <patrick.fantou@icn.siemens.de>]

Hi Kurt and Chris,
 
I am not sure this discussion really brings us further.

There is no choice with some attributes like certificates.

I fully support David´s proposal:
"The use of the ;binary encoding option, i.e. by
requesting or returning the attributes with descriptions
"userCertificate;binary" or "caCertificate;binary" has no effect on the
transfer syntax."

Patrick

> -----Ursprüngliche Nachricht-----
> Von: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
> Gesendet: Dienstag, 9. April 2002 17:19
> An: Christopher Oliva
> Cc: David Chadwick; Mark Wahl; steven.legg@adacel.com.au; 'LDAP BIS';
> 'PKIX'
> Betreff: RE: LDAP Certificate transfer syntax
> 
> 
> At 10:05 AM 2002-04-09, Christopher Oliva wrote:
> >> ;binary must be present when the binary encoding is transferred. 
> >> ;binary must not be present when the native encoding is 
> transferred. 
> >
> >Where is that stated in the RFC ? There are no such statements. 
> 
> It is implied by the language of RFC 2251.  When a protocol
> provides multiple possible transfer encodings for a particular
> value, the protocol needs to provide a clear indication of
> which transfer encoding is being used.  In LDAPv3, absence
> and presence of transfer options is used to indicate which
> transfer encoding is used. 
> 
> Kurt
>