CLDAP issues
Simon E Spero <ses@tipper.oit.unc.edu> Fri, 10 December 1993 20:39 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08392;
10 Dec 93 15:39 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08388;
10 Dec 93 15:39 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa17359;
10 Dec 93 15:39 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP
id <g.06555-0@haig.cs.ucl.ac.uk>; Fri, 10 Dec 1993 19:48:40 +0000
Received: from tipper.oit.unc.edu by bells.cs.ucl.ac.uk with Internet SMTP
id <g.05672-0@bells.cs.ucl.ac.uk>; Fri, 10 Dec 1993 19:48:23 +0000
Received: from localhost.oit.unc.edu by tipper.oit.unc.edu (SMI4.1/FvK 1.02)
id AA01789; Fri, 10 Dec 93 14:48:06 EST
Message-Id: <9312101948.AA01789@tipper.oit.unc.edu>
To: ldap@umich.edu, osi-ds@cs.ucl.ac.uk
Subject: CLDAP issues
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 10 Dec 93 14:48:05 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Simon E Spero <ses@tipper.oit.unc.edu>
I'm now adding a UDP listener to my proto-server, and there's a couple of changes I'd like to bounce off people. 1) Creating a new type 'CDLAPMessage', which would include the authentication paramaters from BindRequest. 2) Adding a CLDAPSearchResponse which would be a sequence of LDAP search responses. Tim has made a good case that this isn't needed, but it would seem to make things a lot simpler if we can wrap up all response together. Simon
- CLDAP issues Simon E Spero
- Re: CLDAP issues Alan Young
- Re: CLDAP issues Simon E Spero
- Re: CLDAP issues Alan Young
- Re: CLDAP issues Alan Young
- Re: CLDAP issues Simon E Spero