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

Re: Comments on draft-ietf-ldapext-trigger-01.txt

To: Ian Goldsmith <ian.goldsmith@isocor.com>
Subject: Re: Comments on draft-ietf-ldapext-trigger-01.txt
From: Mark Smith <mcs@netscape.com>
Date: Thu, 13 Aug 1998 17:37:39 -0700
Cc: Tim Howes <howes@netscape.com>, Alan Lloyd <Alan.Lloyd@OpenDirectory.com.au>, ietf-ldapext@netscape.com
Organization: Netscape Communications
References: <024401bdc70c$30e83060$f2e506c6@ian.isocor.com>
Resent-date: Thu, 13 Aug 1998 17:37:02 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"FOoHC.0.6F1.gQuqr"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

Ian Goldsmith wrote:
> 
> Perhaps implementors should take a note of this issue and provide some form
> of "access control" to limit the use of triggered or persistent search
> operations to authorized users?

A good suggestion.  In fact, the latest triggered search and persistent
search drafts both mention this idea.

--
Mark Smith
Directory Architect / Netscape Communications Corp.
My words are my own, not my employer's.  Got LDAP?

Follow-Ups:
- Re: Comments on draft-ietf-ldapext-trigger-01.txt
  - From: Leif Johansson <leifj@matematik.su.se>

References:
- Re: Comments on draft-ietf-ldapext-trigger-01.txt
  - From: Ian Goldsmith <ian.goldsmith@isocor.com>

Prev by Date: Registration of SASL mechanism DIGEST-MD5
Next by Date: RE: Authentication Methods for LDAP - last call
Index(es):
- Chronological
- Thread