From list@netscape.com  Mon Jan  1 00:11:18 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA13183
	for <ldapext-archive@odin.ietf.org>; Mon, 1 Jan 2001 00:11:18 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f014tQ323563;
	Sun, 31 Dec 2000 20:55:26 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0159G629319;
	Sun, 31 Dec 2000 21:09:16 -0800 (PST)
Resent-Date: Sun, 31 Dec 2000 21:09:16 -0800 (PST)
Date: Sun, 31 Dec 2000 21:08:56 -0800 (PST)
Message-Id: <200101010508.f0158jD08937@ywing.netscape.com>
From: webmaster@OUXX.cashtwoewe.com
To: Friend@netscape.com
Subject:  CHECK THIS VISA CARD OUT! and $$$$ is yours Free!! -SMQD
X-Reply-To:  m58wd@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"clnQ2.A.rIH.6DBU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

VisaRebates.com is giving away FREE Visa cards with flight 
miles on any airline, merchandise points, and more - all FREE. 
And they're giving away millions of dollars to those who refer 
new Cardholders. See more at VisaRebates.com. 
http://www.visarebates.com/Index.cfm?ReferralID=markwitt
Remove instructions;
mailto:m58wd@yahoo.com/?subject=remove




From list@netscape.com  Mon Jan  1 14:39:06 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28343
	for <ldapext-archive@odin.ietf.org>; Mon, 1 Jan 2001 14:39:06 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f01JSK328127;
	Mon, 1 Jan 2001 11:28:20 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f01Jb1w25722;
	Mon, 1 Jan 2001 11:37:01 -0800 (PST)
Resent-Date: Mon, 1 Jan 2001 11:37:01 -0800 (PST)
From: Stig Venås <venaas@alfa.itea.ntnu.no>
Date: Mon, 1 Jan 2001 20:36:25 +0100
To: ietf-ldapext@netscape.com
Subject: ldap_init() and IPv6 addresses
Message-ID: <20010101203625.A25433@itea.ntnu.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Resent-Message-ID: <"TIzqjB.A.oRG.cxNU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

From draft-ietf-ldapext-ldap-c-api-05.txt:

Parameters are:

hostname Contains a space-separated list of hostnames or dotted strings
         representing the IP address of hosts running an LDAP server to
         connect to. Each hostname in the list MAY include a port number
         which is separated from the host itself with a colon (:) char-
         acter.  The hosts will be tried in the order listed, stopping
         with the first one to which a successful connection is made.

   Note: A suitable representation for including a literal IPv6[10]
   address in the hostname parameter is desired, but has not yet been
   determined or implemented in practice.


This has been implemented in OpenLDAP. The format chosen is based on
the URL syntax in RFC 2732 which uses [] around the address, an example
from the RFC:

	http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html

So the format I suggest (and is implemented in OpenLDAP) would then be
to write host and port as [FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80.

Just to make myself clear, here are some other examples:

ldap_init("[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]", LDAP_PORT )

ldap_init("[FEDC:BA98::7654:3210] 127.0.0.1", LDAP_PORT )

ldap_init("[FEDC:BA98:7654:3210::1]:390 [FEDC:BA98:7654::1]:391", LDAP_PORT )

ldap_init("[FEDC:BA98:7654:3210::1]:390 [FEDC:BA98:7654:3210::1]", LDAP_PORT )

My question then, can we agree on this format and use it in the next
revision of the draft, or is there anyone that doesn't like this?

Stig

-- 
Stig Venaas
UNINETT



From list@netscape.com  Mon Jan  1 19:55:21 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29495
	for <ldapext-archive@odin.ietf.org>; Mon, 1 Jan 2001 19:55:20 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f020dj323326;
	Mon, 1 Jan 2001 16:39:45 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f020ra217267;
	Mon, 1 Jan 2001 16:53:36 -0800 (PST)
Resent-Date: Mon, 1 Jan 2001 16:53:36 -0800 (PST)
Message-ID: <20010102012240.28803.qmail@web1611.mail.yahoo.com>
Date: Mon, 1 Jan 2001 17:22:40 -0800 (PST)
From: Sixto J Rosario <sixto143@yahoo.com>
Subject: Information request
To: ietf-ldapext@netscape.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Message-ID: <"qrKh3D.A.hNE.PaSU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Im interesting in investing in high yield offshore
programs. Contact me as soon as possible.

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/



From list@netscape.com  Tue Jan  2 11:12:16 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19524
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 11:12:15 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f02Fug328463;
	Tue, 2 Jan 2001 07:56:43 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f02GAZo21909;
	Tue, 2 Jan 2001 08:10:35 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 08:10:35 -0800 (PST)
Date: Tue, 2 Jan 2001 08:10:07 -0800 (PST)
Message-Id: <200101021610.f02GA6B00388@xwing.netscape.com>
From: wongwangping@JDWN.yahoo.com
To: .JXKO@netscape.com
Subject:   Amazing Profit Sharing Program. Free To Join. -YHOL
X-Reply-To:  pingingw@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"x0PLWC.A.BWF.61fU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello ,
We got your address as someone who are interested in home based business.
If this message gets to you wrongly.  We apolozise for any inconveniences caused.
To remove yourself from this mailing list, please forward this mail to    
                               pingingw@yahoo.com    
 with the subject "Remove" on it.

How ever if this mail doesn't bother you. Please take a closer look, it might change your life.

GOLD CLUB

If I told you that you could get PAID for doing NOTHING ,would you believe me?
Probably not, but that is what we offer you!

Yes, read it again!

NO ADVERTISING!
NO CALLING!
NO MEETINGS!
NO PRODUCT SELLING!
NO MAILING!
NO RECRUITING OF PEOPLE!
NO NEED TO TALK YOUR FRIENDS INTO IT!
NO TIME REQUIRED!

And best of all, it's FREE!

NO OBLIGATIONS, YOU MAY JOIN OR
LEAVE WHENEVER YOU WANT!

If you want to get involved, please mail to    
               pingingw@yahoo.com     
with "More Info" in the subject line. Thank you.



Best regards,

Steve Wong



Hello ,
We got your address as someone who are interested in home based business.
If this message gets to you wrongly.  We apolozise for any inconveniences caused.
To remove yourself from this mailing list, please forward this mail to < wongwangping@yahoo.com> with 
the subject "Remove" on it.

How ever if this mail doesn't bother you. Please take a closer look, it might change your life.
It is free to sign up! It's an amazing Profit Sharing Program.
YOU PAY ONLY WHEN YOU ARE ASSURED TO RECEIVE THE
PHASE 3 PAYOUT OF US$800.
and then it costs you a low one time out-of-pocket
investment of $75 USD.

The way that we have structured the compensation plan, we know that
it is definitely possible for each member to reach the 5th phase and
receive $6000 and continue doing so every week.

Sound interesting? Check the plan kisted below.

PHASE      ENTRY FEE        CYCLE/PAYOUT
  1           FREE         $ 200 (recycled)
  2           FREE         $ 600 (recycled)
  3           $ 75         $ 800 (paid to you)*
  4         $1,000**      $3,000 (recycled)
  5           FREE        $6,000 (paid to you)*
INFINITY    $3,000**      $6,000 (paid to you)*

*A 5% deduction will be made from these amounts before a payout is
submitted.
**This will be deducted from the preceding phase. Your only
out-of-pocket expense is $75 USD.

If you want to get involved, please mail to   < wongwangping@yahoo.com>     with "More Info" in the
subject line. Thank you.



Best regards,

Steve Wong




From list@netscape.com  Tue Jan  2 12:44:01 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA20454
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 12:44:01 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f02HQj311666;
	Tue, 2 Jan 2001 09:26:48 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f02Hecc18100;
	Tue, 2 Jan 2001 09:40:38 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 09:40:38 -0800 (PST)
Message-ID: <3A521251.C94DE1ED@worldspot.com>
Date: Tue, 02 Jan 2001 09:39:29 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Java API: LDAPMessage accessor for LDAPException
References: <sa4fa550.033@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"ltky7C.A.iaE.VKhU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Jim Sermersheim wrote:
> 
> Rob,
> 
> There are (perhaps) dozens of extended operations that are not described in Internet-Drafts. Some of these, as well as possible future IETF documented extended operatoins, have the ability to not only return one of the well known (and limited) LDAP error values, but return other "extended" error information as well (in the value of the extended resonse).
> 
> There must be some way of reading the information returned in the extended operation PDU whether or not an error value is present. To make the case more simple, the Java API is not allowing the client to read the entire allowable set of data being sent by the server.
> 
> Jim

  Wouldn't such an extended operation return success as the LDAP return code (the extended operation was successfully delivered, processed, and a result returned), so there would be no exception? There is a difference between an LDAP protocol failure on the one hand and a privately defined operation result on the other.

Rob


> 
> >>> Rob Weltman <robw@worldspot.com> 12/27/00 8:54:52 PM >>>
> Jim Sermersheim wrote:
> >
> > I've heard a couple people ask how to solve this problem with synchronous calls:
> >
> > Client sends an extended operation to server. Server returns with extended response but an error condition is present. An LDAPException is thrown and caught by the application, but there is no way to read the extended response.
> >
> > Can we add a new method to LDAPException -- public LDAPMessage getLDAPMessage()? It would return null if no LDAPMessage is associated with the response.
> >
> > To date I've told people to use the async methods, but I'd rather the problem just be fixed.
> >
> > Jim
> 
> Jim,
> 
>   In what cases is there a valid response message as well as an error condition? For the other operation types there is either one or the other.
> 
> Rob



From list@netscape.com  Tue Jan  2 13:44:22 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21193
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 13:44:22 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f02IRn326534;
	Tue, 2 Jan 2001 10:27:50 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f02Ifgw27681;
	Tue, 2 Jan 2001 10:41:42 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 10:41:42 -0800 (PST)
Message-Id: <5.0.2.1.0.20010102094815.00a31700@pop.walltech.com>
X-Sender: bgreenblatt@pop.walltech.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 02 Jan 2001 09:49:26 -0800
To: Rob Weltman <robw@worldspot.com>, Jim Sermersheim <jimse@novell.com>
From: Bruce Greenblatt <bgreenblatt@directory-applications.com>
Subject: Re: Java API: LDAPMessage accessor for LDAPException
Cc: ietf-ldapext@netscape.com
In-Reply-To: <3A521251.C94DE1ED@worldspot.com>
References: <sa4fa550.033@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-Message-ID: <"77m2xB.A.PwG.lDiU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 09:39 AM 1/2/2001 -0800, Rob Weltman wrote:

>   Wouldn't such an extended operation return success as the LDAP return 
> code (the extended operation was successfully delivered, processed, and a 
> result returned), so there would be no exception? There is a difference 
> between an LDAP protocol failure on the one hand and a privately defined 
> operation result on the other.
>
>Rob
>
>

I concur.  There is a well defined mechanism for extensions to return 
privately defined operation results.  Perhaps this needs to be made more 
explicit in the specification.


==============================================
Bruce Greenblatt, Ph. D.
Directory Tools and Application Services, Inc.
http://www.directory-applications.com
See my new Book on Internet Directories: 
http://www.phptr.com/ptrbooks/ptr_0139744525.html



From list@netscape.com  Tue Jan  2 19:19:51 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24334
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 19:19:49 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0303g324412;
	Tue, 2 Jan 2001 16:03:42 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f030HZk20081;
	Tue, 2 Jan 2001 16:17:35 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 16:17:35 -0800 (PST)
Message-Id: <sa520d25.041@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 02 Jan 2001 17:17:18 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <robw@worldspot.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Java API: LDAPMessage accessor for LDAPException
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f030HXv20047
Resent-Message-ID: <"Z2BoAC.A.f5E.e-mU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>>>> Rob Weltman <robw@worldspot.com> 1/2/01 10:39:29 AM >>>
>Jim Sermersheim wrote:
>> 
>> Rob,
>> 
>> There are (perhaps) dozens of extended operations that are not described in Internet-Drafts. Some of these, as well as possible future IETF documented extended operatoins, have the ability to not only return one of the well known (and limited) LDAP error values, but return other "extended" error information as well (in the value of the extended resonse).
>> 
>> There must be some way of reading the information returned in the extended operation PDU whether or not an error value is present. To make the case more simple, the Java API is not allowing the client to read the entire allowable set of data being sent by the server.
>> 
>> Jim
>
>  Wouldn't such an extended operation return success as the LDAP return code (the extended operation was successfully delivered, processed, and a result returned), so there would be no exception? There is a difference between an LDAP protocol failure on the one hand and a privately defined operation result on the other.
>
>Rob

The particular extension that initially sparked this does not return success. Rather, it returns an error value and  also returns additional information in the extended response value. One could imagine an extended operation that returns timeLimitExceeded along with some extra information about the amount of work done before time ran out. These types of extensions aren't trying to augment information surrounding protocol failures per se. They're either trying to augment infromation surrounding othr types of errors (like insufficientAccessRights, noSuchObject, limits, etc).

The ability to do this does exist in the protocol as we know it today. It may be poor design on the extension writers behalf, but there isn't wording that I can find in the specification that warns or suggests not to do it. I believe that it is wrong for the API to hide this protocol information unless the specification explicitly states that when the extended response contains an ldapResult other than success (0), the response value MUST be empty (or ignored by clients).

I just looked at a few I-Ds and it seems to date, this is something that is specified by the extension specification, not the protocol. While some I-Ds specify that the response value is to be ignored in the presence of any result other than success, the LBURP draft defines an extended operation that allows an other (80) result to signify and that more information is held in the extended response value.

Whether this is a bad thing for extension writers to do is a discussion to be had at the protocol level. I don't think we should fix perceived shortcomings by restricting or augmenting the APIs. Until the protocol specification says something about this, I think the APIs need to allow access to this information.

Jim


> 
> >>> Rob Weltman <robw@worldspot.com> 12/27/00 8:54:52 PM >>>
> Jim Sermersheim wrote:
> >
> > I've heard a couple people ask how to solve this problem with synchronous calls:
> >
> > Client sends an extended operation to server. Server returns with extended response but an error condition is present. An LDAPException is thrown and caught by the application, but there is no way to read the extended response.
> >
> > Can we add a new method to LDAPException -- public LDAPMessage getLDAPMessage()? It would return null if no LDAPMessage is associated with the response.
> >
> > To date I've told people to use the async methods, but I'd rather the problem just be fixed.
> >
> > Jim
> 
> Jim,
> 
>   In what cases is there a valid response message as well as an error condition? For the other operation types there is either one or the other.
> 
> Rob



From list@netscape.com  Tue Jan  2 19:34:00 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24417
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 19:34:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f030NB328044;
	Tue, 2 Jan 2001 16:23:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f030VqU25564;
	Tue, 2 Jan 2001 16:31:52 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 16:31:52 -0800 (PST)
Date: Tue, 2 Jan 2001 16:31:32 -0800 (PST)
Message-Id: <200101030031.f030VWD24067@ywing.netscape.com>
From: "glenora"<glynnish@AKLN.excite.com>
To: ietf-ldapext@TFEA.netscape.com
Subject:  / / / SCAM ALERT --- FREE BIZ OP LOCATOR \ \ \ -JFOO
X-Reply-To:  "glenora"<glynnish@excite.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"d6ynQB.A.KPG.3LnU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit



Hi $NAME,  

Last year I thought that ALL ONLINE BUSINESSES were SCAMS.....

Well ... I found out that many of them indeed are scams
that took my money and ran!

However I learned differently about this opportunity!

BUSINESS OPPORTUNITY ALLIANCE has taken a
Popular Internet Concept and Elevated It To A NEW Level ...

This professional group of internet marketers seek out, research and report on new 
business opportunities as they come online!

HERE IS THE ACTIVE CRITERIA FOR A BUSINESS OPPORTUNITY TO BE CONSIDERED:

  A  proven track record
  professional and experienced leadership
  identifiable upside trend that maximizes income potential
  legal and legitimate product
  workable compensation plan
  suitable income potential for both part-time and full time affiliates
  Successful and operable support network  


You can JOIN Business Opportunity Alliance FOR FREE -- 
ABSOLUTELY NO OBLIGATION EVER to join a recommended opportunity.

NO HASSLE. 
 NO-ONE WILL CALL YOU. 
 NO QUESTIONS. 
 NO MONEY REQUIRED.
NO EXPERIENCE NECESSARY
NO BETTER OPPORTUNITY AVAILABLE ANYWHERE
INTERNATIONALLY AVAILABLE
THERE'S NOTHING LIKE IT!!!

ACT TODAY and get your FREE personalized website.

<a href="http://www.theincrediblemall.com/index.cgi?id=115"> CLICK HERE<A/>

or use this URL:  http://www.theinrediblemall.com/index.cgi?id=115


REMEMBER .... YOU HAVE NOTHING TO LOSE, BUT PRECIOUS TIME !

**** Your name has been given to me as a person interested in business opportunities.  If 
this is indeed not the case, please accept my apologies and delete this letter.  To be 
removed from this list, please type "remove" in the subject line and hit "reply".

Thank you!






From list@netscape.com  Tue Jan  2 20:01:56 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24539
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 20:01:55 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f030pA303227;
	Tue, 2 Jan 2001 16:51:10 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f030xps05043;
	Tue, 2 Jan 2001 16:59:51 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 16:59:51 -0800 (PST)
Date: Tue, 2 Jan 2001 16:59:38 -0800 (PST)
Message-Id: <200101030059.f030xcB25388@xwing.netscape.com>
From: ychsl@msn.com
To: roqfs@Webfriend.netscape.com
Reply-To: tim7me2@n2mail.com
Subject: I'll Pay Your Joining Fee!                                    [fjrbv]
Resent-Message-ID: <"BDsa0D.A.hOB.GmnU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Greetings!

If you could use $1,500.00 in Jan. I will pay 
your membership IF you are serious.

This plan has a weekly pay out. Product purchase 
optional. ONLY serious people need apply. This 
offer expires 1-10-2001.

For detailed info, please reply with "Send More
Info Please" as the subject.

mailto:tim7u@n2mail.com?subject=Send_More_Info_Please

Wishing You a Great Year!
JR



From list@netscape.com  Tue Jan  2 23:30:13 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA27507
	for <ldapext-archive@odin.ietf.org>; Tue, 2 Jan 2001 23:30:12 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f034Cn322616;
	Tue, 2 Jan 2001 20:12:49 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f034QgY05236;
	Tue, 2 Jan 2001 20:26:42 -0800 (PST)
Resent-Date: Tue, 2 Jan 2001 20:26:42 -0800 (PST)
Date: Tue, 2 Jan 2001 20:26:25 -0800 (PST)
Message-Id: <200101030426.f034QMD07825@ywing.netscape.com>
From: freecd4u52@hotmail.com
To: ietf-ldapext@netscape.com
Subject:  Free CD-ROM 
X-Reply-To:  iinfo-tech54@uip.sanet
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"2M24fC.A.iRB.BoqU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

We would like to thank you for taking the time to read
this e-mail.

In a moment, I will show you how to get a copy of my 
Free Special CD-ROM that shows you specifically how to
start - or expand - your very own business!

It doesn't matter what kind of business you are in. If
you want to learn the secrets to operating a successful
cash-generating business - then you must get your very
own copy of my amazing Special CD-ROM.

With job security a thing of the past, as many as
8,000 people a day are turning to self-employment to
fulfill their financial dreams! This is great for 
America. the only problem is that around 95% of all new
businesses fail within the first five years.

But You Won't Be One Of Them!

My amazing new Special CD-ROM will give you powerful 
infomation that millions of other small business owners
have never heard of. You will discover things like:

"How To Start A Home-Based Business"

"How To Advertise Your Business"

"The Small Business Resource Guide"

And More...

Put simply, this new special CD-ROM will change the way 
that you look at your small business-forever! I don't 
have room to explain everything, so you must get my
Special CD-ROM. It's free with no obligation.

To receive this Special CD-ROM Send $3.00 (No Checks for
this amount) for Express Priority Mail To:

E F Specialty Products, Box 749, Ridgeland, SC 29936

*******************************************************
YES,send me the free Special CD-ROM "Start Your Own 
Business" to the address list below.            

NAME:

ADDRESS: 

CITY: 

STATE:                      ZIP

*******************************************************

This message is sent in compliance of the new e-mail 
bill: SECTION 301. Per Section 301, Paragraph (a)(2)(c)
of S. 1618




From list@netscape.com  Wed Jan  3 03:10:19 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA11498
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 03:10:18 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f037rI307284;
	Tue, 2 Jan 2001 23:53:18 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0387C214416;
	Wed, 3 Jan 2001 00:07:12 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 00:07:12 -0800 (PST)
From: <kasfdmsd@tps0007.surecom.com.tw>
To: <ietf-ldapext@netscape.com>
Date: Wed, 3 Jan 2001 00:53:54
Message-Id: <458.837227.599006@mail.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"PCVPEB.A.-gD.v2tU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY!

STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN 
GET ONE FOR ONLY $11.95 PER MONTH!

DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE 
DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO 
GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A 
SIMPLE PHONE CALL TO  OUR OFFICE.

YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with 
no extra charge!  UNLIMITED TRAFFIC -- no extra charge!

FRONT PAGE EXTENSIONS are FULLY SUPPORTED.

A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS.

ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP 
CHARGE.

FOR DETAILS CALL 1 888 248 0765  if you are outside the USA,
please fax 240 337 8325

Webhosting International

 
 
 
 
 
 
 
 
 



From list@netscape.com  Wed Jan  3 09:00:55 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21946
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 09:00:50 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f03Div302922;
	Wed, 3 Jan 2001 05:44:57 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f03Dwp628522;
	Wed, 3 Jan 2001 05:58:51 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 05:58:51 -0800 (PST)
Message-Id: <sa52cd71.091@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 03 Jan 2001 06:54:18 -0700
From: "Haripriya S" <SHARIPRIYA@novell.com>
To: <ietf-ldapext@netscape.com>
Subject: Re: Returning Partial Results for an operation
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_DF84BBF1.3051688C"
Resent-Message-ID: <"i9bh-B.A.Y9G.aAzU6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_DF84BBF1.3051688C
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

IMO I see two kinds of responses a server may want to return on receiving =
an abandon:

1. A response to the abandon operation itself ( useful to clients to know =
that abandon was received).
2. A partial/full response to the original operation which was abandoned ( =
useful for sending accumulated partial results).

While the first requires an extended request and response and the need for =
the client to understand the same, the second may require a change to =
rfc2251 sec. 4.11 alone:

 "In the event that a server receives an Abandon
   Request on a Search Operation in the midst of transmitting responses
   to the search, that server MUST cease transmitting entry responses to
   the abandoned request immediately, and MUST NOT send the
   SearchResponseDone."

If the first MUST condition in the above passage is removed, and the =
second one retained, the server will be able to send accumulated responses.=
 The above clause is for search, but the same also applies to other =
requests returning partial responses.

The clients should work with this change because, they "MUST be prepared =
to receive results from operations it has abandoned" (4.11).

Thanks and Regards,
Haripriya

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 12/23/00 01:51PM >>>
I'd be happy to co-author an abandon I-D.

The use of an control upon abandon to solicit an
(extended? new?) response would likely not be supported
by an client API.

I believe an extended operation is the best approach.

Kurt




At 06:36 PM 12/22/00 -0700, Roger Harrison wrote:
>Kurt,
>=20
>I, too, have been considering the same thing because there are times when =
it would be very nice to know an abandon has been received and handled.=20
>=20
>In a conversation I had with Haripriya, I suggested just such a thing, =
and Haripriya suggested using a control to request a response for an =
abandon operation. It sounds like Jim wouldn't mind seeing something in =
this area as well.  Should we write something up? If so, do you have an =
opinion as to whether we should use a new extended abandon-with-response =
operation or a control on the current abandon operation?
>=20
>Roger
>
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 12/20/00 09:35PM >>>=20
>At 09:44 PM 12/20/00 -0700, Haripriya S wrote:=20
>>Yes but it would then mandate that the server MUST send partial results =
per entry immediately, and cannot bunch results even if a client wishes =
so, because the state cannot be conveyed once an abandon is received.=20
>
>Abandon semantics also require the server to defer returning=20
>return results of operations issues subsequent to the abandon=20
>operation until the operation being abandoned has been=20
>abandoned or has completed.=20
>
>For this reason, I have been considering specifying a new=20
>abandon operation which, like the X.500 abandon operation,=20
>has a response.=20
>
>Kurt=20

--=_DF84BBF1.3051688C
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>IMO I see two kinds of responses a server may want to return on =
receiving=20
an abandon:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. A response to the abandon operation itself ( useful to clients to =
know=20
that abandon was received).</DIV>
<DIV>2. A partial/full response to the original operation which was =
abandoned (=20
useful for sending accumulated partial results).</DIV>
<DIV>&nbsp;</DIV>
<DIV>While the first requires an extended request and response and the =
need for=20
the client to understand the same, the second may require a change to =
rfc2251=20
sec. 4.11 alone:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;"In the event that a server receives an Abandon<BR>&nbsp;&nbsp;=
=20
Request on a Search Operation in the midst of transmitting=20
responses<BR>&nbsp;&nbsp; to the search, that server MUST cease transmittin=
g=20
entry responses to<BR>&nbsp;&nbsp; the abandoned request immediately, and =
MUST=20
NOT send the<BR>&nbsp;&nbsp; SearchResponseDone."</DIV>
<DIV>&nbsp;</DIV>
<DIV>If the first MUST condition in the above passage is removed, and the =
second=20
one retained, the server will be able to send accumulated responses. =
The=20
above&nbsp;clause is for search, but the same also applies to other =
requests=20
returning partial responses.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The clients&nbsp;should work with this change because, they "MUST =
be=20
prepared to receive results from operations it has abandoned" (4.11).</DIV>=

<DIV>&nbsp;</DIV>
<DIV>Thanks and Regards,</DIV>
<DIV>Haripriya</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt; 12/23/00 =
01:51PM=20
&gt;&gt;&gt;<BR>I'd be happy to co-author an abandon I-D.<BR><BR>The use =
of an=20
control upon abandon to solicit an<BR>(extended? new?) response would =
likely not=20
be supported<BR>by an client API.<BR><BR>I believe an extended operation =
is the=20
best approach.<BR><BR>Kurt<BR><BR><BR><BR><BR>At 06:36 PM 12/22/00 -0700, =
Roger=20
Harrison wrote:<BR>&gt;Kurt,<BR>&gt; <BR>&gt;I, too, have been considering =
the=20
same thing because there are times when it would be very nice to know an =
abandon=20
has been received and handled. <BR>&gt; <BR>&gt;In a conversation I had =
with=20
Haripriya, I suggested just such a thing, and Haripriya suggested using =
a=20
control to request a response for an abandon operation. It sounds like =
Jim=20
wouldn't mind seeing something in this area as well.&nbsp; Should we =
write=20
something up? If so, do you have an opinion as to whether we should use a =
new=20
extended abandon-with-response operation or a control on the current =
abandon=20
operation?<BR>&gt; <BR>&gt;Roger<BR>&gt;<BR>&gt;&gt;&gt;&gt; "Kurt D. =
Zeilenga"=20
&lt;Kurt@OpenLDAP.org&gt; 12/20/00 09:35PM &gt;&gt;&gt; <BR>&gt;At 09:44 =
PM=20
12/20/00 -0700, Haripriya S wrote: <BR>&gt;&gt;Yes but it would then =
mandate=20
that the server MUST send partial results per entry immediately, and =
cannot=20
bunch results even if a client wishes so, because the state cannot be =
conveyed=20
once an abandon is received. <BR>&gt;<BR>&gt;Abandon semantics also =
require the=20
server to defer returning <BR>&gt;return results of operations issues =
subsequent=20
to the abandon <BR>&gt;operation until the operation being abandoned has =
been=20
<BR>&gt;abandoned or has completed. <BR>&gt;<BR>&gt;For this reason, I =
have been=20
considering specifying a new <BR>&gt;abandon operation which, like the =
X.500=20
abandon operation, <BR>&gt;has a response. <BR>&gt;<BR>&gt;Kurt=20
<BR><BR></DIV></BODY></HTML>

--=_DF84BBF1.3051688C--



From list@netscape.com  Wed Jan  3 12:12:57 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA28780
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 12:12:56 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f03H0h308964;
	Wed, 3 Jan 2001 09:00:43 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f03H9Qc23269;
	Wed, 3 Jan 2001 09:09:26 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 09:09:26 -0800 (PST)
Message-Id: <200101031742.TAA27228@asprin.sbuys.co.za>
From: "Jason M Nunes" <ck22n@bettergolf.net>
Subject: Your Chance #3ED0
To: on29s@sbuys.co.za
X-Mailer: Microsoft Outlook Express 4.72.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE VÐßD.1712.3
Mime-Version: 1.0
Date: Wed, 03 Jan 2001 06:55:22 -0500
Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
Resent-Message-ID: <"DdMEQ.A.3qF.Ez1U6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME Message

------=_NextPart_000_007F_01BDF6C7.FABAC1B0
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0"

------=_NextPart_001_0080_01BDF6C7.FABAC1B0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

***** This is an HTML Message ! *****


------=_NextPart_001_0080_01BDF6C7.FABAC1B0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!doctype html public "-//w3c//dtd html 4=2E0
 transitional//en">
 <html>
 <head>
    
    <title>Executive Guild Membership
 ApplicationResponse-O-Matic Form</title>
 </head>
 <body text=3D"#808080" bgcolor=3D"#F6F6CC"
 link=3D"#800040" vlink=3D"#FF0000" alink=3D"#8080C0">
 <p>
 <font color=3D"#000000"><b>Dear Professional,&nbsp;<br>
 <br>
 You have been selected as a potential candidate for a free listing in&nbs=
p;<br>
 the&nbsp; 2001 Edition of the International Executive Guild Registry=2E&n=
bsp;<br>
 <br>
 Please accept our congratulations for this coveted honor=2E&nbsp;<br>
 <br>
 As this edition is so important in view of the new millennium, the&nbsp;<=
br>
 International Executive Guild Registry will be published in two different=
&nbsp;<br>
 formats; the searchable CD-ROM and the Online Registry=2E&nbsp;<br>
 <br>
 Since inclusion can be considered recognition of your career position&nbs=
p;<br>
 and professionalism, each candidate is evaluated in keeping with high&nbs=
p;<br>
 standards of individual achievement=2E In light of this, the Internationa=
l Executive<br>
 Guild thinks that you may make an interesting biographical subject=2E&nbs=
p;<br>
 <br>
 We look forward to your inclusion and appearance in the International&nbs=
p;<br>
 Executive Guild's Registry=2E Best wishes for your continued success=2E&n=
bsp;<br>
 <br>
 International Executive Guild&nbsp;<br>
 Listing Dept=2E&nbsp;</b></font>
 <hr WIDTH=3D"100%">
 <p align=3D"center"><b><i><font color=3D"#000000">If you
 wish to be removed from our list, please submit
 your request</font></i></b>
 <br><b><i><font face=3D"Times New
 Roman,Times"><font color=3D"#000000">at the
 bottom of this email=2E</font></font></i></b>
 </p>
 <hr WIDTH=3D"100%">
 <table WIDTH=3D"695" >
 <caption><script language=3D"JavaScript">
 
 <!--
 function validate_form() {
   validity =3D true; // assume valid
   if (!check_empty(document=2Eform=2Ebusphone=2Evalue))
         { validity =3D false; alert('Day Time
 Phone field is empty!'); }
     if (validity)
         alert ("Thank you for your registration!
 "
                 + "Your form is now being passed
 to your browser's "
                 + "Mail Delivery Sub-System for
 NORMAL"
                 + " NON-ENCRYPTED email
 delivery=2E"
                 + "  All email addresses are
 removed from our system"
                 + " upon registration=2E  Please
 click OK to proceed");
   return validity;
 }

 function check_empty(text) {
   return (text=2Elength > 0); // returns false if
 empty
 }
 
 // -->
 
 </script>
 
 
 <!-- CHANGE EMAIL ADDRESS IN ACTION OF FORM -->
 
 <form name=3D"form"
  method=3D"post"
  action=3D"mailto:dgf89@verizonmail=2Ecom?SUBJECT=3DRegistration Form"
  enctype=3D"text/plain"
  
 <tr>
  </caption>
 <td></td>
 </tr>
 
 <tr>
 <td VALIGN=3DTOP COLSPAN=3D"2">
 <center><b><i><font color=3D"#000000"><font
 size=3D+3>International Executive Guild</font></font></i></b>
 <br><b><font color=3D"#000000"><font
 size=3D+2>Registration Form</font></font></b>
 <br><b><font color=3D"#000000">(US and Canada
 Only)</font></b>
 <br>
 <hr WIDTH=3D"100%"></center>
 </td>
 </tr>
 
 <tr>
 <td VALIGN=3DTOP COLSPAN=3D"2"><i><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D+0>Please
 fill out this form if you would like to be
 included on The International
 Executive Guild, For accuracy and
 publication purposes, please
 complete and send this form at the earliest
 opportunity=2E There is </font>no
 charge or obligation<font size=3D+0> to be listed
 on The International Executive Guild=2E</font></font></font></i>
 <br>
 <hr WIDTH=3D"100%"></td>
 </tr>
 
 <tr>
 <td VALIGN=3DTOP></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Your
 Name</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250" name=3D"Name"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Your
 Company</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250"
 name=3D"Company"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Title</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250"
 name=3D"Title"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Address</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250"
 name=3D"Address"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>City</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250" name=3D"City"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>State
 or Province</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"12" maxlength=3D"50" name=3D"State"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Country</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><select
 NAME=3D"Country" Size=3D"1"><option SELECTED><font
 color=3D"#000000">USA<option
 SELECTED>Canada</font></select></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>ZIP/Postal
 Code</font></font></font></b></td>
 
 <td ALIGN=3DLEFT VALIGN=3DCENTER WIDTH=3D"300"><input
 type=3D"text" value size=3D"12" maxlength=3D"50"
 name=3D"Zip"></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Day
 Time Telephone</font></font></font></b></td>
 
 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"22" maxlength=3D"50"
 name=3D"busphone"></td>
 </tr>
 
 <tr>
 <td>
 <div align=3Dright><b><font
 face=3D"Arial,Helvetica"><font
 color=3D"#000000"><font size=3D-1>Home
 Phone</font></font></font></b></div>
 </td>
 
 <td><input type=3D"text" value size=3D"22"
 maxlength=3D"50" name=3D"homephone"><b><font
 color=3D"#000000"><font size=3D-2>(Not
 To Be Published)</font></font></b></td>
 </tr>
 
 <tr>
 <td>
 <div align=3Dright><b><font
 face=3D"Arial,Helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Email</font></font></font></b></div>
 </td>
 
 <td><input type=3D"text" value size=3D"50"
 maxlength=3D"100" name=3D"Email"></td>
 </tr>
 
 <tr>
 <td></td>
 
 <td></td>
 </tr>
 </table>
 
 <center>
 <p>
 <hr WIDTH=3D"100%"><b><font
 face=3D"ARIAL,HELVETICA"><font
 color=3D"#000000"><font size=3D-1>TO
 HELP US IN CONSIDERING YOUR APPLICATION, PLEASE
 TELL US A LITTLE ABOUT
 YOURSELF=2E=2E=2E</font></font></font></b>
 <br>
 <hr WIDTH=3D"100%"></center>
 
 <center><table WIDTH=3D"81%" >
 <tr>
 <td ALIGN=3DRIGHT VALIGN=3DTOP WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Your
 Business</font></font></font></b></td>
 
 <td>
 <div align=3Dright><input type=3D"text" value
 size=3D"50" maxlength=3D"200"
 name=3D"business"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>(Financial
 Svcs, Banking, Computer Hardware, Software, Professional Svcs,
 Chemicals,
 Apparel, Aerospace, Food, Government, Utility,
 etc=2E)</font></font></font></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT VALIGN=3DTOP WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Type
 of Organization</font></font></font></b></td>
 
 <td>
 <div align=3Dright><input type=3D"text" value size=3D"50" maxlength=3D"25=
0"
 name=3D"Orgtype"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font size=3D-1>(M=
fg,
 Dist/Wholesaler, Retailer, Law Firm,</font></font></font>
 <br><font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>Investment
 Bank, Commercial Bank, University,</font></font></font>
 <br><font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>Financial
 Consultants, Ad Agency, Contractor, Broker,
 etc=2E)</font></font></font></td>
 </tr>
 
 <tr>
 <td VALIGN=3DTOP WIDTH=3D"300">
 <div align=3Dright><b><font face=3D"arial,helvetica"><font
 color=3D"#000000"><font
 size=3D-1>Your
 Business Expertise</font></font></font></b></div>
 </td>
 
 <td>
 <div align=3Dright><input type=3D"text" value size=3D"50" maxlength=3D"25=
0"
 name=3D"expertise"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>(Corp=2EMgmt,
 Marketing, Civil Engineering,</font></font></font>
 <br><font face=3D"arial,helvetica"><font color=3D"#000000"><font size=3D-=
1>Tax
 
 Law, Nuclear Physics, Database Development, Operations, Pathologist,
 Mortgage
 Banking, etc=2E)</font></font></font></td>
 </tr>
 
 <tr>
 <td ALIGN=3DRIGHT VALIGN=3DTOP WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Major
 Product Line</font></font></font></b></td>

 <td>
 <div align=3Dright><input type=3D"text" value size=3D"50" maxlength=3D"25=
0"
 name=3D"product"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>(Integrated
 Circuits, Commercial Aircraft, Adhesives, Cosmetics, Plastic Components,
 
 Snack Foods, etc=2E)</font></font></font></td>
 </tr>
 </table></center>
 
 <center>
 <p><input NAME=3D"submit" TYPE=3D"submit" VALUE=3D" Submit By E-Mail "><i=
nput
 NAME=3D"reset" TYPE=3D"reset" VALUE=3D" Clear Form "></form>
 <br><b><font color=3D"#000000"><font size=3D-1>Note: Submitting this form=

 will
 be made by email, not by use of&nbsp; www=2E&nbsp; Confirmation of its de=
livery
 is made by browsing your outgoing mail=2E</font></font></b>
 <br>
 <hr WIDTH=3D"100%"><b><i><font face=3D"arial,helvetica"><font
 color=3D"#000000"><font
 size=3D-1>Thank
 you for filling in this form, we will contact you with more
 information=2E</font></font></font></i></b>
 <br>
 <hr WIDTH=3D"100%">
 <br><b><font size=3D+1>List
 Removal</font></b>
 <br><b><font color=3D"#000000"><font size=3D-1><a
 href=3D"mailto:ck22n@netscape=2Enet?subject=3Dremove">Click
 Here</a></font></font></b></center>
 
 </body>
 </html>

------=_NextPart_001_0080_01BDF6C7.FABAC1B0--

------=_NextPart_000_007F_01BDF6C7.FABAC1B0--





From list@netscape.com  Wed Jan  3 18:43:28 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA09820
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 18:43:28 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f03NSc323742;
	Wed, 3 Jan 2001 15:28:38 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f03NbKA20323;
	Wed, 3 Jan 2001 15:37:20 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 15:37:20 -0800 (PST)
Message-Id: <sa53552e.023@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 03 Jan 2001 16:36:52 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <robw@worldspot.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Fwd: Re: draft Java-api-12
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_38635C8E.FF9EDCD5"
Resent-Message-ID: <"A6cdmB.A.R9E.ue7U6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_38635C8E.FF9EDCD5
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable



>>> Rob Weltman <robw@worldspot.com> 27-Dec-00 10:53:27 PM >>>
Steven Sonntag wrote:
>=20
> Rob Weltman wrote:
>=20
> >   It might be better instead to eliminate the current unsolicited
> > notification methods and instead have methods to add and remove
> > listeners for usolicited notifications. The implementation can then
> > discard unsolicited notifications if there are no listeners. For
> > example (I haven't thought this through completely yet):
> >
> > LDAPConnection
> >
> > public LDAPResponseListener addUnsolicitedNotificationListener(
> > LDAPResponseListener listener )
> >
> > public void removeUnsolicitedNotificationListener(
> > LDAPResponseListener listener )
> >
> > Rob
> >
>=20
> It seems natural to me that if unsolicited notifications are enabled on
> a
> listener, that the method LDAPListener.getMessageIDs() would include
> message ID 0 in the list of message IDs, and that
> LDAPConnection.abandon(0)
> and LDAPConnection.abandon(listener) could be used to removeUnsolicited
> notifications from a listener or listeners.  This raises some questions.
>=20
> 1) Should getMessageIDs show messageID 0 when unsolicited notification
> are enabled?  (My vote is yes)
>=20
> 2) Should the draft allow abandon to be used to remove unsolicited
> notifications?
> (this means that message ID 0 is treated like a message that never
> completes)
>=20
> 3) If number two is allowed, is removeUnsolicitedNotificationListener()
> necessary?
>=20
> -Steve

  I think it is easier for a client to handle unsolicited notifications as =
out-of-band events rather than lumped together with "normal" solicited =
responses. In almost all cases I would expect a client to want to know =
immediately that an unsolicited notification had arrived rather than =
having to poll and distinguish between solicited and unsolicited notificati=
ons. The event listener model reflects the paradigm of immediate out-of-ban=
d notification of unsolicited messages. Having the unsolicited messages =
ALSO appear in the normal message queue is confusing, error-prone, and not =
very useful as far as I can tell.

Rob
........................................
What you say may be true, but - using the listener paradigm allows the
developer to combine any combination of listeners, normal messages,
and unsolicited messages.  Why make an out of a special out of band API
for something that could be handled naturally by the existing API.

When you say the application wants to know immediately, you mean
the unsolicited notification message should comes up first, i.e. returned
to the application before other normal messages - correct? If the =
unsolicited
notification is mixed with other messages, the draft should specify that
unsolicited messages are returned first.

-Steve

-Steve

--=_38635C8E.FF9EDCD5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV><BR><BR>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; =
27-Dec-00=20
10:53:27 PM &gt;&gt;&gt;<BR>Steven Sonntag wrote:<BR>&gt; <BR>&gt; Rob =
Weltman=20
wrote:<BR>&gt; <BR>&gt; &gt;&nbsp;&nbsp; It might be better instead to =
eliminate=20
the current unsolicited<BR>&gt; &gt; notification methods and instead =
have=20
methods to add and remove<BR>&gt; &gt; listeners for usolicited notificatio=
ns.=20
The implementation can then<BR>&gt; &gt; discard unsolicited notifications =
if=20
there are no listeners. For<BR>&gt; &gt; example (I haven't thought this =
through=20
completely yet):<BR>&gt; &gt;<BR>&gt; &gt; LDAPConnection<BR>&gt; =
&gt;<BR>&gt;=20
&gt; public LDAPResponseListener addUnsolicitedNotificationListener(<BR>&gt=
;=20
&gt; LDAPResponseListener listener )<BR>&gt; &gt;<BR>&gt; &gt; public =
void=20
removeUnsolicitedNotificationListener(<BR>&gt; &gt; LDAPResponseListener=20=

listener )<BR>&gt; &gt;<BR>&gt; &gt; Rob<BR>&gt; &gt;<BR>&gt; <BR>&gt; It =
seems=20
natural to me that if unsolicited notifications are enabled on<BR>&gt; =
a<BR>&gt;=20
listener, that the method LDAPListener.getMessageIDs() would include<BR>&gt=
;=20
message ID 0 in the list of message IDs, and that<BR>&gt;=20
LDAPConnection.abandon(0)<BR>&gt; and LDAPConnection.abandon(listener) =
could be=20
used to removeUnsolicited<BR>&gt; notifications from a listener or=20
listeners.&nbsp; This raises some questions.<BR>&gt; <BR>&gt; 1) Should=20
getMessageIDs show messageID 0 when unsolicited notification<BR>&gt; =
are=20
enabled?&nbsp; (My vote is yes)<BR>&gt; <BR>&gt; 2) Should the draft =
allow=20
abandon to be used to remove unsolicited<BR>&gt; notifications?<BR>&gt; =
(this=20
means that message ID 0 is treated like a message that never<BR>&gt;=20
completes)<BR>&gt; <BR>&gt; 3) If number two is allowed, is=20
removeUnsolicitedNotificationListener()<BR>&gt; necessary?<BR>&gt; =
<BR>&gt;=20
-Steve<BR><BR>&nbsp; I think it is easier for a client to handle unsolicite=
d=20
notifications as out-of-band events rather than lumped together with =
"normal"=20
solicited responses. In almost all cases I would expect a client to want =
to know=20
immediately that an unsolicited notification had arrived rather than =
having to=20
poll and distinguish between solicited and unsolicited notifications. The =
event=20
listener model reflects the paradigm of immediate out-of-band notification =
of=20
unsolicited messages. Having the unsolicited messages ALSO appear in the =
normal=20
message queue is confusing, error-prone, and not very useful as far as I =
can=20
tell.<BR><BR>Rob</DIV>
<DIV>........................................</DIV>
<DIV>What you say may be true, but - using the listener paradigm allows=20
the</DIV>
<DIV>developer to combine any combination of listeners, normal messages,</D=
IV>
<DIV>and unsolicited messages.&nbsp; Why make an out of a special out of =
band=20
API</DIV>
<DIV>for something that could be handled naturally by the existing =
API.</DIV>
<DIV>&nbsp;</DIV>
<DIV>When you say the application wants to know immediately, you mean</DIV>=

<DIV>the unsolicited notification message should comes up first, i.e.=20
returned</DIV>
<DIV>to the application before other normal messages - correct? If&nbsp;the=
=20
unsolicited</DIV>
<DIV>notification&nbsp;is mixed with other messages, the draft should =
specify=20
that</DIV>
<DIV>unsolicited messages are returned first.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve<BR></DIV></BODY></HTML>

--=_38635C8E.FF9EDCD5--



From list@netscape.com  Wed Jan  3 19:16:20 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA10377
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 19:16:20 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0400r308297;
	Wed, 3 Jan 2001 16:00:54 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f040EnU08006;
	Wed, 3 Jan 2001 16:14:49 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 16:14:49 -0800 (PST)
Message-ID: <3A53C034.736DFF2F@worldspot.com>
Date: Wed, 03 Jan 2001 16:13:40 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Steve Sonntag <VTAG@novell.com>
CC: robw@worldspot.com, ietf-ldapext@netscape.com
Subject: Re: Fwd: Re: draft Java-api-12
References: <sa53552e.023@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"eFfzb.A.08B.3B8U6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Steve Sonntag wrote:

>
>
> >>> Rob Weltman <robw@worldspot.com> 27-Dec-00 10:53:27 PM >>>
> Steven Sonntag wrote:
> >
> > Rob Weltman wrote:
> >
> > >   It might be better instead to eliminate the current unsolicited
> > > notification methods and instead have methods to add and remove
> > > listeners for usolicited notifications. The implementation can then
> > > discard unsolicited notifications if there are no listeners. For
> > > example (I haven't thought this through completely yet):
> > >
> > > LDAPConnection
> > >
> > > public LDAPResponseListener addUnsolicitedNotificationListener(
> > > LDAPResponseListener listener )
> > >
> > > public void removeUnsolicitedNotificationListener(
> > > LDAPResponseListener listener )
> > >
> > > Rob
> > >
> >
> > It seems natural to me that if unsolicited notifications are enabled on
> > a
> > listener, that the method LDAPListener.getMessageIDs() would include
> > message ID 0 in the list of message IDs, and that
> > LDAPConnection.abandon(0)
> > and LDAPConnection.abandon(listener) could be used to removeUnsolicited
> > notifications from a listener or listeners.  This raises some questions.
> >
> > 1) Should getMessageIDs show messageID 0 when unsolicited notification
> > are enabled?  (My vote is yes)
> >
> > 2) Should the draft allow abandon to be used to remove unsolicited
> > notifications?
> > (this means that message ID 0 is treated like a message that never
> > completes)
> >
> > 3) If number two is allowed, is removeUnsolicitedNotificationListener()
> > necessary?
> >
> > -Steve
>
>   I think it is easier for a client to handle unsolicited notifications as out-of-band events rather than lumped together with "normal" solicited responses. In almost all cases I would expect a client to want to know immediately that an unsolicited notification had arrived rather than having to poll and distinguish between solicited and unsolicited notifications. The event listener model reflects the paradigm of immediate out-of-band notification of unsolicited messages. Having the unsolicited messages ALSO appear in the normal message queue is confusing, error-prone, and not very useful as far as I can tell.
>
> Rob........................................What you say may be true, but - using the listener paradigm allows thedeveloper to combine any combination of listeners, normal messages,and unsolicited messages.  Why make an out of a special out of band APIfor something that could be handled naturally by the existing API. When you say the application wants to know immediately, you meanthe unsolicited notification message should comes up first, i.e. returnedto the application before other normal messages - correct? If the unsolicitednotification is mixed with other messages, the draft should specify thatunsolicited messages are returned first.
>  -Steve

  No, not at all. With an event listener model, a client that is interested in unsolicited notifications registers as an UnsolicitedNotificationListener. Immediately when an unsolicited notification arrives, a method of the client (e.g. messageReceived) is called with the unsolicited notification as parameter. That way the client is notified immediately and asynchronously rather than having to poll the message queue. Besides being simpler and more convenient for the client, it is much cleaner and less error-prone both for the client and for the implementor of the API. In-band responses are delivered in-band to the submitter of in-band requests; unsolicited notifications are delivered out-of-band to a requestor of unsolicited notifications.

Rob




From list@netscape.com  Wed Jan  3 22:42:29 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA15136
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 22:42:28 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f043W3327639;
	Wed, 3 Jan 2001 19:32:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f043ekA18696;
	Wed, 3 Jan 2001 19:40:46 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 19:40:46 -0800 (PST)
Message-Id: <524qke46iart0gle0p17.748lqm02@na8e3w3.pjsmark.com>
From: webmarketers2001@scqmdn.yahoo.com
Date: Wed, 03 Jan 2001 21:44:29 -0500
To: optinlist@vgxrd
Reply-To: pobox10@post.com
Subject: FREE BIG EARNER!! -xsaf
Content-Type: text/html;
	 charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Resent-Message-ID: <"D2-YUD.A.kjE.8C_U6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8BIT

<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Hello Dear Internet Friends</title>
</head>

<body>

<p><font face="Tw Cen MT" color="#0000FF">Hello Dear Internet Friends, I Have 
A
Real Special One Here!!</font></p>
<p><font face="Tw Cen MT"><b>My sincerest apologies if this message has 
reached
you in error.</b>&nbsp;<br>
We do our best to target our mailings to opt-in email addresses of
entrepreneurial&nbsp;<br>
and opportunity minded individuals from several direct marketing internet
resources.</font></p>
<p><font face="Tw Cen MT"><font size="2">= = = = = = = = = = = = = = = = = = 
= =
= = = = = = = = = = == = =<br>
<b>See Removal Instructions Below!! </b>Remove requests honored promptly!<br>
Please Note: Do not reply to this email to be removed as this is an 
unattended<br>
address and thus will go unheeded. Thank You.&nbsp;<br>
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =<br>
</font><br>
</font><font face="Tw Cen MT"><b>This is a special targeted offering! This 
email
has reached you as someone who<br>
we hope stands to benefit greatly from its reading!</b></font></p>
<p><b><u><font size="4" color="#0000FF" face="Tw Cen MT">L@@k Here!! 
</font><font face="Tw Cen MT" color="#FF0000">Take
advantage of this special offer! Please Read below.</font></u></b></p>
<p><b><font face="Tw Cen MT" color="#FF0000">FREE BIG EARNER!! FREE VISA CARD 
NO
APPLICATION OR<br>
ANNUAL FEES!!&nbsp;</font></b></p>
<p><font face="Tw Cen MT" color="#0000FF">The name of the company is
VisaRebates.com. They have<br>
launched a program to generate the largest number of<br>
credit card holders in the world, and they're giving<br>
away a lot of money to accomplish that.<br>
<br>
&nbsp;They're giving away a FREE Visa card with no<br>
application fee, no annual fee, free flight miles on<br>
any airline and merchandise points, and a 25-day grace<br>
period for those who like to pay off their cards every<br>
month.&nbsp;<br>
<br>
&nbsp;They're paying $10 commission for referring people,<br>
and then $2 when those people refer others, and $2<br>
when they refer people, etc.$2 all the way through 10<br>
levels deep. The multiplication can make that hundreds<br>
of thousands of dollars very fast.<br>
<br>
&nbsp;All this is from a free Visa card that has a super<br>
combination of benefits.&nbsp;<br>
<br>
&nbsp;This thing is growing fast.do you want to check it<br>
out? Then go to:<br>
</font><b><a href="http://3338824965/Index.cfm?ReferralID=Bowie1"><font 
face="Tw Cen MT" size="4" color="#FF0000">CLICK
HERE NOW!!<br>
<br>
</font></a><font face="Tw Cen MT" size="4" color="#FF0000">Have A prosperous
Year!!</font></b><b><font face="Tw Cen MT" color="#FF0000" size="2"><br>
</font></b><b><font face="Tw Cen MT" size="2">= = = = = = = = = = = = = = = = 
=
= = = = = = = = = = = </font></b><font face="Tw Cen MT" size="2">= =&nbsp; = 
= =
= = = = = ==<br>
</font><font face="Tw Cen MT"><span style="color: blue"><b>To
be removed from future mailings at no cost,<span style="FONT-SIZE: 10pt; 
COLOR: blue; FONT-FAMILY: 'Comic Sans MS'">&nbsp;</span></b>&nbsp;
<font color="#ff0000"><b><br>
</b><font size="4"><b><a href="mailto:replyhere@post.com">
Reply</a></b></font></font> <font size="4"><b><a href="mailto:replyhere@post.
com"> Here&nbsp;</a></b></font><b>&nbsp;</b>
and type<b> </b></span><b><span style="COLOR: navy; FONT-FAMILY: 'Comic Sans 
MS'">“</span><span style="COLOR: red; FONT-FAMILY: 'Comic Sans 
MS'">REMOVE</span><span style="COLOR: navy; FONT-FAMILY: 'Comic Sans 
MS'">”</span></b><span style="color: blue">
 in the subject line.
</span></font></p>

<p><font face="Tw Cen MT"><b><font color="#FF0000">Do not reply to this 
e-mail message
to</font></b><span style="color: blue"> be removed as this is an&nbsp; <b> 
<br>
 unattended address and therefore your request cannot be heeded!<br>
</b></span> <b> <font size="2">= = = = = = = = = = = = = = = = = = = = = = = 
= =
= = = = = = = = = = = = = == = =</font></b></font></p>

<p><font face="Tw Cen MT" color="#0000FF">This is not Spam: This message is 
sent in compliance of the new<br>
email Bill HR 1910. Under Bill HR 1910 passed by the 106th US<br>
Congress on May 24, 1999, this message cannot be considered SPAM<br>
as long as we include the way to be removed. </font></p>

</body>

</html>



From list@netscape.com  Wed Jan  3 23:22:12 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15365
	for <ldapext-archive@odin.ietf.org>; Wed, 3 Jan 2001 23:22:11 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0446C305753;
	Wed, 3 Jan 2001 20:06:12 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f044K7w27102;
	Wed, 3 Jan 2001 20:20:07 -0800 (PST)
Resent-Date: Wed, 3 Jan 2001 20:20:07 -0800 (PST)
Date: Fri, 24 Nov 00 00:07:54 EST
From: Undisclosed.Recipients2007@mx.thrunet.com
To: Undisclosed.Recipients1@mx.thrunet.com
Subject: -Generate New Leads and Sales- Market That Product !!!
Message-ID: <Undisclosed.Recipients2007@mx.thrunet.com>
Reply-To: Undisclosed.Recipients2007@mx.thrunet.com
Comments: Authenticated sender is <Undisclosed.Recipients1@mx.thrunet.com>
X-MIMETrack: Itemize by SMTP Server on sritnotes01/Srit-Intranet(Release 5.0.4 |June 8, 2000) at
 2001-01-03 15:11:25,
	Serialize by Router on sritnotes01/Srit-Intranet(Release 5.0.4 |June 8, 2000) at
 2001-01-04 12:28:19,
	Serialize complete at 2001-01-04 12:28:19
MIME-Version: 1.0
Resent-Message-ID: <"OoXzx.A.GnG.2n_U6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

J U S T   R E L E A S E D   

15-MIlion Fresh, Clean E-Mail Addresses + Hi Performance Lists



CALL-1-888-341-4786  TO ORDER !!!




      ***** 15 MILLION CD -  *****
     ***** NOW ONLY $299! *****
This "Special Price" is in effect for the next 96 hours,
after that we go back to our regular price of $399.00 ...
Don't delay... you can be in business tomorrow!  


When your ready to seriously market your product or opportunity
we offer the tools to help you succeed.
Our research has found that many people have tried one or more of
the following internet advertising methods.....

    Free Classifieds? (Don't work anymore)
    Web Site? (Takes thousands of visitors)
    Banners? (Expensive and losing their punch)
    E-Zine? (Hope they have a *huge* subscriber list)
    Search Engines? (Forget it, unless you're in the top 20)

        S O   W H A T   W I L L   W O R K ? 

Although often misunderstood, there is one method that has proven
to succeed time-after-time.

        E - M A I L   M A R K E T I N G ! !

IT'S A FACT... It if you're not using your computer to generate

income,  GOOD income,  you're leaving money on the table.  
Here's what the experts have to say about E-Mail Marketing:
*"E-mail is an incredible lead generation tool"
-Crains Magazine
*"A gold mine for those who can take advantage of
bulk e-mail programs" - The New York Times
*"Blows away traditional Mailing" - Advertising Age

Here's an example of your potential earnings if you have a
product or service that brings you a profit of around $30.
Remember, on the Internet, you can make money 7 days a week, 24
hours a day... even while you sleep, orders come from all over
the world!  

Orders:
Per Day    Weekly      Monthly      Yearly
   1       $  210      $   840      $ 10,080
   2          420        1,680        20,160
   3          630        2,520        30,240
   5        1,050        4,200        50,400
  10        2,100        8,400       100,000
  15        3,150       12,600       151,200

THE QUESTION IS... how do you generate those orders?
The least expensive and fastest way is through E-Mail Marketing.



CALL-1-888-341-4786  TO ORDER !!!


          M I L L I O N S   V O L U M E   12
***New Just Released - and now, 15 Million addresses***
We have just increased our list size from 10-million to
15-million without a corresponding increase in price! 
Over the past 6 years, we have gained a reputation for having the
cleanest, most responsive e-mail address lists in the industry.
No one has gone to the work it takes to produce an e-mail address
list of this quality.

Here's how we prepare our e-mail lists:
1. We clean and eliminate all duplicates. 
2. Next, we use a filter list of 400+ words/phrases to clean even
more. No address with inappropriate or profane wording survives!
3. Then we use our private database of thousands of known
Internet "extremists", those opposed to any kind of commercial
e-mail, and kicked off every one we could find.
4. All domains were verified to insure they're valid.
5. And finally, we sorted the list into easy-to-manage packets of
20,000 addresses in simple text (.txt) format that will work with
any computer operating system. 

WHAT DID WE END UP WITH?
      M I L L I O N S   V O L U M E   12
                    15 Million Addresses Strong!
With this super clean e-mail address lists you'll send less...and
get better results...  

    * Y O U   G E T   W H A T   Y O U   P A Y   F O R *
Our FRESH 15 Million, Volume 12 Address List CD, will result in:
* Higher Response Rates
* Higher Sales Conversion Ratios
* More Receptive prospects; Less Flames & Non-Buyers.
* Less Contact With Anti-Commerce Radicals & Extremists.

Remember that potential income chart at the beginning of
this message? Can you imagine the kind of money you could
make if you mailed one million pieces and sold only one
tenth (.01%) of one percent?  You do the math, you'll be
amazed!
                        
This is not a rental list that is restricted to a one-time
mailing.  You are purchasing an e-mail address list for your own
personal mailings and may use it over-and-over.

DON'T HESITATE on this offer or you will miss out on the least
expensive, most effective way to market... PERIOD!

      F  R  E  E    B  O  N  U  S 
Order within 96 hours and we'll include the following FREE
Bonuse:

Mailing Software (PC Only).  This software has sold for as high
as $399.00 in the past.  Not a demo, but a full working version.
SORRY, SINCE THE SOFTWARE IS FREE WE CANNOT OFFER ANY TECHNICAL
SUPPORT, however set-up instructions and help files are included.

This bonus is yours absolutely FREE if you
order within the next 96 hours --- After that... 
Poof!... it's gone! 

D O N ' T   H E S I T A T E  E-Marketing is the most
effective and fastest way to market anywhere... PERIOD!

O R D E R   N O W . . .OVERNITE SHIPMENT SAME DAY SERVICE 
(M-F) if your order is received before 1pm Central.




      ***** 15 MILLION CD -  *****
     ***** NOW ONLY $299! *****
This "Special Price" is in effect for the next 96 hours,
after that we go back to our regular price of $399.00 ...
Don't delay... you can be in business tomorrow!  

 



_____Yes! I am ordering within 96 hours.



CALL-1-888-341-4786  TO ORDER !!!



I understand that I am purchasing the Millions Vol.12 E-Mail
Address List on a CD, the addresses are not rented, but are mine
to use for my own mailing, over-and-over.  Free bonuses are
included, but cannot be considered part of the financial
transaction.  I understand that it is my responsibility to comply
with any laws applicable to my local area.  As with all software,
once opened the CD may not be returned, however, if found
defective it will be replaced with like product at no charge.










CALL-1-888-341-4786  TO ORDER !!!





J U S T   R E L E A S E D   
        15-MIlion Fresh, Clean E-Mail Addresses













 ******************************************************** 

 This message is sent in compliance of the proposed 
 bill:SECTION 301. 
 Per Section 301, Paragraph (a)(2)(C) of S. 1618, 
 further transmissions to you by the sender of this 
 email may be stopped at no cost to you by sending a 
 reply to this email address with the word remove in 
 the subject line. This message is not intended for 
 residents in the State of Washington, screening of 
 addresses has been done to the best of our technical 
 ability. If you are a Washington, Virginia, or 
 California resident or otherwise wish to be removed 
 from this list, further transmissions to you by the 
 sender of this email may be stopped at no cost to you 
 by sending a reply to   mstrsrvcs@mailme.org 
 with the word remove in the subject line. 

 ********************************************************* 




From list@netscape.com  Thu Jan  4 04:03:53 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA00576
	for <ldapext-archive@odin.ietf.org>; Thu, 4 Jan 2001 04:03:52 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f048ko325045;
	Thu, 4 Jan 2001 00:46:50 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0490ko17660;
	Thu, 4 Jan 2001 01:00:46 -0800 (PST)
Resent-Date: Thu, 4 Jan 2001 01:00:46 -0800 (PST)
Date: Thu, 4 Jan 2001 18:19:07 +0900
From: cbel007@belgium.de
Message-Id: <200101040919.SAA09314@server.bodysonic.co.jp>
To: cbel007@belgium.de
Subject: 100% LEGAL WAY TO GET EVERY CABLE CHANNEL!!!
Resent-Message-ID: <"XSO4R.A.qTE.9uDV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


100% LEGAL WAY TO GET EVERY CABLE CHANNEL!!!

Are you tired of paying the cable company to rent you a
cable converter?

Then why continue to pay them when you can own your own
LEGALLY?

With recent advances in technology it is now cheaper and
easier to buy your own descrambler and never have to rent a
converter again.

Our Maestro Univeral Cable Descrambler works with 99% of all
cable companies and it is 100% Bullet Proof so it will never
get deprogrammed by your cable company.

This ALL IN ONE UNIT is so UNIVERSAL that if you move, it
moves with you.

YOU WILL NEVER HAVE TO RENT OR BUY ANOTHER
CONVERTER/DESCRAMBLER AGAIN!

We are so sure that you will love our product that it comes
with a NO QUESTIONS ASKED 30 DAY MONEY BACK GUARANTEE!

Quantity Discounts are available so please ask.

If you have questions, comments, want to place an order or
would like to be removed from future mailings pleace call
1-800-706-9164.



From list@netscape.com  Thu Jan  4 13:39:05 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12645
	for <ldapext-archive@odin.ietf.org>; Thu, 4 Jan 2001 13:39:04 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f04IMm325049;
	Thu, 4 Jan 2001 10:22:48 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f04IaiI15154;
	Thu, 4 Jan 2001 10:36:44 -0800 (PST)
Resent-Date: Thu, 4 Jan 2001 10:36:44 -0800 (PST)
DATE: 04 Jan 01 1:35:49 PM
FROM: Tp5kdYB0R@mail.jei.co.kr
Message-ID: <Tb3xZ5w7Qc4dEv>
SUBJECT: 2k to 5k a week
Resent-Message-ID: <"omquL.A.4rD.3KMV6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

$ ENTREPRENEURS $
Tired of working for someone else and getting paid what "they" feel you 
are really worth?
Tired of the "get-rich-quick" $5 fantasy programs? Tired of the MLM "dream scene"?
Looking for a legitimate home-based enterprise that can generate you $lOk-$20k+ monthly?
THEN CHECK THIS OUT!!!

80% profit on all sales that pay you from $1250-$6250 per sale
No personal selling or "convince me" tactics involved..
No special skills or equipment required or "inventory" to keep..
Complete information system in place does the explaining for you..
Free-enterprise in its purest form, not MLM or franchise..
Full training and support in an environment of up most integrity..
Exceptional products, not "vitamins, lotions, and potions"..
Lead generation system that brings qualified prospects to you..
Multiple 6 figure income realistically attainable in 1st year..
3 year retirement program... PERIOD!..

This program is all about money... how to make it,
how to keep it, and how to make it work for you..

CALL NOW! ! ! 1-800-336-3250

Leave your name and number twice! I will get you all the information you need to make your own relaxed and intelligent decision about your future..
(Serious inquiries only please)


*********************************************************************
Your Email Address Removal/Deletion Instructions:
   
   We comply with proposed federal legislation regarding unsolicited
   commercial email by providing you with a method for your email address 
   to be permanently removed from our database and any future mailings 
   from our company.
   
   To remove your address, please send an email message with the word REMOVE 
   in the subject line to: opt-out@usa.com 
 
          If you do not type the word REMOVE in the subject line, 
             your request to be removed will not be processed.




From list@netscape.com  Thu Jan  4 14:05:54 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13252
	for <ldapext-archive@odin.ietf.org>; Thu, 4 Jan 2001 14:05:54 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f04Inq329568;
	Thu, 4 Jan 2001 10:49:52 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f04J3m629579;
	Thu, 4 Jan 2001 11:03:48 -0800 (PST)
Resent-Date: Thu, 4 Jan 2001 11:03:48 -0800 (PST)
From: "Paul \(Enxi\) Chou" <enxi@ss8.com>
To: <ietf-ldapext@netscape.com>
Subject: Ask for information about LDAP Server
Date: Thu, 4 Jan 2001 14:05:57 -0500
Message-ID: <NEBBIBFDHMBMMNCAHOPMEEFBCAAA.enxi@ss8.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Resent-Message-ID: <"cA5WpD.A.5NH.TkMV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hi,

Can anyone provide me some information about UNIX/Vxwork based LDAP software
with a database which support/can be configured to LDAP schema (Policy Core
LDAP Schema, etc.) ?

Thanks!
Paul

+------------------------------------------------+
| Paul(enxi) Chou           Software Engineer    |
| SS8 Networks Canada (Toronto)                  |
| 55 Commerce Valley Drive West                  |
| 5th Floor South                                |
| THORNHILL, Ontario  L3T 7B9                    |
| Tel:905-889-1357           Fax: 905-889-9853   |
+------------------------------------------------+




From list@netscape.com  Thu Jan  4 15:51:14 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA15815
	for <ldapext-archive@odin.ietf.org>; Thu, 4 Jan 2001 15:51:13 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f04KZQ318340;
	Thu, 4 Jan 2001 12:35:26 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f04KnNs27307;
	Thu, 4 Jan 2001 12:49:23 -0800 (PST)
Resent-Date: Thu, 4 Jan 2001 12:49:23 -0800 (PST)
Importance: Normal
Subject: Re: ldap acl draft (06): browse needed ?
To: <rbyrne@bebop.France.Sun.COM>
Cc: <ietf-ldapext@netscape.com>
From: George_Robert_Blakley_III@tivoli.com
Date: Thu, 4 Jan 2001 14:52:09 -0600
Message-ID: <OF08914713.256ACBF6-ON862569CA.0072250B@tivoli.com>
X-MIMETrack: Serialize by Router on SCHub/Tivoli Systems(Release 5.0.4a |July 24, 2000) at
 01/04/2001 02:48:32 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Resent-Message-ID: <"aEaRXC.A.FpG.MHOV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Rob,

The intent of the "browse" permission is not to prevent discovery of DNs;
that is what "returnDN" permission is for.

"browse" is to take care of the case where there is a hierarchy of entries
and:

(1) A subject "S" has authority to perform some operation (say "read") on
an entry (call it "E") which is not the root
(2) "S" has no permission to read or otherwise do anything to some entry
"I" which is on the path between the root and "E"
(3) "S" does not know or does not wish to use the explicit name of entry
"E"

An example of this case is when a subject "Bob" has "read" access to a leaf
entry but no access to any other entry,
and does not know the name of any entry in the hierarchy.  Bob wishes to do
a query on some attribute value.  This query
matches an attribute of "E", and hence (since Bob has permission to read
E), E should be returned in response to the
query.

However, if Bob tries to execute the search starting at the only point he
knows about (the root), the query will fail, because
he has no permission to "I" or any other entry on the path between the root
and "E".

This is exactly analogous to the use of the "x" mode bit in the UNIX
filesystem to allow users to traverse directories into
which they cannot write and from which they cannot read.

--bob

Bob Blakley
Chief Scientist, Security
Tivoli Systems, Inc.


ietf-ldapext-request@netscape.com on 12/14/2000 09:22:38 PM

Please respond to <rbyrne@bebop.France.Sun.COM>

To:   <ietf-ldapext@netscape.com>
cc:
Subject:  ldap acl draft (06): browse needed ?




The current acl draft proposes an entry level permission called "browseDN"
(4.2.2).  The idea behind this permssion is to able to set a
policy saying something like "you can see this entry if you name it
explicitly as the base of a search, otherwise not".

At Pittsburgh people seemed to like this permission and I agreed to do a
proposal for this....however, relative
to a single "read" level permission that ignores scoping it does complicate
things.  The definition of the required permissions for
search (5.2) already has to deal with a fair line up of other permssions
(filter (presence and "the rest"), attribute level read, returnDN
and discloseOnError).  While providing more permssions certainly increases
the flexibility of the model,
it also makes it harder to understand and administrate,  so my inclination
is drop the browse permission in favour of a single "read"
permission at the entry level.

My question is do people feel strongly that the "browse" permission is
required ?  If so, please propose a compelling scenario that
really needs this granularity  of control of search permissions.  I will
then include this as a motivating example and propose a way to include
it in the required permssions for search.  Otherwise I intend to drop it
for the 07 draft...

Rob.






From list@netscape.com  Fri Jan  5 00:31:33 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23545
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 00:31:33 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f055FT300883;
	Thu, 4 Jan 2001 21:15:29 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f055TQ211946;
	Thu, 4 Jan 2001 21:29:26 -0800 (PST)
Resent-Date: Thu, 4 Jan 2001 21:29:26 -0800 (PST)
Date: Fri, 5 Jan 2001 13:28:17 +0800
From: Zhang Dawei <eng70755@leonis.nus.edu.sg>
To: "Paul (Enxi) Chou" <enxi@ss8.com>
cc: ietf-ldapext@netscape.com
Subject: Re: Ask for information about LDAP Server
In-Reply-To: <NEBBIBFDHMBMMNCAHOPMEEFBCAAA.enxi@ss8.com>
Message-ID: <Pine.SGI.4.02.10101051320270.12651-100000@leonis.nus.edu.sg>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-Message-ID: <"vPqoiC.A.Y6C.1uVV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

try OpenLDAP.

Check for more information at the website http://www.openldap.org

  
On Thu, 4 Jan 2001, Paul (Enxi) Chou wrote:

> Hi,
> 
> Can anyone provide me some information about UNIX/Vxwork based LDAP software
> with a database which support/can be configured to LDAP schema (Policy Core
> LDAP Schema, etc.) ?
> 
> Thanks!
> Paul
> 
> +------------------------------------------------+
> | Paul(enxi) Chou           Software Engineer    |
> | SS8 Networks Canada (Toronto)                  |
> | 55 Commerce Valley Drive West                  |
> | 5th Floor South                                |
> | THORNHILL, Ontario  L3T 7B9                    |
> | Tel:905-889-1357           Fax: 905-889-9853   |
> +------------------------------------------------+
> 
> 



From list@netscape.com  Fri Jan  5 03:11:33 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA07481
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 03:11:31 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0580g305187;
	Fri, 5 Jan 2001 00:00:42 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0589RY12345;
	Fri, 5 Jan 2001 00:09:27 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 00:09:27 -0800 (PST)
Date: Fri, 5 Jan 2001 00:08:48 -0800 (PST)
Message-Id: <200101050808.f0588kB29954@xwing.netscape.com>
From: livtom2001@XNDC.yahoo.com
To: Friend.QVEF@netscape.com
Subject:  EARN UNLIMITED INCOME WORKING AT HOME -CJGX
X-Reply-To:  livtom2001@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"k3jRh.A.YAD.1EYV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Dear Friend,

There is a possibility that we haven't met, but you were chosen by someone to receive 
this E-Mail because you are a motivated person.
PLEASE, do yourself a favour and PRINT THIS! Read it thoroughly! Be sure you 
don't miss any of the points. Then put it down and walk away.  THEN READ IT 
AGAIN! I am sending you a lot of information that is hard to absorb the first time you 
read it.
If you don't believe this program will work for you, send it to 10-20 of your closest 
friends that you trust and ask them what they think.
THIS REALLY WORKS! Have the faith, and don't miss this opportunity! GET 
INVOLVED and it will work for you as it does for us!!!!!
Due to the popularity of this letter on the Internet, A MAJOR NIGHTLY NEWS 
program recently dedicated an entire show to the investigation of the program 
described below to see if it really can make people money.
The show also investigated whether or not the program was legal.  Their findings 
proved that there are absolutely no laws prohibiting the participation in the program. 
This has helped to show people that this is a simple, harmless and fun way to make 
some extra money at home.
The results have been truly remarkable! So many people are participating that those 
involved are doing much better than ever before! Since everyone makes more as more 
people try it out, it's been very exciting!
You will understand ONLY if you get involved!
********* THE ENTIRE PLAN IS HERE BELOW *********
*** PRINT THIS NOW FOR FUTURE REFERENCE!! ***

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

If you would like to make AT LEAST $50,000 in less than 90 days—READ ON!
(If not, forward this to someone who would like to make this money... It works as 
designed, but only for those who follow it to the letter!)
Please read this program...THEN READ IT AGAIN!!

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

THIS IS A LEGITIMATE, LEGAL, MONEY MAKING OPPORTUNITY!!
It does NOT require you to come into contact with people, either directly or by 
phone. Just follow the instructions, and you WILL make money. This simplified e-mail 
marketing program works perfectly 100% EVERY TIME!
E-mail is the sales tool of the future. Take advantage of this virtually free method of 
advertising NOW!!! The longer you wait, the greater the competition!! Get your piece 
of this action NOW!!!


Hello - My name is Johnathon Rourke, I'm from Rhode Island.
The enclosed information is something I almost let slip through my fingers. Fortunately, 
sometime later I re-read everything and gave some thought and study to it. Two years 
ago, the corporation I worked for the past twelve years downsized and my position 
was eliminated.  After unproductive job interviews, I decided to open my own 
business.
Over the past year, I incurred many unforeseen financial problems.  I owed my family, 
friends and creditors over $35,000. The economy was taking a toll on my business 
and I just couldn't seem to make ends meet.  I had to refinance and borrow against 
my home to support my family and struggling business.
AT THAT MOMENT something significant happened in my life. I am writing to share 
the experience in hopes that this could change your life FOREVER!
FINANCIALLY$$$!!!
In mid December, I received this program in my e-mail. Six months prior to receiving 
this program I had been sending away for information on various business 
opportunities. All of the programs I received, in my opinion, were not cost effective. 
They were either too difficult for me to comprehend, or the initial investment was too 
much for me to risk to see if they would work. But as I was saying, in December of 
1997 I received this program. I didn't send for it, or ask for it, they just got my name 
off a mailing list!
THANK GOODNESS FOR THAT!!! After reading it several times, to make sure I 
was reading it correctly, I couldn't believe my eyes! Here was a MONEY MAKING 
MACHINE I could start immediately without any debt.
Like most of you I was still a little sceptical and a little worried about the legal aspects 
of it all. So I checked it out with the U.S.  Post Office (1-800-725-2161 24-hrs) and 
they confirmed that it is indeed legal!
After determining the program was LEGAL I decided "WHY NOT!?!??"
Initially I sent out 10,000 e-mails. It cost me about $15 for my time on-line. The great 
thing about e-mail is that I don't need any money for printing to send out the program, 
and, because I also send the product (reports) by e-mail, my only expense is my time!
In less than one week, I was starting to receive orders for REPORT #1!  By January 
13, I had received 26 orders for REPORT #1. Your goal is to RECEIVE at least 20 
ORDERS FOR REPORT #1 WITHIN 2 WEEKS. IF YOU DON'T, SEND OUT 
MORE PROGRAMS UNTIL YOU DO.
My first step in making $50,000 in 90 days was done. By January 30, I had received 
196 orders for REPORT #2. Your goal is to RECEIVE AT LEAST 100+ ORDERS 
FOR REPORT #2 WITHIN 2 WEEKS. IF NOT, SEND OUT MORE 
PROGRAMS UNTIL YOU DO! ONCE YOU HAVE 100 ORDERS, THE REST 
IS EASY. RELAX, YOU WILL MAKE YOUR $50,000 GOAL."
Well, I had 196 orders for REPORT #2--96 more than I needed.  So I sat back and 
relaxed. By March 1, of my e-mailing of 10,000, I received $58,000 with more 
coming in every day! I paid off ALL my debts and bought a much needed, new car!
Please take your time to read this plan. IT WILL CHANGE YOUR LIFE 
FOREVER$!!! Remember, it won't work if YOU don't try it!
This program DOES work, BUT you must follow it EXACTLY!
Especially the rules of not trying to place your name in a different place. It won't work 
and you'll lose out on A LOT of money! In order for this program to work, you must 
meet your goal of 20+ orders for REPORT #1, and 100+ orders for REPORT #2 
and YOU WILL MAKE $50,000 or more in 90 days!
I AM LIVING PROOF THAT IT WORKS!!! If you choose not to participate in this 
program, I am sorry. It really is a great opportunity with little cost or risk to you. If 
you choose to participate, follow the program and you will be on your way to financial 
security. If you are a fellow business owner and are in financial trouble like I was, or 
you want to start your own business, consider this a sign. I DID! $$
Sincerely,
Johnathon Rourke

A PERSONAL NOTE FROM THE ORIGINATOR OF THIS PROGRAM:
By the time you have read the enclosed program and reports, you should have 
concluded that such a program, and one that is legal, could not have been created by 
an amateur. Let me tell you a little about myself.  I had a profitable business for 10 
years. Then in 1979 my business began falling off. I was doing the same things that 
were previously successful for me, but it wasn't working. Finally, I figured it out. It 
wasn't me, it was the economy. Inflation and recession had replaced the stable 
economy that had been with us since 1945.
I don't have to tell you what happened to the unemployment rate...  because many of 
you know from first-hand experience. There were more failures and bankruptcies than 
ever before. The middle class was vanishing. Those who knew what they were doing 
invested wisely and moved up. Those who did not, including those who never had 
anything to save or invest, were moving down into the ranks of the poor. As the saying 
goes, "THE RICH GET RICHER AND THE POOR GET POORER." The 
traditional methods of making money will never allow you to "move up" or "get rich"— 
inflation will see to that!
You have just received information that can give you financial freedom for the rest of 
your life, with "NO RISK" and "JUST A LITTLE BIT OF EFFORT." You can make 
more money in the next few months than you have ever imagined. I should also point 
out that I would not see a penny of this money, nor anyone else who has provided a 
testimonial for this program.
I have retired from the program after sending thousands and thousands of programs. 
Follow the program EXACTLY AS INSTRUCTED. Do not change it in any way. It 
works exceedingly well as it is now. Remember to e-mail a copy of this exciting report 
to everyone you can think of. One of the people you send this to may send out 
50,000...and your name will be on every one of them!
REMEMBER though, ----- the MORE YOU SEND OUT, the more potential 
customers you will reach. So my friend, I have given you the ideas, information, 
materials and OPPORTUNITY to become FINANCIALLY INDEPENDENT!
IT IS UP TO YOU!! NOW DO IT!!


BEFORE YOU delete this program from your in-box, as I almost did, take a little 
time to read it and REALLY THINK ABOUT IT. Get a pencil and figure out what 
could happen when YOU participate. Figure out the worst possible response and no 
matter how you calculate it, you will still make a LOT OF MONEY! You will 
definitely get back what you invested. Any doubts you have will vanish when your first 
orders come in.
$$$ IT WORKS!!! $$$
Jody Jacobs Richmond, VA


HERE'S HOW THIS AMAZING PROGRAM WILL MAKE YOU THOUSANDS 
OF DOLLAR$$$$!!!!
This method of raising capital REALLY WORKS 100% EVERY TIME. I am sure 
that you could use up to $50,000 or more in the next 90 days!  Before you say 
"BULL... ", please read this program carefully. This is not a chain letter, but a perfectly 
legal money making business, marketing informational business reports.
As with all multi-level businesses, we build our business by recruiting new partners and 
selling our products. Every state in the USA allows you to recruit new multi-level 
business partners, and we sell and deliver a product for EVERY dollar received.
YOUR ORDERS COME BY MAIL AND ARE FILLED BY E-MAIL, so you are 
not involved in personal selling. You do it privately in your own home, store or office. 
This is the EASIEST marketing plan anywhere! It is simply order filling by email!

The product is informational and instructional material, keys to the secrets for 
everyone on how to open the doors to the magic world of E-COMMERCE , the 
information highway, the wave of the future!
PLAN SUMMARY:
(1)	You order the 4 reports listed below ($5 each). They come to you by email.
(2)	SAVE A COPY OF THIS ENTIRE LETTER and put your name after 
Report #1. Move the other names down.
(3)	Via the Internet, access Yahoo.com or any of the other major search engines 
to locate hundreds of bulk email service companies (search for "bulk email") and 
have them send 25,000 - 50,000 emails for you (about $49+).
(4)	Orders will come to you by postal mail - simply email them the Report they 
ordered. Let me ask you - isn't this about as easy as it gets?!?!?!


By the way there are over 50 MILLION email addresses with millions more joining 
the internet each year so don't worry about "running out" or "saturation". People are 
used to seeing and hearing the same advertisements every day on radio/TV. How 
many times have you received the same pizza flyers on your door? Then one day you 
are hungry for pizza and you order one. Same thing with this letter. I received this 
letter many times - then one day I decided it was time to try it.


YOU CAN START TODAY - JUST DO THESE EASY STEPS:
STEP #1. ORDER THE FOUR REPORTS
Order the four reports shown on the list below (you can't sell them if you don't order 
them).—For each report, send $5.00 CASH, the NAME & NUMBER OF THE 
REPORT YOU ARE ORDERING, YOUR E-MAIL ADDRESS, and YOUR 
NAME & RETURN ADDRESS (in case of a problem) to the person whose name 
appears on the list next to the report.
MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE IN 
CASE OF ANY MAIL PROBLEMS!
Within a few days you will receive, by e-mail, each of the four reports. Save them on 
your computer so you can send them to the 1,000's of people who will order them 
from you.
STEP #2. ADD YOUR MAILING ADDRESS TO THIS LETTER
a.	Look below for the listing of the four reports.
b.	After you've ordered the four reports, delete the name and address under 
REPORT #4. This person has made it through the cycle.
c.	Move the name and address under REPORT #3 down to REPORT #4.
d.	Move the name and address under REPORT #2 down to REPORT #3.
e.	Move the name and address under REPORT #1 down to REPORT #2.
f.	Insert your name/address in the REPORT #1 position.
Please make sure you COPY ALL INFORMATION, every name and address, 
ACCURATELY!
STEP #3. Take this entire letter, including the modified list of names, and save it to 
your computer. Make NO changes to these instructions. Now you are ready to use 
this entire email to send by email to prospects.
Report #1 will tell you how to download bulk email software and email addresses so 
you can send it out to thousands of people while you sleep! Remember that 50,000+ 
new people are joining the Internet every month.
Your cost to participate in this is practically nothing (surely you can afford $20 and 
initial bulk mailing cost). You obviously already have a computer and an Internet 
connection and e-mail is FREE!
There are two primary methods of building your downline:
METHOD #1: SENDING BULK E-MAIL Let's say that you decide to start small, 
just to see how it goes. We'll also assume that you, and all those involved, email out 
only 2,000 programs each. Let's also assume that the mailing receives a 0.5% 
response. The response could be much better! Also, many people will email out 
hundreds of thousands of programs instead of 2,000 (Why stop at 2000?). But 
continuing with this example, you send out only 2,000 programs. With a 0.5% 
response, that is only 10 orders for

REPORT #1. Those 10 people respond by sending out 2,000 programs each for a 
total of 20,000. Out of those 0.5%, 100 people respond and order
REPORT #2. Those 100 mail out 2,000 programs each for a total of 200,000. The 
0.5% response to that is 1,000 orders for
REPORT #3. Those 1,000 send out 2,000 programs each for a 2,000,000 total. The 
0.5% response to that is 10,000 orders for
REPORT #4. That's 10,000 $5 bills for you. CASH!!!  Your total income in this 
example is $50 + $500 + $5,000 + $50,000 for a total of $55,550!!!
REMEMBER FRIEND, THIS IS ASSUMING 1,990 OUT OF THE 2,000 
PEOPLE YOU MAIL TO WILL DO ABSOLUTELY NOTHING AND TRASH 
THIS PROGRAM!
DARE TO THINK FOR A MOMENT WHAT WOULD HAPPEN IF 
EVERYONE, OR HALF SENT OUT 100,000 PROGRAMS INSTEAD OF 
2,000. Many people will do just that and more!
METHOD #2 - PLACING FREE ADS ON THE INTERNET Advertising on the 
Internet is very, very inexpensive, and there are HUNDREDS of FREE places to 
advertise. Let's say you decide to start small just to see how well it works. Assume 
your goal is to get ONLY 10 people to participate on your first level. (Placing a lot of 
FREE ads on the Internet will EASILY get a larger response.) Also assume that 
everyone else in YOUR ORGANIZATION gets ONLY 10 downline members.  
Look how this small number accumulates to achieve the STAGGERING results 
below:
1st level—your first 10 send you $5 ..................……....$50
2nd level--10 members from those 10 ($5 x 100)...........$500
3rd level--10 members from those 100 ($5 x 1,000)......$5,000
4th level--10 members from those 1,000 ($5 x 10,000)..$50,000
$$$$$$ THIS TOTALS -----------------------------------$55,550 $$$$$$
AMAZING ISN'T IT? Remember friends, this assumes that the people who 
participate only recruit 10 people each. Think for a moment what would happen if 
they got 20 people to participate! Most people get 100's of participants and many will 
continue to work this program, sending out programs WITH YOUR NAME ON 
THEM for YEARS! THINK ABOUT IT!


People are going to get emails about this plan from YOU or SOMEBODY ELSE and 
many will work this plan - the question is - Don't you want YOUR NAME to be on 
the emails they will send out?
* * * DON'T MISS OUT!!!
* * * JUST TRY IT ONCE!!! * * *
* * SEE WHAT HAPPENS!!!
*** YOU'LL BE AMAZED!!!* *


ALWAYS PROVIDE SAME-DAY SERVICE ON ALL ORDERS!
This will guarantee that the e-mail THEY send out with YOUR name and address on 
it will be prompt because they can't advertise until they receive the report!


GET STARTED TODAY: PLACE YOUR ORDER FOR THE FOUR REPORTS 
NOW.
Notes: -- ALWAYS SEND $5 CASH (U.S. CURRENCY) FOR EACH REPORT.  
CHECKS NOT ACCEPTED. Make sure the cash is concealed by wrapping it in 
TWO sheets of paper. On one of those sheets of paper write:
(a)	The number & name of the report you are ordering
(b)	Your e-mail address, and
(c)	Your name & postal address.

REPORT #1a "The Insider's Guide to Advertising for Free on the Internet"
ORDER REPORT #1a FROM:
Liviu Tomulescu
P.O. Box 1365
West Perth WA 6872
Australia

NOTE: I, (and every member listed below), am DEDICATED to helping you with this 
program so it will work for you also. This IS a TEAM EFFORT!  We communicate 
by email and even by phone! TRY US!)

REPORT #2a "The Insider's Guide to Sending Bulk E-mail on the Internet"
ORDER REPORT #2a FROM:
MARK GAUDIANO
133 Sutton Ave.
Hopwood, Pa 15445
 

REPORT #3a "The Secrets to Multilevel Marketing on the Internet"
ORDER REPORT #3a FROM:
Kim Kerslake
Bulford Road 
Rai Valley 
Marlborough 7156
New Zealand
 

REPORT #4a "How to become a Millionaire utilizing the Power of
Multilevel Marketing and the Internet"

ORDER REPORT #4a FROM:
DAVID TALTY
P.O. Box 51
Rochester, MA 02770

 

******* TIPS FOR SUCCESS *******
TREAT THIS AS YOUR BUSINESS! Be prompt, professional, and follow the 
directions accurately. —Send for the four reports IMMEDIATELY so you will have 
them when the orders start coming in because:
When you receive a $5 order, you MUST send out the requested product/report. It is 
required for this to be a legal business and they need the reports to send out their 
letters (with your name on them!)
ALWAYS PROVIDE SAME-DAY SERVICE ON THE ORDERS YOU 
RECEIVE. Be patient and persistent with this program - If you follow the instructions 
exactly - results WILL FOLLOW. $$$$
******* YOUR SUCCESS GUIDELINES *******
Follow these guidelines to guarantee your success: If you don't receive 20 orders for 
REPORT #1 within two weeks, continue advertising or sending e-mails until you do. 
Then, a couple of weeks later you should receive at least 100 orders for REPORT#2. 
If you don't, continue advertising or sending e-mails until you do. Once you have 
received 100 or more orders for REPORT #2, YOU CAN RELAX, because the 
system is already working for you, and the cash will continue to roll in!
THIS IS IMPORTANT TO REMEMBER: Every time your name is moved down on 
the list, you are placed in front of a DIFFERENT report. You can KEEP TRACK of 
your PROGRESS by watching which report people are ordering from you.
To generate MORE INCOME, simply send another batch of e-mails or continue 
placing ads and start the whole process again! There is no limit to the income you will 
generate from this business!
Before you make your decision as to whether or not you participate in this program, 
please answer one question. ARE YOU HAPPY WITH YOUR PRESENT 
INCOME OR JOB? If the answer is no, then please look at the following FACTS 
about this SUPER SIMPLE MLM program:
1.NO face-to-face selling, NO meetings, NO inventory!  NO Telephone calls, NO 
big cost to start! Nothing to learn, NO skills needed! (Surely you know how to send 
email?)
2.No equipment to buy - you already have a computer and Internet connection - so 
you have everything you need to fill orders!
3.You are selling a product, which does NOT COST ANYTHING TO PRODUCE 
OR SHIP! (Emailing copies of the reports is FREE!)
4.All of your customers pay you in CA$H! This program will change your LIFE 
FOREVER!! Look at the potential for you to be able to quit your job and live a life of 
luxury you could only dream about!  Imagine getting out of debt and buying the car 
and home of your dreams! Imagine being able to work a super-high paying 
LEISURELY EASY BUSINES FROM HOME!
$$$ FINALLY MAKE SOME DREAMS COME TRUE! $$$
ACT NOW! Take your first step toward achieving financial independence.  Order the 
reports and follow the program outlined above—SUCCESS will be your reward!
Thank you for your time and consideration.
PLEASE NOTE: If you need help with starting a business, registering a business 
name, learning how income tax is handled, etc., contact your local office of the Small 
Business Administration (a Federal Agency) 1-800-827-5722 for free help and 
answers to questions.
Also, the Internal Revenue Service offers free help via telephone and free seminars 
about business tax requirements. Your earnings are highly dependent on your activities 
and advertising. The information contained on this site and in the report constitutes no 
guarantees, stated or implied. In the event that it is determined that this site or report 
constitutes a guarantee of any kind, that guarantee is now void. The earnings amounts 
listed on this site and in the report are estimates only. If you have any questions of the 
legality of this program, contact the Office of Associate Director for Marketing 
Practices, Federal Trade Commission, Bureau of Consumer Protection in 
Washington, DC.


Under Bill s.1618 TITLE III passed by the 105th US Congress this letter cannot be 
considered Spam as long as the sender includes contact information and a method of 
removal. You can reply and request removal, however, this is a one-time e-mail 
transmission and as such no request for removal is necessary.




From list@netscape.com  Fri Jan  5 03:33:58 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA07605
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 03:33:57 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f058N3307164;
	Fri, 5 Jan 2001 00:23:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f058Vl217367;
	Fri, 5 Jan 2001 00:31:47 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 00:31:47 -0800 (PST)
Date: Fri, 5 Jan 2001 00:31:18 -0800 (PST)
Message-Id: <200101050831.f058V7B05532@xwing.netscape.com>
From: u'llmake@WDEN.more.netscape.com
To: @netscape.com
Subject:  $100,000 to you in the next couple of months. -GBTU
X-Reply-To:  m58wd@yohoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"H-ZR_C.A.3OE.xZYV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Want to receive a large amount of money? Give away access to 
a Free Visa Card and get paid $2 down to 10 levels. Do the 
math, if everyone reffers only 5 people. You know 5 people that 
are in need of more money and a Visa Card, right? This can 
mean hundreds of thousands of dollars and more!! Send me an 
e-mail right now, and I'll get the info to you. 
mailto:redbaronm@yahoo.com?subject=moreinfo 




From list@netscape.com  Fri Jan  5 08:57:00 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA12630
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 08:57:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f05Des308323;
	Fri, 5 Jan 2001 05:40:55 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f05Dsrs28550;
	Fri, 5 Jan 2001 05:54:53 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 05:54:53 -0800 (PST)
Message-Id: <200101051351.f05Dp4E20429@smtp13.singnet.com.sg>
X-Sender: try2k@email.com
From: Webmaster <try2k@email.com>
To: "eweb8" <try2k@email.com>
Date: Fri, 05 Jan 2001 21:51:34 +0800
Subject: FREE VISA CARD Pays Up To 10 Level!!! 
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"y5Do7B.A.09G.sIdV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hi,


Wishing you a happy and prosperous 2001!

Take a quick look at the Free Visa Card program.
They're giving away free Visa cards with free flight miles on any airline and 
paying MLM commissions to refer other Cardholders.
They pay out on a huge 10-level plan ($10 for the first level and $2 on the next 
nine).

You already know how many millions of dollars that kind of multiplication can 
generate. Nobody buys a thing. The money comes from the bank because of the value 
of cardholders. This thing is spreading like wildfire. Please check it out.

Request for info!
mailto:amzin@usa.com?subject=Vinfo pls!

Regards.

......................................................................
To be removed from this mailing list please send mailto:holai@usa.com?subject=remove 
me!









From list@netscape.com  Fri Jan  5 10:32:38 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA15031
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 10:32:37 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f05FGO317307;
	Fri, 5 Jan 2001 07:16:25 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f05FUNo27241;
	Fri, 5 Jan 2001 07:30:23 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 07:30:23 -0800 (PST)
Message-Id: <sa558612.008@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Fri, 05 Jan 2001 08:29:58 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <robw@worldspot.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Fwd: Re: draft Java-api-12
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_7D261F92.C5A4E733"
Resent-Message-ID: <"-Byj1B.A.XpG.OieV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_7D261F92.C5A4E733
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable



>>> Rob Weltman <robw@worldspot.com> 03-Jan-01 5:13:40 PM >>>
Steve Sonntag wrote:

>
>
> >>> Rob Weltman <robw@worldspot.com> 27-Dec-00 10:53:27 PM >>>
> Steven Sonntag wrote:
> >
> > Rob Weltman wrote:
> >
> > >   It might be better instead to eliminate the current unsolicited
> > > notification methods and instead have methods to add and remove
> > > listeners for usolicited notifications. The implementation can then
> > > discard unsolicited notifications if there are no listeners. For
> > > example (I haven't thought this through completely yet):
> > >
> > > LDAPConnection
> > >
> > > public LDAPResponseListener addUnsolicitedNotificationListener(
> > > LDAPResponseListener listener )
> > >
> > > public void removeUnsolicitedNotificationListener(
> > > LDAPResponseListener listener )
> > >
> > > Rob
> > >
> >
> > It seems natural to me that if unsolicited notifications are enabled =
on
> > a
> > listener, that the method LDAPListener.getMessageIDs() would include
> > message ID 0 in the list of message IDs, and that
> > LDAPConnection.abandon(0)
> > and LDAPConnection.abandon(listener) could be used to removeUnsolicited=

> > notifications from a listener or listeners.  This raises some =
questions.
> >
> > 1) Should getMessageIDs show messageID 0 when unsolicited notification
> > are enabled?  (My vote is yes)
> >
> > 2) Should the draft allow abandon to be used to remove unsolicited
> > notifications?
> > (this means that message ID 0 is treated like a message that never
> > completes)
> >
> > 3) If number two is allowed, is removeUnsolicitedNotificationListener()=

> > necessary?
> >
> > -Steve
>
>   I think it is easier for a client to handle unsolicited notifications =
as out-of-band events rather than lumped together with "normal" solicited =
responses. In almost all cases I would expect a client to want to know =
immediately that an unsolicited notification had arrived rather than =
having to poll and distinguish between solicited and unsolicited notificati=
ons. The event listener model reflects the paradigm of immediate out-of-ban=
d notification of unsolicited messages. Having the unsolicited messages =
ALSO appear in the normal message queue is confusing, error-prone, and not =
very useful as far as I can tell.
>
> Rob........................................What you say may be true, but =
- using the listener paradigm allows thedeveloper to combine any combinatio=
n of listeners, normal messages,and unsolicited messages.  Why make an out =
of a special out of band APIfor something that could be handled naturally =
by the existing API. When you say the application wants to know immediately=
, you meanthe unsolicited notification message should comes up first, i.e. =
returnedto the application before other normal messages - correct? If the =
unsolicitednotification is mixed with other messages, the draft should =
specify thatunsolicited messages are returned first.
>  -Steve

  No, not at all. With an event listener model, a client that is interested=
 in unsolicited notifications registers as an UnsolicitedNotificationListen=
er. Immediately when an unsolicited notification arrives, a method of the =
client (e.g. messageReceived) is called with the unsolicited notification =
as parameter. That way the client is notified immediately and asynchronousl=
y rather than having to poll the message queue. Besides being simpler and =
more convenient for the client, it is much cleaner and less error-prone =
both for the client and for the implementor of the API. In-band responses =
are delivered in-band to the submitter of in-band requests; unsolicited =
notifications are delivered out-of-band to a requestor of unsolicited =
notifications.

Rob
................................................................

You are describing a callback mechanism, but the interface described
in earlier e-mails, just registered an LDAPResponseListener which has
no callback semantics associated with it.  Are you thinking of a new
kind of listener.  In our previous discussion you suggested the following =
API

> > public LDAPResponseListener addUnsolicitedNotificationListener(
> > LDAPResponseListener listener )
> >
> > public void removeUnsolicitedNotificationListener(
> > LDAPResponseListener listener )

Are you thinking of adding a method to LDAPResponseListener to
register a callback method?

-Steve

--=_7D261F92.C5A4E733
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px"><FONT=20
size=3D1></FONT>
<DIV><BR><BR>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; =
03-Jan-01=20
5:13:40 PM &gt;&gt;&gt;<BR>Steve Sonntag wrote:<BR><BR>&gt;<BR>&gt;<BR>&gt;=
=20
&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; 27-Dec-00 10:53:27 =
PM=20
&gt;&gt;&gt;<BR>&gt; Steven Sonntag wrote:<BR>&gt; &gt;<BR>&gt; &gt; Rob =
Weltman=20
wrote:<BR>&gt; &gt;<BR>&gt; &gt; &gt;&nbsp;&nbsp; It might be better =
instead to=20
eliminate the current unsolicited<BR>&gt; &gt; &gt; notification methods =
and=20
instead have methods to add and remove<BR>&gt; &gt; &gt; listeners for=20
usolicited notifications. The implementation can then<BR>&gt; &gt; &gt; =
discard=20
unsolicited notifications if there are no listeners. For<BR>&gt; &gt; =
&gt;=20
example (I haven't thought this through completely yet):<BR>&gt; &gt;=20
&gt;<BR>&gt; &gt; &gt; LDAPConnection<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; =
public=20
LDAPResponseListener addUnsolicitedNotificationListener(<BR>&gt; &gt; =
&gt;=20
LDAPResponseListener listener )<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; public =
void=20
removeUnsolicitedNotificationListener(<BR>&gt; &gt; &gt; LDAPResponseListen=
er=20
listener )<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Rob<BR>&gt; &gt; &gt;<BR>&gt=
;=20
&gt;<BR>&gt; &gt; It seems natural to me that if unsolicited notifications =
are=20
enabled on<BR>&gt; &gt; a<BR>&gt; &gt; listener, that the method=20
LDAPListener.getMessageIDs() would include<BR>&gt; &gt; message ID 0 in =
the list=20
of message IDs, and that<BR>&gt; &gt; LDAPConnection.abandon(0)<BR>&gt; =
&gt; and=20
LDAPConnection.abandon(listener) could be used to removeUnsolicited<BR>&gt;=
 &gt;=20
notifications from a listener or listeners.&nbsp; This raises some=20
questions.<BR>&gt; &gt;<BR>&gt; &gt; 1) Should getMessageIDs show =
messageID 0=20
when unsolicited notification<BR>&gt; &gt; are enabled?&nbsp; (My vote =
is=20
yes)<BR>&gt; &gt;<BR>&gt; &gt; 2) Should the draft allow abandon to be =
used to=20
remove unsolicited<BR>&gt; &gt; notifications?<BR>&gt; &gt; (this means =
that=20
message ID 0 is treated like a message that never<BR>&gt; &gt;=20
completes)<BR>&gt; &gt;<BR>&gt; &gt; 3) If number two is allowed, is=20
removeUnsolicitedNotificationListener()<BR>&gt; &gt; necessary?<BR>&gt;=20
&gt;<BR>&gt; &gt; -Steve<BR>&gt;<BR>&gt;&nbsp;&nbsp; I think it is easier =
for a=20
client to handle unsolicited notifications as out-of-band events rather =
than=20
lumped together with "normal" solicited responses. In almost all cases I =
would=20
expect a client to want to know immediately that an unsolicited notificatio=
n had=20
arrived rather than having to poll and distinguish between solicited =
and=20
unsolicited notifications. The event listener model reflects the paradigm =
of=20
immediate out-of-band notification of unsolicited messages. Having the=20
unsolicited messages ALSO appear in the normal message queue is confusing,=
=20
error-prone, and not very useful as far as I can tell.<BR>&gt;<BR>&gt;=20
Rob........................................What you say may be true, but - =
using=20
the listener paradigm allows thedeveloper to combine any combination of=20
listeners, normal messages,and unsolicited messages.&nbsp; Why make an out =
of a=20
special out of band APIfor something that could be handled naturally by =
the=20
existing API. When you say the application wants to know immediately, =
you=20
meanthe unsolicited notification message should comes up first, i.e. =
returnedto=20
the application before other normal messages - correct? If the=20
unsolicitednotification is mixed with other messages, the draft should =
specify=20
thatunsolicited messages are returned first.<BR>&gt;&nbsp; -Steve<BR><BR>&n=
bsp;=20
No, not at all. With an event listener model, a client that is interested =
in=20
unsolicited notifications registers as an UnsolicitedNotificationListener.=
=20
Immediately when an unsolicited notification arrives, a method of the =
client=20
(e.g. messageReceived) is called with the unsolicited notification as =
parameter.=20
That way the client is notified immediately and asynchronously rather =
than=20
having to poll the message queue. Besides being simpler and more convenient=
 for=20
the client, it is much cleaner and less error-prone both for the client =
and for=20
the implementor of the API. In-band responses are delivered in-band to =
the=20
submitter of in-band requests; unsolicited notifications are delivered=20
out-of-band to a requestor of unsolicited=20
notifications.<BR><BR>Rob<BR>..............................................=
..................</DIV>
<DIV>&nbsp;</DIV>
<DIV>You are describing a callback mechanism, but the interface described</=
DIV>
<DIV>in earlier e-mails, just registered an LDAPResponseListener which =
has</DIV>
<DIV>no callback semantics associated with it.&nbsp; Are you thinking of =
a=20
new</DIV>
<DIV>kind of listener.&nbsp; In our previous discussion you suggested =
the=20
following API</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; &gt; public LDAPResponseListener=20
addUnsolicitedNotificationListener(<BR>&gt; &gt; LDAPResponseListener =
listener=20
)<BR>&gt; &gt;<BR>&gt; &gt; public void=20
removeUnsolicitedNotificationListener(<BR>&gt; &gt; LDAPResponseListener=20=

listener )</DIV>
<DIV>&nbsp;</DIV>
<DIV>Are you thinking of adding a method to LDAPResponseListener to</DIV>
<DIV>register a callback method?</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve<BR><BR></DIV></BODY></HTML>

--=_7D261F92.C5A4E733--



From list@netscape.com  Fri Jan  5 11:23:58 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15970
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 11:23:57 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f05GDH326871;
	Fri, 5 Jan 2001 08:13:17 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f05GM2Q16864;
	Fri, 5 Jan 2001 08:22:02 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 08:22:02 -0800 (PST)
Message-Id: <200101051620.f05GKeg13149@jupiter.accesscable.net>
X-Sender: goldenhord@usa.net
From: Maximum Profits <goldenhord@usa.net>
To: ietf-ldapext@netscape.com
Date: Fri, 05 Jan 2001 12:14:44 -0400
Subject: Company Seeking persons to place ads on Net.. Good money, Training available
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Resent-Message-ID: <"97DelB.A.CHE.pSfV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id f05GDH326871
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA15970

Hello!

We are currently seeking individuals to place small classified ads for our clients. 
 You get paid per response. ($1.00 per response can make you thousands.!) NO 
Selling!! We can teach you how to place ads if your not sure so you don't miss 
out on this genuine MONEY MAKING business opportunity. Please request more information 
by sending an email with "ADINFO" in the subject line to:
WC9547@yahoo.com
********************************************************************************Note: 
This can in no way be considered SPAM!  You are receiving this email as a confirmation 
of you posting your link on my site:

Please as we don’t believe in spamming, and should somehow your email address 
be on our listings and you want us to remove it.  Please just send us an email 
with the word “Remove” in the subject line.  We will honour your request as fast 
as possible, thank you. We wish you the greatest success in your online business. 
 







From list@netscape.com  Fri Jan  5 11:34:19 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16164
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 11:34:19 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f05GIE325305;
	Fri, 5 Jan 2001 08:18:14 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f05GWDk21008;
	Fri, 5 Jan 2001 08:32:13 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 08:32:13 -0800 (PST)
Message-ID: <3A55F7F4.FCF5D7A7@worldspot.com>
Date: Fri, 05 Jan 2001 08:36:04 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: Steve Sonntag <VTAG@novell.com>
CC: robw@worldspot.com, ietf-ldapext@netscape.com
Subject: Re: Fwd: Re: draft Java-api-12
References: <sa558612.008@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"UyIkED.A.-HF.McfV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Steve Sonntag wrote:

>
>
> >>> Rob Weltman <robw@worldspot.com> 03-Jan-01 5:13:40 PM >>>
> Steve Sonntag wrote:
>
> >
> >
> > >>> Rob Weltman <robw@worldspot.com> 27-Dec-00 10:53:27 PM >>>
> > Steven Sonntag wrote:
> > >
> > > Rob Weltman wrote:
> > >
> > > >   It might be better instead to eliminate the current unsolicited
> > > > notification methods and instead have methods to add and remove
> > > > listeners for usolicited notifications. The implementation can then
> > > > discard unsolicited notifications if there are no listeners. For
> > > > example (I haven't thought this through completely yet):
> > > >
> > > > LDAPConnection
> > > >
> > > > public LDAPResponseListener addUnsolicitedNotificationListener(
> > > > LDAPResponseListener listener )
> > > >
> > > > public void removeUnsolicitedNotificationListener(
> > > > LDAPResponseListener listener )
> > > >
> > > > Rob
> > > >
> > >
> > > It seems natural to me that if unsolicited notifications are enabled on
> > > a
> > > listener, that the method LDAPListener.getMessageIDs() would include
> > > message ID 0 in the list of message IDs, and that
> > > LDAPConnection.abandon(0)
> > > and LDAPConnection.abandon(listener) could be used to removeUnsolicited
> > > notifications from a listener or listeners.  This raises some questions.
> > >
> > > 1) Should getMessageIDs show messageID 0 when unsolicited notification
> > > are enabled?  (My vote is yes)
> > >
> > > 2) Should the draft allow abandon to be used to remove unsolicited
> > > notifications?
> > > (this means that message ID 0 is treated like a message that never
> > > completes)
> > >
> > > 3) If number two is allowed, is removeUnsolicitedNotificationListener()
> > > necessary?
> > >
> > > -Steve
> >
> >   I think it is easier for a client to handle unsolicited notifications as out-of-band events rather than lumped together with "normal" solicited responses. In almost all cases I would expect a client to want to know immediately that an unsolicited notification had arrived rather than having to poll and distinguish between solicited and unsolicited notifications. The event listener model reflects the paradigm of immediate out-of-band notification of unsolicited messages. Having the unsolicited messages ALSO appear in the normal message queue is confusing, error-prone, and not very useful as far as I can tell.
> >
> > Rob........................................What you say may be true, but - using the listener paradigm allows thedeveloper to combine any combination of listeners, normal messages,and unsolicited messages.  Why make an out of a special out of band APIfor something that could be handled naturally by the existing API. When you say the application wants to know immediately, you meanthe unsolicited notification message should comes up first, i.e. returnedto the application before other normal messages - correct? If the unsolicitednotification is mixed with other messages, the draft should specify thatunsolicited messages are returned first.
> >  -Steve
>
>   No, not at all. With an event listener model, a client that is interested in unsolicited notifications registers as an UnsolicitedNotificationListener. Immediately when an unsolicited notification arrives, a method of the client (e.g. messageReceived) is called with the unsolicited notification as parameter. That way the client is notified immediately and asynchronously rather than having to poll the message queue. Besides being simpler and more convenient for the client, it is much cleaner and less error-prone both for the client and for the implementor of the API. In-band responses are delivered in-band to the submitter of in-band requests; unsolicited notifications are delivered out-of-band to a requestor of unsolicited notifications.
>
> Rob
> ................................................................ You are describing a callback mechanism, but the interface describedin earlier e-mails, just registered an LDAPResponseListener which hasno callback semantics associated with it.  Are you thinking of a newkind of listener.  In our previous discussion you suggested the following API > > public LDAPResponseListener addUnsolicitedNotificationListener(
> > > LDAPResponseListener listener )
> > >
> > > public void removeUnsolicitedNotificationListener(
> > > LDAPResponseListener listener ) Are you thinking of adding a method to LDAPResponseListener toregister a callback method? -Steve
>

  It might be better to define a new interface for the callback.

 public void addUnsolicitedNotificationListener(
    LDAPUnsolicitedNotificationListener listener )

public void removeUnsolicitedNotificationListener(
    LDAPUnsolicitedNotificationListener listener )


public interface LDAPUnsolicitedNotificationListener {
   public void messageReceived( LDAPMessage msg );
}


Rob




From list@netscape.com  Fri Jan  5 12:06:36 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16879
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 12:06:36 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f05Gtc306087;
	Fri, 5 Jan 2001 08:55:39 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f05H4NA16030;
	Fri, 5 Jan 2001 09:04:23 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 09:04:23 -0800 (PST)
Message-Id: <sa559c1a.011@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Fri, 05 Jan 2001 10:04:06 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Cc: "Alan Clark" <ACLARK@novell.com>
Subject: Re: Fwd: Re: draft Java-api-12
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_6338019A.650447E0"
Resent-Message-ID: <"zhiGPD.A.b5D.V6fV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_6338019A.650447E0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

This makes more sense to me now.  Although both mechanisms work,
the callback paradigm has the advantage of immediate notification to the
application.  Thanks for the clarification.  I think this is a better way =
to go.

I also believe we should add Kurt's suggestion, that requests should
not use message ID of 0 - i.e. let it be reserved for unsolicited =
notifications.

-Steve


>>> Rob Weltman <robw@worldspot.com> 05-Jan-01 9:36:04 AM >>>
Steve Sonntag wrote:

>
>
> >>> Rob Weltman <robw@worldspot.com> 03-Jan-01 5:13:40 PM >>>
> Steve Sonntag wrote:
>
> >
> >
> > >>> Rob Weltman <robw@worldspot.com> 27-Dec-00 10:53:27 PM >>>
> > Steven Sonntag wrote:
> > >
> > > Rob Weltman wrote:
> > >
> > > >   It might be better instead to eliminate the current unsolicited
> > > > notification methods and instead have methods to add and remove
> > > > listeners for usolicited notifications. The implementation can =
then
> > > > discard unsolicited notifications if there are no listeners. For
> > > > example (I haven't thought this through completely yet):
> > > >
> > > > LDAPConnection
> > > >
> > > > public LDAPResponseListener addUnsolicitedNotificationListener(
> > > > LDAPResponseListener listener )
> > > >
> > > > public void removeUnsolicitedNotificationListener(
> > > > LDAPResponseListener listener )
> > > >
> > > > Rob
> > > >
> > >
> > > It seems natural to me that if unsolicited notifications are enabled =
on
> > > a
> > > listener, that the method LDAPListener.getMessageIDs() would include
> > > message ID 0 in the list of message IDs, and that
> > > LDAPConnection.abandon(0)
> > > and LDAPConnection.abandon(listener) could be used to removeUnsolicit=
ed
> > > notifications from a listener or listeners.  This raises some =
questions.
> > >
> > > 1) Should getMessageIDs show messageID 0 when unsolicited notificatio=
n
> > > are enabled?  (My vote is yes)
> > >
> > > 2) Should the draft allow abandon to be used to remove unsolicited
> > > notifications?
> > > (this means that message ID 0 is treated like a message that never
> > > completes)
> > >
> > > 3) If number two is allowed, is removeUnsolicitedNotificationListener=
()
> > > necessary?
> > >
> > > -Steve
> >
> >   I think it is easier for a client to handle unsolicited notifications=
 as out-of-band events rather than lumped together with "normal" solicited =
responses. In almost all cases I would expect a client to want to know =
immediately that an unsolicited notification had arrived rather than =
having to poll and distinguish between solicited and unsolicited notificati=
ons. The event listener model reflects the paradigm of immediate out-of-ban=
d notification of unsolicited messages. Having the unsolicited messages =
ALSO appear in the normal message queue is confusing, error-prone, and not =
very useful as far as I can tell.
> >
> > Rob........................................What you say may be true, =
but - using the listener paradigm allows thedeveloper to combine any =
combination of listeners, normal messages,and unsolicited messages.  Why =
make an out of a special out of band APIfor something that could be =
handled naturally by the existing API. When you say the application wants =
to know immediately, you meanthe unsolicited notification message should =
comes up first, i.e. returnedto the application before other normal =
messages - correct? If the unsolicitednotification is mixed with other =
messages, the draft should specify thatunsolicited messages are returned =
first.
> >  -Steve
>
>   No, not at all. With an event listener model, a client that is =
interested in unsolicited notifications registers as an UnsolicitedNotifica=
tionListener. Immediately when an unsolicited notification arrives, a =
method of the client (e.g. messageReceived) is called with the unsolicited =
notification as parameter. That way the client is notified immediately and =
asynchronously rather than having to poll the message queue. Besides being =
simpler and more convenient for the client, it is much cleaner and less =
error-prone both for the client and for the implementor of the API. =
In-band responses are delivered in-band to the submitter of in-band =
requests; unsolicited notifications are delivered out-of-band to a =
requestor of unsolicited notifications.
>
> Rob
> ................................................................ You are =
describing a callback mechanism, but the interface describedin earlier =
e-mails, just registered an LDAPResponseListener which hasno callback =
semantics associated with it.  Are you thinking of a newkind of listener.  =
In our previous discussion you suggested the following API > > public =
LDAPResponseListener addUnsolicitedNotificationListener(
> > > LDAPResponseListener listener )
> > >
> > > public void removeUnsolicitedNotificationListener(
> > > LDAPResponseListener listener ) Are you thinking of adding a method =
to LDAPResponseListener toregister a callback method? -Steve
>

  It might be better to define a new interface for the callback.

public void addUnsolicitedNotificationListener(
    LDAPUnsolicitedNotificationListener listener )

public void removeUnsolicitedNotificationListener(
    LDAPUnsolicitedNotificationListener listener )


public interface LDAPUnsolicitedNotificationListener {
   public void messageReceived( LDAPMessage msg );
}


Rob

--=_6338019A.650447E0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px">
<DIV><FONT size=3D1>This makes more sense to me now.&nbsp; Although =
both=20
mechanisms work,</FONT></DIV>
<DIV><FONT size=3D1>the callback paradigm has the advantage of immediate=20=

notification to the</FONT></DIV>
<DIV><FONT size=3D1>application.&nbsp; Thanks for the clarification.&nbsp; =
I think=20
this is a better way to go.</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>I also believe we should add Kurt's suggestion, that =
requests=20
should</FONT></DIV>
<DIV><FONT size=3D1>not use message ID of 0 - i.e. let it be reserved =
for=20
unsolicited notifications.</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>-Steve</FONT></DIV>
<DIV><BR><BR>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; =
05-Jan-01=20
9:36:04 AM &gt;&gt;&gt;<BR>Steve Sonntag wrote:<BR><BR>&gt;<BR>&gt;<BR>&gt;=
=20
&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; 03-Jan-01 5:13:40 =
PM=20
&gt;&gt;&gt;<BR>&gt; Steve Sonntag wrote:<BR>&gt;<BR>&gt; &gt;<BR>&gt;=20
&gt;<BR>&gt; &gt; &gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; =
27-Dec-00=20
10:53:27 PM &gt;&gt;&gt;<BR>&gt; &gt; Steven Sonntag wrote:<BR>&gt; =
&gt;=20
&gt;<BR>&gt; &gt; &gt; Rob Weltman wrote:<BR>&gt; &gt; &gt;<BR>&gt; &gt; =
&gt;=20
&gt;&nbsp;&nbsp; It might be better instead to eliminate the current=20
unsolicited<BR>&gt; &gt; &gt; &gt; notification methods and instead have =
methods=20
to add and remove<BR>&gt; &gt; &gt; &gt; listeners for usolicited =
notifications.=20
The implementation can then<BR>&gt; &gt; &gt; &gt; discard unsolicited=20
notifications if there are no listeners. For<BR>&gt; &gt; &gt; &gt; =
example (I=20
haven't thought this through completely yet):<BR>&gt; &gt; &gt; &gt;<BR>&gt=
;=20
&gt; &gt; &gt; LDAPConnection<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt; =
&gt;=20
public LDAPResponseListener addUnsolicitedNotificationListener(<BR>&gt; =
&gt;=20
&gt; &gt; LDAPResponseListener listener )<BR>&gt; &gt; &gt; &gt;<BR>&gt; =
&gt;=20
&gt; &gt; public void removeUnsolicitedNotificationListener(<BR>&gt; &gt; =
&gt;=20
&gt; LDAPResponseListener listener )<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; =
&gt;=20
&gt; Rob<BR>&gt; &gt; &gt; &gt;<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; It =
seems=20
natural to me that if unsolicited notifications are enabled on<BR>&gt; =
&gt; &gt;=20
a<BR>&gt; &gt; &gt; listener, that the method LDAPListener.getMessageIDs() =
would=20
include<BR>&gt; &gt; &gt; message ID 0 in the list of message IDs, and=20
that<BR>&gt; &gt; &gt; LDAPConnection.abandon(0)<BR>&gt; &gt; &gt; and=20
LDAPConnection.abandon(listener) could be used to removeUnsolicited<BR>&gt;=
 &gt;=20
&gt; notifications from a listener or listeners.&nbsp; This raises some=20
questions.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; 1) Should getMessageIDs =
show=20
messageID 0 when unsolicited notification<BR>&gt; &gt; &gt; are enabled?&nb=
sp;=20
(My vote is yes)<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; 2) Should the draft =
allow=20
abandon to be used to remove unsolicited<BR>&gt; &gt; &gt;=20
notifications?<BR>&gt; &gt; &gt; (this means that message ID 0 is treated =
like a=20
message that never<BR>&gt; &gt; &gt; completes)<BR>&gt; &gt; &gt;<BR>&gt; =
&gt;=20
&gt; 3) If number two is allowed, is=20
removeUnsolicitedNotificationListener()<BR>&gt; &gt; &gt; necessary?<BR>&gt=
;=20
&gt; &gt;<BR>&gt; &gt; &gt; -Steve<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp; I =
think=20
it is easier for a client to handle unsolicited notifications as out-of-ban=
d=20
events rather than lumped together with "normal" solicited responses. In =
almost=20
all cases I would expect a client to want to know immediately that an=20
unsolicited notification had arrived rather than having to poll and =
distinguish=20
between solicited and unsolicited notifications. The event listener =
model=20
reflects the paradigm of immediate out-of-band notification of unsolicited=
=20
messages. Having the unsolicited messages ALSO appear in the normal =
message=20
queue is confusing, error-prone, and not very useful as far as I can=20
tell.<BR>&gt; &gt;<BR>&gt; &gt; Rob........................................=
What=20
you say may be true, but - using the listener paradigm allows thedeveloper =
to=20
combine any combination of listeners, normal messages,and unsolicited=20
messages.&nbsp; Why make an out of a special out of band APIfor something =
that=20
could be handled naturally by the existing API. When you say the applicatio=
n=20
wants to know immediately, you meanthe unsolicited notification message =
should=20
comes up first, i.e. returnedto the application before other normal =
messages -=20
correct? If the unsolicitednotification is mixed with other messages, the =
draft=20
should specify thatunsolicited messages are returned first.<BR>&gt; =
&gt;&nbsp;=20
-Steve<BR>&gt;<BR>&gt;&nbsp;&nbsp; No, not at all. With an event listener =
model,=20
a client that is interested in unsolicited notifications registers as =
an=20
UnsolicitedNotificationListener. Immediately when an unsolicited notificati=
on=20
arrives, a method of the client (e.g. messageReceived) is called with =
the=20
unsolicited notification as parameter. That way the client is notified=20
immediately and asynchronously rather than having to poll the message =
queue.=20
Besides being simpler and more convenient for the client, it is much =
cleaner and=20
less error-prone both for the client and for the implementor of the API. =
In-band=20
responses are delivered in-band to the submitter of in-band requests;=20
unsolicited notifications are delivered out-of-band to a requestor of=20
unsolicited notifications.<BR>&gt;<BR>&gt; Rob<BR>&gt;=20
................................................................ You =
are=20
describing a callback mechanism, but the interface describedin earlier =
e-mails,=20
just registered an LDAPResponseListener which hasno callback semantics=20
associated with it.&nbsp; Are you thinking of a newkind of listener.&nbsp; =
In=20
our previous discussion you suggested the following API &gt; &gt; =
public=20
LDAPResponseListener addUnsolicitedNotificationListener(<BR>&gt; &gt; =
&gt;=20
LDAPResponseListener listener )<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; public =
void=20
removeUnsolicitedNotificationListener(<BR>&gt; &gt; &gt; LDAPResponseListen=
er=20
listener ) Are you thinking of adding a method to LDAPResponseListener=20
toregister a callback method? -Steve<BR>&gt;<BR><BR>&nbsp; It might be =
better to=20
define a new interface for the callback.<BR><BR>public void=20
addUnsolicitedNotificationListener(<BR>&nbsp;&nbsp;&nbsp;=20
LDAPUnsolicitedNotificationListener listener )<BR><BR>public void=20
removeUnsolicitedNotificationListener(<BR>&nbsp;&nbsp;&nbsp;=20
LDAPUnsolicitedNotificationListener listener )<BR><BR><BR>public =
interface=20
LDAPUnsolicitedNotificationListener {<BR>&nbsp;&nbsp; public void=20
messageReceived( LDAPMessage msg=20
);<BR>}<BR><BR><BR>Rob<BR><BR><BR></DIV></BODY></HTML>

--=_6338019A.650447E0--



From list@netscape.com  Fri Jan  5 23:15:53 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA29456
	for <ldapext-archive@odin.ietf.org>; Fri, 5 Jan 2001 23:15:53 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0644x319316;
	Fri, 5 Jan 2001 20:04:59 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f064DiM05854;
	Fri, 5 Jan 2001 20:13:44 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 20:13:44 -0800 (PST)
Date: Fri, 5 Jan 2001 20:13:31 -0800 (PST)
Message-Id: <200101060413.f064DUD15270@ywing.netscape.com>
From: BEL.EADN@ywing.netscape.com
To: Everyone.ILAI@netscape.com
Subject:  Twice Voted #1 Business -TKSE
X-Reply-To:  belbirkdale@hotmail.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"jM6Ds.A.TaB.3tpV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit


Dear Friend:

AS SEEN ON NATIONAL TV:

''Making over half million dollars every 4 to 5 months from your
home for an investment of only $25 U.S. Dollars expense one
time''

THANKS TO THE COMPUTER AGE AND THE INTERNET!
BE A MILLIONAIRE LIKE OTHERS WITHIN A YEAR !!

Before you say ''Bull'' , please read the following. This is the
letter you have been hearing about on the news lately. Due to the
popularity of this letter on the internet, a national weekly news
program recently devoted an entire show to the investigation of
this program described below , to see if it really can make people
money.

The show also investigated whether or not the program was legal.
Their findings proved once and for all that there are ''absolutely
NO laws prohibiting the participation in the program and if people
can follow the simple instructions, they are bound to make
some mega bucks with only $25 out of pocket cost''.

DUE TO THE RECENT INCREASE OF POPULARITY & RESPECT
THIS PROGRAM HAS ATTAINED, IT IS CURRENTLY WORKING
BETTER THAN EVER.

This is what one had to say:

''Thanks to this profitable opportunity. I was approached
many times before but each time I passed on it. I am so glad
I finally joined just to see what one could expect in return
for the minimal effort and money required. To my astonishment, I
received total $ 610,470.00 in 21 weeks, with money still
coming in''.

Pam Hedland, Fort Lee, New Jersey.
-------------------------------------------------------------------------=


Here is another testimonial:

''This program has been around for a long time but I never
believed in it. But one day when I received this again in
the mail I decided to gamble my $25 on it. I followed the
simple instructions and walaa ..... 3 weeks later the money
started to come in. First month I only made $240.00 but
the next 2 months after that I made a total of $290,000.00.
So far, in the past 8 months by re-entering the program,I
have made over $710,000.00 and I am playing it again.
The key to success in this program is to follow the simple
steps and NOT change anything .''

More testimonials later but first,

****** PRINT THIS NOW FOR YOUR FUTURE REFERENCE *******

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
If you would like to make at least $500,000 every 4 to 5 months
easily and comfortably, please read the following...THEN READ
IT AGAIN and AGAIN !!!
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

FOLLOW THE SIMPLE INSTRUCTION BELOW AND YOUR
FINANCIAL DREAMS WILL COME TRUE, GUARANTEED!

INSTRUCTIONS:

**** Order all 5 reports shown on the list below.

**** For each report, send $5 CASH, THE NAME & NUMBER OF THE
REPORT YOU ARE ORDERING and YOUR E-MAIL ADDRESS
to the person whose name appears ON THAT LIST next to the report.
MAKE SURE YOUR RETURN ADDRESS IS ON YOUR ENVELOPE
TOP LEFT CORNER in case of any mail problems.

**** When you place your order, make sure you order each of the 5
reports. You will need all 5 reports so that you can save them on your
computer and resell them. YOUR TOTAL COST $5 X 5 =3D $25.00.

**** Within a few days you will receive, via e-mail, each of the 5
reports from these 5 different individuals. Save them on your computer
so they will be accessible for you to send to the 1,000's of people
who will order them from you. Also make a floppy of these
reports and keep it on your desk in case something happens to your
computer.

****.IMPORTANT - DO NOT alter the names of the people who are
listed next to each report, or their sequence on the list, in
any way other than what is instructed below in step '' 1 through
6 '' or you will loose out on majority of your profits. Once you
understand the way this works, you will also see how it does not work if
you change it.

Remember, this method has been tested, and if you alter it, it
will NOT work!!! People have tried to put their friends/relatives names
on all five thinking they could get all the money. But it does not work
this way. Believe us, we all have tried to be greedy and then nothing
happened.  So Do Not try to change anything other than what is =
instructed.
Because if you do, it will not work for you. Remember, honesty reaps the
reward!!!

1.. After you have ordered all 5 reports, take this advertisement
and REMOVE the name & address of the person in REPORT # 5. This
person has made it through the cycle and is no doubt counting
their fortune.

2.... Move the name & address in REPORT # 4 down TO REPORT # 5.

3.... Move the name & address in REPORT # 3 down TO REPORT # 4.

4.... Move the name & address in REPORT # 2 down TO REPORT # 3.

5.... Move the name & address in REPORT # 1 down TO REPORT # 2

6.... Insert YOUR name & address in the REPORT # 1 Position.

PLEASE MAKE SURE you copy every name & address ACCURATELY !
==========================================================

Take this entire letter, with the modified list of names, and save
it on your computer. DO NOT MAKE ANY OTHER CHANGES.
Save this on a disk as well just in case if you loose any data.

To assist you with marketing your business on the internet, the
5 reports you purchase will provide you with invaluable
marketing information which includes how to send bulk e-mails legally,
 where to find thousands of free classified ads and much more.

There are 2 Primary methods to get this venture going:

METHOD # 1 : BY SENDING BULK E-MAIL LEGALLY
====================================================

Let's say that you decide to start small, just to see how it
goes, and we will assume you and those involved after you send out only
5,000 e-mails each. Let's also assume that the mailing receive only a
0.2% response (the response could be much better but lets just
say it is only 0.2% . Also many people will send out hundreds of
thousands e-mails instead of only 5,000 each).

Continuing with this example, you send out only 5,000 e-mails.
With a 0.2% response, that is only 10 orders for report # 1.
Those 10 people responded by sending out 5,000 e-mail
each for a total of 50,000. Out of those 50,000 e-mails only
0.2% responded with orders. That's =3D 100 people responded
and ordered Report # 2. Those 100 people mail out 5,000
e-mails each for a total of 500,000 e-mails. The 0.2% response
to that is 1000 orders for Report # 3. Those 1000 people send
out 5,000 e-mails each for a total of 5 million e-mails sent out.
The 0.2% response to that is 10,000 orders for Report # 4.
Those 10,000 people send out 5,000 e-mails each for a total of
50,000,000 (50 million) e-mails. The 0.2% response to that is
100,000 orders for Report # 5.

THAT'S 100,000 ORDERS TIMES $5 EACH =3D $500,000.00 (half million).

Your total income in this example is:
1..... $50 +
2..... $500 +
3..... $5,000 +
4..... $50,000 +
5..... $500,000 ......... Grand Total =3D $555,550.00

NUMBERS DO NOT LIE. GET A PENCIL & PAPER AND FIGURE
OUT THE WORST POSSIBLE RESPONSES AND NO MATTER
HOW YOU CALCULATE IT, YOU WILL STILL MAKE A LOT OF
MONEY !


-------------------------------------------------------------------------=
---
---------

REMEMBER FRIEND, THIS IS ASSUMING ONLY 10 PEOPLE
ORDERING OUT OF 5,000 YOU MAILED TO. Dare to think for
a moment what would happen if everyone, or half or even one 4th
of those people mailed 100,000 e-mails each or more? There are
over 150 million people on the internet worldwide and counting.
Believe me, many people will do just that, and more!

METHOD # 2 : BY PLACING FREE ADS ON THE INTERNET
====================================================

Advertising on the net is very very inexpensive and there are
hundreds of FREE places to advertise. Placing a lot of free ads
on the internet will easily get a larger response. We strongly
suggest you start with Method # 1 and add METHOD # 2 as you go
along.

For every $5 you receive, all you must do is e-mail them the Report
they ordered. That's it . Always provide same day service on all
orders. This will guarantee that the e-mail they send out, with your
name and address on it, will be prompt because they can not advertise
until they receive the report.

_____________________ AVAILABLE REPORTS_____________________

ORDER EACH REPORT BY ITS NUMBER & NAME ONLY.

Notes: Always send $5 cash (U.S. CURRENCY) for each Report.
Checks NOT accepted. Make sure the cash is concealed by wrapping
it in at least 2 sheets of paper. On one of those sheets of paper,
Write the NUMBER & the NAME of the Report you are ordering, YOUR
E-MAIL ADDRESS and your name and postal address.


PLACE YOUR ORDER FOR THESE REPORTS NOW:
==========================================================

REPORT # 1 : ''The Insider's Guide to Advertising for Free on the Net''

Order Report # 1 from:

BEL
P.O. Box 802
Capalaba
Qld 4157
AUSTRALIA  (Don't forget to use an airmail postage stamp!)

__________________________________________________

REPORT # 2 : ''The Insider's Guide to Sending Bulk e-mail on the Net''

Order Report # 2 from :

DA McKie
11 Burwana Pl
Birkdale
QLD 4159
AUSTRALIA  (Don't forget to use an airmail postage stamp!)

_________________________________________________

REPORT # 3 : ''The Secret to Multilevel marketing on the net''

Order Report # 3 from:

ATA
P.O. Box 813
Red Deer, AB, Canada
T4N 5H2.
__________________________________________________

REPORT # 4 : ''How to become a millionaire utilizing MLM & the Net''

Order Report # 4 from:

OCC
P.O. Box 1075
Auburn, AL 36831-1075
U.S.A.
____________________________________________________

REPORT # 5 : ''HOW TO SEND 1 MILLION E-MAILS FOR FREE''

Order Report # 5 from:

R. Jones
446 S. Anaheim Hills Rd, #141B
Anaheim, CA 92807-4858
U.S.A.
__________________________________________________
$$$$$$$$$ YOUR SUCCESS GUIDELINES $$$$$$$$$$$

Follow these guidelines to guarantee your success:

If you do not receive at least 10 orders for Report #1 within 2
 weeks, continue sending e-mails until you do.

After you have received 10 orders, 2 to 3 weeks after that
you should receive 100 orders or more for REPORT # 2.
If you did not, continue advertising or sending e-mails until
you do.

Once you have received 100 or more orders for Report # 2,
YOU CAN RELAX, because the system is already working for
you , and the cash will continue to roll in !

THIS IS IMPORTANT TO REMEMBER : Every time your name is
moved down on the list, you are placed in front of a different report.
You can KEEP TRACK of your PROGRESS by watching which
report people are ordering from you. IF YOU WANT TO GENERATE
MORE INCOME SEND ANOTHER BATCH OF E-MAILS AND
START THE WHOLE PROCESS AGAIN. There is NO LIMIT to
the income you can generate from this business !!!
____________________________________________________

FOLLOWING IS A NOTE FROM THE ORIGINATOR OF THIS PROGRAM:

"You have just received information that can give you financial
freedom for the rest of your life, with NO RISK and JUST A
LITTLE BIT OF EFFORT. You can make more money in the
next few weeks and months than you have ever imagined.

Follow the program EXACTLY AS INSTRUCTED. Do Not change
it in any way. It works exceedingly well as it is now.
Remember to e-mail a copy of this exciting report after you
have put your name and address in Report #1 and moved others to
#2...........# 5 as instructed above. One of the people you send this to
may send out 100,000 or more e-mails and your name will be on everyone
of them. Remember though, the more you send out the more potential
customers you will reach.

So my friend, I have given you the ideas, information,
materials and opportunity to become financially independent.
IT IS UP TO YOU NOW !

************** MORE TESTIMONIALS ****************

'' My name is Mitchell. My wife , Jody and I live in Chicago.
I am an accountant with a major U.S. Corporation and I
make pretty good money. When I received this program I grumbled
to Jody about receiving ''junk mail''. I made fun of the
whole thing, spouting my knowledge of the population and
percentages involved. I ''knew'' it wouldn't work. Jody
totally ignored my supposed intelligence and few days later she jumped
in with both feet. I made merciless fun of her, and was ready to
lay the old ''I told you so'' on her when the thing didn't
work. Well, the laugh was on me! Within 3 weeks she had received
50 responses. Within the next 45 days she had received a
total of $ 147,200.00 all cash! I was shocked. I have
joined Jody in her ''hobby''.

Mitchell Wolf, M.D. ,
Chicago, Illinois

------------------------------------------------------------

'' Not being the gambling type, it took me several weeks to
make up my mind to participate in this plan. But conservative that
I am, I decided that the initial investment was so little
that there was just no way that I wouldn't get enough orders to at
least get my money back.

I was surprised when I found my medium size post office box
crammed with orders. I made $319,210.00 in the first 12
weeks. The nice thing about this deal is that it does not matter
where people live. There simply isn't a better investment
with a faster return and so big''.

Dan Sondstrom, Alberta,
 Canada

-----------------------------------------------------------

'' I had received this program before. I deleted it, but
later I wondered if I should have given it a try. Of course, I had
no idea who to contact to get another copy, so I had to wait
until I was e-mailed again by someone else.........11 months
passed then it luckily came again...... I did not delete this
one! I made more than $490,000 on my first try and all the
money came within 22 weeks''.

 Susan De Suza,
New York, N.Y.

----------------------------------------------------

'' It really is a great opportunity to make relatively easy
money with little cost to you. I followed the simple
instructions carefully and within 10 days the money
started to come in. My first month I made $ 20, 560.00
and by the end of third month my total cash count was
$ 362,840.00. Life is beautiful, Thanx to internet''.

Fred Dellaca, Westport,
New Zealand

------------------------------------------------------------


 ORDER YOUR REPORTS TODAY AND GET STARTED ON
YOUR ROAD TO FINANCIAL FREEDOM !

===========================================================

If you have any questions of the legality of this program, contact the
Office of Associate Director for Marketing Practices, Federal Trade
Commission, Bureau of Consumer Protection, Washington, D.C.

////////////////////////////////////////////////
ONE TIME MAILING, NO NEED TO REMOVE
//////////////////////////////////////////////

This message is sent in compliance of the proposed bill SECTION 301.
per Section 301, Paragraph (a)(2)(C) of S. 1618. Further transmission to
you by the sender of this e-mail may be stopped at no cost to you by
sending a reply to : belbirkdale@hotmail.com with the word Remove in the
subject line.


-------- T H E   E N D ---------






From list@netscape.com  Sat Jan  6 02:29:32 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA14001
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 02:29:31 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f067Ih329931;
	Fri, 5 Jan 2001 23:18:43 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f067RSU09553;
	Fri, 5 Jan 2001 23:27:28 -0800 (PST)
Resent-Date: Fri, 5 Jan 2001 23:27:28 -0800 (PST)
Date: Fri, 5 Jan 2001 23:27:04 -0800 (PST)
Message-Id: <200101060727.f067R4B00644@xwing.netscape.com>
From: dcc<ccochran@AEPP.themail.com>
To: ietf-ldapext@netscape.com
Subject:  ietf-ldapext, You Can Make Money and Automate Your Business
X-Reply-To:  dcc<ccohran@themail.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"4HvX-D.A._UC.fjsV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

ietf-ldapext,

What would a $2,000 check in the mail every 15th of the month do for you?

How would you like to make this money stress free month after month.

A stress Free system to keep you income growing.

Get more information by sending a blank email to

      teamforce2@getresponse.com   or take a look at

      http://pagina.de/cdc

   




From list@netscape.com  Sat Jan  6 07:27:54 2001
Received: from netscape.com ([205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA15117
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 07:27:54 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f06CBm302056;
	Sat, 6 Jan 2001 04:11:48 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f06CPmI25432;
	Sat, 6 Jan 2001 04:25:48 -0800 (PST)
Resent-Date: Sat, 6 Jan 2001 04:25:48 -0800 (PST)
Date: Sat, 6 Jan 2001 04:25:17 -0800 (PST)
Message-Id: <200101061225.f06CPGB04979@xwing.netscape.com>
From: neveraspam@DTUQ.yahoo.com
To: My@xwing.netscape.com, New@xwing.netscape.com, Friend.MIWK@netscape.com
Subject:  Financial Education Equals Financial Independence -FMEJ
X-Reply-To:  neveraspam@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"MoLYwC.A.tMG.K7wV6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Every month over 1,000,000 new Internet users come on-line. 950,000 of 
these people want to make a living from internet commerce. 

But they haven't got the slightest idea how to go about it. 

I am forming a small team of committed people who are really
serious about their financial future.

Do you really want to be financially free?

Do you want to END your money pressures forever?

Do you want to add an EXTRA SOURCE of INCOME to your life?


If you answered "YES" to the above questions, you are serious

about your financial future and I want to work DIRECTLY WITH YOU!


I want to share one of my most rewarding money making opportunities 
with you.  Go directly to

http://www.skyboom.com/instantprofit3/submit.html

<a href="http://www.skyboom.com/instantprofit3/submit.html">CLICK 
HERE</a>

"I have never seen a faster, simpler way to create a stream of income"

I know this sounds too good to be true.  I was very skeptical at first; 

finally I agreed to check it out.  As a test I selected a small group 

of people and introduced them to this incredible opportunity.  Within 

a few short months several of them were earning extraordinary 

amounts of money. In the space of one short year some of them 

have become financially free.  Needless to say the test WORKED,

I was absolutely amazed.


Would you like to learn to do the same as my original group?

Once again, I am forming a small group of people

to work with me.  I WANT YOU to work with me and I WANT 

YOU to far exceed what my original group did!

ARE YOU WILLING TO:

1. Talk to me personally about this opportunity?
2. Be a leader in my organization?
3. Train directly with me?
4. Be open minded and teachable?
5. Keep all my marketing information CONFIDENTIAL?

If your interest in the phenomenal opportunity is at least a 7 on a 
scale of 1 to 10 go to my special web site at:

http://www.skyboom.com/instantprofit3/submit.html

<a href="http://www.skyboom.com/instantprofit3/submit.html">CLICK 
HERE</a>


On that site you will receive FREE up to date special reports about
e-commerce and owning your own business from home.  You will then be 
forwarded to a special online presentation.  I guarantee by the 
time you read the special reports and watch our presentation your 
interest level will be a "Rock Solid 10 out of 10".  

Respond immediately and let's get started now!

http://www.skyboom.com/instantprofit3/submit.html
<a href="http://www.skyboom.com/instantprofit3/submit.html">CLICK 
HERE</a>

I look forward to working with you 

NO SPECIAL SKILLS OR EXPERIENCE REQUIRED. We will give you all 
the training and personal support you will need to ensure your success!

This LEGITIMATE HOME-BASED INCOME OPPORTUNITY can put you 
back in Control of your Time, Your Finances, and Your Life!

If you've tried other opportunities in the past that have failed to live up to
their promises, THIS IS DIFFERENT THAN ANYTHING ELSE YOU'VE 
SEEN!

YOUR FINANCIAL PAST DOES NOT HAVE TO BE YOUR FINANCIAL 
FUTURE!

"All our dreams can come true - if we have the courage to pursue them" - 
Walt Disney

To your success in life and business

http://www.skyboom.com/instantprofit3/submit.html
 
Thank you for your time


________________________________________________________________
Our research indicates this information may be of interest to you. If you have 
received this email by mistake or wish to be removed please send an email to 
mailto:neveraspam@yahoo.com with 'remove' in the subject line and you will 
NEVER receive another email from me.  All removal requests are 
automatically removed.

Thank you.

This entire message is sent in compliance of the new e-mail bill: SECTION 
301. Per Section 301, Paragraph (a) (2) (C) of S. 1618, 
________________________________________________________________







From list@netscape.com  Sat Jan  6 12:18:17 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16466
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 12:18:17 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f06H7R326976;
	Sat, 6 Jan 2001 09:07:27 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f06HGEA10706;
	Sat, 6 Jan 2001 09:16:14 -0800 (PST)
Resent-Date: Sat, 6 Jan 2001 09:16:14 -0800 (PST)
Message-Id: <5.0.2.1.0.20010106085618.00a805d0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Sat, 06 Jan 2001 09:15:26 -0800
To: George_Robert_Blakley_III@tivoli.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: ldap acl draft (06): browse needed ?
Cc: <rbyrne@bebop.France.Sun.COM>, <ietf-ldapext@netscape.com>
In-Reply-To: <OF08914713.256ACBF6-ON862569CA.0072250B@tivoli.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"r-CVM.A.AnC.dL1V6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Bob,

If I understand your suggestion properly, you wish to have a
mechanism where return entries is controlled by controls placed
upon 'intermediate' entries.  I define an intermediate entry
as any entry between the 'base' and matching entry excluding
both.

In implementations that I am familiar with, providing such
functionality would be extremely difficult as they use indexing
systems to locate matching entries and don't examine intermediate
entries (or ACLs upon intermediate entries) to determine whether
or not to returned matched entries.  Doing so would be require
significant redesign of such implementations.

I would suggest that any ACL feature which required servers relying
on the contents of intermediate entries be OPTIONAL.

Kurt

At 02:52 PM 1/4/01 -0600, George_Robert_Blakley_III@tivoli.com wrote:
>Rob,
>
>The intent of the "browse" permission is not to prevent discovery of DNs;
>that is what "returnDN" permission is for.
>
>"browse" is to take care of the case where there is a hierarchy of entries
>and:
>
>(1) A subject "S" has authority to perform some operation (say "read") on
>an entry (call it "E") which is not the root
>(2) "S" has no permission to read or otherwise do anything to some entry
>"I" which is on the path between the root and "E"
>(3) "S" does not know or does not wish to use the explicit name of entry
>"E"
>
>An example of this case is when a subject "Bob" has "read" access to a leaf
>entry but no access to any other entry,
>and does not know the name of any entry in the hierarchy.  Bob wishes to do
>a query on some attribute value.  This query
>matches an attribute of "E", and hence (since Bob has permission to read
>E), E should be returned in response to the
>query.
>
>However, if Bob tries to execute the search starting at the only point he
>knows about (the root), the query will fail, because
>he has no permission to "I" or any other entry on the path between the root
>and "E".
>
>This is exactly analogous to the use of the "x" mode bit in the UNIX
>filesystem to allow users to traverse directories into
>which they cannot write and from which they cannot read.
>
>--bob
>
>Bob Blakley
>Chief Scientist, Security
>Tivoli Systems, Inc.
>
>
>ietf-ldapext-request@netscape.com on 12/14/2000 09:22:38 PM
>
>Please respond to <rbyrne@bebop.France.Sun.COM>
>
>To:   <ietf-ldapext@netscape.com>
>cc:
>Subject:  ldap acl draft (06): browse needed ?
>
>
>
>
>The current acl draft proposes an entry level permission called "browseDN"
>(4.2.2).  The idea behind this permssion is to able to set a
>policy saying something like "you can see this entry if you name it
>explicitly as the base of a search, otherwise not".
>
>At Pittsburgh people seemed to like this permission and I agreed to do a
>proposal for this....however, relative
>to a single "read" level permission that ignores scoping it does complicate
>things.  The definition of the required permissions for
>search (5.2) already has to deal with a fair line up of other permssions
>(filter (presence and "the rest"), attribute level read, returnDN
>and discloseOnError).  While providing more permssions certainly increases
>the flexibility of the model,
>it also makes it harder to understand and administrate,  so my inclination
>is drop the browse permission in favour of a single "read"
>permission at the entry level.
>
>My question is do people feel strongly that the "browse" permission is
>required ?  If so, please propose a compelling scenario that
>really needs this granularity  of control of search permissions.  I will
>then include this as a motivating example and propose a way to include
>it in the required permssions for search.  Otherwise I intend to drop it
>for the 07 draft...
>
>Rob.



From list@netscape.com  Sat Jan  6 12:41:28 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16552
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 12:41:28 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f06HV8328536;
	Sat, 6 Jan 2001 09:31:08 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f06Hdtg14884;
	Sat, 6 Jan 2001 09:39:55 -0800 (PST)
Resent-Date: Sat, 6 Jan 2001 09:39:55 -0800 (PST)
Message-Id: <5.0.2.1.0.20010106092124.00a86580@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Sat, 06 Jan 2001 09:39:10 -0800
To: "Haripriya S" <SHARIPRIYA@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: abandon/cancel (Was: Returning Partial Results for an
  operation)
Cc: <ietf-ldapext@netscape.com>
In-Reply-To: <sa52cd71.091@prv-mail25.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"v8IJKD.A.SoD.qh1V6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 06:54 AM 1/3/01 -0700, Haripriya S wrote:
>IMO I see two kinds of responses a server may want to return on receiving an abandon:
> 
>1. A response to the abandon operation itself ( useful to clients to know that abandon was received).
>2. A partial/full response to the original operation which was abandoned ( useful for sending accumulated partial results).

The X.500 abandon operation has a response and requires that
the abandoned operation also has a response containing the
'abandoned' result.

>While the first requires an extended request and response and the need for the client to understand the same, the second may require a change to rfc2251 sec. 4.11 alone:

One must not confuse the existing LDAP abandon operation and
a new operation implementing the X.500 semantics.  I intend to
call this new operation the 'Cancel' extended operation such that
one will not (easily) confuse LDAP 'Abandon' requirements with
its requirements.  I do not believe any change to RFC 2251
will be need to fully specify a 'Cancel' operation which has
semantics similar to the X.500 Abandon operation.

Kurt




From list@netscape.com  Sat Jan  6 18:16:39 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18437
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 18:16:38 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f06N5H315084;
	Sat, 6 Jan 2001 15:05:17 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f06NE3g10373;
	Sat, 6 Jan 2001 15:14:03 -0800 (PST)
Resent-Date: Sat, 6 Jan 2001 15:14:03 -0800 (PST)
From: "Larry Tunis" <mnpx@2bmail.co.uk>
Subject: Get rid of your "LOVE HANDLES' in 24 hours # 65D
To: lose39f@ywing.netscape.com
X-Mailer: Microsoft Outlook Express 4.72.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V(null).1712.3
Mime-Version: 1.0
Date: Sat, 06 Jan 2001 15:24:11 -0500
Content-Type: text/plain; charset="iso-8859-1"
Message-Id: <200101070712557.SM00166@fkerkrej>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f06NE2v10347
Resent-Message-ID: <"41dShC.A.zhC.6a6V6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

JUST IN TIME FOR THE HOLIDAYS!!!!!!

It only takes an hour of your time
to gently rub in our miracle gel and
.. LOSE 4-6 INCHES OF STUBBORN FAT OVERNIGHT!

****FLATTEN your stomach.
****RE-SHAPE your butt.
****TRIM your thighs.
****REDUCE cellulite everywhere!


^^^WITHOUT strict diets
^^^WITHOUT strenuous exercise
^^^WITHOUT harmful metabolism boosters
^^^WITHOUT expensive surgery


Do you want to...

[   ]  GET SLIM for the Holidays & STAY SLIM?

[   ]  EAT WHAT YOU WANT at Holiday feasts and
        festivities but GET RID OF those extra  inches FAST?

[   ]  BEGIN THE NEW YEAR without having to
        go on ANOTHER DIET?


YOU CAN DO IT ALL!!!!!
with the safe and reliable overnight results of
our MIRACLE GEL.
It's safe to use as often as once a week
to help you lose more and more inches
OR...
to lose the added inches
of too much Holiday celebrating!


            GUARANTEED RESULTS!

"My wife was scheduled for $6,000 liposuction surgery.
We saw your ad and decided your product was worth
trying first. Words can't express our delight!   My wife
lost four inches in her midriff and three inches in her waist,
much more than the 'average results' in your ad. Needless
to say, we cancelled the surgery."
                                            Eric Larsen, Lacrosse, WI

"I'm a professional singer, and I'm on the road a lot.  I lost
almost two inches in my waistline in the first 24 hours.
I am very proud of the fact that I have lost this waistline
and obliques fat."
                                            David Hutchins, Hickory,
NC

"I lost one inch in my waist, one inch in my hips, and two inches
in my thighs. The overnight results with your product are
really great!  Thank you!"
                                            Susan Meir, New York, NY


FOR MORE FREE INFORMATION, lots of testimonials, and
a step-by-step description of how this product safely creates
such amazing overnight results 

Reply To:  
mailto:cxz82@verizonmail.com?subject=more_info

CALL US:    520-203-4572 (9am-6pm, MST Mon-Sun)
You'll talk to people who have used our miracle gels.

////////////////////////////////////////////////////////
If you wish to be removed from our list please reply to
mailto:mnpx@torchmail.com?subject=remove
////////////////////////////////////////////////////////





From list@netscape.com  Sat Jan  6 21:48:41 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20507
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 21:48:40 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f072bo325776;
	Sat, 6 Jan 2001 18:37:50 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f072kbc13464;
	Sat, 6 Jan 2001 18:46:37 -0800 (PST)
Resent-Date: Sat, 6 Jan 2001 18:46:37 -0800 (PST)
From: streambiz2002@mail.com
Message-Id: <200101070229.KAA07217@cinms.ptt.js.cn.>
To: streambiz2003@aol.com
Date: Sat, 06 Jan 01 20:09:53 EST
Subject: Make Money While You Sleep!
Resent-Message-ID: <"P13SpB.A.GSD.Li9V6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Hi,


 I thought I'd drop this one time quick note to let you know 
about an EXCELLENT e-Commerce Business which has enjoyed rapid 
and  consistent growth in the last 3 years. 


 It may fit very well into your business portfolio.  This is the 
EASIEST and the BEST online business today,  virtually a SELF-RUN 
ONLINE BUSINESS. It's TWICE voted as the #1 online business.  



 *Christian, of Marion, OH. writes:  


  "I'm having 10 times the success with this business as I did 
with my other MLMs that I tried. I have a personal closure rate of 
about 80%. And I attribute that totally to the system that you have 
created. It truly is the best company out there. 

 Since  joining in August of this year, I have been approached by 3  
distributors of other companies, including 1 co-founder, but after 
explaining what I do in my business and how I work the opportunity, 
I guess they've given up knowing that their program is much harder 
to achieve success in."   

 If your current program demands that you sell products and sponsor 
others you will fail 90% of the time! Put yourself in the power position; 
win 90% of the time offering a program that  everyone wants to be 
involved with! 



 Simply click below to visit the award-winning website:  

http://12.21.34.21/streambiz1

It will ONLY take a minute to find out.  

You will be glad that you did!


  I received your e-mail as someone interested in 
Internet Business  Opportunities. If I received your e-mail 
in error, or you are no  longer interested, click here to be 
removed Be sure REMOVE is in the Subject Title and you will 
not be contacted again:  
mailto:streambiz002@yahoo.com?subject=Remove
 
 Thank you!
 



From list@netscape.com  Sat Jan  6 23:45:15 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22052
	for <ldapext-archive@odin.ietf.org>; Sat, 6 Jan 2001 23:45:14 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f074YK301149;
	Sat, 6 Jan 2001 20:34:21 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f074h7c00926;
	Sat, 6 Jan 2001 20:43:07 -0800 (PST)
Resent-Date: Sat, 6 Jan 2001 20:43:07 -0800 (PST)
Message-Id: <sa57912c.078@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Sat, 06 Jan 2001 21:42:04 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@openldap.org>, <George_Robert_Blakley_III@tivoli.com>
Cc: <rbyrne@bebop.France.Sun.COM>, <ietf-ldapext@netscape.com>
Subject: Re: ldap acl draft (06): browse needed ?
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f074h5v00902
Resent-Message-ID: <"v5AGyD.A.MO.aP_V6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

I agree with Kurt's view. At a point in NDS's past, we had to abandon the hierarchical, or tree-walk type of searching that required the browse permission due to the scalability and performance constraints it imposed.

Jim

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/6/01 10:15:26 AM >>>
Bob,

If I understand your suggestion properly, you wish to have a
mechanism where return entries is controlled by controls placed
upon 'intermediate' entries.  I define an intermediate entry
as any entry between the 'base' and matching entry excluding
both.

In implementations that I am familiar with, providing such
functionality would be extremely difficult as they use indexing
systems to locate matching entries and don't examine intermediate
entries (or ACLs upon intermediate entries) to determine whether
or not to returned matched entries.  Doing so would be require
significant redesign of such implementations.

I would suggest that any ACL feature which required servers relying
on the contents of intermediate entries be OPTIONAL.

Kurt

At 02:52 PM 1/4/01 -0600, George_Robert_Blakley_III@tivoli.com wrote:
>Rob,
>
>The intent of the "browse" permission is not to prevent discovery of DNs;
>that is what "returnDN" permission is for.
>
>"browse" is to take care of the case where there is a hierarchy of entries
>and:
>
>(1) A subject "S" has authority to perform some operation (say "read") on
>an entry (call it "E") which is not the root
>(2) "S" has no permission to read or otherwise do anything to some entry
>"I" which is on the path between the root and "E"
>(3) "S" does not know or does not wish to use the explicit name of entry
>"E"
>
>An example of this case is when a subject "Bob" has "read" access to a leaf
>entry but no access to any other entry,
>and does not know the name of any entry in the hierarchy.  Bob wishes to do
>a query on some attribute value.  This query
>matches an attribute of "E", and hence (since Bob has permission to read
>E), E should be returned in response to the
>query.
>
>However, if Bob tries to execute the search starting at the only point he
>knows about (the root), the query will fail, because
>he has no permission to "I" or any other entry on the path between the root
>and "E".
>
>This is exactly analogous to the use of the "x" mode bit in the UNIX
>filesystem to allow users to traverse directories into
>which they cannot write and from which they cannot read.
>
>--bob
>
>Bob Blakley
>Chief Scientist, Security
>Tivoli Systems, Inc.
>
>
>ietf-ldapext-request@netscape.com on 12/14/2000 09:22:38 PM
>
>Please respond to <rbyrne@bebop.France.Sun.COM>
>
>To:   <ietf-ldapext@netscape.com>
>cc:
>Subject:  ldap acl draft (06): browse needed ?
>
>
>
>
>The current acl draft proposes an entry level permission called "browseDN"
>(4.2.2).  The idea behind this permssion is to able to set a
>policy saying something like "you can see this entry if you name it
>explicitly as the base of a search, otherwise not".
>
>At Pittsburgh people seemed to like this permission and I agreed to do a
>proposal for this....however, relative
>to a single "read" level permission that ignores scoping it does complicate
>things.  The definition of the required permissions for
>search (5.2) already has to deal with a fair line up of other permssions
>(filter (presence and "the rest"), attribute level read, returnDN
>and discloseOnError).  While providing more permssions certainly increases
>the flexibility of the model,
>it also makes it harder to understand and administrate,  so my inclination
>is drop the browse permission in favour of a single "read"
>permission at the entry level.
>
>My question is do people feel strongly that the "browse" permission is
>required ?  If so, please propose a compelling scenario that
>really needs this granularity  of control of search permissions.  I will
>then include this as a motivating example and propose a way to include
>it in the required permssions for search.  Otherwise I intend to drop it
>for the 07 draft...
>
>Rob.



From list@netscape.com  Sun Jan  7 09:12:17 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA08105
	for <ldapext-archive@odin.ietf.org>; Sun, 7 Jan 2001 09:12:16 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f07E1l325933;
	Sun, 7 Jan 2001 06:01:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f07EAZk24778;
	Sun, 7 Jan 2001 06:10:35 -0800 (PST)
Resent-Date: Sun, 7 Jan 2001 06:10:35 -0800 (PST)
Date: Sun, 7 Jan 2001 06:10:31 -0800 (PST)
To: acrp@windows.ru
From: <acrp@windows.ru>
Subject: HAVE THE GREAT CREDIT YOU DESERVE!!! 
Message-ID: <97882450401@goliath.camtech.net.au>
Resent-Message-ID: <"M-igvD.A.4CG.ajHW6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


HAVE THE GREAT CREDIT YOU DESERVE!!! 

Have you ever tried to buy something but was turned down
because you had less than perfect credit? If so then you owe
it to yourself to read this email.

IT WILL CHANGE YOUR CREDIT LIFE FOREVER.

We have taken our years of experience and compiled it into a
104 page e-book that is 100% GUARANTEED to IMPROVE YOUR
CREDIT.

A recent customer had this to say:

"Hello, my name is John Bentley! IN 1987 I owned my own
business, however to a slow economy I had to file
bankruptcy. I would up loosing my business, my home, car and
most of my other ownings. Then I was fortunate enough to
find out about the ADVANCED CREDIT RESTORATION PROGRAM. I
took the time to read your email and it has truely changed
my life. Within 3 months of ordering your program I had
LEGALLY acquried a NEW CREDIT FILE. By following your
program I was able to load that new credit file with all
kinds of GOOD CREDIT in only 6 months.

It has now been 1 year since I bought this program and I now
have 250,000 in CREDIT CARDS and have recently bought ON
CREDIT a new $185,000 home and financed a NEW $36,000 Lexus.

Thank You for sharing your information with me and allowing
me to regain control of my CREDIT and my FUTURE."

John Bentley
Los Angelos

Over the last few years we have received thousands of
positive letters from customers just like this one. We have
had people have even better results than this.

This program will provide you all the information you need
to:

1.) Open a NEW CREDIT FILE 100% LEGALLY

2.) Legally PLACE POSITIVE CREDIT REPORTS on your NEW CREDIT
FILE 100% LEGALLY

3.) How to REMOVE BAD REPORTS from you CREDIT FILE 100%
LEGALLY

By using our program you will be able to:

1.) Buy a NEW CAR

2.) Buy a NEW HOUSE

3.) Go on VACATION

4.) Get MARRIED in STYLE

5.) Start your OWN BUSINESS

6.) ENJOY LIFE FINANCIALLY WORRY FREE

We have seen similar programs selling on the Internet for
HUNDREDS OF DOLLARS. We are not going to CHARGE YOU HUNDREDS
OF DOLLARS. We aren't even going to charge you ONE HUNDRED
DOLLARS. If you fill out the form below and mail CHECK OR
MONEY ORDER to:

R. Colbert

1442 SW 10th Street

Fort Lauderdale, FL  33312
____________________________________________________________

YOU WILL ONLY PAY $29.95 FOR TOTAL FINANCIAL FREEDOM
____________________________________________________________

Please print this email and fill out the form below:
____________________________________________________________

Full Name:         ____________________________________
Address:           ____________________________________
Address2:          ____________________________________
City/State/Zip:    ____________________________________
Daytime Phone:     ____________________________________
Evening Phone:     ____________________________________
Email Address:     ____________________________________

** We respect your privacy and will not share any of the
above information with any other persons or companies. **

# e-Books Desired: ____________________________________

Total Order Price: ____________________________________

** If you wish to order more than one e-Book or are buying
this one as a gift please provide the email addresses of
each person that you are buying a e-Book for and we will
email it directly to them with a GIFT CARD from you. **

Recipient #1:      ____________________________________
Recipient #2:      ____________________________________
Recipient #3:      ____________________________________
Recipient #4:      ____________________________________
Recipient #5:      ____________________________________
Recipient #6:      ____________________________________
Recipient #7:      ____________________________________
Recipient #8:      ____________________________________
Recipient #9:      ____________________________________
Recipient #10:     ____________________________________

** If you order 3 or more e-Books as gifts we will send you
the e-Book for FREE! **



From list@netscape.com  Sun Jan  7 11:17:01 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08687
	for <ldapext-archive@odin.ietf.org>; Sun, 7 Jan 2001 11:17:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f07G0m319368;
	Sun, 7 Jan 2001 08:00:49 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f07GEps13569;
	Sun, 7 Jan 2001 08:14:51 -0800 (PST)
Resent-Date: Sun, 7 Jan 2001 08:14:51 -0800 (PST)
Date: Sun, 7 Jan 2001 08:14:48 -0800 (PST)
Message-Id: <200101071614.f07GEmD15080@ywing.netscape.com>
From: ltgrx@hotmail.com
To: lvroh@Netfriends.netscape.com
Reply-To: tim16me2@n2mail.com
Subject: FLAT RATE LONG DISTANCE - YOU BE THE JUDGE!                                    [awgos]
Resent-Message-ID: <"Zg3AdD.A.vTD.6XJW6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

1st Fixed Phone Rate USA, CANADA & INTERNATIONAL 
               
SAVE SAVE SAVE  LONG DISTANCE  SAVE SAVE SAVE 

Incredible fixed monthly rates for long distance. 
Call to over 200 countries including India, 
Pakistan, Ukraine, etc... 
             
EXCELLENT QUALITY FROM ANY PHONE, EVEN CELLULAR   
No Credit Checks, Easy To Pay, Most Fantastic 
Value Residential and Small Business Perfect 
   
CHOOSE FROM THE CANADA PLAN, USA PLAN, AND
INTERNATIONAL PLAN.  

For detailed info please reply with "Send More 
Info Please" as the subject.

mailto:tim17@n2mail.com?subject=Send_More_Info_Please

Thanks for your time!
Dave
              



From list@netscape.com  Sun Jan  7 15:48:57 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10045
	for <ldapext-archive@odin.ietf.org>; Sun, 7 Jan 2001 15:48:57 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f07Kc6314698;
	Sun, 7 Jan 2001 12:38:06 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f07Kkto29867;
	Sun, 7 Jan 2001 12:46:55 -0800 (PST)
Resent-Date: Sun, 7 Jan 2001 12:46:55 -0800 (PST)
Message-ID: <00001cbd0f2a$000060f3$0000159c@209.162.52.75>
To: <Undisclosed.Recipients@ywing.netscape.com>
From: donjrb@excite.com
Subject: Email market place
Date: Sat, 06 Jan 2001 09:50:02 -0800
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Reply-To: remove101@excite.com
Resent-Message-ID: <"Uyt2r.A.OSH.-WNW6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: quoted-printable

<HTML>
<BODY bgColor=3D#FFFF80>

<FONT face=3D"MS Sans Serif">
<FONT size=3D3>  <BR>
<B>   Looking For Sales, or Exposure,<BR>
  we offer fresh targeted or general emails<BR>
  sent for you with current email addresses.<BR>
  Watch your business grow.</B> <BR>
<BR>
          <B>  We GUARANTEE response !</B> <BR>
<BR>
  * Daily reports on your email send !<BR>
<BR>
 *<I>  </I><U> 2001 Introductory Special !!!</U> <BR>
<BR>
 * We can even create your ad or announcement for you !<BR>
<BR>
<BR>
<FONT color=3D"#0000FF">  CALL  8 am. - 3:30 pm. P.S.T. </FONT>
<FONT color=3D"#0000FF"><U>  702-242-5725  or  702-528-2400</U></FONT> <BR=
>
 <BR>
<FONT size=3D2> <BR>
<BR>
 For removal see below.<BR>
<BR>
 <BR>
<BR>
<BR>
<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
 Sorry if you received this message in error.<BR>
 If you wish to be removed. Please, type "REMOVE"<BR>
 in the subject line:MAILTO:  remove101@excite.com<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
 <BR>
<BR>
</FONT></FONT></FONT><p><p><p><p><p><p><p><p><p><p><p><FONT face=3D"MS San=
s Serif"><p><FONT size=3D3>  <BR><p><B>   Looking For Sales, or Exposure,<=
BR><p>  we offer fresh targeted or general emails<BR><p><p><p><p></BODY></HTML>




From list@netscape.com  Sun Jan  7 15:52:23 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10074
	for <ldapext-archive@odin.ietf.org>; Sun, 7 Jan 2001 15:52:22 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f07KaF302571;
	Sun, 7 Jan 2001 12:36:16 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f07KoIU01343;
	Sun, 7 Jan 2001 12:50:18 -0800 (PST)
Resent-Date: Sun, 7 Jan 2001 12:50:18 -0800 (PST)
From: <success3003@hotmail.com>
Subject: FREE SOFTWARE.....A Complete Marketing Package!!
Date: Sun, 7 Jan 2001 10:03:57
Message-Id: <190.107586.877237@mail.datanet.ab.ca>
Resent-Message-ID: <"zrCo_C.A.tU.JaNW6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

FREE Software - FREE Opportunity

If you are determined to succeed on the Internet 
then visit our web site.

Here is what we offer you with your FREE membership.

*  FREE 2 E-Mail Address Extractor Programs!
*  FREE Email List Management program!
*  FREE The BEST E-Mail program on the Net! 
*  FREE Classified Ad submitter program! 
*  FREE Functional FFA Link submission program!
*  FREE Internet Training! 
*  FREE Internet Tools! 
*  FREE WebPainter! 
*  FREE E-Book Creation Software! 
*  FREE HTML Editing Program!
*  FREE FFA's! 
*  FREE Autoresponders! 
*  FREE Report - Creating Profitable Ads! 
*  FREE Meta-Tag Generating Program! 
*  FREE Automatic Keyword Generator! 
*  FREE E-Book Building an MLM Empire!
*  FREE Dozens of Fantastic Marketing E-Books!

***Plus Much Much More***

This is just the TIP of the Iceberg folks!

Check it out.

For more info mail to:
success3008@yahoo.com
 
 
 
 
 
 
 
 
 
 
 
 
 



From list@netscape.com  Sun Jan  7 23:03:59 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA13413
	for <ldapext-archive@odin.ietf.org>; Sun, 7 Jan 2001 23:03:58 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f083lF326374;
	Sun, 7 Jan 2001 19:47:15 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0841IM01171;
	Sun, 7 Jan 2001 20:01:18 -0800 (PST)
Resent-Date: Sun, 7 Jan 2001 20:01:18 -0800 (PST)
From: <clsdcks@www.tarron.lt>
To: <ietf-ldapext@netscape.com>
Date: Sat, 6 Jan 2001 02:46:00
Message-Id: <95.506289.427397@mail.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"HOuPgD.A.2R.NuTW6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY!

STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN 
GET ONE FOR ONLY $11.95 PER MONTH!

DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE 
DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO 
GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A 
SIMPLE PHONE CALL TO  OUR OFFICE.

YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with 
no extra charge!  UNLIMITED TRAFFIC -- no extra charge!

FRONT PAGE EXTENSIONS are FULLY SUPPORTED.

A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS.

ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP 
CHARGE.

FOR DETAILS CALL 1 888 248 0765  if you are outside the USA,
please fax 240 337 8325

Webhosting International

 
 
 
 
 
 
 
 
 



From list@netscape.com  Mon Jan  8 11:04:02 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08849
	for <ldapext-archive@odin.ietf.org>; Mon, 8 Jan 2001 11:04:01 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f08Fln314351;
	Mon, 8 Jan 2001 07:47:49 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f08G1rk08295;
	Mon, 8 Jan 2001 08:01:53 -0800 (PST)
Resent-Date: Mon, 8 Jan 2001 08:01:53 -0800 (PST)
Date: Mon, 8 Jan 2001 08:01:14 -0800 (PST)
Message-Id: <200101081601.f08G1DD04095@ywing.netscape.com>
From: alucoc@HCRB.yahoo.com
To: .WVLB@netscape.com
Subject:  Turn $35 Into $88,620 WITHOUT LIFTING A FINGER, 200% on your investment or money back -NMOK
X-Reply-To:  alucof@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"SWUgpD.A.EBC.vReW6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello! 

Dear friends,

 Turn $35 Into $88,620 WITHOUT LIFTING A FINGER Or $164,220 By Pushing A Few Keys 
 200% Return On Your Money  withIn 60 Days - OR YOUR MONEY BACK 

 And this is only the beginning! 

 Impossible? 

 Well to be honest with you, that may have been the case before you visited our program. But since
 you're here, that's no longer the case! 

 You see, with our unheard of and unsurpassed GUARANTEE we intend to prove to you beyond a
 shadow of a doubt, that what you're reading now is ABSOLUTELY TRUE or we'll gladly refund your
 one-time-only $35 subscription fee. No questions asked! 

 That said, you'll only lose by not joining...fair enough? 
 
Thank you for your time. Let me show you how to turn $45 into $88,620.00 and only pay one time out of 
pocket money when you are assured to earn $88,620.00

The game is called Skeptic's Heaven and it is only open for Gold-Club member, so please join for FREE as a 
gold club member.

Please visit         http://gold-club.net/sponsor.asp?PW99518

So why Gold-Club?
Because,  in Skeptic's Heaven you need six downline to qualify for bonuses. Once you sign with Gold-
Club you don't have to recruit anyone Gold-Club will put downline under you. And the beauty is you don't 
have to pay until you have enough downline placed under you. In other words, you only pay when you 
are assured to have the bonuses. Isn't that great? I beg you would see how gold-club work for you now.
By the way it's free to sign. Give it a try.

After you become a member of Gold-Club, visit the members' area and you'll find that there are more than 
Skeptic's Heaven avaible. Brief through.

Interesed ? Well, read on and find out how Gold-Club work for you.

Thank you for your interest in our business. We sincerely invite you to join us, as this club will only benefit 
you and would not cause you a penny until you can see your profit. 
Sound too good to be true ? Yes! It is true and in fact it's very logical.

In Gold-Club,  You
PAY NOTHING,
DO NOTHING 
AND YET YOU GET PAID!!!!!!!!!

This club is specially designed for those who are not good in selling products and recruiting people. And 
yet they are very interested in MLM business because of the great profit that they can make through MLM.


How It Works ?
Well, as soon as you join our club you will be put in a member pool that is filled with new members 
repeatedly. When a group contains enough people to fill our safety criteria, one person of the group joins 
the current, established MLM company that we are associated with and then he is removed from the 
group. You are moved up one level each time this happens (usually only three levels) and then you are 
requested to join the MLM company too. Until this happens you don't have to do anything but wait (can take 
from only 3-4 days up to several weeks). Remember that you are free to leave anytime in this process and 
that you haven't paid anything!

As soon as you have joined with the real MLM company we have your guaranteed downline ready for you 
in the member pools and we send out requests to them to join under you. This means that you can start 
earning money from your sponsored people almost immediately!


Please visit     http://gold-club.net/sponsor.asp?PW99518

It's free to join anyway. Give yourself a chance!


OTHER OPPORTUNITIES
Read your e-mai land get paid. Free to join.
Visit  http://www.mintmail.com/?m=200889

Get A FREE visa card with no annual fee, earn commissions by reffering to others,up to 7 levels deep.
Free to join

Visit       http://www.VisaRebates.com/Index.cfm?ReferralID=piwong




Thank you, for your time. Good luck.



Best regards,

Steve

If this message gets to you in error please send us an e-mail with the subject
"remove" on it.

mailto:alucof@yahoo.com





From list@netscape.com  Tue Jan  9 09:33:11 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA12525
	for <ldapext-archive@odin.ietf.org>; Tue, 9 Jan 2001 09:33:11 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f09EH0327997;
	Tue, 9 Jan 2001 06:17:00 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f09EV6E25476;
	Tue, 9 Jan 2001 06:31:06 -0800 (PST)
Resent-Date: Tue, 9 Jan 2001 06:31:06 -0800 (PST)
Date: Tue, 9 Jan 2001 06:30:59 -0800 (PST)
Message-Id: <200101091430.f09EUnB17809@xwing.netscape.com>
From: InquireToday@ispchannel.com
To: @netscape.com
Subject:  Over35 Free Newsletter - Syndrome X
X-Reply-To:  InquireToday@ispchannel.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"5Mun0.A.gNG.pCyW6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Over35 Free Newsletter 
WHAT IS SYNDROME X?

Syndrome X is the first stage of a silent but deadly disease that's becoming epidemic 
in the US – diabetes.  Syndrome X usually appears 10 years or so before the onset of 
diabetes.  At present 16 million Americans suffer from Type 2 diabetes, although one 
in three don't even know they have it, and millions more show signs of Syndrome X.  
Even more disturbing is that this disease, once found solely in the over-40 crowd, is 
now appearing in children as young as 10.  

Syndrome X is characterized by insulin resistance, abdominal obesity, high cholesterol 
and high blood pressure.  It's estimated that 20-30 percent of all middle-aged 
Americans suffer from Syndrome X – although the occurrence among Blacks and 
Native Americans is about 50 percent.  Left unchecked, Syndrome X frequently 
leads to the development of diabetes and significantly increases the risk of heart 
disease.  

Though heredity plays a part, lifestyle choices – including lack of physical activity, 
obesity and the over-consumption of carbohydrates – carry much of the blame for the 
development of both Syndrome X and diabetes.  The good news is that science has 
already identified many readily available nutrients that significantly enhance the body's 
ability to properly use insulin, and help regulate blood sugar levels.  With proper diet 
and regular exercise, it's possible to halt the progression of Syndrome X and even 
prevent the devastating consequences of diabetes all together.

More on Syndrome X and its prevention next week.

Feel free to forward.

Removal: TakeMeOff@ispchannel.com  
(thank you!)

Subscribe, Questions, Suggestions: InquireToday@ispchannel.com




From list@netscape.com  Wed Jan 10 06:53:40 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA13617
	for <ldapext-archive@odin.ietf.org>; Wed, 10 Jan 2001 06:53:39 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ABbtG08083;
	Wed, 10 Jan 2001 03:37:55 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0ABq3219119;
	Wed, 10 Jan 2001 03:52:03 -0800 (PST)
Resent-Date: Wed, 10 Jan 2001 03:52:03 -0800 (PST)
Date: Wed, 10 Jan 2001 13:49:17 +0200
Message-ID: <B0000035196@invitros-server.invitros.lv>
To: moreinfo9998@aol.com
From: <moreinfo9998@aol.com>
Subject: Re: I saw your web site
Resent-Message-ID: <"bLEe7B.A.dqE.izEX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


Dear Web Merchant,

My company has taken notice of your on-line presence and
wanted to bring a few things to your attention.

Over the past several years, we have spoken with hundreds of
online merchants like you, who unfortunately are not happy.
The reason for their unhappiness varies but all seem to have
common issues.

Here are a few examples of some problem issues:

-  I can’t get my Web site updated with new material.

-  My Web site was supposed to be completed within 2 wks,
it's been over 2 mnths.

-  changes made to my Web site, are not what I requested and
take another month to get them right.

-  I can’t get any technical support for my growing Internet
needs.

-  Nobody returns my calls, regarding Web site issues and
they can’t answer the questions I have.

-  My monthly maintenance seems a little expensive for the
services I receive.

-  I want my own domain name but it is too expensive.

-  My Web site take a long time to download compared to
other sites.

Do you and your company have any of these issues?  If so,
you may want to look into finding another Web site
development and hosting company.  My company has helped
hundreds of companies with the same problems and they still
can’t believe the difference! We specialize in Internet
solutions and strategies.

That’s all.

Your company has an objective when it comes to the Internet
and we have a solution.

Here are a few things one can expect from our company.

-  Professional Web site appearance and layout. -  Excellent
technical support. -  Super fast Internet connection and
download speeds. -  Some of the most competitive pricing in
the nation! -  Super fast Web site updates. -  Advanced
level services including JAVA, CGI, ActiveX, Cold Fusion,
and more!

If any of these areas interest you and you would like to
find out more about our company, we would like to welcome
you to call 1 888-585-8658 or Print the Form and Fax back to
1-800-243-0358.  To receive more info about our services
reply to moreinfo9998@aol.com

[    ]  Web Site Redesign  [    ] Generate Traffic to your
Web Site

[    ]  Web Site Marketing [    ] Premium Search Engine
Submission

[    ]  Web Site Design    [    ]  Add E-commerce to an
existing Web site

[    ]  Targeted email campaign by Industry, Category, or
SIC Codes

[    ]  Low Cost Hosting starting at 9.95

[    ]  TOP 10 Search Engine Placement

COMPANY NAME: ______________________________________

CONTACT:  ___________________________________________

EMAIL:  ______________________________________________

PHONE:  ___________________   FAX:  ___________________

DOMAIN NAME:  _______________________________________

This email is being sent in compliance with Senate bill
1618,Title 3, Section 301. Per Section 301, Paragraph (a)(2)
(c)of S.1618,
http://rs9.loc.gov/cgi-bin/query/D?c106:2:./temp/~c106JIzSIO
:: Further transmissions to you by the sender of this email
may be stopped at no cost to you by sending a reply to this
email address with the word "remove" in the subject line.



From list@netscape.com  Wed Jan 10 07:39:43 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14542
	for <ldapext-archive@odin.ietf.org>; Wed, 10 Jan 2001 07:39:43 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ACSls14960;
	Wed, 10 Jan 2001 04:28:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0ACbcQ28175;
	Wed, 10 Jan 2001 04:37:38 -0800 (PST)
Resent-Date: Wed, 10 Jan 2001 04:37:38 -0800 (PST)
Date: Wed, 10 Jan 2001 04:36:46 -0800 (PST)
Message-Id: <200101101236.f0ACakB10181@xwing.netscape.com>
From: gpinfo4u@themail.com
To: Information@xwing.netscape.com, Seeker@netscape.com
Subject:   Which turns you on? Time? Money? or Both?!
X-Reply-To:  "Gerry" gpinfo4u@themail.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"3sOAhC.A.t3G.QeFX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

I received your e-mail address as someone interested in an Internet Business Opportunity. If I received 
your e-mail in error, or you are no longer interested, please click the reply button and type REMOVE" 
in the Subject Line and you will not be contacted again. Thank 
You									

If you own a home-based business or want one, and are trying 
to market it on the Internet, let me ask you a few questions:

1. Would you like to have the email address of EVERYONE 
who VISITS your home-based business website?

2. Would you like to have an automatic email responder 
system that sends each VISITOR follow-up messages over 
any period of time?

3. Would you like to be able to instantly update everyone 
who has EVER VISITED your website with company 
announcements or events they can benefit from?

4. Would you like to be able to set up follow-up notes that
automatically are sent on your prospect’s birthday, 
anniversary or other special days?

5. Would you like to start your OWN newsletter and build a 
relationship with your prospects so when it’s the right 
time for them to start a home-based business they think 
of YOU!?

6. Would you like to know which advertisements, email blasts, 
banners, links, newsletters (online AND offline) are most 
effective for your particular opportunity and which ones 
are a waste of your time and money?

7. Would you like to know your exact COST PER VISITOR and 
REVENUE PER VISITOR?

8. Would you like your advertising to actually MAKE YOU MONEY?

9. Would you like to SELL A SYSTEM FIRST, rather than the 
product or compensation plan, so that anyone who says 
"yes" can see themselves duplicating your business 
immediately?

10. Would you like a duplicatable training system that teaches 
you and your new recruits exactly how to build massive 
success in your home-based business, and step-by-step 
instructions for finding leads on the Internet?

11. Would you like a website that makes you AUTOMATIC FAST 
MONEY with affiliate program links while you focus on 
your home-based business?

12. Would you buy me a cheap cup of coffee each day if I 
could deliver all this to you?
Send me an e-mail at <mailto:gpinfo4u@themail.com> 
To your success,
Gerry R. Porter






From list@netscape.com  Wed Jan 10 09:06:05 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16905
	for <ldapext-archive@odin.ietf.org>; Wed, 10 Jan 2001 09:06:04 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ADt4s22237;
	Wed, 10 Jan 2001 05:55:04 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0AE3tU18242;
	Wed, 10 Jan 2001 06:03:55 -0800 (PST)
Resent-Date: Wed, 10 Jan 2001 06:03:55 -0800 (PST)
Message-ID: <0000773a0715$00002dc2$00003eaa@>
To: <Undisclosed.Recipients@ywing.netscape.com>
From: leah262@excite.com
Subject: Don't miss the Internet wave
Date: Mon, 08 Jan 2001 21:15:42 -0800
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Reply-To: remove101@excite.com
Resent-Message-ID: <"mfaWeB.A.qcE.KvGX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: quoted-printable

<HTML>
<BODY bgColor=3D#FFFF80>

<FONT face=3D"MS Sans Serif">
<FONT size=3D3>  <BR>
<B>   Looking For Sales, or Exposure,<BR>
  we offer fresh targeted or general emails<BR>
  sent for you with current email addresses.<BR>
  Watch your business grow.</B> <BR>
<BR>
          <B>  We GUARANTEE response !</B> <BR>
<BR>
  * Daily reports on your email send !<BR>
<BR>
 *<I>  </I><U> 2001 Introductory Special !!!</U> <BR>
<BR>
 * We can even create your ad or announcement for you !<BR>
<BR>
<BR>
<FONT color=3D"#0000FF">  CALL  8 am. - 3:30 pm. P.S.T. </FONT>
<FONT color=3D"#0000FF"><U>  702-242-5725  or  702-528-2400</U></FONT> <BR=
>
 <BR>
<FONT size=3D2> <BR>
<BR>
 For removal see below.<BR>
<BR>
 <BR>
<BR>
<BR>
<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
 Sorry if you received this message in error.<BR>
 If you wish to be removed. Please, type "REMOVE"<BR>
 in the subject line:MAILTO:  remove101@excite.com<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
 <BR>
<BR>
</FONT></FONT></FONT><p><p><p><p><p><p><p><p><p><p>








<p><FONT face=3D"MS Sans Serif"><p><FONT size=3D3>  <BR><p><B>   Looking F=
or Sales, or Exposure,<BR><p>  we offer fresh targeted or general emails<B=
R><p>  sent for you with current email addresses.<BR><p>  Watch your busin=
ess grow.</B> <BR><p><BR><p><p></BODY></HTML>




From list@netscape.com  Wed Jan 10 23:03:21 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA12452
	for <ldapext-archive@odin.ietf.org>; Wed, 10 Jan 2001 23:03:16 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0B3qQs21062;
	Wed, 10 Jan 2001 19:52:26 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0B41IA12236;
	Wed, 10 Jan 2001 20:01:18 -0800 (PST)
Resent-Date: Wed, 10 Jan 2001 20:01:18 -0800 (PST)
X-Sender: incomeforyoujan2001@hotmail.com
From: Scott <incomeforyoujan2001@hotmail.com>
To: "Opportunity Seeker" <incomeforyoujan2001@hotmail.com>
Date: Wed, 10 Jan 2001 20:44:00 -0800
Subject: $2000+ Per Week & VACATIONS
Reply-To: incomeforyoujan2001@hotmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20010111040111.GTDE4166.priv-edtnes09-hme0.telusplanet.net@localhost>
Resent-Message-ID: <"cVtJVC.A.6-C.NATX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit


My name is Scott Klarenbach and I'm responding to your recent request for a business 
opportunity that you can grow from home.  

How would you like to market a $15,000 Vacation package that includes 3 Cruises, 
23 vacations worldwide, and over $4,000 in FREE airfare for the unbelievable 
price of only $1,295? - OF WHICH YOU WILL EARN $1,000 COMMISSION PER SALE!

This package is over 15 years old, and all of the companies represented are upstanding 
members of the Better Business Bureau. We have affiliations with some of the 
LARGEST Multi-Billion Dollar Companies in the travel industry.

All of the selling is done for you.  We have daily national conference calls, 
and a great website that you can use to sell the package.  If you didn't make 
$3,000 last week, and you haven't been on at least 2 Cruises so far this year, 
then you have to call right now!

This is the most AMAZING package you will ever see, and it literally sells itself. 
 We have directors that are earning over $8,000 per week.

If this sounds interesting, call my toll free number for some recorded information. 
 The number is 1-800-701-7654.


To be removed from this mailing, please send a blank email to removeme304@hotmail.com
Please understand that the tampering with this email address will only result 
in the inability to remove those who wish to be deleted.  Take care.


Your own FREE ISP is waiting for you at netzero.  Just visit www.netzero.net



From list@netscape.com  Thu Jan 11 07:30:44 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA29157
	for <ldapext-archive@odin.ietf.org>; Thu, 11 Jan 2001 07:30:43 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0BCJks01710;
	Thu, 11 Jan 2001 04:19:46 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0BCSdw09225;
	Thu, 11 Jan 2001 04:28:39 -0800 (PST)
Resent-Date: Thu, 11 Jan 2001 04:28:39 -0800 (PST)
Date: Thu, 11 Jan 2001 04:28:06 -0800 (PST)
Message-Id: <200101111228.f0BCRjB01847@xwing.netscape.com>
From: muny@BNEL.comp.net
To: Business@xwing.netscape.com, seeker.OLJM@netscape.com
Subject:  Work from Home! Guaranteed Minimum Monthly Income$$$ -QDOB
X-Reply-To:  rdbaronm@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"AFpTwC.A.nPC.1baX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Have Your Downline Built 
BEFORE 
You Spend Any Money! 

This program even offers you a Monthly Guaranteed 
Minimum Income !!

Guaranteed DOWNLINE, Guaranteed INCOME! 
It's International

Don't miss out on this Great Opportunity to secure yourself 
a Guaranteed.
Monthly Minimum Income!!!

It's FREE to join our Post Launch Program !!! Your FREE 
membership # 
will also be entered into a lucky draw to WIN $100 to shop 
online !!

ALL new members who join after you will be placed in ONE 
Straight Line 
down UNDER you.

YOU can easily get 500-1,000 members under YOU in a 
month !!

There is absolutely NO RISK to get involved and NO 
COST to join our 
Post Launch Program.

To Sign Up:
Simply reply to: markwitt@egyptian.net
Put in the Subject Line: Send My FREE Membership 
(required!!)
Place in the letter Content: Your First and Last Name 
(required!!)
Your Email Address if different from the current one.

All information comes with your FREE Membership!

You have nothing to lose and potentially a lot to gain. 

JOIN TODAY !!! 

We will confirm your position and send you your Member 
Number 
and a special report as soon as possible.


____________________________________________
Internet Services
For Permanent Remove
mailto:m58wd@yahoo.com?subject=remove






From list@netscape.com  Thu Jan 11 17:22:34 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA15629
	for <ldapext-archive@odin.ietf.org>; Thu, 11 Jan 2001 17:22:33 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0BM6CG09468;
	Thu, 11 Jan 2001 14:06:12 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0BMKNY03583;
	Thu, 11 Jan 2001 14:20:23 -0800 (PST)
Resent-Date: Thu, 11 Jan 2001 14:20:23 -0800 (PST)
Subject: FREE Digital Satellite System
From: Satellite334@excite.com
Message-Id: <ulxjuyajrqo.asuylaigdrqloigi@ns1.netstrategy.com.au>
Date: Thu, 11 Jan 2001 15:17:27 -0700
To: BEST-Satellite-deals@youmailbox-t.co.com
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7BIT
Resent-Message-ID: <"TEmi_.A.Y3.lGjX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7BIT


For a limited time, 
we'll give you this top-of-the-line Digital Satellite System 
absolutely FREE! 

We'll even include Free Installation!

Just call Toll-Free: 1-877-897-2871  to be Guaranteed Your FREE Satellite 
Today!!
                       
Includes:
· Free Installation. 
· Over 500 Channels of Quality Digital Television.
· Interactive television capability.
· Innovative 20" Satellite Dish.
· On screen graphics, stereo receiver and infrared remote.

If you call today, we'll throw in a second reciever to use for your second TV 
set.

Call 1-877-897-2871 to arrange delivery, and begin surfing through 500 
Channels Today.  Operators are standing by 24 hours/day.

Call Now! 1-877-897-2871



From list@netscape.com  Thu Jan 11 21:55:36 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA18843
	for <ldapext-archive@odin.ietf.org>; Thu, 11 Jan 2001 21:55:35 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0C2d8G20655;
	Thu, 11 Jan 2001 18:39:09 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0C2ebw01632;
	Thu, 11 Jan 2001 18:40:37 -0800 (PST)
Resent-Date: Thu, 11 Jan 2001 18:40:37 -0800 (PST)
Date: Thu, 11 Jan 2001 18:31:39 -0800 (PST)
Message-Id: <200101120231.f0C2Vd529923@ywing.netscape.com>
From: ntlzj@hotmail.com
To: aflxh@Cyberwavefriend.netscape.com
Reply-To: ron02me2@n2mail.com
Subject: EARN $1000 EVERY TIME SOMEONE SPENDS $89!                                    [bjxum]
Resent-Message-ID: <"8mHALD.A.cU.S6mX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

EARN $1000 EVERY TIME SOMEONE SPENDS $89!

If YOU did not make at least $2,000 last week. then 
you'd be FOOLISH not to check this out! 


"I sent out a 1000 piece fax blast, got 25 calls, 
had 14 messages, and signed up 11 people! That's 
$11,000 in one week! Thank you God!"
Derrick Alexander. - Atlanta,GA


"WOW! I needed to make ALOT of MONEY immediately when 
I started, for some BILLS! Did I ever! My first DAY I 
made $6,000! Thanks to all the FREE tools and help 
from my sponsor, my life will never be the same!"     
David Webster. - Newport Beach,CA

This is the most explosive income opportunity I've 
ever seen! It's NOT an MLM! There are NO MEETINGS, 
INVENTORY, or STRESS! You simply operate a wholesale/
retail business. You market a fabulous travel package 
that earns you $1000 PER SALE! With $89 down we approve 
98% FINANCING making this EASY TO SELL! AND EACH 
CUSTOMER BRINGS YOU 2 SALES WORTH ANOTHER $2000 IN 
YOUR POCKET! 

Eventually you'll MAKE $5000 A WEEK IN YOUR UNDERWEAR..
ANSWERING THE PHONE! SEE FOR YOURSELF.  CHECK US OUT!

For detailed info, reply with "Yes Send Info Please"
as the subject.

mailto:ron02me@n2mail.com?subject=Yes_Send_Info_Please
                                                                          
DON'T WAIT ANOTHER DAY.  DO IT NOW!

Have a Great Day!
Ron



From list@netscape.com  Fri Jan 12 01:07:57 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA22792
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 01:07:57 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0C5piG05706;
	Thu, 11 Jan 2001 21:51:44 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0C65tc15315;
	Thu, 11 Jan 2001 22:05:55 -0800 (PST)
Resent-Date: Thu, 11 Jan 2001 22:05:55 -0800 (PST)
Date: Thu, 11 Jan 2001 22:05:39 -0800 (PST)
Message-Id: <200101120605.f0C65Jq22023@xwing.netscape.com>
From: TDelaine@ltdlimited.com
To: futurecustomer@netscape.com
Subject:  Decorative Russian Lacquer Art
X-Reply-To:  russianart@ltdlimited.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"2vreMC.A.ruD.B7pX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Please note:  If you did not request this information simply delete this email or 
reply to the remove address at the bottom. Thank you!

Dear Friend,

This email is a special introduction to the world of Russian decorative art.  This is your 
special opportunity to own a truly unique and special form of 21st Century dating back to 
the 1700's.  Take a moment to read this special announcement.

Artshop of Saint Petersburg
http://www.ltdlimited.com/russianart/

Alexander Tikhonov and 40 local artisans in Saint Petersburg Russia established a joint 
venture with DeLaine LTD Limited to provide unique lacquer eggs and hand-made dolls.  
This venture began in 1999 and DeLaine LTD Limited has received numerous orders and 
inquiries on this unique decorative artwork.  Additionally, DeLaine LTD Limited has also 
reached an agreement to feature the artwork of Nina Novikova.  Nina has graciously made 
herself available to do custom paintings (from a scanned photograph) as well as her 
original paintings.

You now have the opportunity to see art work that is, in the words of Alexander Tikhonov, 
"art for the people's sake!"  This artwork is beautifully handcrafted and will enhance your 
home or office.

DeLaine LTD Limited would like to invite you to visit Artshop of Saint Petersburg and 
discover the world of Russian decorative art. You can visit our web site at the link listed 
below.

Secure ordering is available and we gladly accept Mastercard and Visa.  Don't wait!  
Take this special introductory opportunity to own a wonderful piece of Russian decorative 
art today!

Thank you for your time and we hope you will see this decorative art is truly something 
special.  Enjoy!

Note:  If you would like to receive the Artshop of Saint Petersburg newsletter, 
follow the instructions on the left-hand side of the home page.  Thanks again for 
your time!

Artshop of Saint Petersburg
http://www.ltdlimited.com/russianart/ 
"A Joint Venture between artisans of St. Petersburg and DeLaine LTD Limited. 
____________________________________________________________
Best Wishes from your Friends at DeLaine LTD Limited!
http://www.ltdlimited.com
____________________________________________________________
This message is sent in compliance of the new e-mail bill: 
Senate bill 1618, Title 3, section 301.

ALL REMOVES TO THIS ADDRESS WILL BE HONORED
Send your request to remove@ltdlimited.com and type Remove in the subject line 
of the message.  Please do not send removes to the interested address as you may end 
up receiving the information.




From list@netscape.com  Fri Jan 12 04:30:01 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA06476
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 04:30:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0C9INs24328;
	Fri, 12 Jan 2001 01:18:23 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0C9RHo22357;
	Fri, 12 Jan 2001 01:27:17 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 01:27:17 -0800 (PST)
To: BEST-Satellite-deals@youmail.co-com.netscape.com
Message-Id: <otnskwr.vtvlnirktcdxw@mail.hayat.com.tr>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Date: Fri, 12 Jan 2001 02:23:55 -0700
Subject: Your FREE Satellite TV System with Installation
From: Satellite33@excite.com
Resent-Message-ID: <"8UojT.A.2cF.z3sX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8BIT


For a limited time, 
we'll give you this top-of-the-line Digital Satellite System 
absolutely FREE! 

We'll even include Free Installation!

Just call Toll-Free: 1-877-897-2871  to be Guaranteed Your FREE Satellite 
Today!!
                       
Includes:
· Free Installation. 
· Over 500 Channels of Quality Digital Television.
· Interactive television capability.
· Innovative 20" Satellite Dish.
· On screen graphics, stereo receiver and infrared remote.

If you call today, we'll throw in a second reciever to use for your second TV 
set.

Call 1-877-897-2871 to arrange delivery, and begin surfing through 500 
Channels Today.  Operators are standing by 24 hours/day.

Call Now! 1-877-897-2871



From list@netscape.com  Fri Jan 12 05:10:34 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA06691
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 05:10:34 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0C9sCG22603;
	Fri, 12 Jan 2001 01:54:12 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0CA8Oc01796;
	Fri, 12 Jan 2001 02:08:24 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 02:08:24 -0800 (PST)
Date: Fri, 12 Jan 2001 02:07:54 -0800 (PST)
Message-Id: <200101121007.f0CA7eq27543@xwing.netscape.com>
From: zoran@australink.net
To: @netscape.com
Subject:  Y.E.S.
X-Reply-To:  zoran@australink.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"BJlAhC.A.ib.VetX6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

WARNING
 If you don't read this important letter,  it could cost you $70,000 this
 year!
 _/_/_/_/_/_/
 Or you can click on the link for a shortcut to money.
 http://globalws.net/show.cgi/zoran

 Statistics:
 Every 11 seconds someone starts a new Home Based Business. Some 8000 people a day are leaving 
their jobs and joining the 27.1 million at-home self employed, and the numbers are growing at the rate of 
over one million per year. 14.1 million home businesses are full time and numbers are increasing at the rate 
of 500,000 per year. 13.1 mullion home business are part time and the numbers are increasing at the rate 
of 600,000 per year. 66% of home businesses are owned by women, although men are catching up :-) Its 
been considered the greatest opportunity to increase the quality of your life and achieve financial freedom. 
The average Home Based Business earns nearly double the national average! The national average (USA-
Australia) is $26,000 per year if you exclude politicians. At the same time, the 27.1 million Home Based 
Business are averaging $50,250. Nearly twice as much! And 20% of them earn more than $75,000 per 
year.
 _/_/_/_/_/_/_/
 If these facts have caught your attention, then read on. Or you can click on the link for a shortcut to 
money.
http://globalws.net/show.cgi/zoran
 _/_/_/_/_/_/_/
 Do you feel like you are too busy  earning a living to make any real money? Are you tired of living "pay 
cheque to pay cheque" like I was? Do you dream of a better lifestyle for yourself and your family?
 If so, I urge you to take the next step in our screening process to find out just EXACTLY what we're 
doing. I guarantee it will change your life forever, just as it has for so many others.

 Someone very wise told us something we've never forgotten...."Successful people do what 
Unsuccessful people won't". Which are you? What if this really IS the opportunity you've been looking for?
 What do you have to loose by thoroughly checking it out before making a decision that it's not for you? 
And remember....Knowledge ISN'T power. ACTION IS!

 I look forward to helping you get started with your new home business, and talking with you very soon!
 And don't forget.....opportunity is usually disguised behind what most of us call HARD WORK!!!

 And here is the one for the road:
 Knock knock
 Who is there?
 Opportunity...
 impossible- Opportunity knocks only once.

 And I am Zoran, Your new friend from Aussieland






From list@netscape.com  Fri Jan 12 12:31:57 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13207
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 12:31:56 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0CHKrs15374;
	Fri, 12 Jan 2001 09:20:53 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0CHTmI26069;
	Fri, 12 Jan 2001 09:29:48 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 09:29:48 -0800 (PST)
From: <JLR@koolbits.com>
Subject: Millionaires Made Monthly
Date: Sat, 13 Jan 2001 02:56:55
Message-Id: <746.359873.387201@>
Resent-Message-ID: <"jYTrG.A.CXG.K8zX6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Dear Friends & Future Millionaire: 

AS SEEN ON NATIONAL TV: 
Making over half million dollars every 4 to 5 months from your home for 
an investment of only $25 U.S. Dollars expense one time 
THANK'S TO THE COMPUTER AGE AND THE INTERNET ! 
================================================== 
BE A MILLIONAIRE LIKE OTHERS WITHIN A YEAR!!! 
Before you say ''Bull'', please read the following. This is the letter you 
have been hearing about on the news lately. Due to the popularity of 
this letter on the Internet, a national weekly news program recently devoted 
an entire show to the investigation of this program described below, to see 
if it really can make people money. The show also investigated whether or 
not the program was legal. 
Their findings proved once and for all that there are ''absolutely NO Laws 
prohibiting the participation in the program and if people can follow the 
simple instructions, they are bound to make some mega bucks with only 
$25 out of pocket cost''. DUE TO THE RECENT INCREASE OF 
POPULARITY & RESPECT THIS PROGRAM HAS ATTAINED, 
IT IS CURRENTLY WORKING BETTER THAN EVER. 
This is what one had to say: ''Thanks to this profitable opportunity. I 
was approached many times before but each time I passed on it. I am 
so glad I finally joined just to see what one could expect in return for the 
minimal effort and money required. To my astonishment, I received total  $610,470.00 in 21 weeks, 
with money still coming in." 
Pam Hedland, Fort Lee, New Jersey. 
=================================================== 
Here is another testimonial: "This program has been around for a long 
time but I never believed in it. But one day when I received this again 
in the mail I decided to gamble my $25 on it. I followed the simple 
instructions and walaa ..... 3 weeks later the money started to come in. 
First month I only made $240.00 but the next 2 months after that I made 
a total of $290,000.00. So far, in the past 8 months by re-entering the 
program, I have made over $710,000.00 and I am playing it again. The 
key to success in this program is to follow the simple steps and NOT change 
anything.'' More testimonials later but first, 
===== PRINT THIS NOW FOR YOUR FUTURE REFERENCE ====== 
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 
If you would like to make at least $500,000 every 4 to 5 months easily and 
comfortably, please read the following...THEN READ IT AGAIN and AGAIN!!! 
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 
FOLLOW THE SIMPLE INSTRUCTION BELOW AND YOUR FINANCIAL 
DREAMS WILL COME TRUE, GUARANTEED! INSTRUCTIONS: 
=====Order all 5 reports shown on the list below ===== 
For each report, send $5 CASH, THE NAME & NUMBER OF THE REPORT 
YOU ARE ORDERING and YOUR E-MAIL ADDRESS to the person whose 
name appears ON THAT LIST next to the report. MAKE SURE YOUR RETURN 
ADDRESS IS ON YOUR ENVELOPE TOP LEFT CORNER in case of any mail 
problems. 
=== When you place your order, make sure you order each of the 5 reports. 
You will need all 5 reports so that you can save them on your computer 
and resell them. YOUR TOTAL COST $5 X 5=$25.00. 
Within a few days you will receive, vie e-mail, each of the 5 reports from 
these 5 different individuals. Save them on your computer so they will be 
accessible for you to send to the 1,000's of people who will order them 
from you. Also make a floppy of these reports and keep it on your desk in 
case something happen to your computer. 
IMPORTANT - DO NOT alter the names of the people who are listed next 
to each report, or their sequence on the list, in any way other than what is 
instructed below in step '' 1 through 6 '' or you will loose out on majority 
of your profits. Once you understand the way this works, you will also see 
how it does not work if you change it. Remember, this method has been 
tested, and if you alter, it will NOT work !!! People have tried to put their 
friends/relatives names on all five thinking they could get all the money. But 
it does not work this way. Believe us, we all have tried to be greedy and then 
nothing happened. So Do Not try to change anything other than what is 
instructed. Because if you do, it will not work for you. 
Remember, honesty reaps the reward!!! 
1.... After you have ordered all 5 reports, take this advertisement and 
REMOVE the name & address of the person in REPORT # 5. This person 
has made it through the cycle and is no doubt counting their fortune. 
2.... Move the name & address in REPORT # 4 down TO REPORT # 5. 
3.... Move the name & address in REPORT # 3 down TO REPORT # 4. 
4.... Move the name & address in REPORT # 2 down TO REPORT # 3. 
5.... Move the name & address in REPORT # 1 down TO REPORT # 2 
6.... Insert YOUR name & address in the REPORT # 1 Position. PLEASE MAKE 
SURE you copy every name & address ACCURATELY! 
========================================================== 
**** Take this entire letter, with the modified list of names, and save it on your 
computer. DO NOT MAKE ANY OTHER CHANGES. 
Save this on a disk as well just in case if you loose any data. To assist you with 
marketing your business on the internet, the 5 reports you purchase will provide 
you with invaluable marketing information which includes how to send bulk 
e-mails, where to find thousands of free classified ads and much more. 
There are 2 Primary methods to get this venture going: 
METHOD # 1: BY SENDING BULK E-MAIL 
========================================================== 
Let's say that you decide to start small, just to see how it goes, and we will 
assume You and those involved send out only 5,000 e-mails each. Let's 
also assume that the mailing receive only a 0.2% response (the response 
could be much better but lets just say it is only 0.2%. Also many people 
will send out hundreds of thousands e-mails instead of only 5,000 each). 
Continuing with this example, you send out only 5,000 e-mails. With a 0.2% 
response, that is only 10 orders for report # 1. Those 10 people responded 
by sending out 5,000 e-mail each for a total of 50,000. Out of those 50,000 
e-mails only 0.2% responded with orders. That's=100 people responded and 
ordered Report # 2. 
Those 100 people mail out 5,000 e-mails each for a total of 500,000 e-mails. 
The 0.2% response to that is 1000 orders for Report # 3. 
Those 1000 people send out 5,000 e-mails each for a total of 5 million e-mails 
sent out. The 0.2% response to that is 10,000 orders for Report # 4. 
Those 10,000 people send out 5,000 e-mails each for a total of 50,000,000 
(50 million) e-mails. The 0.2% response to that is 100,000 orders for Report 
# 5 THAT'S 100,000 ORDERS TIMES $5 EACH=$500,000.00 (half million). 
Your total income in this example is: 1..... $50 + 2..... $500 + 3..... $5,000 + 4 
... $50,000 + 5..... $500,000 ........ Grand Total=$555,550.00 
NUMBERS DO NOT LIE. GET A PENCIL & PAPER AND FIGUREOUT 
THE WORST POSSIBLE RESPONSES AND NO MATTER HOW YOU 
CALCULATE IT, YOU WILL STILL MAKE A LOT OF MONEY ! 
========================================================= 
REMEMBER FRIEND, THIS IS ASSUMING ONLY 10 PEOPLE 
ORDERING OUT OF 5,000 YOU MAILED TO. 
Dare to think for a moment what would happen if everyone or half or even 
one 4th of those people mailed 100,000e-mails each or more? There are 
over 150 million people on the Internet worldwide and counting. Believe me, 
many people will do just that, and more! 
METHOD # 2 : BY PLACING FREE ADS ON THE INTERNET 
======================================================= 
Advertising on the net is very very inexpensive and there are hundreds 
of FREE places to advertise. Placing a lot of free ads on the Internet will 
easily get a larger response. We strongly suggest you start with Method # 1 
and then METHOD # 2 as you go along. For every $5 you receive, all you 
must do is e-mail them the Report they ordered. That's it. Always provide 
same day service on all orders. 
This will guarantee that the e-mail they send out, with your name and 
address on it, will be prompt because they can not advertise until they 
receive the report. 
=========== AVAILABLE REPORTS ==================== 
ORDER EACH REPORT BY ITS NUMBER & NAME ONLY. Notes: 
Always send $5 cash (U.S. CURRENCY) for each Report. Checks NOT 
accepted. Make sure the cash is concealed by wrapping it in at least 2 sheets 
of paper. On one of those sheets of paper, Write the NUMBER & the NAME 
of the Report you are ordering, YOUR E-MAIL ADDRESS and your name 
and postal address. 
PLACE YOUR ORDER FOR THESE REPORTS NOW : 
==================================================== 
REPORT # 1: "The Insider's Guide to Advertising for Free on the Net" 
Order Report #1 from: 

JL Ross
163 Fisher Parade
Pakuranga, Auckland 1706
New Zealand
___________________________________________________________ 
REPORT # 2: "The Insider's Guide to Sending Bulk e-mail on the Net" 
Order Report # 2 from: 

S. R. 
212 Woodland Drive 
McMinnville, Tn 37110 
USA
____________________________________________________________ 
REPORT # 3: "Secret to Multilevel Marketing on the Net" 
Order Report # 3 from : 

Aaron Joseph 
PO Box 21155 
Columbia Heights, MN 55412 
USA

____________________________________________________________ 
REPORT # 4: "How to Become a Millionaire Utilizing MLM & the Net" 
Order Report # 4 from:

C.J. Kalata 
P.O.Box 130157 
Roseville, MN 55113-0002 
USA
____________________________________________________________ 
REPORT #5: "How to Send Out 0ne Million e-mails for Free" 
Order Report # 5 from: 

R.B. 
Box 21115 
Grande Prairie 
Alberta, T8V-6W7 
Canada
____________________________________________________________ 
$$$$$$$$$ YOUR SUCCESS GUIDELINES $$$$$$$$$$$ 
Follow these guidelines to guarantee your success: 
=== If you do not receive at least 10 orders for Report #1 within 2 
weeks, continue sending e-mails until you do. 
=== After you have received 10 orders, 2 to 3 weeks after that you 
should receive 100 orders or more for REPORT # 2. If you did not, 
continue advertising or sending e-mails until you do. 
=== Once you have received 100 or more orders for Report # 2, YOU 
CAN RELAX, because the system is already working for you, and the 
cash will continue to roll in ! THIS IS IMPORTANT TO REMEMBER: 
Every time your name is moved down on the list, you are placed in front 
of a Different report. 
You can KEEP TRACK of your PROGRESS by watching which report 
people are ordering from you. IF YOU WANT TO GENERATE MORE 
INCOME SEND ANOTHER BATCH OF E-MAILS AND START 
THE WHOLE PROCESS AGAIN. 
There is NO LIMIT to the income you can generate from this business !!! 
====================================================== 
FOLLOWING IS A NOTE FROM THE ORIGINATOR OF THIS 
PROGRAM: You have just received information that can give you 
financial freedom for the rest of your life, with NO RISK and JUST 
A LITTLE BIT OF EFFORT. You can make more money in the next 
few weeks and months than you have ever imagined. Follow the program 
EXACTLY AS INSTRUCTED. Do Not change it in any way. It works 
exceedingly well as it is now. 
Remember to e-mail a copy of this exciting report after you have put 
your name and address in Report #1 and moved others to #2 ...........# 5 
as instructed above. One of the people you send this to may send out 
100,000 or more e-mails and your name will be on every one of them. 
Remember though, the more you send out the more potential customers 
you will reach. 
So my friend, I have given you the ideas, information, materials and 
opportunity to become financially independent. IT IS UP TO YOU NOW ! 
============ MORE TESTIMONIALS ================ 
"My name is Mitchell. My wife, Jody and I live in Chicago. I am an 
accountant with a major U.S. Corporation and I make pretty good money. 
When I received this program I grumbled to Jodyaboutreceiving ''junk 
mail''. I made fun of the whole thing,spoutingmy knowledge of the population 
and percentages involved. I ''knew'' it wouldn't work. Jody totally ignored 
my supposed intelligence and few days later she jumped in with both feet. I 
made merciless fun of her, and was ready to lay the old ''I told you so'' on 
her when the thing didn't work. Well, the laugh was on me! Within 3 weeks 
she had received 50 responses. Within the next 45 days she had received 
total $ 147,200.00 ........... all cash! I was shocked. I have joined Jody 
in her ''hobby''. 
Mitchell Wolf M.D., Chicago, Illinois 
====================================================== 
''Not being the gambling type, it took me several weeks to make up my 
mind to participate in this plan. But conservative that I am, I decided that 
the initial investment was so little that there was just no way that I 
wouldn't get enough orders to at least get my money back''. '' I was 
surprised when I found my medium size post office box crammed with 
orders. I made $319,210.00in the first 12 weeks. The nice thing about 
this deal is that it does not matter where people live. There simply isn't a 
better investment with a faster return and so big." 
Dan Sondstrom, Alberta, Canada 
======================================================= 
''I had received this program before. I deleted it, but later I wondered 
if I should have given it a try. Of course, I had no idea who to contact to 
get another copy, so I had to wait until I was e-mailed again by someone 
else.........11 months passed then it luckily came again...... I did not 
delete this one! I made more than $490,000 on my first try and all the 
money came within 22 weeks." 
Susan De Suza, New York, N.Y. 
======================================================= 
''It really is a great opportunity to make relatively easy money with 
little cost to you. I followed the simple instructions carefully and 
within 10 days the money started to come in. My first month I made 
$20,560.00 and by the end of third month my total cash count was 
$362,840.00. Life is beautiful, Thanx to internet.". 
Fred Dellaca, Westport, New Zealand 
======================================================= 
ORDER YOUR REPORTS TODAY AND GET STARTED ON 
'YOUR' ROAD TO FINANCIAL FREEDOM ! 
======================================================= 
If you have any questions of the legality of this program, contact the 
Office of Associate Director for Marketing Practices, Federal Trade 
Commission, Bureau of Consumer Protection, Washington, D.C. 



 
 
 
 
 
 
 
 
 
 
 
 
 



From list@netscape.com  Fri Jan 12 18:17:04 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26787
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 18:17:03 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0CN0dG03097;
	Fri, 12 Jan 2001 15:00:39 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0CNEq211122;
	Fri, 12 Jan 2001 15:14:52 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 15:14:52 -0800 (PST)
Message-Id: <200101122314.f0CNEkq07609@xwing.netscape.com>
X-Sender: wind-n-sea@usa.net
From: Freesubmit Team <wind-n-sea@usa.net>
To: "Opportunity Seeker" <wind-n-sea@usa.net>
Date: Fri, 12 Jan 2001 17:14:45 -0600
Subject: FREE: Promote Your URL + Great Income Opportunity!
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Priority: 1
Resent-Message-ID: <"apZQuD.A.gtC.r_4X6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

IMPORTANT - FREE FOR A LIMITED TIME ONLY!

We all know the hassle of submitting forms and entering your
details countless of times to multiple search engines and FFA
sites just to get your URL listed. What if you could submit to all
those sites (7,304 sites to be exact), with just ONE submission?

With our software "Always Freesubmit", you can submit your
website's URL and ads to 1800+ search engines, FFA pages,
Classified Ad sites, plus popular business related directories on
the Net - a combined total of 7,304 unique locations, all for FREE!

Yes, that's right, FREE! - Always Freesubmit is currently available
for download FREE at our site at:

   http://softwarefree.terrashare.com

Hurry! Download it today as this FREE download may be removed at
any time in the future.

While you are at the site, please take a look at the other great
offers and FREE software that we have available for your
downloading pleasure.

EXTRA BONUS: Want to know about a great income opportunity? How
does a monthly residual income in excess of $10,000 sound? Now
that is definitely worth a look! More details at our site.

See you there!


The Freesubmit Team


0
NO SPAM POLICY:
We send our message to over 2,000 opt-in mailing lists,
customers, contacts and targetted prospects under the category
of Business, Business Opportunities, Network Marketing, MLM
and Home Business.

If we have reached you in error, we apologize. Please submit
your name and email at the "Remove" section at our site, and you
will be added to our remove database. We honor all remove requests
and do not sell or publish email addresses.




From list@netscape.com  Fri Jan 12 21:33:18 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28442
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 21:33:18 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0D2LDs21551;
	Fri, 12 Jan 2001 18:21:14 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0D2U8c00633;
	Fri, 12 Jan 2001 18:30:08 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 18:30:08 -0800 (PST)
Content-Type: text/plain;
	 charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Message-Id: <fc4y4sepa2siv8bv6d6k.sw0c6sekh65a6s62@mail.gr>
From: Paging29@digiweb.nl
Date: Sat, 13 Jan 2001 10:28:56 -0500
To: Thompson@essenet.it
Subject: We want to give you a Brand New Free 2-Way Motorola Pager ...
Resent-Message-ID: <"Zm0nl.A.cJ.u27X6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8BIT

FREE 2-Way Motorola PAGER           New 2-Way Motorola  pager for FREE!

No long term contract
No activation fee
No big prepayment of airtime
No credit check

PAGING AMERICA is going to give you absolutely Free the Brand new
2-Way Motorola pager. This top of the line pager will even
receive your 2-Way.  Included with your new pager is the technology
that allows you to respond to 2-Ways you receive.

Don't pass this offer up! Call 800-381-5922 TODAY while supplies last

Why pay $189.00 at a retail store when we're giving you this pager 
absolutely FREE.  Your new pager will come with its own e-mail
address so you can receive your e-mails as well as alpha-numeric
and numeric messages instantly where ever you are.

Your new two-way pager has features like 50,000 character memory, 
message time stamping, automatic garbled message correction, beeps
or vibrates, incandescent backlight, saved message folder, a unique
never out of range feature that allows your pager to retrieve
messages sent earlier when your pager was out of range or turned
completely off.  You can also receive weather, news and sports. 

This Motorola pager is small and light weight.  All we ask before
we'll ship you your new Free pager is for you to allow us to
provide some airtime for you. There is no long term contract or
credit check. Airtime is month to month and can be cancelled at
any time. 

This pager will come pre-programmed with its own e-mail address as 
well as a local telephone number to receive numeric pages. This
pager comes with a complete 30 day money back guarantee, if after
receiving this pager you're not completely happy, send it back and
receive a full refund.

For immediate delivery call Paging America at 800-381-5922

To be removed send email to abolishus@yahoo.com



From list@netscape.com  Fri Jan 12 22:12:51 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA29724
	for <ldapext-archive@odin.ietf.org>; Fri, 12 Jan 2001 22:12:51 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0D2uYG02834;
	Fri, 12 Jan 2001 18:56:34 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0D3Alo09686;
	Fri, 12 Jan 2001 19:10:47 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 19:10:47 -0800 (PST)
Date: Fri, 12 Jan 2001 19:10:13 -0800 (PST)
Message-Id: <200101130310.f0D3ABq27850@xwing.netscape.com>
From: Flat Rate Calling <usefulfreebies@VVIH.lycos.com>
To: @netscape.com
Subject:  The BEST Flat Rate Phone Calling!
X-Reply-To:  allfree@usefulfreebies.every1.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"CtK8Z.A.CXC.2c8X6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

TRULY Unlimited Flat Rate Phone Calling! 

* Quality Fiber Optic Lines NO VOIP 
* NO Contracts 
* Available 24/7/365 in 48 states 
* Faxing & Conference Calling Allowed 
* NO Distortion or Busy Signals 
* THE Best Service in America Today 

Stop wasting time and money on the pretenders...get the only REAL flat 
rate service that will be here for you now and always. 
Send a blank email for the details>>> 

mailto:usefulfreebies@lycos.com?subject=FLAT_RATE






From list@netscape.com  Sat Jan 13 02:43:48 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15656
	for <ldapext-archive@odin.ietf.org>; Sat, 13 Jan 2001 02:43:47 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0D7Wks13180;
	Fri, 12 Jan 2001 23:32:46 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0D7ffY00926;
	Fri, 12 Jan 2001 23:41:41 -0800 (PST)
Resent-Date: Fri, 12 Jan 2001 23:41:41 -0800 (PST)
From: mortgage@thegulls.co.uk
Message-Id: <200101130637.EAA26647@terax.teranet.com.br>
Subject: READY FOR A FINANCIAL CHANGE?
Date: Fri, 12 Jan 2001 23:18:15 -0700
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_221A_00003FB2.00002712"
X-Priority: 3
X-MSMail-Priority: Normal
Resent-Message-ID: <"l9mB2B.A.MO.0aAY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

------=_NextPart_000_221A_00003FB2.00002712
Content-Type: text/html;

<HTML>
<BODY>

<FONT face="MS Sans Serif">
<FONT size=2> Partners Wanted:<BR>
<BR>
With a minimum payment of $100.00<BR>
Without a social security number<BR>
Without a credit check<BR>
Develop a secondary  income of<BR>
$500 to $5,000 a day or more -- you decide!<BR>
Unlimited global market, unlimited income, all confidential<BR>
Eliminate your debts.<BR>
Secure your assets.<BR>
Retain All your hard earned money<BR>
And pass your wealth on to your heirs<BR>
The Super Rich have done this for years.....<BR>
Isn't it time YOU started?<BR>
<BR>
For Information Call: 1-800-336-4974<BR>
<BR>
Speak to the founders, ask any questions before you decide,<BR>
this offshore income plan clearly speaks for itself.<BR>
Great incentive for new partners.<BR>
<BR>
To be removed please reply to:<BR>
movemeplease19@looksmart.com.au<BR>
<BR>
</FONT></FONT><p><p><p><p><p><p><p><p><p><p>
<p><FONT face="MS Sans Serif"><p><FONT size=2> Partners Wanted:<BR><p><BR><p>With a minimum payment of $100.00<BR><p>Without a social security number<BR><p>Without a credit check<BR><p>Develop a secondary  income of<BR><p>$500 to $5,000 a day or more -- you decide!<BR><p><p><p><p></BODY></HTML>


------=_NextPart_000_221A_00003FB2.00002712--


From list@netscape.com  Sat Jan 13 05:37:12 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA16176
	for <ldapext-archive@odin.ietf.org>; Sat, 13 Jan 2001 05:37:12 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0DAQXs21764;
	Sat, 13 Jan 2001 02:26:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0DAZSA27504;
	Sat, 13 Jan 2001 02:35:28 -0800 (PST)
Resent-Date: Sat, 13 Jan 2001 02:35:28 -0800 (PST)
Date: Sat, 13 Jan 2001 02:35:11 -0800 (PST)
To: tatter44@jee.com
From: <carson@pixi.com>
Subject: 30% off ALL FRESH LEADS NETWORKERS DREAM!!
Reply-To: fkjdfgh@hjguh.net
X-PMFLAGS: 4578574854545.23
X-UIDL: 34384737846_7438644984.232
Comments: Authenticated Sender is <jhdfgs@aol.com>
Message-Id: 3487284784_fhdjhdfsg@hjjh.com
Resent-Message-ID: <"3nwYZB.A.WtG.u9CY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


ATTENTION!!! ATTENTION!!! ATTENTION!!!

HUGE NEW YEAR SALE ON FRESH LEADS!!! OVER 30% OFF ALL LEADS! PRICES ARE ONLY GOOD THROUGH 1-20-01. WE SELL LEADS SPECIFIC TO YOUR OPPORTUNITY, THEY ARE ALL EXPERIENCED NETWORKERS, AND ALL COLLECTED FRESH WITHIN 14 DAYS!

MAKE IT HAPPEN!!!
CLICK ON THE LINK BELOW!!!

http://www.geocities.com/freshleads777/redirect3.htm



From list@netscape.com  Sat Jan 13 06:15:20 2001
Received: from netscape.com ([205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA16359
	for <ldapext-archive@odin.ietf.org>; Sat, 13 Jan 2001 06:15:20 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0DAxBG00561;
	Sat, 13 Jan 2001 02:59:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0DBDPw04002;
	Sat, 13 Jan 2001 03:13:25 -0800 (PST)
Resent-Date: Sat, 13 Jan 2001 03:13:25 -0800 (PST)
To: millbiz@aol.com
Message-Id: <199912112040.MAA94626@addr6.addr.com>
Date: Sat, 13 Jan 01 00:15:43 EST
From: smartbiz_2001@icrazy.com
Subject: Make Money While You SLEEP!
Resent-Message-ID: <"xdQ5e.A.59.ThDY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Dear Friend,

Perhaps this might be of interest to you.
If not, please disregard.

I thought I'd drop this one time quick note to let you know about an
EXCELLENT e-Commerce business which has enjoyed rapid and
consistent growth in the last 4 years. It may fit very well into your
business portfolio.

This is the EASIEST and the BEST on-line business today, virtually
a SELF-RUN ONLINE BUSINESS. It's TWICE voted as the #1 on-line
business.

*Christian, of Marion, OH. writes:

"I'm having 10 times the success with this business as
I did with my other MLMs that I tried. I have a personal closure
rate of about 80%. And I attribute that totally to the system that
you have created. It truly is the best company out there. Since
joining in August of this year, I have been approached by 3
distributors of other companies, including 1 co-founder, but
after explaining what I do in my business and how I work the
opportunity, I guess they've given up knowing that their program
is much harder to achieve success in."

If your current program demands that you sell products and
sponsor others you will fail 90% of the time! Put yourself in the
power position; win 90% of the time offering a program that
everyone wants to be involved with!

Simply click below to examine our award-winning web site:

http://www.cyberturf.com/businessopp/index.html

You will be glad you did!

In the event you get a 404 URL error at the above website, 
PLEASE send an email to smartbiz_2001@gtemail.net with MORE INFO
as the subject line.  I will add your name to our autoresponder and
your info will be on its way. 

With My Warmest Regards,
Bob
<A HREF="http://www.cyberturf.com/businessopp/index.html">Click Here</A>


I have purchased your e-mail in a bulk list as someone interested in 
Internet Business Opportunities. If I received your e-mail in error, or you are no
longer interested, click here to be removed. Be sure REMOVE is in
the Subject Title and you will not be contacted again:
mailto:businessopp80@n2.com?subject=Remove

Please understand that any effort to disrupt, close or block the REMOVE account
can only result in difficulties for others wanting to be removed from our
mailing list.

****************************************************************
Under Bill s.1618 TITLE III passed by the 105th US Congress this 
letter cannot be considered spam as long as the sender includes 
contact information and a method of removal. 
****************************************************************



From list@netscape.com  Sat Jan 13 15:59:34 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20079
	for <ldapext-archive@odin.ietf.org>; Sat, 13 Jan 2001 15:59:33 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0DKjGs19881;
	Sat, 13 Jan 2001 12:45:16 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0DKsDw04717;
	Sat, 13 Jan 2001 12:54:13 -0800 (PST)
Resent-Date: Sat, 13 Jan 2001 12:54:13 -0800 (PST)
Message-Id: <200101132054.f0DKs9q17081@xwing.netscape.com>
X-Sent: 13 Jan 2001 20:53:33 GMT
From: <exp121300@yahoo.com>
Subject: New Targeted E-Mail List TODAY!
Date: Sat, 13 Jan 2001 11:16:24
Resent-Message-ID: <"jvsfGC.A.bJB.0BMY6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

  *******New List TODAY!!******** 

                          
Visit the site for more details!
http://www.megspace.com/business/xyzlist

The key to success in marketing online is reaching the people who 
are really interested in your ad! 

You need targeted e-mails of business opportunity seekers
who are ACTIVELY marketing online and trying to expand their
business TODAY!

-->   Highly Deliverable Lists!
  Our lists are cleaned and updated on a daily basis! Which means 
we have the lowest undeliverable rate out there!  We've also made 
sure to filter out all those unwanted e-mail address such as 
mil, .org, .org, .gov, etc.
                          


Visit the site for more details!
http://www.megspace.com/business/xyzlist

 10,000 opportunity seekers e-mails for only $10
**New List TODAY**
 25,000 opportunity seekers e-mails for only $20
 50,000 opportunity seekers e-mails for only $35
100,000 opportunity seekers e-mails for only $50
250,000 opportunity seekers e-mails for only $70

- Promotions!

**FREE with EVERY order, demo of ListMan e-mail manager software 
to manage your e-mails list, Free and Easy Credit Tips, and 
Insider Secrets: Creating Profitable Classified Ads

**Order 50,000 or more e-mails and receive Express Mail Server to 
send your e-mails FREE!  
-Send your e-mails safely bypassing your ISP's mail server!
-This is not a demo but a permanent license for the software!
-FREE Net Detective

**Order 100,000 or more e-mails and receive:

- InfoDisk  with 1000+ Money Making Reports
- URL cloaking software
- CheckMAN software
Combined value of over $250!  Yours FREE!
_______________________________________________________________
I received your e-mail as someone interested in Internet Business 
Opportunities. If I received your e-mail in error, or you are no 
longer interested, you can be removed at no cost to you simply by 
pressing "Reply" and place "Remove" in the Subject line.
_________________________________________________________________
 
 
 
 
 
 
 
 
 



From list@netscape.com  Sun Jan 14 01:48:58 2001
Received: from netscape.com ([205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA00117
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 01:48:58 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0E6WaG22765;
	Sat, 13 Jan 2001 22:32:36 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0E6kpA05898;
	Sat, 13 Jan 2001 22:46:51 -0800 (PST)
Resent-Date: Sat, 13 Jan 2001 22:46:51 -0800 (PST)
Date: Mon, 15 Jan 2001 08:29:04 +0200
From: bm21@prodigy.com
Message-Id: <200101150629.IAA11724@mail.capemohair.co.za>
To: bm21@prodigy.com
Subject: IS YOUR WEB SITE MAKING MONEY?
Resent-Message-ID: <"48fWhD.A.4bB.ZtUY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


Is Your Web Site Making Money?

Now more then ever, e-commerce is becoming a way of life.
Every day millions of people are logging on to the web to
conduct business, purchase products and hire services.  Many
merchants have already established their online presence
with the capability of accepting credit cards to accommodate
their growing marketplace where everything one can imagine
is right at the consumer's fingertips.   Is your Web Site
Ready?

Retail Rates as low as 1.5% and $0.20 per Transaction! Mail
Order and Internet Rates as low as 2.25% and $0.20 per
Transaction! No Application Fee! No Set Up Fee! 99% Approval
Guaranteed Shopping Carts available fully integrated with
the payment gateway

Discover how easy, flexible and affordable online payments
can be

EASY- See how Harbor-net's payment gateway plugs seamlessly
into your web site

FLEXIBLE - From simple products such as the web terminal and
shopping carts to building your complete online store

AFFORDABLE - Prices set for businesses of all sizes

Click here and see how you can start making money today!

Fax: 877-582-2128 Tel:  800-728-4445




From list@netscape.com  Sun Jan 14 10:26:35 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA08908
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 10:26:34 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0EFFEs10650;
	Sun, 14 Jan 2001 07:15:23 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0EFOCw24099;
	Sun, 14 Jan 2001 07:24:12 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 07:24:12 -0800 (PST)
Date: Sun, 14 Jan 2001 07:24:05 -0800 (PST)
Message-Id: <200101141524.f0EFO4q05115@xwing.netscape.com>
From: opportunity@bacpari.com.br.netscape.com
To: @netscape.com
Subject:  The best opportunity this year!
X-Reply-To:  lixo12@usa.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"talDK.A.R4F.bScY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit


It is Amazing ... and FREE!
During the last October we sponsored 114,402 new distributors in 131
countries worldwide. Today, we have over 800,000 affiliates in
193 countries.(And
we have only scratched the surface! - According The New York Times there 
are
332 millions people conected worldwide.)
EVEN MORE AMAZING:
These unprecedented numbers came without mailing a single brochure, 
audio, or
videotape. Not a single long-distance phone call was made...or fax sent. 
We
did it 100% via the Internet . Network Marketing on the Web has arrived! 
Want
to know more? You can test drive the system FREE!
Just click on this link then watch the magic. 


http://clicktosurf.to/biz8


*************************************************************************
*************************************************************************
**
This message is sent in compliance of the proposed bill: SECTION 301. Per 
Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you 
by the sender of this email may be stopped at no cost to you by sending a 
reply to this email address with the word remove in the subject line. 
*************************************************************************
*************************************************************************
**







From list@netscape.com  Sun Jan 14 13:25:57 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09744
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 13:25:57 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0EIEqs20014;
	Sun, 14 Jan 2001 10:14:52 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0EINnU23265;
	Sun, 14 Jan 2001 10:23:49 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 10:23:49 -0800 (PST)
From: <casdckas@bb.sanet.sk>
To: <ietf-ldapext@netscape.com>
Date: Sun, 14 Jan 2001 09:37:22
Message-Id: <479.390212.718269@mail.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"n31DvB.A.PrF.06eY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

GET YOUR OWN 150 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY!

STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN 
GET ONE FOR ONLY $11.95 PER MONTH!

DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE 
DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO 
GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A 
SIMPLE PHONE CALL TO  OUR OFFICE.

YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with 
no extra charge!  UNLIMITED TRAFFIC -- no extra charge!

FRONT PAGE EXTENSIONS are FULLY SUPPORTED.

A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS.

ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP 
CHARGE.

FOR DETAILS CALL 1 888 248 0765  if you are outside the USA,
please fax 240 337 8325

Webhosting International

 
 
 
 
 
 
 
 
 
 
 



From list@netscape.com  Sun Jan 14 15:28:26 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10480
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 15:28:25 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0EKC3G02741;
	Sun, 14 Jan 2001 12:12:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0EKQK614317;
	Sun, 14 Jan 2001 12:26:20 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 12:26:20 -0800 (PST)
Date: Sun, 14 Jan 2001 12:26:15 -0800 (PST)
Message-Id: <200101142026.f0EKQEq20736@xwing.netscape.com>
From: <andkais77@gmx.net>
To: andkais77@gmx.net
Subject: News
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Message-ID: <"5JwTSC.A.bfD.rtgY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id f0EKC3G02741
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA10480


Hi Kalle! 
Mal wieder ein paar Surftips für Dich. 
Also wenn Du mich fragst die besten Maedels, 20 Studios mit Livebild und Chat im Netz 
findest Du unter 
http://www.lifegirl.de oder http://www.ero-channel.de oder http://www.stripline.de
die beste Singleseite ist 
http://www.zweiherzen.de 
die verliebtesten Lesben sind unter
http://www.lesbenhaus.de zu finden.

Also Kalle nix wie hin. 
PS: Kannst mir ja nächsten Freitag von deinen tollen Erfahrungen berichten.

  
---------------------------------------------------------------
unregistrierte Demoversion  
http://www.aquadrat.de/download/psmail.htm
Referenz zu http://www.stripline.de
Referenz zu http://www.selfproducer.de
co. 2000
---------------------------------------------------------------



From list@netscape.com  Sun Jan 14 17:10:54 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10867
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 17:10:54 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ELsVG07950;
	Sun, 14 Jan 2001 13:54:31 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0EM8m202032;
	Sun, 14 Jan 2001 14:08:48 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 14:08:48 -0800 (PST)
Date: Sun, 14 Jan 2001 14:08:42 -0800 (PST)
Message-Id: <200101142208.f0EM8gq20594@xwing.netscape.com>
From: <andkais77@gmx.net>
To: andkais77@gmx.net
Subject: News
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Message-ID: <"EXjDVB.A.ef.vNiY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id f0ELsVG07950
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA10867


Hi Kalle! 
Mal wieder ein paar Surftips für Dich. 
Also wenn Du mich fragst die besten Maedels, 20 Studios mit Livebild und Chat im Netz 
findest Du unter 
http://www.lifegirl.de oder http://www.ero-channel.de oder http://www.stripline.de
die beste Singleseite ist 
http://www.zweiherzen.de 
die verliebtesten Lesben sind unter
http://www.lesbenhaus.de zu finden.

Also Kalle nix wie hin. 
PS: Kannst mir ja nächsten Freitag von deinen tollen Erfahrungen berichten.

  
---------------------------------------------------------------
unregistrierte Demoversion  
http://www.aquadrat.de/download/psmail.htm
Referenz zu http://www.stripline.de
Referenz zu http://www.selfproducer.de
co. 2000
---------------------------------------------------------------



From list@netscape.com  Sun Jan 14 18:20:05 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11083
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 18:20:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0EN41G11600;
	Sun, 14 Jan 2001 15:04:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0ENIJ613663;
	Sun, 14 Jan 2001 15:18:19 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 15:18:19 -0800 (PST)
Date: Sun, 14 Jan 2001 15:18:14 -0800 (PST)
Message-Id: <200101142318.f0ENIE505106@ywing.netscape.com>
From: <andkais77@gmx.net>
To: andkais77@gmx.net
Subject: Newslettet
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Message-ID: <"TFc7O.A.KVD.6OjY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id f0EN41G11600
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA11083


Hi Kalle! 
Mal wieder ein paar Surftips für Dich. 
Also wenn Du mich fragst die besten Maedels, 20 Studios mit Livebild und Chat im Netz 
findest Du unter 
http://www.lifegirl.de oder
http://www.ero-channel.de oder 
http://www.stripline.de

die beste Singleseite ist 
http://www.zweiherzen.de 

die verliebtesten Lesben sind unter
http://www.lesbenhaus.de zu finden.

Also Kalle nix wie hin. 
PS: Kannst mir ja nächsten Freitag von deinen tollen Erfahrungen berichten.
  
---------------------------------------------------------------
unregistrierte Demoversion  
http://www.aquadrat.de/download/psmail.htm
Referenz zu http://www.stripline.de
Referenz zu http://www.selfproducer.de
co. 2000
---------------------------------------------------------------



From list@netscape.com  Sun Jan 14 19:20:39 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA11437
	for <ldapext-archive@odin.ietf.org>; Sun, 14 Jan 2001 19:20:38 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0F04iG14724;
	Sun, 14 Jan 2001 16:04:44 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0F0J1k23874;
	Sun, 14 Jan 2001 16:19:01 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 16:19:01 -0800 (PST)
Date: Sun, 14 Jan 2001 16:18:54 -0800 (PST)
Message-Id: <200101150018.f0F0Isq26773@xwing.netscape.com>
From: <andkais77@gmx.net>
To: andkais77@gmx.net
Subject: News
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Message-ID: <"AfvQsB.A.n0F.yHkY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id f0F04iG14724
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA11437


Hi Kalle! 
Mal wieder ein paar Surftips für Dich. 
Also wenn Du mich fragst die besten Maedels, 20 Studios mit Livebild und Chat im Netz 
findest Du unter 
http://www.lifegirl.de oder
http://www.ero-channel.de oder 
http://www.stripline.de

die beste Singleseite ist 
http://www.zweiherzen.de 

die verliebtesten Lesben sind unter
http://www.lesbenhaus.de zu finden.

Also Kalle nix wie hin. 
PS: Kannst mir ja nächsten Freitag von deinen tollen Erfahrungen berichten.
  
---------------------------------------------------------------
unregistrierte Demoversion  
http://www.aquadrat.de/download/psmail.htm
Referenz zu http://www.stripline.de
Referenz zu http://www.selfproducer.de
co. 2000
---------------------------------------------------------------



From list@netscape.com  Mon Jan 15 00:41:06 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA15528
	for <ldapext-archive@odin.ietf.org>; Mon, 15 Jan 2001 00:41:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0F5UMs26795;
	Sun, 14 Jan 2001 21:30:23 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0F5dKI17861;
	Sun, 14 Jan 2001 21:39:20 -0800 (PST)
Resent-Date: Sun, 14 Jan 2001 21:39:20 -0800 (PST)
Date: Sun, 14 Jan 2001 21:39:11 -0800 (PST)
Message-Id: <200101150539.f0F5dAq20903@xwing.netscape.com>
From: zoran@australink.net
To: @netscape.com
Subject:  Y.E.S.
X-Reply-To:  zoran@australink.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"X-mR9.A.xWE.H0oY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

HELLO THERE.
I am Zoran and I would like to introduce this brand spanking NEW bizop. My Wife Huang Jian and Myself 
with help of some of the best programers in the field, have just completed the FIRST in the World Global 
2x2 Matrix. It is multiphase and multi entry, therefore UNLIMITED income. Fast return on investment. Please 
check it out on http://globalws.net/show.cgi/zoran
We need help in launching it. Today is 15 of Jan. and we started it on the first. We have 60 people some in 
USA, some in Australia, Sudan Denmark and Philippines.
Either way, please respond with either criticism or praise. 
I am your new friend from Aussieland
Zoran

 And here is the one for the road:
 Knock knock
 Who is there?
 Opportunity...
 impossible- Opportunity knocks only once.

 And I am Zoran, Your new friend from Aussieland
http://globalws.net/show.cgi/zoran
http://australink.net




From list@netscape.com  Mon Jan 15 03:43:52 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA29672
	for <ldapext-archive@odin.ietf.org>; Mon, 15 Jan 2001 03:43:51 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0F8XFs07749;
	Mon, 15 Jan 2001 00:33:15 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0F8gDg18545;
	Mon, 15 Jan 2001 00:42:13 -0800 (PST)
Resent-Date: Mon, 15 Jan 2001 00:42:13 -0800 (PST)
Date: Mon, 15 Jan 2001 00:41:19 -0800 (PST)
Message-Id: <200101150841.f0F8fD517116@ywing.netscape.com>
From: happy@newyear.com.tw.netscape.com
To: only@for.you.com
Subject: =?big5?Q?=AF=AC=B1z -- =B7s=A6~=A7=D6=BC=D6?=
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_J155r11cJ4CwD8ndixosJQ"
X-Mailer: Microsoft Outlook Express 5.50.4133.2499
X-Priority: 3
X-MSMail-Priority: Normal
Resent-Message-ID: <"YQdPZB.A.RhE.jfrY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multi-part message in MIME format.

------=_NextPart_J155r11cJ4CwD8ndixosJQ
Content-Type: multipart/alternative;
	boundary="----=_NextPart_J155r11cJ4CwD8ndixosJQAA"


------=_NextPart_J155r11cJ4CwD8ndixosJQAA
Content-Type: text/plain;
Content-Transfer-Encoding: base64

UGxlYXNlIFJlYWQgSFRNTCBNZXNzYWdlICEhIQ==


------=_NextPart_J155r11cJ4CwD8ndixosJQAA
Content-Type: text/html;
	charset="big5"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT48L3RpdGxlPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVu
dC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9YmlnNSI+DQo8c3R5bGUgdHlwZT0i
dGV4dC9jc3MiPg0KPCEtLQ0KLmZoMTUgeyAgbGluZS1oZWlnaHQ6IDE1MCV9DQotLT4NCjwvc3R5
bGU+DQo8L2hlYWQ+DQoNCjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPg0KPGNlbnRlcj4NCiAgPGZv
bnQgY29sb3I9IiNGRjAwMDAiIHNpemU9IjYiPjxiPq+sILF6ILdzIKZ+IKfWILzWPC9iPjwvZm9u
dD48YnI+DQogIDxicj4NCiAgPGEgaHJlZj0iaHR0cDovL2dvbW9zLnN1bnVwLm5ldCIgdGFyZ2V0
PSJfYmxhbmsiPjxpbWcgc3JjPSJodHRwOi8vZ29tb3Muc3VudXAubmV0LzAwbWwvcGM4MDYvUGM4
MDYuanBnIiB3aWR0aD0iNTAwIiBoZWlnaHQ9IjQwMCIgYm9yZGVyPSIwIj48L2E+IA0KICA8YnI+
DQogIDxociBzaXplPSIxIj4NCiAgPHRhYmxlIHdpZHRoPSI1MzEiIGJvcmRlcj0iMSIgY2VsbHNw
YWNpbmc9IjAiIGNlbGxwYWRkaW5nPSI1IiBib3JkZXJjb2xvcmxpZ2h0PSIjMDAwMDAwIiBib3Jk
ZXJjb2xvcmRhcms9IiNGRkZGRkYiIGJnY29sb3I9IiNDQ0NDRkYiPg0KICAgIDx0cj4NCiAgICAg
IDx0ZCBjbGFzcz0iZmgxNSI+PGI+VmV2b3ggs7uvxblxuKOu4KX+qHSmQ7DTq348L2I+PGJyPg0K
ICAgICAgICA8aHIgc2l6ZT0iMSI+DQogICAgICAgIKR1vHSqvcDnIC4gr1O7+aflsOIgLiCmyrNm
pL2lcbFNwmSwqq/Fq34gLiA8Zm9udCBjb2xvcj0iI0ZGRkZGRiI+PGI+pf6tsSA1MCUgpK2n6a9T
veY8L2I+PC9mb250Pjxicj4NCiAgICAgICAgsXqv4KdRpc6zb63Tvve3fLZSqOyqq7ZXqdKtyKq6
wHW96LDTq36hQbCqtq6kaqTooUG7+a3IpKOkWjxicj4NCiAgICAgICAgPGEgaHJlZj0iaHR0cDov
L2dvbW9zLnN1bnVwLm5ldCIgdGFyZ2V0PSJfYmxhbmsiPkdPTU9TIMHKvK+lq6Rqs2OpsTwvYT4g
PGZvbnQgY29sb3I9IiNGRkZGRkYiPmh0dHA6Ly9nb21vcy5zdW51cC5uZXQ8L2ZvbnQ+PC90ZD4N
CiAgICA8L3RyPg0KICA8L3RhYmxlPg0KICA8YnI+DQogIDxicj4NCiAgPGJyPg0KPC9jZW50ZXI+
DQo8L2JvZHk+DQo8L2h0bWw+IA==


------=_NextPart_J155r11cJ4CwD8ndixosJQAA--
------=_NextPart_J155r11cJ4CwD8ndixosJQ--





From list@netscape.com  Mon Jan 15 04:10:44 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA29850
	for <ldapext-archive@odin.ietf.org>; Mon, 15 Jan 2001 04:10:43 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0F8sJG13734;
	Mon, 15 Jan 2001 00:54:19 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0F98bE24082;
	Mon, 15 Jan 2001 01:08:37 -0800 (PST)
Resent-Date: Mon, 15 Jan 2001 01:08:37 -0800 (PST)
Date: Mon, 15 Jan 2001 01:08:18 -0800 (PST)
Message-Id: <200101150908.f0F98H522651@ywing.netscape.com>
From: capnetn@ARHO.netscape.net
To: ietf-ldapext@UODH.netscape.com
Subject:  How To Get Out Of Debt FAST, While Saving Thousands! -TQMA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"dgbTcD.A.A4F.T4rY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Friends,

If you have received this message in error,
please excuse the intrusion and reply remove.

How To Get Out Of Debt And Past Off Loans FASTER,
While Saving Thousands In Interest!
*Mortgages
*Equity Loans
*Boat Loans
*RV Loans
*Student Loans
*Credit Cards
*Unclaimed Funds
*Capital Search
*Gov Contracts
*Business Plans
ANY LOAN!

Request Your FREE Computer Loans Analysis!

http://www.debtfreeusa.net/credit

reup@usmr.net

9179719856@mobile.att.net

http://www.affiliate.bigstep.com




From list@netscape.com  Mon Jan 15 08:24:39 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA04136
	for <ldapext-archive@odin.ietf.org>; Mon, 15 Jan 2001 08:24:38 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0FD8AG00291;
	Mon, 15 Jan 2001 05:08:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0FDMTY17090;
	Mon, 15 Jan 2001 05:22:29 -0800 (PST)
Resent-Date: Mon, 15 Jan 2001 05:22:29 -0800 (PST)
From: <dasldsal@axil.eureka.lk>
To: <ietf-ldapext@netscape.com>
Date: Mon, 15 Jan 2001 04:35:27
Message-Id: <276.43712.531931@mail.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"afdNAB.A.wKE.UmvY6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

GET YOUR OWN 150 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY!

STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN 
GET ONE FOR ONLY $11.95 PER MONTH!

DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE 
DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO 
GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A 
SIMPLE PHONE CALL TO  OUR OFFICE.

YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with 
no extra charge!  UNLIMITED TRAFFIC -- no extra charge!

FRONT PAGE EXTENSIONS are FULLY SUPPORTED.

A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS.

ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP 
CHARGE.

FOR DETAILS CALL 1 888 248 0765  if you are outside the USA,
please fax 240 337 8325

Webhosting International

 
 
 
 
 
 



From list@netscape.com  Tue Jan 16 01:23:52 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA25619
	for <ldapext-archive@odin.ietf.org>; Tue, 16 Jan 2001 01:23:51 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0G67qG14091;
	Mon, 15 Jan 2001 22:07:52 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0G6MBs20914;
	Mon, 15 Jan 2001 22:22:11 -0800 (PST)
Resent-Date: Mon, 15 Jan 2001 22:22:11 -0800 (PST)
Date: Mon, 15 Jan 2001 22:22:08 -0800 (PST)
Message-Id: <200101160622.f0G6M8516532@ywing.netscape.com>
From: cashgenerator2002@yahoo.com
To: @netscape.com
Subject:  CLEARLY SEE YOUR FUTURE!
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"Z9v0LC.A.gGF.Si-Y6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

<HTML><BODY>

<P><FONT FACE = "Arial" COLOR = "#000000" SIZE = "2">JOURNEY WITHIN!
<P>Relive your past through Regression Viewing.
<P>Clearly see your future through Progression Viewing.
<P>For complete details, email &lta href="mailto:cashgenerator2002@yahoo.com&gtcashgenerator2002@yahoo.com&lt/a&gt.
<P>Please type "Journey Within" on subject line.
</BODY></HTML>



From list@netscape.com  Tue Jan 16 07:27:16 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA08875
	for <ldapext-archive@odin.ietf.org>; Tue, 16 Jan 2001 07:27:15 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0GCEjs13756;
	Tue, 16 Jan 2001 04:14:45 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0GCNiI27532;
	Tue, 16 Jan 2001 04:23:44 -0800 (PST)
Resent-Date: Tue, 16 Jan 2001 04:23:44 -0800 (PST)
To: <ietf-ldapext@netscape.com>
From: <cashbyfax22222@aol.com>
Subject: cash by fax info
Message-Id: <200101161941625.SM00185@fdfs908092sdf>
Date: Tue, 16 Jan 2001 19:42:38 +0800
Resent-Message-ID: <"bQukGD.A.6tG.P1DZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


THIS IS THE NEW LINK.  TYPO IN THE LAST ONE.

http://www.geocities.com/cashbyfax22222/newest.html



From list@netscape.com  Tue Jan 16 21:12:07 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25142
	for <ldapext-archive@odin.ietf.org>; Tue, 16 Jan 2001 21:12:07 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0H26Qs15769;
	Tue, 16 Jan 2001 18:06:26 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0H26RQ05955;
	Tue, 16 Jan 2001 18:06:27 -0800 (PST)
Resent-Date: Tue, 16 Jan 2001 18:06:27 -0800 (PST)
From: BMJHT@aol.com
Message-ID: <7f.ee1e5e7.279657ea@aol.com>
Date: Tue, 16 Jan 2001 21:05:30 EST
Subject: MPS Router's by Motorola 6520
To: ietf-ldapext@netscape.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 127
Resent-Message-ID: <"Qf7WW.A.xcB.i4PZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Is there any interest in these routers for resale?  I am curious as to how to 
get information on them? Thank you if you can help, thank you if you can't. 
Bruce Terwilliger



From list@netscape.com  Wed Jan 17 03:11:21 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA14536
	for <ldapext-archive@odin.ietf.org>; Wed, 17 Jan 2001 03:11:21 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0H88Bs21552;
	Wed, 17 Jan 2001 00:08:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0H88Cc01779;
	Wed, 17 Jan 2001 00:08:12 -0800 (PST)
Resent-Date: Wed, 17 Jan 2001 00:08:12 -0800 (PST)
Date: Wed, 17 Jan 2001 00:08:08 -0800 (PST)
Message-Id: <200101170808.f0H888Z22433@xwing.netscape.com>
From: cashgenerator2002@yahoo.com
To: @netscape.com
Subject:  CLEARLY SEE YOUR FUTURE!
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"Kp00FD.A.Rb.rLVZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

<HTML><BODY>

<P><FONT FACE = "Arial" COLOR = "#000000" SIZE = "2">JOURNEY WITHIN!
<P>Relive your past through Regression Viewing.
<P>Clearly see your future through Progression Viewing.
<P>For complete details, email &lta href="mailto:cashgenerator2002@yahoo.com&gtcashgenerator2002@yahoo.com&lt/a&gt.
<P>Please type "Journey Within" on subject line.
</BODY></HTML>



From list@netscape.com  Wed Jan 17 08:56:40 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA17718
	for <ldapext-archive@odin.ietf.org>; Wed, 17 Jan 2001 08:56:39 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0HDsJG16549;
	Wed, 17 Jan 2001 05:54:19 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0HDsJ612937;
	Wed, 17 Jan 2001 05:54:19 -0800 (PST)
Resent-Date: Wed, 17 Jan 2001 05:54:19 -0800 (PST)
Date: Wed, 17 Jan 2001 05:53:45 -0800 (PST)
Message-Id: <200101171353.f0HDri507035@ywing.netscape.com>
From: akuac@KPXE.yahoo.com
To: .WRKV@netscape.com
Subject:  GOLDEN OPPORTUNITY! OWN A HOUSE & CAR WITH AS LITTLE AS $100-00 -PFPK
X-Reply-To:  pingingw@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"CbWBcC.A.3JD.KQaZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello!
Thanks for your interest. You have the opportunity to be on the ground floor of this brand new MLM 
company. There are only less than 100 member in the group and it's multiplying very quickly. Hurry up! 
Secure your position today. You will be amazed by the way this plan works for you. Once you success, 
you're subject to rertirement. PLEASE VISIT   http://www.globalws.net/show.cgi/piwong
FOR MORE DETAILS.

Thank you, for your time. Good luck.



Best regards,

Steve

If this message gets to you in error please send us an e-mail with the subject
"remove" on it.

mailto:pingingw@yahoo.com





From list@netscape.com  Wed Jan 17 12:57:00 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22994
	for <ldapext-archive@odin.ietf.org>; Wed, 17 Jan 2001 12:57:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0HHt6s25171;
	Wed, 17 Jan 2001 09:55:06 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0HHt5s05169;
	Wed, 17 Jan 2001 09:55:05 -0800 (PST)
Resent-Date: Wed, 17 Jan 2001 09:55:05 -0800 (PST)
Content-return: allowed
Date: Wed, 17 Jan 2001 12:54:42 -0500
From: "Slone, Skip" <skip.slone@lmco.com>
Subject: LDAP/X.500 Alignment
To: "LDAPExt Mailing List (E-mail)" <ietf-ldapext@netscape.com>
Message-id: <B23207A86E7BD411A7000008C7E6693C77F919@emss03m03.orl.lmco.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Resent-Message-ID: <"kkPNeC.A.SQB.4xdZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7BIT

At the San Diego meeting, a new X.500-initiated work item on "maximizing
alignment between LDAP and X.500" was briefly introduced to the ldapext WG.
The philosophy behind this work is one of removing barriers  -- barriers to
LDAP/X.500 interoperability, and barriers to implemention resulting from
X.500's OSI legacy.  The goal of this work is to combine the collective
talents of LDAP and X.500 experts in a way that facilitates the development
of directory solutions that are both compelling and pragmatic. 

The document describing this work can be found at
ftp://ftp.bull.com/pub/OSIdirectory/Orlando2000Output/LDAPalignmentWD.pdf. 

The document contains about four pages of real content, and the major
section headers are as follows:
  - General Philosophy
  - Removal of Barriers
  - Distributed Operations
  - Related Entries
  - Name Resolution
  - Protocol / Presentation Interoperability
  - Schema
  - Replication and Metadirectory
  - Security
  - New Functionality

I will be attending the X.500 group's upcoming meeting the week of January
29, and would welcome the perspective of members of this group. I invite
interested parties to take a look at this document and to share your
thoughts with me during the time remaining before the X.500 meeting. I also
plan to attend the IETF meeting in Minneapolis, where I should be available
to discuss the latest developments from the X.500 group's perspective. 

Because the topic list covers a wide range, the resulting work is likely to
span multiple LDAP-related WGs. Accordingly, I am sending this initial
message to several WG lists. However, to minimize cross-postings, I am
sending the initial message separately to each of the various lists in hope
that any ensuing discussions can be contained within the relevant group.

Thanks,

 -- Skip Slone



From list@netscape.com  Wed Jan 17 19:09:54 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29340
	for <ldapext-archive@odin.ietf.org>; Wed, 17 Jan 2001 19:09:53 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0I07hG01123;
	Wed, 17 Jan 2001 16:07:43 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0I07hY14742;
	Wed, 17 Jan 2001 16:07:43 -0800 (PST)
Resent-Date: Wed, 17 Jan 2001 16:07:43 -0800 (PST)
Date: Wed, 17 Jan 2001 16:07:41 -0800 (PST)
Message-Id: <200101180007.f0I07eZ00103@xwing.netscape.com>
From: jltkb@msn.com
To: ntthq@MyFriend.netscape.com
Reply-To: t2m3@bigfoot.com
Subject: INCREDIBLE Cash Flow!                                    [sctjh]
Resent-Message-ID: <"HOmAR.A.EmD.OPjZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

MAKE $30,000 IN THE NEXT 40 TO 60 DAYS!

Sell our Idea to 3 People... Who Sell 3 People...
Then they follow you through our revolutionary
Wealth Generating System Making More Money Faster
and Easier than you ever dreamed possible!

To start your incredible chain reaction through
our program, all you have to do is just find
3 people who want to make lots of money,

NOT buy lots of products!

When your 3 enter the  Program you've already earned
your first $1,000 AND it’s just the beginning! Next
you're on your way to $5500 check from the SAME three
people...and it's all AUTOMATIC, now!

AND...IT'S STILL JUST THE BEGINNING!

NOW, you are MOVING!  Your LIFE IS REALLY CHANGING, NOW!

Your three people are now making you checks of $5000
and $10,000 AND THERE'S STILL SO MUCH MORE! I could go
ON AND ON...it's SO exciting! But, just to keep it
simple, let me put it this way...

EACH AND EVERY SALE IS WORTH AN AVERAGE OF $14,000
TO YOU! AND...EVERYONE LOVES YOUR PRODUCT... PROFIT!
Get the whole scoop! and be IN THE GREEN for the
HOLIDAYS THIS YEAR!  Please reply with "Cashflow Info" as
your subject.

mailto:t2m2@bigfoot.com?subject=Cashflow_Info

Have a Prosperous Day!



From list@netscape.com  Thu Jan 18 00:14:45 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06018
	for <ldapext-archive@odin.ietf.org>; Thu, 18 Jan 2001 00:14:44 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0I5Cas02977;
	Wed, 17 Jan 2001 21:12:36 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0I5Ccg08429;
	Wed, 17 Jan 2001 21:12:38 -0800 (PST)
Resent-Date: Wed, 17 Jan 2001 21:12:38 -0800 (PST)
Message-Id: <200101180512.f0I5CJZ07440@xwing.netscape.com>
From: <cashews@series2000.com>
To: <ietf-ldapext@netscape.com>
Subject:  LOOK! ..FULL HEALTH CARE ONLY $40/MO.! 
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 18 Jan 2001 00:02:14
Resent-Message-ID: <"Y_eD1B.A.bDC.FtnZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

NEWS YOU CAN USE RIGHT NOW!---- Health Care --- Wealth Savings ... and...Wealth  Making

Please read and follow the  instructions BELOW. (Steps 1-4)
Note: Because the info is in color and professionally packed
and ready to be mailed to you, it is not copied, duplicated
or faxed because it looses its professionality. We mail all our
responses VIA US POSTAL MAIL. Thank You...Peet

Please note: This  Health Program is not Available in these 2 states:
Washington State and California.
IT is AVAILABLE  in all the other 50 US STATES.

NEWS you can use today!

(Please PASS this info. on to those that need it) if you are not
interested.
HELP SOMEBODY ELSE. They will THANK YOU.

For more Information.
1. Please REPLY WITH more info in subject box  AND email your Postal
mailing address  to me and I Will rush your info to you......Peet

NO WAITING PERIOD
NO CLAIM FORMS TO FILL OUT
ALL PRE EXISTING  CONDITIONS ACCEPTED
NO TURNDOWNS
24-HRS. TO BE  IN ROLLED AFTER SIGNING UP
AND MUCH, MUCH MORE!
PLUS YOU CAN BE AN INDEPENDENT RE-SELLER REP.OF THIS PROGRAM.
AND EARN COMMISSIONS.
2. OR You may call toll free for more information
> and to get a free full color brochure mailed to your
> home or business by us postal mail service

3. CALL TOLL FREE: 1-888-719-8399 TODAY!

4. OR YOU MAY FAX YOUR NAME AND MAILING ADDRESS TO US
> AT: FAX # 1-( 757 ) - 852-9570
and we will send you the required free FULL COLOR information Brochure by
postal mail.

WE received your name as someone who wants opt in good free information offers.
If this mail has reached you in error, Please accept my apology. Thank you.

To be removed please reply with remove.
This is  A one time bulletin MAILING. No
other mail will be sent. Thank you.

DO SOMETHING TO SAVE YOUR HEALTH AND WEALTH TODAY !
THINK HOW IMPORTANT LIFE, HEALTH AND HAPPINESS REALLY MEAN
TO YOUR WELL BEING- DO SOMETHING  ABOUT IT NOW!!

P. S. DISTRIBUTORS and REPRESENTATIVES WELCOMED AND NEEDED. 



From list@netscape.com  Thu Jan 18 02:24:24 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA20511
	for <ldapext-archive@odin.ietf.org>; Thu, 18 Jan 2001 02:24:23 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0I7MCG17116;
	Wed, 17 Jan 2001 23:22:12 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0I7MDo04712;
	Wed, 17 Jan 2001 23:22:13 -0800 (PST)
Resent-Date: Wed, 17 Jan 2001 23:22:13 -0800 (PST)
Date: Wed, 17 Jan 2001 23:21:40 -0800 (PST)
Message-Id: <200101180721.f0I7LdZ12246@xwing.netscape.com>
From: "Billy"<dadyjeff@LRSY.bellsouth.net>
To: ietf-ldapext@XVHG.netscape.com
Subject:  Free Vacation - No Catch
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"2U7epD.A.WJB.kmpZ6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello ietf-ldapext,
Get Your Free Vacation Now. Go to the URL below an enter your email address and you are finished. 
THAT's IT. Enjoy you Free Vacation.

http://www.cyberweb-design.com
Click the Ad Response link in the Navigation bar

This is a special pre-launch invatation and a limited time offer Act Now!

Thank You
B. J. Wilbourn




From list@netscape.com  Thu Jan 18 16:25:18 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05719
	for <ldapext-archive@odin.ietf.org>; Thu, 18 Jan 2001 16:25:18 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ILNSG05828;
	Thu, 18 Jan 2001 13:23:28 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0ILNSE00696;
	Thu, 18 Jan 2001 13:23:28 -0800 (PST)
Resent-Date: Thu, 18 Jan 2001 13:23:28 -0800 (PST)
Date: Thu, 18 Jan 2001 13:23:23 -0800 (PST)
Message-Id: <200101182123.f0ILNNZ28503@xwing.netscape.com>
From: cashgenerator2002@yahoo.com
To: @netscape.com
Subject:  CLEARLY SEE YOUR FUTURE!
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"81e1qD.A.KK.O71Z6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

<HTML><BODY>

<P><FONT FACE = "Arial" COLOR = "#000000" SIZE = "2">JOURNEY WITHIN!
<P>Relive your past through Regression Viewing.
<P>Clearly see your future through Progression Viewing.
<P>For complete details, email &lta href="mailto:cashgenerator2002@yahoo.com&gtcashgenerator2002@yahoo.com&lt/a&gt.
<P>Please type "Journey Within" on subject line.
</BODY></HTML>



From list@netscape.com  Thu Jan 18 21:06:30 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08088
	for <ldapext-archive@odin.ietf.org>; Thu, 18 Jan 2001 21:06:29 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0J24JG25415;
	Thu, 18 Jan 2001 18:04:19 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0J24Ks00855;
	Thu, 18 Jan 2001 18:04:20 -0800 (PST)
Resent-Date: Thu, 18 Jan 2001 18:04:20 -0800 (PST)
Message-ID: <3A67A048.C291B0C2@openwave.com>
Date: Thu, 18 Jan 2001 18:02:48 -0800
From: sanjay jain <sanjay.jain@openwave.com>
Reply-To: sanjay.jain@openwave.com
Organization: Openwave Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ldapext <ietf-ldapext@netscape.com>
Subject: a compare operation question ...
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"t7NIMB.A.DN.iC6Z6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
If the attribute used in the AVA in a compare operation
<br>does not have an equality matching rule then is the compare
<br>result FALSE (similar to search filter semantics) or is it
<br>an error case ?
<p>thanks
<br>sanjay</html>





From list@netscape.com  Thu Jan 18 21:57:24 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA09483
	for <ldapext-archive@odin.ietf.org>; Thu, 18 Jan 2001 21:57:24 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0J2t6s19705;
	Thu, 18 Jan 2001 18:55:06 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0J2t7624088;
	Thu, 18 Jan 2001 18:55:07 -0800 (PST)
Resent-Date: Thu, 18 Jan 2001 18:55:07 -0800 (PST)
Message-Id: <5.0.2.1.0.20010118183634.00ab0ba0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 18 Jan 2001 18:54:12 -0800
To: sanjay.jain@openwave.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: a compare operation question ...
Cc: ldapext <ietf-ldapext@netscape.com>
In-Reply-To: <3A67A048.C291B0C2@openwave.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"7X3EDD.A.73F.Ky6Z6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 06:02 PM 1/18/01 -0800, sanjay jain wrote:
>If the attribute used in the AVA in a compare operation 
>does not have an equality matching rule then is the compare 
>result FALSE (similar to search filter semantics)

A search filter in this case would actually be Undefined.
While search does not return entries where the filter
evaluates to Undefined, compare returns true iff the
assertion is true, false iff false, and an error if the
assertion cannot be evaluated/reported for any reason.

>or is it 
>an error case ? 

It's an error case, specifically inappropriateMatching.

Kurt



From list@netscape.com  Fri Jan 19 00:47:28 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA12182
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 00:47:26 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0J5hus12672;
	Thu, 18 Jan 2001 21:43:56 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0J5hvg14080;
	Thu, 18 Jan 2001 21:43:57 -0800 (PST)
Resent-Date: Thu, 18 Jan 2001 21:43:57 -0800 (PST)
Message-Id: <sa67718a.034@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Thu, 18 Jan 2001 22:43:35 -0700
From: "Vijay Kn" <KNVIJAY@novell.com>
To: "<"<ietf-ldapext@netscape.com>
Subject: Submission: draft-knvijay-ldapext-clientcachingproxy-01.txt
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_0C575CEA.36575A59"
Resent-Message-ID: <"dgJFtB.A.ubD.cQ9Z6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_0C575CEA.36575A59
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

An update to the 'LDAP Client Caching Proxy Model ' draft was submitted to =
IETF recently. Reviews/comments on the same are welcome.

The I-D is available at:=20
http://www.ietf.org/internet-drafts/draft-knvijay-ldapext-clientcachingprox=
y-01.txt

Regards
Vijay

--=_0C575CEA.36575A59
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 12pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV><FONT size=3D2>An update to the 'LDAP Client Caching Proxy Model ' =
draft was=20
submitted to IETF recently. <FONT size=3D2>Reviews/comments on the same =
are=20
welcome.</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>The I-D is available at: </FONT></DIV>
<DIV><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-knvijay-ldapext-clientcac=
hingproxy-01.txt"><FONT=20
size=3D2>http://www.ietf.org/internet-drafts/draft-knvijay-ldapext-clientca=
chingproxy-01.txt</FONT></A></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>Regards</FONT></DIV>
<DIV><FONT size=3D2>Vijay</FONT></DIV></BODY></HTML>

--=_0C575CEA.36575A59--



From list@netscape.com  Fri Jan 19 03:22:18 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA26017
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 03:22:17 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0J8K7s29902;
	Fri, 19 Jan 2001 00:20:07 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0J8KAw23806;
	Fri, 19 Jan 2001 00:20:10 -0800 (PST)
Resent-Date: Fri, 19 Jan 2001 00:20:10 -0800 (PST)
X-Sender: tnjinc@hotmail.com
From: "tnjinc@hotmail.com" <tnjinc@hotmail.com>
To: ietf-ldapext@netscape.com
Date: Sat, 20 Jan 2001 03:20:24 -0800
Subject: Make $700 - $7000 a Month ! 
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <0bfda1818081311FE8@mail8.triad.rr.com>
Resent-Message-ID: <"5qZf4B.A.szF.4i_Z6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello Friend,
***********************************************************************
 This is a one-time mailing .If you are receiving this email more 
 than once Please allow me to apologize! I am now organizing my
 contact list!  
***********************************************************************  
 Make $700-$7000 a month with this program within 90 days or less!
  
 This is an invitation to all who wants to join !
 T&J Enterprises has developed alliances with a great online
 business .That will fit in everyone life. 


You'll get access to key subject areas like...

 Goal Setting 
 Motivation 
 Success 
 Relationships 
 Peak Performance 
 Attitude 
 Financial 
 Romance 
 Health & Friends 
 Management 
 Sales 
 Marriage 
 And 18 more vitally important growth areas.  

 
 To Ensure success for those who want to join T&J Enterprises
 we have went even further! We created Wealth Team 2001 
 which be used to help build a marketing team that will set the 
 standard for income earners online!
 
                          

You can change what your are earning until you change your thinking!
Personal growth proceeds financial growth! 

Act Now! The cost of this online business is only $20.00 a month 
         Join Wealth Team 2001 for Free! Commit to join the 
         online business and WT2001 will help build you business!
         
         

Subscribe:  send a blank email to :WealthTeam2001-subscribe@egroups.com  
***********************************************************************
to to be removed simply to do not subscribe to the list
you will not get any further mailings
***********************************************************************



From list@netscape.com  Fri Jan 19 06:32:14 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA27296
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 06:32:13 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0JBU7G25477;
	Fri, 19 Jan 2001 03:30:07 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0JBU6w09483;
	Fri, 19 Jan 2001 03:30:06 -0800 (PST)
Resent-Date: Fri, 19 Jan 2001 03:30:06 -0800 (PST)
Date: Fri, 19 Jan 2001 20:41:51 +0900
From: <Opt_In155157@aol.com>
Message-Id: <200101191141.AC31970@gukwon.chungju.ac.kr>
To: Opt-in223@ausi.com
Subject: I made $750 my first week with Newbies!
Resent-Message-ID: <"0010lB.A.3TC.9UCa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com



 ====================================================================== 
   Opt In Club Opportunities  
   Help stamp out spam by going Opt In. 
 ====================================================================== 



 ==============================
 I made $750 my first week with Newbies!
 ==============================
 
 
 The NEWBIE GUIDE is Fantastic!! 
 
 Not since the days of CETC, Cookie Cutter, or ReferEveryone 
 have we seen such an explosion! 
 
 I seriously made $750 my first week with Newbies! 
 
 And YOU can make money, too!
 
 Mailto:NewbieMoney1@newmail.net
 
 
 * One-time fee of $49.95 
 * NOT MLM 
 * YOU make 100% of the $49.95 sale 
 * Especially tailored to Beginners 
 * Complete Marketing Tools available 
 * Access to Merchant Account
 * The HTML creator and AD tracker were worth the entire $49.95 to me! - 
 
 
 Act NOW - Newbies will help you achieve your online financial goals for 2001!
 
 Send Email Now To: Mailto:NewbieMoney1@newmail.net



 ====================================================================== 
  To be unsubscribe from future mailings, 
  click the link mailto:unsubscribe201@newmail.net 
 ======================================================================
 



From list@netscape.com  Fri Jan 19 10:27:15 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00524
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 10:27:14 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0JFP7G17184;
	Fri, 19 Jan 2001 07:25:08 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0JFP8k03001;
	Fri, 19 Jan 2001 07:25:08 -0800 (PST)
Resent-Date: Fri, 19 Jan 2001 07:25:08 -0800 (PST)
Message-ID: <051301c0822c$0f37f030$779a6ac2@isocor.ie>
From: "Damian Power" <damian.power@cp.net>
To: "IETF LDAPEXT" <ietf-ldapext@netscape.com>,
        "IETF LDAPBIS" <ietf-ldapbis@openldap.org>
Subject: Binary Syntax and the binary Attribute Type option
Date: Fri, 19 Jan 2001 15:25:31 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Resent-Message-ID: <"ufCqfC.A.nu.SxFa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hi,

I have a question somewhat related to the "AttributeTypeValue and binary"
thread currently on the ELSE and LDAPBIS lists, but different enough that I
don't want to pollute that thread.

Simply put, my question is this: given that an Attribute Type is defined as
having Binary syntax (1.3.6.1.4.1.1466.115.121.1.5), is the ;binary option
required when referring to that attribute in protocol? For example,
attribute type "foo" has Binary syntax. If I request this attribute in a
search, do I refer to it as "foo" or "foo;binary"?

I don't believe the RFCs make a clear statement either way, so I'm looking
to see if a particular interpretation has gained acceptance. My personal
feeling is that the option should not be required.

I accept that the presence/absence of the option doesn't affect the value
returned.

Regards,

Damian.





From list@netscape.com  Fri Jan 19 11:10:13 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01216
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 11:10:12 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0JG8Xs20424;
	Fri, 19 Jan 2001 08:08:34 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0JG8XQ20278;
	Fri, 19 Jan 2001 08:08:33 -0800 (PST)
Resent-Date: Fri, 19 Jan 2001 08:08:33 -0800 (PST)
From: <emed11@libero.it>
Subject: Obtain Biotech IPOs!    70
Date: Fri, 19 Jan 2001 11:05:38
Message-Id: <41.111251.1766@libero.it>
Reply-To: emed11@libero.it
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by cins.hanyang.ac.kr id AAA319173
Resent-Message-ID: <"NgL_hB.A.R8E._ZGa6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: quoted-printable


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=3D(0073)file://C:\WINDOWS\Temporary%20Internet%20File=
s\OLKC225\A0007-1-A2-00.html -->
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-1=
252">
<META content=3D"Microsoft FrontPage 4.0" name=3DGENERATOR>
<META content=3DFrontPage.Editor.Document name=3DProgId></HEAD>
<BODY bgColor=3D#cccccc>
<DIV align=3Dcenter>
<TABLE borderColor=3D#003366 cellSpacing=3D5 borderColorDark=3D#003366 ce=
llPadding=3D14=20
width=3D550 borderColorLight=3D#003366 border=3D2>
  <TBODY>
  <TR>
    <TD width=3D"100%" bgColor=3D#ffffff>
      <P class=3DMsoBodyText align=3Dcenter><B><FONT face=3DVerdana color=
=3D#003399=20
      size=3D4>Help Beta Test Our Site and Be Eligible to Purchase Shares=
 of=20
      Future IPOs In Which We Participate**</FONT></B></P>
      <P class=3DMsoBodyText style=3D"TEXT-ALIGN: left" align=3Dleft><FON=
T face=3DArial=20
      size=3D2>eMedsecurities has selected you as a possible participant =
to help=20
      test our online stock-trading engine for knowledge-based investing =
in the=20
      life sciences.&nbsp; For your cooperation, <B>you will be eligible =
to purchase=20
      shares of future IPOs</B> in which we participate, for as long as y=
ou=20
      maintain your account with us.&nbsp; This is limited to only <B>50 =
qualified=20
      testers!&nbsp; </B><a href=3D"mailto:emedsec@libero.it">Request Mor=
e
      Information</a>.**</FONT></P>
      <P class=3DMsoBodyText align=3Dcenter><B><FONT face=3DVerdana color=
=3D#003399=20
      size=3D3>eMedsecurities=85 The Cure for the Common Portfolio!</FONT=
></B></P>
      <P class=3DMsoBodyText style=3D"TEXT-ALIGN: left" align=3Dleft><FON=
T face=3DArial=20
      size=3D2>eMedsecurities provides you with a wealth of information, =
all=20
      compiled in a single, easy-to-use resource.&nbsp; Learn about new r=
esearch=20
      and upcoming treatments for migraine headache, stroke, epilepsy, br=
ain=20
      tumor and much more.&nbsp; Obtain critical investment information a=
bout the=20
      companies that are developing these treatments.&nbsp; eMedsecuritie=
s empowers=20
      you to make more informed investment decisions.&nbsp; <a href=3D"ma=
ilto:emedsec@libero.it">Request
      More Information</a>.**</FONT></P>
      <P class=3DMsoNormal><B><FONT face=3DArial size=3D2>Participation i=
n
      eMedsecurities' Beta Test allows you:</FONT></B></P>
      <UL>
        <LI>
        <P class=3DMsoNormal=20
        style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
        face=3DArial size=3D2 color=3D"#003399">Eligibility to purchase s=
hares of IPOs in which=20
        eMedsecurities participates for as long as you maintain your=20
        account**</FONT></B> </P>
        <LI>
        <P class=3DMsoNormal=20
        style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
        face=3DArial size=3D2 color=3D"#003399">Valuable research of the =
entire product=20
        pipeline of companies, including stages of clinical development, =
by=20
        industry or specific disease</FONT></B> </P>
        <LI>
        <P class=3DMsoNormal=20
        style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
        face=3DArial size=3D2 color=3D"#003399">Useful information about =
industry trends, recent=20
        developments and upcoming IPOs</FONT></B> </P>
        <LI>
        <P class=3DMsoNormal=20
        style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
        face=3DArial size=3D2 color=3D"#003399">Commitment to customer se=
rvice featuring=20
        our Live Customer Service Online</FONT></B> </P>
        <LI>
        <P class=3DMsoNormal=20
        style=3D"mso-list: l1 level1 lfo2; tab-stops: list .5in; line-hei=
ght: 100%; margin-top: 0; margin-bottom: 0"><B><FONT=20
        face=3DArial size=3D2 color=3D"#003399">Dedication to fast trade =
executions at the best=20
        possible price</FONT></B> </P>
      </UL>
      <P align=3Dleft><FONT face=3DArial size=3D2>The following guideline=
s will=20
      explain what we expect from an eMedsecurities Beta Tester:</FONT></=
P>
      <UL>
        <LI>
        <P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Open a funded eMedsecurities=20
        account</FONT> </P>
        <LI>
        <P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Visit our online trading site onc=
e=20
        a week</FONT> </P>
        <LI>
        <P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Execute trades through our web=20
        site in accordance with your normal practice</FONT> </P>
        <LI>
        <P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Submit feedback to eMedsecurities=
' development team through a questionnaire sent via=20
        email</FONT> </P>
        <LI>
        <P align=3Dleft style=3D"line-height: 100%; margin-top: 0; margin=
-bottom: 0"><FONT face=3DArial size=3D2>Provide us with additional=20
        feedback regarding the site as needed</FONT> </P></LI></UL>
      <P align=3Dleft><FONT face=3DArial size=3D2>The test is limited to =
only 50 Beta=20
      Testers so sign up now to be considered!&nbsp; <a href=3D"mailto:em=
edsec@libero.it">Request
      More Information</a>.**</FONT>=20
      <P align=3Dleft><B><FONT face=3DArial size=3D2>Please note:</FONT><=
/B><FONT=20
      face=3DArial size=3D2> All applications for the Beta Test must be s=
ubmitted by
      January 24, 2001 to be considered.</FONT>=20
      <P align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      style=3D"mso-bidi-font-size: 12.0pt; mso-fareast-font-family: Times=
 New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bi=
di-language: AR-SA">Please=20
      be advised that your information will stay in our proprietary datab=
ase and=20
      will not be sold, traded, given or otherwise provided to outside ve=
ndors.&nbsp;
      We respect your privacy.</SPAN></FONT>=20
      <P align=3Dleft>=20
      <P align=3Dleft><FONT face=3DArial size=3D1><SPAN=20
      style=3D"mso-fareast-font-family: Times New Roman; mso-ansi-languag=
e: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">By=20
      submitting your information, you implicitly state that this is some=
thing=20
      that interests you and that you<br>
      agree to receive periodic emails from=20
      eMedsecurities.</SPAN></FONT>=20
      <P class=3DMsoNormal><FONT face=3DArial size=3D1>Research indicated=
 that you=20
      might benefit from our offer.&nbsp; To be removed instantly and per=
manently from=20
      our database, simply <a href=3D"mailto:emed11@libero.it">click here=
</a>.&nbsp;
      We respect=20
      all removal requests.</FONT></P><FONT face=3DArial size=3D1>**<B> R=
estrictions=20
      Apply:</B>&nbsp; <SPAN style=3D"COLOR: red"><B>Beta test not open t=
o residents of:&nbsp;
      HI, IL, MI, MN, MS, NE, NH, TN, TX.</B></SPAN>&nbsp; Initial Public=
=20
      Offerings are considered speculative investments and as such may no=
t be=20
      appropriate for every investor. If an investor chooses to participa=
te in=20
      IPOs, there are certain restrictions that apply:&nbsp; <B><SPAN=20
      style=3D"COLOR: red">Flipping</SPAN>- </B>The first time an investo=
r sells=20
      his/her shares within the first 30 days the issue is trading in the=
=20
      secondary market, that investor will not be allocated shares for th=
e next=20
      90 days following the sale.&nbsp; The second time that investor =93=
flips=94,=20
      they will not be allocated IPO shares for 180 days.&nbsp; The third=
 time=20
      that investor =93flips=94, they lose their IPO allocations permanen=
tly.<SPAN=20
      style=3D"COLOR: red">&nbsp; <B>Transferring shares</B></SPAN><B>- <=
/B>If the=20
      investor transfers IPO shares out of their account within the first=
 30=20
      days the issue is trading in the secondary market, they will perman=
ently=20
      lose their IPO allocations.&nbsp; <B>Beta investors will be chosen =
from=20
      all the applicants based on their income, net worth and investing=20
      experience.&nbsp;</B> IPO shares will only be allocated from transa=
ctions in=20
      which eMedsecurities participates in the underwriting. A0007-1-A2</=
FONT>=20
    </TD></TR></TBODY></TABLE></DIV></BODY></HTML>



From list@netscape.com  Fri Jan 19 19:57:54 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA08652
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 19:57:53 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0K0t3G02369;
	Fri, 19 Jan 2001 16:55:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0K0t4k11972;
	Fri, 19 Jan 2001 16:55:04 -0800 (PST)
Resent-Date: Fri, 19 Jan 2001 16:55:04 -0800 (PST)
Date: Fri, 19 Jan 2001 16:54:06 -0800 (PST)
Message-Id: <200101200054.f0K0ru506588@ywing.netscape.com>
From: kimo.member.epaper@ywing.netscape.com
To: mail@ywing.netscape.com
Subject: Welcome to kimo
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_kkIXGeBBGB6Q1RF"
X-Mailer: Kimo member mailer 1.05
X-Priority: 3
X-MSMail-Priority: Normal
Resent-Message-ID: <"v8LCwB.A.i6C.nHOa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multi-part message in MIME format.

------=_NextPart_kkIXGeBBGB6Q1RF
Content-Type: multipart/alternative;
	boundary="----=_NextPart_kkIXGeBBGB6Q1RFAA"


------=_NextPart_kkIXGeBBGB6Q1RFAA
Content-Type: text/plain;
Content-Transfer-Encoding: base64

UGxlYXNlIFJlYWQgSFRNTCBNZXNzYWdlICEhIQ==


------=_NextPart_kkIXGeBBGB6Q1RFAA
Content-Type: text/html;
	charset="big5"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT5XZWxjb21lIEtJTU88L3RpdGxlPg0KPG1ldGEgaHR0cC1l
cXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9YmlnNSI+DQo8
c3R5bGUgdHlwZT0idGV4dC9jc3MiPg0KPCEtLQ0KLmZoMTUgeyAgbGluZS1oZWlnaHQ6IDE1MCV9
DQotLT4NCjwvc3R5bGU+DQo8L2hlYWQ+DQoNCjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPg0KPGNl
bnRlcj4NCiAgPGJyPg0KICA8YSBocmVmPSJ3d3cua2ltby5jb20udHciIHRhcmdldD0iX2JsYW5r
Ij48aW1nIHNyYz0iaHR0cDovL3d3dy5raW1vLmNvbS50dy9lbmcvcGljL2tpbW9fdGl0bGVfZS5n
aWYiIGJvcmRlcj0iMCI+PC9hPjxicj4NCiAgPGJyPg0KICA8Zm9udCBjb2xvcj0iI0ZGMDAwMCI+
PGI+SEFQUFkgTkVXUyBZRUFSPC9iPjwvZm9udD48YnI+DQogIDxicj4NCiAgV2Vsb2NtZSB0byBN
eSBzaXRlLjxicj4NCiAgPGJyPg0KICA8YSBocmVmPSJodHRwOi8vd3d3LmtpbW8uY29tLnR3IiB0
YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5raW1vLmNvbS50dzwvYT48YnI+DQogIDxhIGhyZWY9
Imh0dHA6Ly93d3cua2ltby5jb20udHciIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3LmtpbW8u
Y29tIDwvYT4gDQo8L2NlbnRlcj4NCjwvYm9keT4NCjwvaHRtbD4g


------=_NextPart_kkIXGeBBGB6Q1RFAA--
------=_NextPart_kkIXGeBBGB6Q1RF--





From list@netscape.com  Fri Jan 19 23:32:37 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA12070
	for <ldapext-archive@odin.ietf.org>; Fri, 19 Jan 2001 23:32:37 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0K4UUG21346;
	Fri, 19 Jan 2001 20:30:30 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0K4UVs05842;
	Fri, 19 Jan 2001 20:30:31 -0800 (PST)
Resent-Date: Fri, 19 Jan 2001 20:30:31 -0800 (PST)
Date: Fri, 19 Jan 2001 20:30:19 -0800 (PST)
Message-Id: <200101200430.f0K4U9Z13278@xwing.netscape.com>
From: lljqx@msn.com
To: gnmfc@Friendsoftheweb.netscape.com
Reply-To: tim18a@n2mail.com
Subject: An INCREDIBLE CashFlow!                                    [ewcgz]
Resent-Message-ID: <"416SaB.A.9aB.mRRa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

MAKE $30,000 IN THE NEXT 40 TO 60 DAYS!

Sell our Idea to 3 People... Who Sell 3 People...
Then they follow you through our revolutionary
Wealth Generating System Making More Money Faster
and Easier than you ever dreamed possible!

To start your incredible chain reaction through
our program, all you have to do is just find
3 people who want to make lots of money,

NOT buy lots of products!

When your 3 enter the  Program you've already earned
your first $1,000 AND it’s just the beginning! Next
you're on your way to $5500 check from the SAME three
people...and it's all AUTOMATIC, now!

AND...IT'S STILL JUST THE BEGINNING!

NOW, you are MOVING!  Your LIFE IS REALLY CHANGING, NOW!

Your three people are now making you checks of $5000
and $10,000 AND THERE'S STILL SO MUCH MORE! I could go
ON AND ON...it's SO exciting! But, just to keep it
simple, let me put it this way...

EACH AND EVERY SALE IS WORTH AN AVERAGE OF $14,000
TO YOU! AND...EVERYONE LOVES YOUR PRODUCT... PROFIT!
Get the whole scoop! and be IN THE GREEN for the
HOLIDAYS THIS YEAR!  Please reply with "Cashflow Info" as
your subject.

mailto:tim18@n2mail.com?subject=Cashflow_Info

Please Note... Should my email address is shut down 
by the Flamers actions. Please "Fax" your response 
with your name__,email address___, and the Subject 
header "Incredible Cashflow" to: 305-425-3205. 

Have a Great Day!

      



From list@netscape.com  Sat Jan 20 13:38:41 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28826
	for <ldapext-archive@odin.ietf.org>; Sat, 20 Jan 2001 13:38:41 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0KIaRs26593;
	Sat, 20 Jan 2001 10:36:27 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0KIaRM20040;
	Sat, 20 Jan 2001 10:36:27 -0800 (PST)
Resent-Date: Sat, 20 Jan 2001 10:36:27 -0800 (PST)
Date: Sat, 20 Jan 2001 10:36:22 -0800 (PST)
From: Barry Johnson <barryjohnson55@themail.com>
To: <ietf-ldapext@netscape.com>
Message-Id: <419.436911.56429711barryjohnson55@themail.com>
Subject: WEIGHTLOSS MIRICLE BREAKTHROUGH !!
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"RzbiOD.A.24E.qqda6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

                    ***** SCIENTIFIC WEIGHTLOSS BREAKTHROUGH !!! ******

*Featured on CNN AND 20/20 THIS MONTH !!!
*Loose 12 LBS in 30 DAYS GUARANTEED !!!
*Absolutely No Dieting
*ALWAYS 100% EFFECTIVE !!!


                  ((((( EAT WHATEVER YOU WANT AND KEEP LOOSING !!! )))))

*Proven to work everytime !!!
*Proven to be 100% safe !!!
*Blocks the Absorbtion of fat from food !!!
*Significantly Lowers Cholesterol  Levels !!!


http://fiberlean.8k.com 



From list@netscape.com  Sat Jan 20 16:32:06 2001
Received: from netscape.com ([205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA29323
	for <ldapext-archive@odin.ietf.org>; Sat, 20 Jan 2001 16:32:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0KLTtG12298;
	Sat, 20 Jan 2001 13:29:55 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0KLTtk21004;
	Sat, 20 Jan 2001 13:29:55 -0800 (PST)
Resent-Date: Sat, 20 Jan 2001 13:29:55 -0800 (PST)
Date: Sat, 20 Jan 2001 13:29:51 -0800 (PST)
Message-Id: <200101202129.f0KLTp520149@ywing.netscape.com>
To: HV@ksshoes.de
From: <HV@ksshoes.de>
Subject: At Last, Herbal V, the all natural alternative!
Resent-Message-ID: <"tcHK9C.A.6HF.SNga6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


Herbal V: An Incredible All-Natural Healthy Alternative To V----a


  Herbal V is the All Natural Approach to Male Virility,
  Vitality and Pleasure.



Available N o w ! 


Welcome to the New Sexual Revolution.

It's the all natural male potency and pleasure pill that men 
everywhere are buzzing about. Herbal V is safe, natural and
specifically formulated to help support male sexual function
and pleasure. You just take two easy-to-swallow tablets
one hour before sex. And there's more great news - you can
get Herbal V for less than $1 a pill.

Amazing word of mouth praise on Herbal V has been spreading 
like wildfire-already over 1,500,000 men  have chosen
Herbal V. Since it is 100% natural you will never have
to worry about safety. Try doctor-recommended Herbal V
today and have the greatest night of your life!


Herbal V... Bringing Back the Magic!


1,585,000 men can't be wrong. To date over 1 million men 
have tried the super supplement Herbal V.
Here is why: 

No Doctor Visit Required 
Available Over the Counter 
Not a Drug 
100% Natural 
Safe, No Worries 
Highest Quality Pharmaceutical-Grade Pure Nutriceuticals 
Guaranteed Potency & Purity 

Be a Real Man Again!

Questions and Answers

What is Herbal V?

Herbal V is a proprietary blend that was specifically
developed as a safe alternative for men who prefer
an all-natural approach to address impotence and boost
sexual performance. This amazing formula first became
popular with Hollywood insiders and the wealthy elite.
They were maximizing their sex lives, long before it 
was available to the general public. 

How does Herbal V work?

Developed by a team whose goal was to create the perfect 
all-natural aphrodisiac. Herbal V is the result of that
remarkable effort. The Herbal V formula contains a precise
blend of cutting edge pro-sexual nutrients from around
the world that provide nutritional support, making it
possible for a man to have a pleasurable sexual experience. 

What can Herbal V do for me?

Herbal V helps support male sexual function and 
pleasure in a safe and natural manner. Simply put, 
it can make your sex life incredible. 

Is Herbal V Safe?

One of the great things about Herbal V is that it is
not a drug. It is an incredible herbal dietary supplement
that provides nutritional support for male sexual function
and pleasure. One of the most comforting features of
Herbal V is that you never have to worry about safety. 

Herbal V: Safe - Natural - Exciting

Many have speculated that because Herbal V is so
popular with men, it must contain prescription drugs
or chemical components. Herbal V does not contain any 
elements or traces of any prescription drug. Herbal V 
is made using the world's most technologically advanced
state-of-the-art cold processing equipment to ensure
maximum purity. Herbal V has been independently analyzed
by the nation's premier testing facility to ensure purity,
quality and to end the rumors that, because it is so
popular, it must somehow be chemical. It is not.
Herbal V is natural - just as it says on the label.
Herbal V is simply fantastic! 

Herbal V: Ingredients

Yohimbe, saw palmetto, avena sativa, androstenedione,
guarana, taurine, siberian ginseng, tribulus terrestris. 
Tribulus Terrestis is certified to enhanced testosterone
levels by increasing Luteinzing hormone (LH) levels. 
Androstenedione which is a precursor to testosterone
unlocks bound testosterone and makes it biologically
active again quickly. This means a dramatic surge in 
desire. Avena Sativa Stimulates the neurotransmitter 
pleasure centers to maximum capacity. This greatly
intensifies pleasure.

Just listen to what Herbal V has done for the sex lives
of people like you!

“On a scale of 1 to 10, it's a 15. Electrifying. It's like 
a wonder pill!” 
— Justin Q B., New Haven, Texas

“I haven't had sexual relations in 11 years. Then with 
Herbal V it was... wow! It works again!” 
— Sid R., Lakeland, Florida

“I had sex four times in one night. It made me feel
like a 19-year-old again.” 
— Chip S, Beech Mountain, North Carolina

“Herbal V has turned my husband into a Sexual Superman! 
I like the fact that it's all natural and has no
side effects. It's bringing back the good old days.” 
— Jennifer B, Beverly Hills, California 

The above testimonials are from product literature, 
and we have not independently verified them.
However, the following testimonial is from a "senior"
gentleman who has purchased his second bottle of
Herbal V. When we heard his words with our own ears,
we asked his permission to print them here. 

 “Man! I'm wild as I can be! I feel like I'm 25 years old again! 
I'm not believing this!” 
                          — Mr. Murphy, age 64, Lampart, IL.



Risk Free: Double Your Money Back Guarantee

If Herbal V does not give the desired results as stated
above, simply return the unused portion for a
double-your money back refund. No questions asked ! 

Order Now: Safe, Fast, Secure, Private

Herbal V with its DOUBLE YOUR MONEY BACK GUARANTEE is
available only through this special promotional offer.
Herbal V arrives in plain packaging for your privacy.
Any and all information is kept strictly confidential.

Payment Methods

You may FAX or Postal Mail Checks, MasterCard, Visa,
& American Express.payments. Money Orders
are accepted only by Postal Mail. 


Each bottle of Herbal V contains 30 tablets, approximately
a 1 month supply.


Step 1: Place a check by your desired quanity.


______ 1 Bottle of Herbal V  $28


______ 2 Bottles of Herbal V $48


______ 3 Bottles of Herbal V $59


Please add $6 shipping and handling for any size order. 
[ Total cost including shipping & handling, 
1 bottle=$34, 2 bottles=$54, 3 bottles=$65 ]

International Orders
Please add $18 shipping and handling for any size order.
[ Total cost including shipping & handling,
1 bottle=$46, 2 bottles=$66, 3 bottles=$77 ]
We cannot accept foreign checks.
International money orders or credit cards only.

Step 2: Place a check by your desired payment method 
and complete fields if necessary.


_____Check or CHECK-BY-FAX [details below]


_____Money Order 


_____American Express 
Account Number__________________ Exp____/____

_____Visa
Account Number__________________ Exp____/____

_____MasterCard
Account Number__________________ Exp____/____

 

Step 3: Please complete and print the following fields clearly.


Name ___________________________________________________ 


Address _________________________________________________


City ____________________________________________________ 


State ___________________________________________________ 


Zip _____________________________________________________ 


E-mail __________________________________________________ 


Signature _________________________________________________
[ required for check and credit card orders]



             Toll Free FAX Order Line: 1-800-940-6590
If faxing in your order, please state whether you require
a fax, email, or no confirmation at all. 
Allow up to one day for confirmation, if requested.
FAX orders are processed immediately.

  Or, print & mail to: LSN   
                       273 S. State Rd. 7, #193
                       Margate, FL 33068-5727                


        ______________________________________________________


*CHECK BY FAX ORDERS: Complete the check as normal. Tape
the check in the area below. Below the check, clearly write
the check number, all numbers at the bottom of the check,
& your name. Tape the check below and fax the check to the
toll free FAX number above. Void the check. Our merchant
will electronically debit your account for the amount of 
the check; your reference number for this transaction will
be your check number. Nothing could be safer & easier !

                          TAPE CHECK BELOW















              _____________________________________________________________

This is a one time mailing: Removal is automatic and no further 
contact is necessary. Please Note: Herbal V is not intended to
diagnose, treat, cure or prevent any disease. As individuals differ,
so will results. Herbal V helps provide herbal and nutritional support
for male sexual performance. The FDA has not evaluated these 
statements. For details about our double your money back guarantee,
please write to the above address, attention consumer affairs 
department; enclose a self addressed stamped envelope for this and any 
requested contact information.
Thank You.



From list@netscape.com  Sat Jan 20 22:45:08 2001
Received: from netscape.com ([205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA03079
	for <ldapext-archive@odin.ietf.org>; Sat, 20 Jan 2001 22:45:07 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0L3h2G00690;
	Sat, 20 Jan 2001 19:43:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0L3h3c21942;
	Sat, 20 Jan 2001 19:43:03 -0800 (PST)
Resent-Date: Sat, 20 Jan 2001 19:43:03 -0800 (PST)
X-Apparently-From: <earnhere@yahoo.com>
Message-ID: <130262001102134737930@mail.yahoo.com>
X-EM-Version: 5, 0, 0, 14
X-EM-Registration: #01B0530810E603002D00
From: "CC Group" <earnhere@yahoo.com>
Subject: Free Software Downloads For You !
Date: Sat, 20 Jan 2001 21:47:37 -0600
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Resent-Message-ID: <"G_wy8C.A.bWF.Frla6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This email is being sent as it may be of interest to you.
This is a one time mailing and you will not be contacted
again.  

Get Free Software that you can download instantly 
here !  Only for a limited time and totally FREE !!

Powerful programs that work that you can use right now 
for instant traffic. Promoters, List Manager, Email Manager,
Meta Tag Builder, Fantastic Ad Builder and more.
Only for a limited time and totally FREE !!

We'll also send you free information on how to 
earn immediate income online and how to bring 
thousands to your website. We can PROVE that
you can earn immediate income, so Grab an ID #
and WATCH what happens !! 

PLUS - We'll give you FREE PROMOTIONAL SOFTWARE 
for just taking a peek !

Download this software and watch what happens !!

http://freesoftware.ipfox.com







_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



From list@netscape.com  Sat Jan 20 23:28:16 2001
Received: from netscape.com ([205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA03241
	for <ldapext-archive@odin.ietf.org>; Sat, 20 Jan 2001 23:28:15 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0L4QBs27663;
	Sat, 20 Jan 2001 20:26:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0L4QCM29023;
	Sat, 20 Jan 2001 20:26:12 -0800 (PST)
Resent-Date: Sat, 20 Jan 2001 20:26:12 -0800 (PST)
From: <oldies@apexmail.com>
Subject: FREE...Visa Card Pays Up To 10 Levels!!!
Date: Sun, 21 Jan 2001 08:49:29
Message-Id: <275.391975.330071@server01>
Resent-Message-ID: <"nTyN8D.A.NFH.iTma6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Hi,


Wishing you a happy and prosperous 2001!

Take a quick look at the Free Visa Card program.
They're giving away free Visa cards with free flight miles on any 
airline and paying MLM commissions to refer other Cardholders.
They pay out on a huge 10-level plan ($10 for the first level and 
$2 on the next nine).

You already know how many millions of dollars that kind of 
multiplication can generate. Nobody buys a thing. The money comes 
from the bank because of the value of cardholders. This thing is 
spreading like wildfire. Please check it out.

Request for info!
mailto:jona01@excite.com?subject=Vinfo pls!

Regards.

................................................................
**This is a one-time mailing.  There is no need to remove 
yourself to stop further mailings.
 
 
 
 
 
 
 
 
 
 
 
 
 



From list@netscape.com  Sun Jan 21 11:01:23 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09534
	for <ldapext-archive@odin.ietf.org>; Sun, 21 Jan 2001 11:01:23 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0LFxUG03390;
	Sun, 21 Jan 2001 07:59:35 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0LFxUk12635;
	Sun, 21 Jan 2001 07:59:30 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 07:59:30 -0800 (PST)
Date: Sun, 21 Jan 2001 07:58:55 -0800 (PST)
Message-Id: <200101211558.f0LFwtZ23291@xwing.netscape.com>
From: malatras@SDUY.usa.net
To: klm.SQXD@netscape.com
Subject:  NEW "Internet" Work from home Program! MONEY NEVER STOPS! -UHQK
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"3eKxlC.A.JFD.hdwa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

NEW "Internet" Work from home Program! MONEY 
NEVER STOPS!

Dear friend,

I received your e-mail as someone interested in Internet Business 
Opportunities.

My name is Michalis Malatras.  I have been a member of Streamline for about some months and 
it has been a great experience.  Streamline has eliminated all the hassles of the other MLM 
companies, by giving you FREE tools you need to succeed, by helping you to build your 
downline with the trademarked Online Recruiter; the pressure of having to find people to 
sponsor is gone.  I could do nothing and my business would grow, but with a little effort it could 
explode.  

This is not something that happened to me ten years ago and now you are getting my success 
story.  This is a business that I have just been involved with for the past months and it has 
already
exceeded all my expectations! 

Streamline is by no means a get rich quick scheme.  Streamline has married three of the hottest 
trends:  Internet, Natural Wellness and MLM.  The technology breakthrough of the internet has 
finally 
made MLM feasible and hassle free.  It can happen -- the technology is there.

$firstname. Please check out my JUST UPDATED WEBSITES to find out why so many are  now 
beginning to achieve financial independence through Streamline.

http://www.cyber-action.com/oed/mnm.html

Once you are ready, you simply enroll online and get it all started today!

Keep in mind that Streamline offers 30 days money back guarantee.  
The risk is none.

My Warmest Regards,

Michalis Malatras
Streamline International
Proud Member of the MainStream Success Team
--------------------------------------------------------------------------
If I received your e-mail in error, or you are no longer interested, please accept our apologies. 
You can be removed at no cost to you simply by pressing "Reply" and place "Remove" in the 
Subject line.
--------------------------------------------------------------------------




From list@netscape.com  Sun Jan 21 11:02:53 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09545
	for <ldapext-archive@odin.ietf.org>; Sun, 21 Jan 2001 11:02:52 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0LG0oG03863;
	Sun, 21 Jan 2001 08:00:50 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0LG0og13516;
	Sun, 21 Jan 2001 08:00:50 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 08:00:50 -0800 (PST)
Date: Sun, 21 Jan 2001 08:00:33 -0800 (PST)
Message-Id: <200101211600.f0LG0X524771@ywing.netscape.com>
From: malatras@HFHP.usa.net
To: klm.KRFM@netscape.com
Subject:  NEW "Internet" Work from home Program! MONEY NEVER STOPS! -QQLV
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"B64wjB.A.6SD.xewa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

NEW "Internet" Work from home Program! MONEY 
NEVER STOPS!

Dear friend,

I received your e-mail as someone interested in Internet Business 
Opportunities.

My name is Michalis Malatras.  I have been a member of Streamline for about some months and 
it has been a great experience.  Streamline has eliminated all the hassles of the other MLM 
companies, by giving you FREE tools you need to succeed, by helping you to build your 
downline with the trademarked Online Recruiter; the pressure of having to find people to 
sponsor is gone.  I could do nothing and my business would grow, but with a little effort it could 
explode.  

This is not something that happened to me ten years ago and now you are getting my success 
story.  This is a business that I have just been involved with for the past months and it has 
already
exceeded all my expectations! 

Streamline is by no means a get rich quick scheme.  Streamline has married three of the hottest 
trends:  Internet, Natural Wellness and MLM.  The technology breakthrough of the internet has 
finally 
made MLM feasible and hassle free.  It can happen -- the technology is there.

$firstname. Please check out my JUST UPDATED WEBSITES to find out why so many are  now 
beginning to achieve financial independence through Streamline.

http://www.cyber-action.com/oed/mnm.html

Once you are ready, you simply enroll online and get it all started today!

Keep in mind that Streamline offers 30 days money back guarantee.  
The risk is none.

My Warmest Regards,

Michalis Malatras
Streamline International
Proud Member of the MainStream Success Team
--------------------------------------------------------------------------
If I received your e-mail in error, or you are no longer interested, please accept our apologies. 
You can be removed at no cost to you simply by pressing "Reply" and place "Remove" in the 
Subject line.
--------------------------------------------------------------------------




From list@netscape.com  Sun Jan 21 11:05:14 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09556
	for <ldapext-archive@odin.ietf.org>; Sun, 21 Jan 2001 11:05:13 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0LG3As29048;
	Sun, 21 Jan 2001 08:03:10 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0LG3A614611;
	Sun, 21 Jan 2001 08:03:10 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 08:03:10 -0800 (PST)
Date: Sun, 21 Jan 2001 08:02:42 -0800 (PST)
Message-Id: <200101211602.f0LG2fZ24487@xwing.netscape.com>
From: malatras@NTOS.usa.net
To: klm.IXMQ@netscape.com
Subject:  NEW "Internet" Work from home Program! MONEY NEVER STOPS! -CKXA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"-id5DB.A.BkD.9gwa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

NEW "Internet" Work from home Program! MONEY 
NEVER STOPS!

Dear friend,

I received your e-mail as someone interested in Internet Business 
Opportunities.

My name is Michalis Malatras.  I have been a member of Streamline for about some months and 
it has been a great experience.  Streamline has eliminated all the hassles of the other MLM 
companies, by giving you FREE tools you need to succeed, by helping you to build your 
downline with the trademarked Online Recruiter; the pressure of having to find people to 
sponsor is gone.  I could do nothing and my business would grow, but with a little effort it could 
explode.  

This is not something that happened to me ten years ago and now you are getting my success 
story.  This is a business that I have just been involved with for the past months and it has 
already
exceeded all my expectations! 

Streamline is by no means a get rich quick scheme.  Streamline has married three of the hottest 
trends:  Internet, Natural Wellness and MLM.  The technology breakthrough of the internet has 
finally 
made MLM feasible and hassle free.  It can happen -- the technology is there.

$firstname. Please check out my JUST UPDATED WEBSITES to find out why so many are  now 
beginning to achieve financial independence through Streamline.

http://www.cyber-action.com/oed/mnm.html

Once you are ready, you simply enroll online and get it all started today!

Keep in mind that Streamline offers 30 days money back guarantee.  
The risk is none.

My Warmest Regards,

Michalis Malatras
Streamline International
Proud Member of the MainStream Success Team
--------------------------------------------------------------------------
If I received your e-mail in error, or you are no longer interested, please accept our apologies. 
You can be removed at no cost to you simply by pressing "Reply" and place "Remove" in the 
Subject line.
--------------------------------------------------------------------------




From list@netscape.com  Sun Jan 21 11:17:46 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09611
	for <ldapext-archive@odin.ietf.org>; Sun, 21 Jan 2001 11:17:45 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0LGFhG05451;
	Sun, 21 Jan 2001 08:15:43 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0LGFig17287;
	Sun, 21 Jan 2001 08:15:44 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 08:15:44 -0800 (PST)
Date: Sun, 21 Jan 2001 08:15:26 -0800 (PST)
Message-Id: <200101211615.f0LGFP528424@ywing.netscape.com>
From: malatras@EWXO.usa.net
To: klm.KLQR@netscape.com
Subject:  NEW "Internet" Work from home Program! MONEY NEVER STOPS! -NJHO
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"i2-WK.A.1NE.vswa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

NEW "Internet" Work from home Program! MONEY 
NEVER STOPS!

Dear friend,

I received your e-mail as someone interested in Internet Business 
Opportunities.

My name is Michalis Malatras.  I have been a member of Streamline for about some months and 
it has been a great experience.  Streamline has eliminated all the hassles of the other MLM 
companies, by giving you FREE tools you need to succeed, by helping you to build your 
downline with the trademarked Online Recruiter; the pressure of having to find people to 
sponsor is gone.  I could do nothing and my business would grow, but with a little effort it could 
explode.  

This is not something that happened to me ten years ago and now you are getting my success 
story.  This is a business that I have just been involved with for the past months and it has 
already
exceeded all my expectations! 

Streamline is by no means a get rich quick scheme.  Streamline has married three of the hottest 
trends:  Internet, Natural Wellness and MLM.  The technology breakthrough of the internet has 
finally 
made MLM feasible and hassle free.  It can happen -- the technology is there.

$firstname. Please check out my JUST UPDATED WEBSITES to find out why so many are  now 
beginning to achieve financial independence through Streamline.

http://www.cyber-action.com/oed/mnm.html

Once you are ready, you simply enroll online and get it all started today!

Keep in mind that Streamline offers 30 days money back guarantee.  
The risk is none.

My Warmest Regards,

Michalis Malatras
Streamline International
Proud Member of the MainStream Success Team
--------------------------------------------------------------------------
If I received your e-mail in error, or you are no longer interested, please accept our apologies. 
You can be removed at no cost to you simply by pressing "Reply" and place "Remove" in the 
Subject line.
--------------------------------------------------------------------------




From list@netscape.com  Sun Jan 21 11:48:24 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09745
	for <ldapext-archive@odin.ietf.org>; Sun, 21 Jan 2001 11:48:23 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0LGkNs01822;
	Sun, 21 Jan 2001 08:46:23 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0LGkNg22660;
	Sun, 21 Jan 2001 08:46:23 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 08:46:23 -0800 (PST)
Date: Sun, 21 Jan 2001 08:45:54 -0800 (PST)
Message-Id: <200101211645.f0LGjsZ04815@xwing.netscape.com>
From: malatras@GJWJ.usa.net
To: klm.ECQJ@netscape.com
Subject:  NEW "Internet" Work from home Program! MONEY NEVER STOPS! -XJCJ
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"4p3ZpC.A.yhF.eJxa6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

NEW "Internet" Work from home Program! MONEY 
NEVER STOPS!

Dear friend,

I received your e-mail as someone interested in Internet Business 
Opportunities.

My name is Michalis Malatras.  I have been a member of Streamline for about some months and 
it has been a great experience.  Streamline has eliminated all the hassles of the other MLM 
companies, by giving you FREE tools you need to succeed, by helping you to build your 
downline with the trademarked Online Recruiter; the pressure of having to find people to 
sponsor is gone.  I could do nothing and my business would grow, but with a little effort it could 
explode.  

This is not something that happened to me ten years ago and now you are getting my success 
story.  This is a business that I have just been involved with for the past months and it has 
already
exceeded all my expectations! 

Streamline is by no means a get rich quick scheme.  Streamline has married three of the hottest 
trends:  Internet, Natural Wellness and MLM.  The technology breakthrough of the internet has 
finally 
made MLM feasible and hassle free.  It can happen -- the technology is there.

$firstname. Please check out my JUST UPDATED WEBSITES to find out why so many are  now 
beginning to achieve financial independence through Streamline.

http://www.cyber-action.com/oed/mnm.html

Once you are ready, you simply enroll online and get it all started today!

Keep in mind that Streamline offers 30 days money back guarantee.  
The risk is none.

My Warmest Regards,

Michalis Malatras
Streamline International
Proud Member of the MainStream Success Team
--------------------------------------------------------------------------
If I received your e-mail in error, or you are no longer interested, please accept our apologies. 
You can be removed at no cost to you simply by pressing "Reply" and place "Remove" in the 
Subject line.
--------------------------------------------------------------------------




From list@netscape.com  Sun Jan 21 20:11:39 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA12298
	for <ldapext-archive@odin.ietf.org>; Sun, 21 Jan 2001 20:11:39 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0M19Us28169;
	Sun, 21 Jan 2001 17:09:31 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0M19Wk15563;
	Sun, 21 Jan 2001 17:09:32 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 17:09:32 -0800 (PST)
Message-ID: <3A6B893B.2C8EBA63@worldspot.com>
Date: Sun, 21 Jan 2001 17:13:31 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: ietf-ldapext@netscape.com
Subject: Open issues with the Java LDAP API draft
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"V3Fe6.A.5yD.Lh4a6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

  These are the issues that have been raised (that I am aware of) with the latest Java LDAP Internet Draft (http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-java-api-12.txt), along with my own proposals for disposition.

  Nothing major, I don't think, and I'd like to conclude discussion on them in a week or so and update the Internet Draft.

Rob


1.-------------------------------------------------------------------

4.23 public class LDAPNameFormSchema 
                 extends LDAPSchemaElement 
     
    The LDAPNameFormSchema class represents the definition of a Name 
    Form. It is used to discover or modify the allowed naming attributes 
    for a particular object class. See [2] for a description of SAME form 
    representation in LDAP.
  
 second to last line should be (error in caps)
  
    for a particular object class. See [2] for a description of NAME form 

Rob: typo


2.-------------------------------------------------------------------

In sections 4.6.7, 4.26.1, 4.38.1, and 4.40.1, "host" is defined as
a hostname or dotted string which may include trailing colon and port
number.  This does not allow IPv6 addresses to be specified, and
should be changed to comply with RFC 2732:

      host          = hostname | IPv4address | IPv6reference
      ipv6reference = "[" IPv6address "]"

For example:

      "[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80"
      ldap://[3ffe:2a00:100:7031::1]:1050/o=abc

Rob: OK


3.-------------------------------------------------------------------

 One change that I suggested was way off base now
 that I look at it again.  That change is the
 change of values of the LDAP operation constants
  
 BIND_REQUEST 0 -> 0x60
  
 etc.
  
 That is certainly one thing I didn't read carefully
 enough.  Somehow I got it into my head
 that it was a numeric sequence, but on a more careful
 examination, the numbers come straight from
 RFC 2251.  I think that next draft should
 put the numbers back the way they were
 before.  We shouldn't be encoding the
 operation values with the ASN1 constructed, primitive
 bits, etc., just the operation value itself.
  
 Sorry for the miscue
  
 -Steve

Rob: suggest reverting to the values listed in the prior draft.


4.a-----------------------------------------------------------------

It might be better to eliminate the current unsolicited notification methods and instead have methods to add and remove listeners for usolicited notifications. The implementation can then discard unsolicited notifications if there are no listeners: 

In LDAPConnection:

public void addUnsolicitedNotificationListener(
    LDAPUnsolicitedNotificationListener listener )

public void removeUnsolicitedNotificationListener(
    LDAPUnsolicitedNotificationListener listener )

New interface:

public interface LDAPUnsolicitedNotificationListener {
   public void messageReceived( LDAPMessage msg );
}

Rob: that's my proposal; it allows instant notification of unsolicited messages without polling, and I think that is what applications need.

4.b-----------------------------------------------------------------

From Kurt:
I believe there should be an explicit requirement:
  Implementations MUST generate requests with a non-zero message ID.

Rob: agree


5.-------------------------------------------------------------------

The draft is incorrect: LDAPEntry.getAttribute returns a single attribute, as does
LDAPAttributeSet.getAttribute. 

Rob: typo


6.-------------------------------------------------------------------

In the sample code for asynchronous search on in section 9.2 of IETF draft 12. The getReferrals() method should be used instead of getUrls().

Rob: agree


7.-------------------------------------------------------------------

So shouldn't both the input stream and the output stream be set
in one atomic operation so it is thread safe?

Rob: I don't think there is a need for that. It is easy to add a synchronized wrapper for the two methods if a particular implementation needs to guard against (for example) different threads asynchronously changing the input stream but not the output stream. Actually, if an application has threads doing that, it's asking for trouble anyway. You really don't want one thread changing the input and output streams (even if they are done simultaneously) behind the back of another thread.



From list@netscape.com  Mon Jan 22 00:11:31 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16275
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 00:11:30 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0M59KG15040;
	Sun, 21 Jan 2001 21:09:20 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0M59Lk28342;
	Sun, 21 Jan 2001 21:09:21 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 21:09:21 -0800 (PST)
Message-Id: <200101220509.f0M59JZ13260@xwing.netscape.com>
Date: Sun, 21 Jan 2001 22:09:29 -0700
From: "Mike Grub" <grubmike@hotmail.com>
To: ietf-ldapext@netscape.com
X-Sender: grubmike@hotmail.com
Subject: Going Platinum !!! Miss This & Miss Out!!!
Reply-To: grubmike@hotmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"E4mbWC.A.k6G.AC8a6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Dear Fellow Entrepreneurs,

Going Platinum is...free...or you can opt to participate in the Going Platinum 
Affiliate Program (GPAP) for a one time cost of $25.
Each Round of the GPAP is a 3 X 3 forced matrix (3-9-27).

http://www.goingplat.bizland.com/going.html


Bronze round: fill your 3-9-27 $322.50 monthly
Silver round: fill your 3-9-27 $1,612.50 monthly
Gold round: fill your 3-9-27 $14,512.50 monthly
PLATINUM RND: fill your 3-9-27 $80,512.50 monthly
===================================================
The entire procession from Bronze to Platinum is completely self-funding. You 
NEVER have to pay another dime!

IT GETS EVEN BETTER...the chart above is just one small part of the total Going 
Platinum commission structure. You will be rewarded "big time" for anything and 
everything the Internet
has to offer...YOU WILL OWN IT...plus ALL revenue generated from every feature 
is paid to YOU!

IT GETS EVEN BETTER...CompuBank will pay you $50 on the spot when you sign up. 
Details at the website.

You will also be able to participate in our low cost TEAM co-op to over 250,000 
extremely targeted prospects. You will be a part of the finest TEAM in the entire 
Going Platinum community.

You'll be kicking yourself FOREVER if you miss out on this.Everyday that passes 
you leave money behind. Get in on the excitement and secure your future right 
now:
http://www.goingplat.bizland.com/going.html

Let's Make 2001 the Best Year Ever! 




From list@netscape.com  Mon Jan 22 03:02:18 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00318
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 03:02:18 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0M7xLs25228;
	Sun, 21 Jan 2001 23:59:22 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0M7xOA01536;
	Sun, 21 Jan 2001 23:59:24 -0800 (PST)
Resent-Date: Sun, 21 Jan 2001 23:59:24 -0800 (PST)
Message-ID: <0000511474cb$0000381b$00001f61@formy.com.pl>
To: <Undisclosed.Recipients@ywing.netscape.com>
From: credit@fiberia.com
Subject: Start Immediately!
Date: Sun, 21 Jan 2001 23:45:44 -0500
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Resent-Message-ID: <"AleDDB.A.uX.ah-a6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: quoted-printable

<HTML>
<BODY>

<FONT size=3D2> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$<BR>
NEW YORK FINANCIAL GENIUS WANTS TO REVEAL<BR>
TO YOU THE JEALOUSLY GUARDED SECRETS OF THE<BR>
RICH AND POWERFUL, AND HOW TO USE THEM TO RAKE<BR>
IN $1500+/WEEK IN EASY FAST CASH, STARTING<BR>
IMMEDIATELY--GUARANTEED!<BR>
$$$$$$$$$$$$4U$4U4U4U4U4U4U4U$$$$$$$$$$$$$$$$<BR>
----------------------------------------------------------<BR>
Dear Sir/Madam:<BR>
<BR>
How are you today? We hope you're doing great.  We are<BR>
happy to announce that after two long years of further<BR>
research, testing, updating, and revision of our famous<BR>
cash program "The Quick Cash Secret Banking System"<BR>
(QCSBS), we are finally ready to release it again to the <BR>
public! So, thank your lucky stars for receiving this <BR>
unique invitation, because our cash system can<BR>
put awesome cash in your bank account!<BR>
<BR>
Have you ever wondered why a few people in the world<BR>
seem to have a "magic wand" that brings them riches and<BR>
all the good things in life, while the rest<BR>
of the majority of the people are hardly surviving?<BR>
If yes, please stop wondering and let us show you why<BR>
and how!<BR>
<BR>
For the first time, all the powerful jealously guarded<BR>
SECRETS of the Rich and Powerful (that enable them to<BR>
"wheel and deal" and pile up bundles of cash) are being<BR>
released to the public, for the benefit of anyone who<BR>
seriously desires financial security and true success!<BR>
<BR>
In our  "Quick Cash Secret Banking System", (QCSBS)<BR>
 you'll discover one of the most powerful cash generating<BR>
secrets of the Rich and famous. How to open a<BR>
"SPECIAL" bank account, do 1-2hrs daily legal bank<BR>
transactions and rake in $1,500+/week in solid cash!<BR>
(100% legal and guaranteed, no scam involved!)<BR>
You can do it from any country, at anytime and<BR>
whenever you like!<BR>
<BR>
It is the fastest and easiest way in the world to<BR>
generate piles of cash at the speed of light!<BR>
Some of our associates and customers are currently<BR>
Using this powerful cash system to generate<BR>
$1,500, $2,500 and even $3,000/week!<BR>
<BR>
You'll discover a list of all the insiders' SECRET sources<BR>
of FREE MONEY (No Payback!). You are guaranteed to get<BR>
at least $10,000 free cash to spend as you please!<BR>
<BR>
In addition, when you order for our cash system, you <BR>
Automatically qualify to receive information on how to <BR>
obtain $5000 credit line (which is as good as cash) from <BR>
our associated bank,  regardless of your current credit <BR>
history and financial status. We will show how to <BR>
build this $5000 into a cash flow of $50,000 within<BR>
a few  months.<BR>
<BR>
In addition, we reveal to you, a powerful, jealously-guarded,<BR>
little known New York multi-millionaires' fast cash creation<BR>
strategy that will  enable you to raise "$100,000 in 24hrs",<BR>
instantly, without any investment or hard work! (You get this <BR>
when you become our sales agent!)<BR>
<BR>
<BR>
Thank you.<BR>
<BR>
Sincerely,<BR>
Scott Locy<BR>
Phone: 1-877-222-0249<BR>
FAX: 1-877-844-2500 ext. 257<BR>
e-mail: locy@prontomail.com<BR>
<BR>
Quick Cash Secret Banking System (QCSBS)<BR>
<BR>
</FONT>
</BODY>
</HTML>




From list@netscape.com  Mon Jan 22 03:14:05 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00389
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 03:14:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0M8CSs26747;
	Mon, 22 Jan 2001 00:12:28 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0M8CVg04421;
	Mon, 22 Jan 2001 00:12:31 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 00:12:31 -0800 (PST)
Date: Mon, 22 Jan 2001 00:12:27 -0800 (PST)
Message-Id: <200101220812.f0M8CQZ05059@xwing.netscape.com>
From: cashgenerator2002@yahoo.com
To: @netscape.com
Subject:  RETIRE QUICKLY!
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"foP8u.A.sEB.tt-a6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

<HTML><BODY>

<P><FONT FACE = "Arial" COLOR = "#000000" SIZE = "2">AUTOMATED HOME BUSINESS
<P>NO Selling!
<P>UNLIMITED income!!
<P>Please visit: www.retirequickly.com/85037 to see and hear complete presentation.
</BODY></HTML>



From list@netscape.com  Mon Jan 22 12:50:10 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10172
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 12:50:10 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0MHlrG22998;
	Mon, 22 Jan 2001 09:47:53 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0MHlqo28965;
	Mon, 22 Jan 2001 09:47:52 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 09:47:52 -0800 (PST)
Message-Id: <sa6c0fc1.061@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Mon, 22 Jan 2001 10:47:12 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_6D363621.5736662B"
Resent-Message-ID: <"ZWxMwD.A.QCH.BJHb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_6D363621.5736662B
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Minor typo related to item 5.  The description of attrName

"See 4.3.5for the syntax and semantics"

needs a space after 4.3.5
...........................................................................=
......
7. Bibliography

[7] should refer to draft version 05 of the ldap-c-api
...........................................................................=
.......

-Steve

------------------------
Steve Sonntag
Novell, Inc., the leading provider of Net services software



>>> Rob Weltman <robw@worldspot.com> 21-Jan-01 6:13:31 PM >>>
  These are the issues that have been raised (that I am aware of) with the =
latest Java LDAP Internet Draft (http://www.ietf.org/internet-drafts/draft-=
ietf-ldapext-ldap-java-api-12.txt), along with my own proposals for =
disposition.

  Nothing major, I don't think, and I'd like to conclude discussion on =
them in a week or so and update the Internet Draft.

Rob



5.-------------------------------------------------------------------

The draft is incorrect: LDAPEntry.getAttribute returns a single attribute, =
as does
LDAPAttributeSet.getAttribute.=20

Rob: typo

--=_6D363621.5736662B
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px">
<DIV><FONT size=3D1></FONT>Minor typo related to item 5.&nbsp; The =
description of=20
attrName</DIV>
<DIV>&nbsp;</DIV>
<DIV>"See 4.3.5for the syntax and semantics"</DIV>
<DIV>&nbsp;</DIV>
<DIV>needs a space after 4.3.5</DIV>
<DIV>......................................................................=
...........</DIV>
<DIV>7. Bibliography</DIV>
<DIV>&nbsp;</DIV>
<DIV>[7] should refer to draft version 05 of the ldap-c-api</DIV>
<DIV>......................................................................=
............</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV>------------------------<BR>Steve Sonntag<BR>Novell, Inc., the =
leading=20
provider of Net services software</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR><BR>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; =
21-Jan-01=20
6:13:31 PM &gt;&gt;&gt;<BR>&nbsp; These are the issues that have been =
raised=20
(that I am aware of) with the latest Java LDAP Internet Draft (<A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-java-ap=
i-12.txt),">http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-jav=
a-api-12.txt),</A>=20
along with my own proposals for disposition.<BR><BR>&nbsp; Nothing major, =
I=20
don't think, and I'd like to conclude discussion on them in a week or so =
and=20
update the Internet=20
Draft.<BR><BR>Rob<BR><BR><BR><BR>5.----------------------------------------=
---------------------------<BR><BR>The=20
draft is incorrect: LDAPEntry.getAttribute returns a single attribute, =
as=20
does<BR>LDAPAttributeSet.getAttribute. <BR><BR>Rob:=20
typo<BR><BR><BR></DIV></BODY></HTML>

--=_6D363621.5736662B--



From list@netscape.com  Mon Jan 22 14:39:43 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12841
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 14:39:42 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0MJbVs29846;
	Mon, 22 Jan 2001 11:37:32 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0MJWNM29242;
	Mon, 22 Jan 2001 11:32:23 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 11:32:23 -0800 (PST)
X-Apparently-From: <meistertek@yahoo.com>
Message-ID: <1742120011122193320950@compuserve>
X-EM-Version: 5, 0, 0, 14
X-EM-Registration: #01B0530810E603002D00
Reply-To: meistertek@yahoo.com
From: "meistertek@yahoo.com" <meistertek@yahoo.com>
To: ietf-ldapext@netscape.com
Subject: >>>CONGRATULATIONS!! YOU WON!!<<< 
Date: Mon, 22 Jan 2001 14:33:20 -0500
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Resent-Message-ID: <"WwWsXB.A.YFH.-qIb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

CONGRATULATIONS!! YOU WON!!

YOUR FREE MEMBERSHIP!!

CHECK IT OUT!

1000+ MEMBERS A MONTH!!

ALL new members that come into the club
COMPANY WIDE will go under YOU.

A true VERTICAL downline.
YOU can easily get 1000+ members
under YOU in a month!

How would you like a GUARANTEED
Commission every Month?

JOIN FREE!!!........JOIN FREE!!!!
To join our FREE Postlaunch Program

Go to sign Up at:

<http://www.geocities.com/webnetek>
----------------------------------------------------------------------------
----

This is NOT SPAM. Your name was received as someone interested in business
opportunities, or we have communicated in the past. We apologize if you
have received this in error. This is a ONE TIME mailing; however, if you
would like to insure removal, reply with "Remove" in the subject line. 
















_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



From list@netscape.com  Mon Jan 22 16:47:54 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA15209
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 16:47:53 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0MLjEs24827;
	Mon, 22 Jan 2001 13:45:14 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0MLjFo05096;
	Mon, 22 Jan 2001 13:45:15 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 13:45:15 -0800 (PST)
Message-Id: <sa6c4757.080@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Mon, 22 Jan 2001 14:44:28 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_401B1BD7.45247448"
Resent-Message-ID: <"e6pbqC.A.WPB.pnKb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_401B1BD7.45247448
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Rob,

In looking at the LDAPConnection object, I think the text should
be clarified as to which methods affect / apply to the global connection
(the source object) v.s. an individual clone of the LDAPConnection=20
object.  Here is my swag at it - omitting requests except bind, connect
& disconnect.

add/RemoveUnsolicitedNotificationListener - connection
bind - connection & and possibly clone - see note
          (Note: if disconnected when attempting bind, the=20
          API attempts a reconnect which now makes it
          specific to the clone the bind is done on.  Is this
          the intended behavior? - see 4.6.4 & 4.6.5.  I vote
          that bind does not attempt reconnect, but throws an
          exception instead).
connect - clone
disconnect - clone
finalize - clone
getAuthenticationDN - connection
getAuthenticationMethod - connection
getAuthenticationPassword - connection
get/setConstraints - clone
getHost - connection
get/setInputStream - connection
get/setOutputStream - connection
getPort - connection
get/setProperty - clone
getProtocolVersion - connection
getResponseControls - clone
getSaslBindCallBackHandler - connection
getSaslBindProperties - connection
get/setSearchConstraints - clone
getSocketFactory - connection
setSocketFactory - static connection
isBound - connecton
isConnected - connection
is/startTLS - connection

-Steve






------------------------
Steve Sonntag
Novell, Inc., the leading provider of Net services software

--=_401B1BD7.45247448
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px">
<DIV>Rob,</DIV>
<DIV>&nbsp;</DIV>
<DIV>In looking at the LDAPConnection object, I think the text should</DIV>=

<DIV>be clarified as to which methods affect / apply to the global=20
connection</DIV>
<DIV>(the source object) v.s. an individual clone of the LDAPConnection =
</DIV>
<DIV>object.&nbsp; Here is my swag at it - omitting requests except =
bind,=20
connect</DIV>
<DIV>&amp; disconnect.</DIV>
<DIV>&nbsp;</DIV>
<DIV>add/RemoveUnsolicitedNotificationListener - connection</DIV>
<DIV>bind - connection &amp; and possibly clone - see note</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Note: if=20
disconnected when attempting bind, the </DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; API attempts =
a=20
reconnect which now makes it</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specific to =
the=20
clone the bind is done on.&nbsp; Is this</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the intended=20=

behavior? - see 4.6.4 &amp; 4.6.5.&nbsp; I vote</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that bind does =
not=20
attempt reconnect, but throws an</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exception=20
instead).</DIV>
<DIV>connect - clone</DIV>
<DIV>disconnect - clone</DIV>
<DIV>finalize - clone</DIV>
<DIV>getAuthenticationDN - connection</DIV>
<DIV>getAuthenticationMethod - connection</DIV>
<DIV>getAuthenticationPassword - connection</DIV>
<DIV>get/setConstraints - clone</DIV>
<DIV>getHost - connection</DIV>
<DIV>get/setInputStream - connection</DIV>
<DIV>get/setOutputStream - connection</DIV>
<DIV>getPort - connection</DIV>
<DIV>get/setProperty - clone</DIV>
<DIV>getProtocolVersion - connection</DIV>
<DIV>getResponseControls - clone</DIV>
<DIV>getSaslBindCallBackHandler - connection</DIV>
<DIV>getSaslBindProperties - connection</DIV>
<DIV>get/setSearchConstraints - clone</DIV>
<DIV>getSocketFactory - connection</DIV>
<DIV>setSocketFactory - static connection</DIV>
<DIV>isBound - connecton</DIV>
<DIV>isConnected - connection</DIV>
<DIV>is/startTLS - connection</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>------------------------<BR>Steve Sonntag<BR>Novell, Inc., the =
leading=20
provider of Net services software</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--=_401B1BD7.45247448--



From list@netscape.com  Mon Jan 22 18:37:00 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16746
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 18:37:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0MNZNG01817;
	Mon, 22 Jan 2001 15:35:23 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0MNZOU01203;
	Mon, 22 Jan 2001 15:35:24 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 15:35:24 -0800 (PST)
Message-Id: <200101222335.f0MNZLZ28463@xwing.netscape.com>
X-Apparently-From: <exp121300@yahoo.com>
From: <exp121300@yahoo.com>
Subject: Best targeted e-mails!
Date: Mon, 22 Jan 2001 13:35:54
Resent-Message-ID: <"yT7dhC.A.hS.6OMb6"@glacier>
To: ietf-ldapext@netscape.com
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

  *******New List 1-20-01!!******** 

                          
Visit the site for more details!
http://www.geocities.com/silverem1329

The key to success in marketing online is reaching the people who 
are really interested in your ad! 

You need targeted e-mails of business opportunity seekers
who are ACTIVELY marketing online and trying to expand their
business TODAY!

-->   Highly Deliverable Lists!
  Our lists are cleaned and updated on a daily basis! Which means 
we have the lowest undeliverable rate out there!  We've also made 
sure to filter out all those unwanted e-mail address such as 
mil, .org, .org, .gov, etc.
                          


Visit the site for more details!
http://www.geocities.com/silverem1329

 10,000 opportunity seekers e-mails for only $10
**New List 1-20-01**
 25,000 opportunity seekers e-mails for only $20
 50,000 opportunity seekers e-mails for only $35
100,000 opportunity seekers e-mails for only $50
275,000 opportunity seekers e-mails for only $70

- Promotions!

**FREE with EVERY order, demo of ListMan e-mail manager software 
to manage your e-mails list, Free and Easy Credit Tips, and 
Insider Secrets: Creating Profitable Classified Ads

**Order 50,000 or more e-mails and receive Express Mail Server to 
send your e-mails FREE!  
-Send your e-mails safely bypassing your ISP's mail server!
-This is not a demo but a permanent license for the software!
-FREE Net Detective

**Order 100,000 or more e-mails and receive:

- InfoDisk  with 1000+ Money Making Reports
- URL cloaking software
- CheckMAN software
Combined value of over $250!  Yours FREE!
_______________________________________________________________
I received your e-mail as someone interested in Internet Business 
Opportunities. If I received your e-mail in error, or you are no 
longer interested, you can be removed at no cost to you simply by 
pressing "Reply" and place "Remove" in the Subject line.
_________________________________________________________________
 
 
 
 
 
 
 
 
 
 

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



From list@netscape.com  Mon Jan 22 21:27:16 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA19211
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 21:27:15 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0N2P9s26448;
	Mon, 22 Jan 2001 18:25:09 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0N2PAg16633;
	Mon, 22 Jan 2001 18:25:10 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 18:25:10 -0800 (PST)
Message-Id: <5.0.2.1.0.20010122172630.00a6f700@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 22 Jan 2001 18:25:00 -0800
To: ietf-ldapext@netscape.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Java LDAP API and the Java Community Process
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"cecruC.A.nDE.FuOb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

The Java Community Program is the recognized organization
responsible for publishing Java API specifications. 

The JCP appears to independently review IETF Java API
specifications prior to them becoming JCP approved
specifications such as was done with RFC2853 (JCP 72), the
Java GSSAPI API.  Though the RFC2853 was adopted "as is",
the JCP could have adopted it with changes.  This clearly
would have lead to interoperability problems between
competing specifications.  It is unclear whether RFC2853
should be progressed now that there is a JCP controlled
revision process.

If and when the IETF LDAP Java is published as an RFC,
it would likely be submitted to the JCP for review.  They
may or may adopt it and if they do, they may make changes.
This would lead to interoperability problems between
competing specifications.

The JCP has on going work in LDAP (JNDI) and related
networking services (SASL, TLS).  It seems reasonable to
assume that the JCP would likely not accept an IETF Java
API without change.

To avoid problems caused by having two competing Java LDAP
API specifications, I recommend this work be continued under
the auspices of the JCP and removed from the WG charter.

Kurt



From list@netscape.com  Mon Jan 22 21:44:52 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20279
	for <ldapext-archive@odin.ietf.org>; Mon, 22 Jan 2001 21:44:52 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0N2glG03250;
	Mon, 22 Jan 2001 18:42:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0N2gmo21560;
	Mon, 22 Jan 2001 18:42:48 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 18:42:48 -0800 (PST)
Message-ID: <3A6CEF7C.E38C1366@worldspot.com>
Date: Mon, 22 Jan 2001 18:42:04 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@openldap.org>
CC: ietf-ldapext@netscape.com
Subject: Re: Java LDAP API and the Java Community Process
References: <5.0.2.1.0.20010122172630.00a6f700@router.boolean.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"GDQPJC.A.mQF.n-Ob6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

  In the Sun perception, there is no need for a Java LDAP API because of the existence of JNDI. There is almost zero possibility that a Java LDAP API would be considered by the JCP.

Rob


"Kurt D. Zeilenga" wrote:
> 
> The Java Community Program is the recognized organization
> responsible for publishing Java API specifications.
> 
> The JCP appears to independently review IETF Java API
> specifications prior to them becoming JCP approved
> specifications such as was done with RFC2853 (JCP 72), the
> Java GSSAPI API.  Though the RFC2853 was adopted "as is",
> the JCP could have adopted it with changes.  This clearly
> would have lead to interoperability problems between
> competing specifications.  It is unclear whether RFC2853
> should be progressed now that there is a JCP controlled
> revision process.
> 
> If and when the IETF LDAP Java is published as an RFC,
> it would likely be submitted to the JCP for review.  They
> may or may adopt it and if they do, they may make changes.
> This would lead to interoperability problems between
> competing specifications.
> 
> The JCP has on going work in LDAP (JNDI) and related
> networking services (SASL, TLS).  It seems reasonable to
> assume that the JCP would likely not accept an IETF Java
> API without change.
> 
> To avoid problems caused by having two competing Java LDAP
> API specifications, I recommend this work be continued under
> the auspices of the JCP and removed from the WG charter.
> 
> Kurt



From list@netscape.com  Tue Jan 23 01:49:49 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA28898
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 01:49:49 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0N6m3s20328;
	Mon, 22 Jan 2001 22:48:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0N6m5g23526;
	Mon, 22 Jan 2001 22:48:05 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 22:48:05 -0800 (PST)
Message-Id: <5.0.2.1.0.20010122154103.00a31430@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 22 Jan 2001 22:47:32 -0800
To: Rob Weltman <robw@worldspot.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Open issues with the Java LDAP API draft
Cc: ietf-ldapext@netscape.com
In-Reply-To: <3A6B893B.2C8EBA63@worldspot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"EJxu2D.A.UvF.kkSb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 05:13 PM 1/21/01 -0800, Rob Weltman wrote:
>  These are the issues that have been raised (that I am aware of) with the latest Java LDAP Internet Draft (http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-java-api-12.txt), along with my own proposals for disposition.

I have a few other issues.  Many of these have been
discussed previously.

The API appears to support both LDAPv2 and LDAPv3 but appears
to assumes use of UTF-8 regardless of the protocol.  LDAPv2
directoryStrings are restricted to T.61.  In addition, certain
LDAPv2 protocol strings (e.g. all LDAPStrings) are restricted
to IA5.  If LDAPv2 is to be support, it should be fully
supported and a normative reference to LDAPv2 should be stated.
If LDAPv2 is not to be supported, all mention of LDAPv2 should
be stricken.  I believe this API should not attempt to support
both LDAPv2 and LDAPv3.  As LDAPv2 will be moved to historical
status upon publication of an LDAPv3 Draft Standard, I recommend
this API support only LDAPv3.

API contains a reference to RFC 1823, an Informational RFC.
If this is non-normative, it should be noted.  If normative,
there is a standard track maturity issue in that RFC 1823 is
informational.  It appears to be normative to me.  

The abstract refers to the expired async API I-D unnecesarily.

It appears that the API specification requires implementation
of LDAP Language Tags, an extension to the "core" protocol
specification.  The core API should only require implementation
of the "core" protocol specification.  APIs for non-core
extensions should be detailed in API extensions.

Java, IIRC, uses UCS-2.  LDAP allows the full (31-bit) set of
ISO-10646-1 characters encoded in UTF-8.  There should be some
comment as what is to be done with characters outside of UCS-2
but with ISO-10646-1.

There should be a normative reference to Java language
specification(s) [core + required extensions (SASL/TLS)].
The relationship with JNDI should also be discussed.

Appears the default behavior is to chase referrals.  As I've
noted previously on this list, this is not a wise default from
a security perspective.  The default should be not to chase
referrals (period).

LDAP_PARTIAL_RESULTS?  There should be no mention of this.  However,
I note that the API should be capable of treating unrecognized
result codes returned by servers (including those reserved by API
specifications) as unknown errors.

Missing normative references:
        Java API Spec
        Java SASL API Spec
        Java TLS API Spec
        ldaps (LDAP over SSL)
        RFC 2222, RFC 2829, RFC 2830

Kurt



From list@netscape.com  Tue Jan 23 02:07:04 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA06354
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 02:07:03 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0N74vs22519;
	Mon, 22 Jan 2001 23:04:57 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0N74xo27355;
	Mon, 22 Jan 2001 23:04:59 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 23:04:59 -0800 (PST)
Message-Id: <5.0.2.1.0.20010122190659.00a9bec0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 22 Jan 2001 23:04:45 -0800
To: Rob Weltman <robw@worldspot.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Java LDAP API and the Java Community Process
Cc: ietf-ldapext@netscape.com
In-Reply-To: <3A6CEF7C.E38C1366@worldspot.com>
References: <5.0.2.1.0.20010122172630.00a6f700@router.boolean.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"efmlK.A.JrG.a0Sb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 06:42 PM 1/22/01 -0800, Rob Weltman wrote:
>In the Sun perception, there is no need for a Java LDAP API because of the existence of JNDI. 

I think it's fairly reasonable to prefer a Java Standard Extension,
such as JNDI, over one which isn't.

> There is almost zero possibility that a Java LDAP API would be considered by the JCP.

There is zero possibility if it's not submitted to the JCP.

I believe there is a significant possibility that JNDI will be
extended by the JCP to incorporate most, if not all, of the
functionality of the LDAPext LDAP API.

It seems odd that we would recognize the JCP as the providing
the definitive specification of the Java Language, numerous
Internet protocol APIs, but not the LDAP API. 

In the end, there should be one Standard LDAP API.  Whether we
like it or not, that will be a JCP approved specification.  If
we want to have an impact upon this specification, we need to
work within the JCP not outside it.

Kurt



From list@netscape.com  Tue Jan 23 02:34:43 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA06617
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 02:34:43 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0N7X3s24766;
	Mon, 22 Jan 2001 23:33:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0N7X5o04022;
	Mon, 22 Jan 2001 23:33:05 -0800 (PST)
Resent-Date: Mon, 22 Jan 2001 23:33:05 -0800 (PST)
Message-ID: <3A6D3476.DD02FA52@worldspot.com>
Date: Mon, 22 Jan 2001 23:36:22 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@openldap.org>
CC: Rob Weltman <robw@worldspot.com>, ietf-ldapext@netscape.com
Subject: Re: Java LDAP API and the Java Community Process
References: <5.0.2.1.0.20010122172630.00a6f700@router.boolean.net> <5.0.2.1.0.20010122190659.00a9bec0@router.boolean.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"ObY6vC.A.k-.vOTb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

"Kurt D. Zeilenga" wrote:
> 
> At 06:42 PM 1/22/01 -0800, Rob Weltman wrote:
> >In the Sun perception, there is no need for a Java LDAP API because of the existence of JNDI.
> 
> I think it's fairly reasonable to prefer a Java Standard Extension,
> such as JNDI, over one which isn't.

  They serve different purposes. JNDI's purpose is not to expose the LDAP protocol, and that has important consequences.

 
> > There is almost zero possibility that a Java LDAP API would be considered by the JCP.
> 
> There is zero possibility if it's not submitted to the JCP.
> 
> I believe there is a significant possibility that JNDI will be
> extended by the JCP to incorporate most, if not all, of the
> functionality of the LDAPext LDAP API.
> 
> It seems odd that we would recognize the JCP as the providing
> the definitive specification of the Java Language, numerous
> Internet protocol APIs, but not the LDAP API.
> 
> In the end, there should be one Standard LDAP API.  Whether we
> like it or not, that will be a JCP approved specification.  If
> we want to have an impact upon this specification, we need to
> work within the JCP not outside it.

  I do work inside it. I'm spec lead for JSR 28 (SASL API), which started out as an Internet Draft. I've also been involved off and on with JNDI since the beginning of 1997, more in the beginning. JNDI and the Java LDAP API have branched off in different directions because they have different purposes in life. I wasn't willing to confine the API to what can be done with a generic directory interface because there were and are important LDAP features that developers want to exploit and which don't fit the JNDI template. And of course JNDI needs to abstract from the protocols it encapsulates in order to achieve its goals.

  Unfortunately not everyone realizes that.

Rob



From list@netscape.com  Tue Jan 23 07:36:45 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09557
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 07:36:44 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0NCYQG19195;
	Tue, 23 Jan 2001 04:34:26 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0NCYQ221678;
	Tue, 23 Jan 2001 04:34:26 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 04:34:26 -0800 (PST)
Message-Id: <200101231233.HAA09306@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ietf-ldapext@netscape.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-zeilenga-ldap-cancel-00.txt
Date: Tue, 23 Jan 2001 07:33:54 -0500
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <"y8GsrD.A.cSF.RpXb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: LDAP Cancel Extended Operation
	Author(s)	: K. Zeilenga
	Filename	: draft-zeilenga-ldap-cancel-00.txt
	Pages		: 5
	Date		: 22-Jan-01
	
This specification describes an extended operation to cancel (or
abandon) an outstanding operation.   Unlike the LDAP Abandon operation
[RFC2251] but like the DAP Abandon operation [X.511], this operation
has a response to indicate whether or not the operation was
successful.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-cancel-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-zeilenga-ldap-cancel-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-zeilenga-ldap-cancel-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010122143409.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-zeilenga-ldap-cancel-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-zeilenga-ldap-cancel-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010122143409.I-D@ietf.org>

--OtherAccess--

--NextPart--




From list@netscape.com  Tue Jan 23 07:36:53 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09586
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 07:36:52 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0NCYXG19300;
	Tue, 23 Jan 2001 04:34:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0NCYX621809;
	Tue, 23 Jan 2001 04:34:33 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 04:34:33 -0800 (PST)
Message-Id: <200101231233.HAA09290@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ietf-ldapext@netscape.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-zeilenga-ldap-authpasswd-04.txt
Date: Tue, 23 Jan 2001 07:33:49 -0500
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <"I4CFLC.A.LUF.XpXb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: LDAP Authentication Password Attribute
	Author(s)	: K. Zeilenga
	Filename	: draft-zeilenga-ldap-authpasswd-04.txt
	Pages		: 9
	Date		: 22-Jan-01
	
This document describes schema in support of user/password
authentication in a LDAP directory including the authPassword
attribute type.  This attribute type holds values derived from the
user's password(s) (commonly using cryptographic strength one-way
hash).  authPassword is intended to used instead of userPassword.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-authpasswd-04.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-zeilenga-ldap-authpasswd-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-zeilenga-ldap-authpasswd-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010122143400.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-zeilenga-ldap-authpasswd-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-zeilenga-ldap-authpasswd-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010122143400.I-D@ietf.org>

--OtherAccess--

--NextPart--




From list@netscape.com  Tue Jan 23 16:10:48 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24633
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 16:10:47 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0NL8YG08436;
	Tue, 23 Jan 2001 13:08:35 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0NL8aU24058;
	Tue, 23 Jan 2001 13:08:36 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 13:08:36 -0800 (PST)
Date: Tue, 23 Jan 2001 13:08:28 -0800 (PST)
Message-Id: <200101232108.f0NL8S521586@ywing.netscape.com>
From: dcsenterprises2001@yahoo.com
To: people.VRRI@netscape.com
Subject:  Hello
X-Reply-To:  dcsenterprises2001@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"_rfZnC.A.e3F.RLfb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello,

Would you consider granting me permisssion to send you information 
on an automated online business opportunity?

David Dale
dCs Enterprises
dcsenterprises2001@yahoo.com








From list@netscape.com  Tue Jan 23 17:35:43 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25673
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 17:35:42 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0NMXQb02513;
	Tue, 23 Jan 2001 14:33:27 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0NLtJ617161;
	Tue, 23 Jan 2001 13:55:19 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 13:55:19 -0800 (PST)
Message-Id: <5.0.2.1.0.20010123134238.00adeaa0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 23 Jan 2001 13:54:46 -0800
To: ietf-ldapext@netscape.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: AuthPassword I-D: draft-zeilenga-ldap-authpasswd-04.txt
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"pvJga.A.oLE.C3fb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

The I-D has been updated to remove specific support for SASL.
Though this attribute could be used to support SASL user/password
authentications mechanisms such as DIGEST-MD5, it is unclear to
me whether or not this is the best approach for these mechanisms.

In addition, the I-D now includes a recommendation that hashed
values be protected as if they were the actual plain text
passwords.

Your comments are solicited.



From list@netscape.com  Tue Jan 23 17:55:22 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25882
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 17:55:21 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0NMrlb06779;
	Tue, 23 Jan 2001 14:53:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0NLxEY18393;
	Tue, 23 Jan 2001 13:59:14 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 13:59:14 -0800 (PST)
Message-Id: <5.0.2.1.0.20010123135455.00ae0d00@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 23 Jan 2001 13:59:17 -0800
To: ietf-ldapext@netscape.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Cancel I-D: draft-zeilenga-ldap-cancel-00.txt
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"FCqWrD.A.9eE.u6fb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This draft describes an LDAPv3 extended operation intended
to be used instead of the abandon operation in situations
requiring a result indication.  It's based on the X.511
abandon operation.

Your comments are solicited.



From list@netscape.com  Tue Jan 23 17:55:25 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25901
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 17:55:25 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0NMrkb06770;
	Tue, 23 Jan 2001 14:53:46 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0NMnQQ13600;
	Tue, 23 Jan 2001 14:49:26 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 14:49:26 -0800 (PST)
Date: Tue, 23 Jan 2001 14:49:12 -0800 (PST)
From: crdt@blomtiming.no
Message-Id: <200101232249.f0NMn2Z13410@xwing.netscape.com>
To: simone54xz@aol.com
Resent-Message-ID: <"BAMKqC.A.pSD.tpgb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
Subject: Unidentified subject!
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

e.com, jhsclly@netscape.com
From: <crdt@blomtiming.no>
Subject: Excellent Credit In Less Than 30 Days- GUARANTEED !
MIME-Version: 1.0
Content-Type: text/plain; charset=unknown-8bit
content-length: 4385
Message-Id: <20010123234746.SM00302@a1>
Date: Tue, 23 Jan 2001 23:48:55 +0100


GUARANTEED EXCELLENT CREDIT IN 30 DAYS ! 

 
Is your credit less than perfect?


If so, then you must read this email.
  
We have compiled a 104 page e-book GUARANTEED
to give you an excellent credit rating in 
less than 30 days. You can download this 
information today for only $29, and enjoy all
the benefits of excellent credit within 30 
days.
 
A recent customer had this to say:
 
"Hello, my name is John Simmers. In 1997, I
owned my own business...however, due to a
slow economy I had to file bankruptcy. 
Creditors reposed, my home, car and most of
my other belongings. Then I was fortunate enough
to find out about the Financial Freedom 
Services Ltd. It has truly changed my life.
Within 2 weeks of ordering your e-book, I was
able to obtain a copy or my credit report, 
remove every negative item, and place over
$5,000 in true, positive credit information 
on my credit file. 
 
It has now been 1 year since I bought this
program and I now have $130,000 in unsecured
credit lines and have recently financed a new
$285,000 home with $0 down and a new $56,000
Lexus.
 
Thank You for sharing your knowledge with me
and allowing me to regain control of my credit
and my life."
 
		Sincerely,
		John Simmers
		Los Angeles, CA
 
Over the last few years we have received 
thousands of positive letters from customers
just like this one. 
 
This e-boox will show you how to legally:
 
  - obtain your credit report quickly and at
    no charge;
 
  - instantly add positive, legal items on 
    your credit report;
 
  - quickly and easily remove negative items
    permanently from your credit file.
 
We guarantee in less than 30 days, our 
information will allow you to do all of the 
following:
 
  - buy a new car;

  - buy a home;

  - take a vacation;

  - start your own business;

  - enjoy life without financial troubles.


RISK FREE GUARANTEE

If, for any reason, you are unable attain
excellent credit in less than 30 days, your
money will be refunded with our " No questions
asked refund policy. " 
 
_____________________________________________
 

FINANCIAL FREEDOM COSTS JUST $29. 

_____________________________________________
 

To order, simply complete the fields below
enclose a $29 check or money order and mail
to:


	Apex
	Attn: R. Colbert
	MailRoom Post Office Box  #0215
	Coral Springs, FL 33067-0215

 
To download this information today, you may
fax this form toll free to 888.244.4366.
 
Your checking account will be electronically
debited for $29.00 by ECT Payment Systems.
Orders faxed before 12:00 pm EST are 
processed and emailed the same day. Orders
after 12:00pm will be processed and emailed
on the next day.

If you do not have access to a fax machine,
you may send faxes for free from many web
based email accounts, such as yahoo.com, 
ureach.com, jfax.com, and many others.

______________________________________________


PLEASE TYPE OR PRINT ALL FIELDS BELOW CLEARLY


Name:           ___________________________


Address:        ___________________________


City/State/Zip: ___________________________


Phone:          ___________________________


Email Address:  ___________________________


Bank Name:      ___________________________ 


Bank Address:   ___________________________


Check Number:   ___________________________

All Numbers at
Check Bottom:   ___________________________


FAX TOLL FREE TO 888.244.4366 or mail to:


	Apex
	Attn: R. Colbert
	MailRoom Post Office Box  #0215
	Coral Springs, FL 33067-0215


** We respect your privacy and will not share
any of the above information with any other 
persons or companies. **


.............................................
This is a one time email transmission, either
requested by you or by someone you know. The
information provided is for educational
purposes only and FFS Ltd is not providing a
service. This offer is void where prohibited.
This cannot be considered spam as long as the
sender includes a method of removal at no cost
to the recipient as stated in bill s.1618 
TITLE III passed by the 105th US Congress. 
This is a one time email transmission; no need
for removal is required. If you do not respond,
FFS Lts will not contact you and you will be
automatically removed.



From list@netscape.com  Tue Jan 23 20:49:21 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27877
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 20:49:20 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0O1keG03955;
	Tue, 23 Jan 2001 17:46:40 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0O1kfQ13294;
	Tue, 23 Jan 2001 17:46:41 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 17:46:41 -0800 (PST)
Message-Id: <sa6d5724.087@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 23 Jan 2001 10:04:12 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <Kurt@openldap.org>, <robw@worldspot.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_02595884.6C0D5C17"
Resent-Message-ID: <"1xf3zC.A.SPD.AQjb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_02595884.6C0D5C17
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Kurt,

The default behavior for following referrals is specified in
the LDAPConstraints object.  The boolean doReferrals parameter
controls whether referrals are followed or not.  The default
for this parameter is "FALSE", i.e. referrals are not
automatically followed [period].  See also 4.7.8.

-Steve

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 22-Jan-01 11:47:32 PM >>>
At 05:13 PM 1/21/01 -0800, Rob Weltman wrote:
>  These are the issues that have been raised (that I am aware of) with =
the latest Java LDAP Internet Draft (http://www.ietf.org/internet-drafts/dr=
aft-ietf-ldapext-ldap-java-api-12.txt), along with my own proposals for =
disposition.

I have a few other issues.  Many of these have been
discussed previously.

............cut................

Appears the default behavior is to chase referrals.  As I've
noted previously on this list, this is not a wise default from
a security perspective.  The default should be not to chase
referrals (period).
.............cut................

Kurt

--=_02595884.6C0D5C17
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px"><FONT=20
size=3D1></FONT>
<DIV>Kurt,</DIV>
<DIV>&nbsp;</DIV>
<DIV>The default behavior for following referrals is specified in</DIV>
<DIV>the LDAPConstraints object.&nbsp; The boolean doReferrals parameter</D=
IV>
<DIV>controls whether referrals are followed or not.&nbsp; The default</DIV=
>
<DIV>for this parameter is "FALSE", i.e. referrals are not</DIV>
<DIV>automatically followed [period].&nbsp; See also 4.7.8.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve<BR><BR>&gt;&gt;&gt; "Kurt D. Zeilenga" &lt;Kurt@OpenLDAP.org&gt=
;=20
22-Jan-01 11:47:32 PM &gt;&gt;&gt;<BR>At 05:13 PM 1/21/01 -0800, Rob =
Weltman=20
wrote:<BR>&gt;&nbsp; These are the issues that have been raised (that I am =
aware=20
of) with the latest Java LDAP Internet Draft (<A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-java-ap=
i-12.txt),">http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-jav=
a-api-12.txt),</A>=20
along with my own proposals for disposition.<BR><BR>I have a few other=20
issues.&nbsp; Many of these have been<BR>discussed=20
previously.<BR><BR>............cut................</DIV>
<DIV><BR>Appears the default behavior is to chase referrals.&nbsp; As=20
I've<BR>noted previously on this list, this is not a wise default =
from<BR>a=20
security perspective.&nbsp; The default should be not to chase<BR>referrals=
=20
(period).<BR>.............cut................<BR><BR>Kurt<BR><BR></DIV></BO=
DY></HTML>

--=_02595884.6C0D5C17--



From list@netscape.com  Tue Jan 23 21:48:18 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA29396
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 21:48:17 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0O2kAb29684;
	Tue, 23 Jan 2001 18:46:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0O2kBw09334;
	Tue, 23 Jan 2001 18:46:11 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 18:46:11 -0800 (PST)
Message-Id: <sa6d6353.093@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 23 Jan 2001 10:56:10 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_297273D3.7F1E4F1C"
Resent-Message-ID: <"GNQEUD.A.eRC.yHkb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_297273D3.7F1E4F1C
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Rob,

I think the wording for the method getResponseControls in the
LDAPConnection class needs to be clarified slightly to clarify
that it applies only to non search operations, e.g.

"Returns the latest Server Controls for non search  operations
returned by a Directory Server with a response to an LDAP
request from the current thread, or null if the latest
response contained no Server Controls."

-Steve


------------------------
Steve Sonntag
Novell, Inc., the leading provider of Net services software



>>> Rob Weltman <robw@worldspot.com> 21-Jan-01 6:13:31 PM >>>
  These are the issues that have been raised (that I am aware of) with the =
latest Java LDAP Internet Draft (http://www.ietf.org/internet-drafts/draft-=
ietf-ldapext-ldap-java-api-12.txt), along with my own proposals for =
disposition.

  Nothing major, I don't think, and I'd like to conclude discussion on =
them in a week or so and update the Internet Draft.

Rob

--=_297273D3.7F1E4F1C
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px">
<DIV><FONT size=3D1></FONT>Rob,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I think the wording for the method getResponseControls in the</DIV>
<DIV>LDAPConnection class needs to be clarified slightly to clarify</DIV>
<DIV>that it applies only to non search operations, e.g.</DIV>
<DIV>&nbsp;</DIV>
<DIV>"Returns the latest Server Controls for non search&nbsp; operations</D=
IV>
<DIV>returned by a Directory Server&nbsp;with a response to an LDAP</DIV>
<DIV>request from the current thread, or null&nbsp;if the latest</DIV>
<DIV>response contained no Server Controls."</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>------------------------<BR>Steve Sonntag<BR>Novell, Inc., the =
leading=20
provider of Net services software</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; 21-Jan-01 =
6:13:31=20
PM &gt;&gt;&gt;<BR>&nbsp; These are the issues that have been raised (that =
I am=20
aware of) with the latest Java LDAP Internet Draft (<A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-java-ap=
i-12.txt),">http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-jav=
a-api-12.txt),</A>=20
along with my own proposals for disposition.<BR><BR>&nbsp; Nothing major, =
I=20
don't think, and I'd like to conclude discussion on them in a week or so =
and=20
update the Internet Draft.<BR><BR>Rob<BR><BR><BR></DIV></BODY></HTML>

--=_297273D3.7F1E4F1C--



From list@netscape.com  Tue Jan 23 22:40:24 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA00972
	for <ldapext-archive@odin.ietf.org>; Tue, 23 Jan 2001 22:40:23 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0O3cFG20156;
	Tue, 23 Jan 2001 19:38:15 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0O3cHY27140;
	Tue, 23 Jan 2001 19:38:17 -0800 (PST)
Resent-Date: Tue, 23 Jan 2001 19:38:17 -0800 (PST)
Message-Id: <5.0.2.1.0.20010123192837.00a86400@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 23 Jan 2001 19:37:53 -0800
To: "Steve Sonntag" <VTAG@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Open issues with the Java LDAP API draft
Cc: <robw@worldspot.com>, <ietf-ldapext@netscape.com>
In-Reply-To: <sa6d5724.087@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"mM71OB.A.ynG.o4kb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 10:04 AM 1/23/01 -0700, Steve Sonntag wrote:
>The default behavior for following referrals is specified in
>the LDAPConstraints object.  The boolean doReferrals parameter
>controls whether referrals are followed or not.  The default
>for this parameter is "FALSE", i.e. referrals are not
>automatically followed [period].  See also 4.7.8.

I was mislead by section 1 (top of page 10).  A clarification
in this paragraph as to the default behavior might be appropriate.

Kurt



From list@netscape.com  Wed Jan 24 11:52:45 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA25314
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 11:52:44 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OGp1b19246;
	Wed, 24 Jan 2001 08:51:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OGp1k28966;
	Wed, 24 Jan 2001 08:51:01 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 08:51:01 -0800 (PST)
Message-Id: <sa6ea564.060@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 24 Jan 2001 09:50:28 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_FEA5A6C4.AECF9DF9"
Resent-Message-ID: <"Q9Xor.A.UEH.0fwb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_FEA5A6C4.AECF9DF9
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable


LDAPReferralException=20

4.27 public class LDAPReferralException=20
                  extends LDAPException=20
   =20
   This exception, derived from LDAPException, is thrown when a server=20
   returns a referral and automatic referral following has not been=20
   enabled.=20

Add to the above

    or automatic referral following could not follow any referrals.

-Steve

--=_FEA5A6C4.AECF9DF9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>&nbsp;</DIV>
<DIV>LDAPReferralException </DIV>
<DIV>&nbsp;</DIV>
<DIV>4.27 public class LDAPReferralException=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
extends LDAPException <BR>&nbsp;&nbsp;&nbsp; <BR>&nbsp;&nbsp; This =
exception,=20
derived from LDAPException, is thrown when a server <BR>&nbsp;&nbsp; =
returns a=20
referral and automatic referral following has not been <BR>&nbsp;&nbsp; =
enabled.=20
<BR></DIV>
<DIV>Add to the above</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp; or automatic referral following could not follow =
any=20
referrals.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV></BODY></HTML>

--=_FEA5A6C4.AECF9DF9--



From list@netscape.com  Wed Jan 24 12:10:07 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25663
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 12:10:07 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OH6xG24136;
	Wed, 24 Jan 2001 09:06:59 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OH6wI24226;
	Wed, 24 Jan 2001 09:06:58 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 09:06:58 -0800 (PST)
Message-ID: <3A6F0C9F.4B4D0333@worldspot.com>
Date: Wed, 24 Jan 2001 09:10:55 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: Steve Sonntag <VTAG@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Open issues with the Java LDAP API draft
References: <sa6ea564.061@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"8UzY_.A.N5F.vuwb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Steve Sonntag wrote:

>   LDAPReferralException 4.27 public class LDAPReferralException
>                   extends LDAPException
>
>    This exception, derived from LDAPException, is thrown when a server
>    returns a referral and automatic referral following has not been
>    enabled.Add to the above     or automatic referral following could not follow any referrals. -Steve

  That sounds hard to handle for a client. Are you thinking of the case where the referral points to a server which is inaccessible or which doesn't accept the credentials of the requestor? How would the client know which of those problems was being flagged if there is only a referral exception? And consequently, how would the client know what to do about it?

Rob




From list@netscape.com  Wed Jan 24 12:33:19 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26080
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 12:33:19 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OHVeb27211;
	Wed, 24 Jan 2001 09:31:40 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OHVeI04783;
	Wed, 24 Jan 2001 09:31:40 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 09:31:40 -0800 (PST)
Reply-To: hahnt@us.ibm.com
X-Priority: 3 (Normal)
Importance: Normal
To: ietf-ldapext@netscape.com
Subject: Comments on draft-seilenga-lldap-cancel-00.txt
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
From: "Timothy Hahn" <hahnt@us.ibm.com>
Message-ID: <OF5AB9A3F1.885A7409-ON852569DE.006005DD@pok.ibm.com>
Date: Wed, 24 Jan 2001 12:31:35 -0500
X-MIMETrack: Serialize by Router on D01MLC96/01/M/IBM(Release 5.0.6 |January 4, 2001) at
 01/24/2001 12:31:36 PM,
	Serialize complete at 01/24/2001 12:31:36 PM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 006005F1852569DE_="
Resent-Message-ID: <"zkkr6D.A.dKB.7Fxb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multipart message in MIME format.
--=_alternative 006005F1852569DE_=
Content-Type: text/plain; charset="us-ascii"

Greetings,

In section 4.1, the existing return codes for the protocol are being added 
to with four additional values.  The values seem appropriate only for the 
Cancel extended operation.

I suggest that the existing return codes are not changed.  Rather, I 
suggest that the Cancel Response contain:

CancelResponseValue ::= SEQUENCE {
        cancelResultCode ENUMERATED {
                canceled (0),
                noSuchOperation (1),
                tooLate (2),
                cannotCancel (3)
        }
}

This way, the existing protocol data elements are not infringed upon by 
the added extended operation.

My other commnets are editorial and will be sent directly to Kurt.

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681
--=_alternative 006005F1852569DE_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Greetings,</font>
<br>
<br><font size=2 face="sans-serif">In section 4.1, the existing return codes for the protocol are being added to with four additional values. &nbsp;The values seem appropriate only for the Cancel extended operation.</font>
<br>
<br><font size=2 face="sans-serif">I suggest that the existing return codes are not changed. &nbsp;Rather, I suggest that the Cancel Response contain:</font>
<br>
<br><font size=2 face="sans-serif">CancelResponseValue ::= SEQUENCE {</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cancelResultCode ENUMERATED {</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; canceled (0),</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; noSuchOperation (1),</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; tooLate (2),</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cannotCancel (3)</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; }</font>
<br><font size=2 face="sans-serif">}</font>
<br>
<br><font size=2 face="sans-serif">This way, the existing protocol data elements are not infringed upon by the added extended operation.</font>
<br>
<br><font size=2 face="sans-serif">My other commnets are editorial and will be sent directly to Kurt.<br>
</font>
<br><font size=2 face="sans-serif">Regards,<br>
Tim Hahn<br>
<br>
Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681</font>
--=_alternative 006005F1852569DE_=--



From list@netscape.com  Wed Jan 24 13:53:55 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27891
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 13:53:55 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OIokG14488;
	Wed, 24 Jan 2001 10:50:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OIol213825;
	Wed, 24 Jan 2001 10:50:47 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 10:50:47 -0800 (PST)
Message-Id: <5.0.2.1.0.20010124095004.00ab4bb0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 24 Jan 2001 10:49:39 -0800
To: hahnt@us.ibm.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Comments on draft-seilenga-lldap-cancel-00.txt
Cc: ietf-ldapext@netscape.com
In-Reply-To: <OF5AB9A3F1.885A7409-ON852569DE.006005DD@pok.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"KyhA4D.A.vXD.GQyb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Note that the 'canceled' resultCode is to be returned by
canceled operation, not the cancel operation.  I find it
inappropriate to overload this condition onto any other
resultCode.  They already have defined semantics.  The
semantics of being canceled is orthogonal to these
semantics.  Hence, I believe adding an additional resultCode
is, IMO, justified.  I could make similar arguments
with respect to the other result codes.

However, I think the basic issue here is whether or not a
protocol extension to LDAP can amend the ASN.1.  I believe
limited amendments can be made, including:
        - additional elements may be added to sequences, and
        - additional choices may be added,
        - additional values may be added to enumerations.

The base specification states how implementations faced with
unrecognized protocol elements should behave.  However, I
do believe that no extensions should be provided without
mutual agreement of the protocol peers.

Kurt

At 12:31 PM 1/24/01 -0500, Timothy Hahn wrote:

>Greetings, 
>
>In section 4.1, the existing return codes for the protocol are being added to with four additional values.  The values seem appropriate only for the Cancel extended operation. 
>
>I suggest that the existing return codes are not changed.  Rather, I suggest that the Cancel Response contain: 
>
>CancelResponseValue ::= SEQUENCE { 
>        cancelResultCode ENUMERATED { 
>                canceled (0), 
>                noSuchOperation (1), 
>                tooLate (2), 
>                cannotCancel (3) 
>        } 
>} 
>
>This way, the existing protocol data elements are not infringed upon by the added extended operation. 
>
>My other commnets are editorial and will be sent directly to Kurt.
>
>Regards,
>Tim Hahn
>
>Internet: hahnt@us.ibm.com
>Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
>phone: 607.752.6388     tie-line: 8/852.6388
>fax: 607.752.3681 



From list@netscape.com  Wed Jan 24 14:07:06 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28138
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 14:07:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OJ58G17108;
	Wed, 24 Jan 2001 11:05:09 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OJ58c20697;
	Wed, 24 Jan 2001 11:05:09 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 11:05:09 -0800 (PST)
Message-Id: <sa6ec3bd.078@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 24 Jan 2001 11:59:55 -0700
From: "Jim Sermersheim" <JIMSE@novell.com>
To: <Kurt@openldap.org>, <hahnt@us.ibm.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Comments on draft-seilenga-lldap-cancel-00.txt
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0OJ57v20573
Resent-Message-ID: <"DhjozB.A.CDF.jdyb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/24/01 11:49:39 AM >>>
<snip>
>However, I think the basic issue here is whether or not a
>protocol extension to LDAP can amend the ASN.1.  I believe
>limited amendments can be made, including:
>        - additional elements may be added to sequences, and

I agree

>        - additional choices may be added,

I agree

>        - additional values may be added to enumerations.

I cannot find the clause that allows this, can you explain?

Jim



From list@netscape.com  Wed Jan 24 14:07:30 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28203
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 14:07:30 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OJ66G17734;
	Wed, 24 Jan 2001 11:06:07 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OJ66w21564;
	Wed, 24 Jan 2001 11:06:06 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 11:06:06 -0800 (PST)
Reply-To: <John.Liang@openwave.com>
From: "John Liang" <John.Liang@openwave.com>
To: <ietf-ldapext@netscape.com>
Subject: matching rule for server side sorting
Date: Wed, 24 Jan 2001 14:05:51 -0500
Message-ID: <001401c08638$ab3b88b0$07a75b18@ne.mediaone.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Resent-Message-ID: <"FdkztC.A.qQF.deyb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

HI there,

For the matchingrule in the client request of server side sorting,
is it the oid or the string name of this matchingrule?

Let us say, for  matchingrules: ( 2.5.13.18 NAME 
'octetStringOrderingMatch' SYNTAX
1.3.6.1.4.1.1466.115.121.1.40 ). Is it 'octetStringOrderingMatch'
or 1.3.6.1.4.1.1466.115.121.1.40?

Thanks,
--
John Liang




From list@netscape.com  Wed Jan 24 14:24:39 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28464
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 14:24:39 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OJMfb24687;
	Wed, 24 Jan 2001 11:22:41 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OJMfY28538;
	Wed, 24 Jan 2001 11:22:41 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 11:22:41 -0800 (PST)
Message-Id: <sa6ec7a7.031@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 24 Jan 2001 12:16:34 -0700
From: "Jim Sermersheim" <JIMSE@novell.com>
To: <ietf-ldapext@netscape.com>
Cc: <d.w.chadwick@iti.salford.ac.uk>
Subject: Alias pointing to ancestor
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0OJMdv28499
Resent-Message-ID: <"GGrOPD.A.c9G._tyb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

A question has risen in the context of some interoperability tests regarding whether it is allowed to have an alias entry that points to an ancestor entry.

I can't find any reference to this in X.501. I see in section 9.5 that an alias can point to a non-leaf, as well as to another alias, but it doesn't mention pointing to accentors.

I assume it's disallowed, otherwise there should be an instruction regarding how circular dereferencing is to be handled. I couldn't find anything like that in X.511.

Is any of this talked about and I'm just missing it?

Jim



From list@netscape.com  Wed Jan 24 14:40:55 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28694
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 14:40:54 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OJcfG24609;
	Wed, 24 Jan 2001 11:38:42 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OJcfA05527;
	Wed, 24 Jan 2001 11:38:41 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 11:38:41 -0800 (PST)
Message-Id: <5.0.2.1.0.20010124111050.00ada8a0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 24 Jan 2001 11:36:57 -0800
To: "Jim Sermersheim" <JIMSE@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Comments on draft-seilenga-lldap-cancel-00.txt
Cc: <hahnt@us.ibm.com>, <ietf-ldapext@netscape.com>
In-Reply-To: <sa6ec3bd.078@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"YQ4_KC.A.FWB.A9yb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 11:59 AM 1/24/01 -0700, Jim Sermersheim wrote:
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/24/01 11:49:39 AM >>>
><snip>
>>However, I think the basic issue here is whether or not a
>>protocol extension to LDAP can amend the ASN.1.  I believe
>>limited amendments can be made, including:
>>        - additional elements may be added to sequences, and
>
>I agree

This is explicit in RFC 2251, Section 4.


>>        - additional choices may be added,
>
>I agree

There is no specific statement in RFC 2251 allowing such additions.


>>        - additional values may be added to enumerations.
>
>I cannot find the clause that allows this, can you explain?

There is no specific statement in RFC 2251 allowing such additions.

In my view, this I-D proposes a change to the LDAP protocol
using one of the provided extension mechanism.  That is, the
changes are only visible when the extension is being used
by mutual agreement of both peer.  If an extension mechanism
was not used, I would argue the version would have to be
incremented.




From list@netscape.com  Wed Jan 24 14:58:10 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29196
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 14:58:09 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OJuPb03153;
	Wed, 24 Jan 2001 11:56:25 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OJuPc14383;
	Wed, 24 Jan 2001 11:56:25 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 11:56:25 -0800 (PST)
X-Priority: 3 (Normal)
Importance: Normal
To: ietf-ldapext@netscape.com
Subject: Re: Comments on draft-seilenga-lldap-cancel-00.txt
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
From: "Timothy Hahn" <hahnt@us.ibm.com>
Message-ID: <OFB8F02EE4.F65096A6-ON852569DE.006C9A1E@pok.ibm.com>
Date: Wed, 24 Jan 2001 14:56:19 -0500
X-MIMETrack: Serialize by Router on D01MLC96/01/M/IBM(Release 5.0.6 |January 4, 2001) at
 01/24/2001 02:56:20 PM,
	Serialize complete at 01/24/2001 02:56:20 PM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 006D2F81852569DE_="
Resent-Message-ID: <"42MbMD.A.dgD.oNzb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multipart message in MIME format.
--=_alternative 006D2F81852569DE_=
Content-Type: text/plain; charset="us-ascii"

Kurt,

I see, from re-reading X.511 and the abandon description there that the 
original request should return the abandoned (in your description, 
canceled) indication.

This would seem to force the issue of having to add a value to the 
resultCode enumeration in the LDAPResult sequence.

While I am concerned about protocol element updates without some sort of 
version indication noting their addition, I understand your intent and 
your choice to augment the resultCode for the canceled value.  And if 
we're updating resultCode anyway, adding in the other three doesn't seem 
that much more of a leap.

The more general question of what are acceptable amendments to the ASN.1 
is an interesting topic that I hope the list discusses.

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681

To:     Timothy Hahn/Endicott/IBM@IBMUS
cc:     ietf-ldapext@netscape.com 
Subject:        Re: Comments on draft-seilenga-lldap-cancel-00.txt



Note that the 'canceled' resultCode is to be returned by
canceled operation, not the cancel operation.  I find it
inappropriate to overload this condition onto any other
resultCode.  They already have defined semantics.  The
semantics of being canceled is orthogonal to these
semantics.  Hence, I believe adding an additional resultCode
is, IMO, justified.  I could make similar arguments
with respect to the other result codes.

However, I think the basic issue here is whether or not a
protocol extension to LDAP can amend the ASN.1.  I believe
limited amendments can be made, including:
        - additional elements may be added to sequences, and
        - additional choices may be added,
        - additional values may be added to enumerations.

The base specification states how implementations faced with
unrecognized protocol elements should behave.  However, I
do believe that no extensions should be provided without
mutual agreement of the protocol peers.

Kurt

At 12:31 PM 1/24/01 -0500, Timothy Hahn wrote:

>Greetings,
>
>In section 4.1, the existing return codes for the protocol are being 
added to with four additional values.  The values seem appropriate only 
for the Cancel extended operation.
>
>I suggest that the existing return codes are not changed.  Rather, I 
suggest that the Cancel Response contain:
>
>CancelResponseValue ::= SEQUENCE {
>        cancelResultCode ENUMERATED {
>                canceled (0),
>                noSuchOperation (1),
>                tooLate (2),
>                cannotCancel (3)
>        }
>}
>
>This way, the existing protocol data elements are not infringed upon by 
the added extended operation.
>
>My other commnets are editorial and will be sent directly to Kurt.
>
>Regards,
>Tim Hahn
>
>Internet: hahnt@us.ibm.com
>Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
>phone: 607.752.6388     tie-line: 8/852.6388
>fax: 607.752.3681



--=_alternative 006D2F81852569DE_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Kurt,</font>
<br>
<br><font size=2 face="sans-serif">I see, from re-reading X.511 and the abandon description there that the original request should return the abandoned (in your description, canceled) indication.</font>
<br>
<br><font size=2 face="sans-serif">This would seem to force the issue of having to add a value to the resultCode enumeration in the LDAPResult sequence.</font>
<br>
<br><font size=2 face="sans-serif">While I am concerned about protocol element updates without some sort of version indication noting their addition, I understand your intent and your choice to augment the resultCode for the canceled value. &nbsp;And if we're updating resultCode anyway, adding in the other three doesn't seem that much more of a leap.</font>
<br>
<br><font size=2 face="sans-serif">The more general question of what are acceptable amendments to the ASN.1 is an interesting topic that I hope the list discusses.<br>
</font>
<br><font size=2 face="sans-serif">Regards,<br>
Tim Hahn<br>
<br>
Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681<br>
</font>
<p><font size=1 color=#800080 face="sans-serif">To: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">Timothy Hahn/Endicott/IBM@IBMUS</font>
<br><font size=1 color=#800080 face="sans-serif">cc: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">ietf-ldapext@netscape.com</font><font size=1 color=#800080 face="sans-serif"> </font>
<br><font size=1 color=#800080 face="sans-serif">Subject: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">Re: Comments on draft-seilenga-lldap-cancel-00.txt</font>
<br>
<br>
<br>
<br><font size=2><tt>Note that the 'canceled' resultCode is to be returned by<br>
canceled operation, not the cancel operation. &nbsp;I find it<br>
inappropriate to overload this condition onto any other<br>
resultCode. &nbsp;They already have defined semantics. &nbsp;The<br>
semantics of being canceled is orthogonal to these<br>
semantics. &nbsp;Hence, I believe adding an additional resultCode<br>
is, IMO, justified. &nbsp;I could make similar arguments<br>
with respect to the other result codes.<br>
</tt></font>
<br><font size=2><tt>However, I think the basic issue here is whether or not a<br>
protocol extension to LDAP can amend the ASN.1. &nbsp;I believe<br>
limited amendments can be made, including:<br>
 &nbsp; &nbsp; &nbsp; &nbsp;- additional elements may be added to sequences, and<br>
 &nbsp; &nbsp; &nbsp; &nbsp;- additional choices may be added,<br>
 &nbsp; &nbsp; &nbsp; &nbsp;- additional values may be added to enumerations.<br>
</tt></font>
<br><font size=2><tt>The base specification states how implementations faced with<br>
unrecognized protocol elements should behave. &nbsp;However, I<br>
do believe that no extensions should be provided without<br>
mutual agreement of the protocol peers.<br>
</tt></font>
<br><font size=2><tt>Kurt<br>
</tt></font>
<br><font size=2><tt>At 12:31 PM 1/24/01 -0500, Timothy Hahn wrote:<br>
</tt></font>
<br><font size=2><tt>&gt;Greetings,<br>
&gt;<br>
&gt;In section 4.1, the existing return codes for the protocol are being added to with four additional values. &nbsp;The values seem appropriate only for the Cancel extended operation.<br>
&gt;<br>
&gt;I suggest that the existing return codes are not changed. &nbsp;Rather, I suggest that the Cancel Response contain:<br>
&gt;<br>
&gt;CancelResponseValue ::= SEQUENCE {<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;cancelResultCode ENUMERATED {<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;canceled (0),<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;noSuchOperation (1),<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;tooLate (2),<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;cannotCancel (3)<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp;}<br>
&gt;}<br>
&gt;<br>
&gt;This way, the existing protocol data elements are not infringed upon by the added extended operation.<br>
&gt;<br>
&gt;My other commnets are editorial and will be sent directly to Kurt.<br>
&gt;<br>
&gt;Regards,<br>
&gt;Tim Hahn<br>
&gt;<br>
&gt;Internet: hahnt@us.ibm.com<br>
&gt;Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
&gt;phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
&gt;fax: 607.752.3681</tt></font>
<br>
<br>
<br>
--=_alternative 006D2F81852569DE_=--



From list@netscape.com  Wed Jan 24 15:09:37 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA29608
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 15:09:36 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OK7UG01128;
	Wed, 24 Jan 2001 12:07:30 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OK7VY19291;
	Wed, 24 Jan 2001 12:07:31 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 12:07:31 -0800 (PST)
Message-ID: <EB21C070AA75D311A0AC0090271EC45C06517892@us-tr-exch-1.tr.unisys.com>
From: "Salter, Thomas A" <Thomas.Salter@unisys.com>
To: Jim Sermersheim <JIMSE@novell.com>, ietf-ldapext@netscape.com
Cc: d.w.chadwick@iti.salford.ac.uk
Subject: RE: Alias pointing to ancestor
Date: Wed, 24 Jan 2001 14:07:01 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Resent-Message-ID: <"M5Av6C.A.JtE.BYzb6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

(I glad to see you copied David Chadwick.)  In his book, Understanding
X.500, he states that the '93 standards allow for circular references and
require the DSA to avoid looping by keeping track of which parts of the tree
have already been searched.  (Section 5.10, p.149)

I can't find an explicit reference in the X.500 standards.  The closest
thing I found is the flowchart in Figure B.10 in Annex B of X.511.  Next to
a decision box labeled "alias object name to be considered?" is the note
"e.g., not already included; does not lead to search loop".

It thus appears the intent was to allow circular references.


A related question that came up in interoperability testing some time ago
had to do with order of the evaluation of search filters and dereferencing
of aliases.  The flowchart B.9 in X.511 clearly indicates that aliases are
dereferenced before the search filters are applied.


 > -----Original Message-----
 > From: Jim Sermersheim [mailto:JIMSE@novell.com]
 > Sent: Wednesday, January 24, 2001 2:17 PM
 > To: ietf-ldapext@netscape.com
 > Cc: d.w.chadwick@iti.salford.ac.uk
 > Subject: Alias pointing to ancestor
 > 
 > 
 > A question has risen in the context of some interoperability 
 > tests regarding whether it is allowed to have an alias entry 
 > that points to an ancestor entry.
 > 
 > I can't find any reference to this in X.501. I see in 
 > section 9.5 that an alias can point to a non-leaf, as well 
 > as to another alias, but it doesn't mention pointing to accentors.
 > 
 > I assume it's disallowed, otherwise there should be an 
 > instruction regarding how circular dereferencing is to be 
 > handled. I couldn't find anything like that in X.511.
 > 
 > Is any of this talked about and I'm just missing it?
 > 
 > Jim
 > 



From list@netscape.com  Wed Jan 24 17:01:36 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA01326
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 17:01:36 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0OLxoG20625;
	Wed, 24 Jan 2001 13:59:50 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0OLxos10228;
	Wed, 24 Jan 2001 13:59:50 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 13:59:50 -0800 (PST)
Message-Id: <sa6eed82.001@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 24 Jan 2001 14:58:05 -0700
From: "Jim Sermersheim" <JIMSE@novell.com>
To: <Kurt@openldap.org>
Cc: <ietf-ldapext@netscape.com>, <hahnt@us.ibm.com>
Subject: Re: Comments on draft-seilenga-lldap-cancel-00.txt
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0OLxmv10204
Resent-Message-ID: <"ZF86dC.A.ifC.VB1b6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/24/01 12:36:57 PM >>>
<snip>
>In my view, this I-D proposes a change to the LDAP protocol
>using one of the provided extension mechanism.  That is, the
>changes are only visible when the extension is being used
>by mutual agreement of both peer.  If an extension mechanism
>was not used, I would argue the version would have to be
>incremented.

This may be a good philosophy, but before it's practiced in I-D's headed for standards track , I think this larger issue should be itself standardized. This kind of thing can be seen by people to extend past the three ammendments you outlined. For example, I remember one of the delete subtree drafts attempting to override protocol behavior (not just wire protocol).

Jim





From list@netscape.com  Wed Jan 24 18:49:08 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA02340
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 18:49:08 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ONj0G14466;
	Wed, 24 Jan 2001 15:45:00 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0ONj0E27294;
	Wed, 24 Jan 2001 15:45:00 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 15:45:00 -0800 (PST)
Message-Id: <5.0.2.1.0.20010124141802.00a56d60@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 24 Jan 2001 15:44:17 -0800
To: "Jim Sermersheim" <JIMSE@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Comments on draft-seilenga-lldap-cancel-00.txt
Cc: <ietf-ldapext@netscape.com>
In-Reply-To: <sa6eed82.001@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"hl9LQC.A.npG.6j2b6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 02:58 PM 1/24/01 -0700, Jim Sermersheim wrote:
>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/24/01 12:36:57 PM >>>
><snip>
>>In my view, this I-D proposes a change to the LDAP protocol
>>using one of the provided extension mechanism.  That is, the
>>changes are only visible when the extension is being used
>>by mutual agreement of both peer.  If an extension mechanism
>>was not used, I would argue the version would have to be
>>incremented.
>
>This may be a good philosophy, but before it's practiced in I-D's headed for standards track, I think this larger issue should be itself standardized.

Well, this I-D is certainly not the first I-D to require
amendments to the ASN.1.  There have been I-D published
suggesting new CHOICEs and/or ENUMERATION values.

I believe it a reasonable interpretation of RFC 2251 that
such is allowed.  I don't view anything in RFC 2251 as
restricting the scope of what extensions might be engineered.
Some extensions requires changes to the ASN.1.  As long
as these changes don't break interoperability with peers
which do not implement the extension, there is no problem.

One could argue that no changes to the ASN.1 is allowed as
no extensibility markers were provided.  If one were to take
this stand, the following types of extensions would be disallowed:
  - additional PDUs (e.g.: partialExtendedResponse)
  - additional authentication methods (these exist)
  - additional search scopes (forthcoming)
  - additional filter choices (extensibleMatching is
    not necessarily extensible enough)

But I note that 2251 failed to use extensibility markers even
where it explicitly stated extensibility is allowed.

I also note that disallowing additional result codes leads
to overloading of existing result codes.  This leads to
significant interoperability problems as it becomes unclear
as to which semantics were meant.

> This kind of thing can be seen by people to extend past the three ammendments you outlined.

I don't think you can stop folks from suggesting odd semantics.
Luckily, we have a fairly active review community which keeps
these from getting progressed on the standard track.

I don't this I-D will have much impact on what others may
or may not suggest otherwise.  A revision to RFC 2251 might
help (that's an LDAPbis issue).  A informational guide on
extension do's and don't might help (that's an LDAPext issue).




  




From bounce-back@phl7.note.com  Wed Jan 24 19:44:09 2001
Received: from phl7.note.com (phl7.note.com [207.8.131.194])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA02608
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 19:44:09 -0500 (EST)
Received: (qmail 24418 invoked by uid 712); 25 Jan 2001 00:44:04 -0000
Date: 25 Jan 2001 00:44:04 -0000
Message-ID: <20010125004404.24406.qmail@phl7.note.com>
From: BOSA2001@AOL.COM
To: <ldapext-archive@ietf.org>
X-Mailer: http://GetResponse.com v. 4.0
X-Originating-IP: not supplied
X-Complaints-To: abuse@GetResponse.com
X-Responder-ID: 101827
X-Remove-Address: ldapext-archive@odin.ietf.org
Ref-id: 000
X-Response-ID: bosa.IMPORT.0.ldapext-archive@odin.ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Subject: BETTER THAN VISA REBATES-MASTERGOLD

GUARANTEED CARD APPROVAL
No Credit or Bad Credit?
It Doesn't Matter!
MEMBERSHIP HAS ITS PRIVILEGES
No Credit Checks!
0% A.P.R.
EVERYONE QUALIFIES
No Social Insurance Number
No Income Verification
Bankruptcy "OK"
Private and Convenient
BUY FOR FREE . . . .
* Your commissions and bonus' could easily exceed your minimum payment from purchases *
MAKE NO PAYMENTS!
Everytime someone who you have sponsored makes a payment on their MASTERGOLD Card account you'll actually receive percentage of the payment as a credit towards your own account.  Receive enough credits and you won't have to make any payments.

For more information visit:   BOSA MASTERGOLD LINK  (www.hometown.aol.com/bosa2001)
<br>
<br>
---<br>
<font size="3" color="#000000">
To remove yourself from further mailings, <a href="http://GetResponse.com/r.cgi?a=bosa&e=ldapext-archive_Xyodin.ietf.org&i=0">click here!</a><br>
</font>


From list@netscape.com  Wed Jan 24 20:02:33 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA02810
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 20:02:33 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0P10Vb11827;
	Wed, 24 Jan 2001 17:00:32 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0P10Vk25542;
	Wed, 24 Jan 2001 17:00:31 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 17:00:31 -0800 (PST)
Message-ID: <6B33416BC4BBD411BCA6009027D0D18CDAFAE2@aspams01.ca.com>
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: hahnt@us.ibm.com, ietf-ldapext@netscape.com
Subject: RE: Comments on draft-seilenga-lldap-cancel-00.txt
Date: Thu, 25 Jan 2001 12:00:23 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Resent-Message-ID: <"FQ_bzD.A.zOG.uq3b6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

I think it is worth looking more closely at the result codes.
 
cancelled is the result returned in the original request (success is the
result returned in the abandon response but this doesn't appear).
 
noSuchOperation, tooLate and cannotCancel are returned in the abandon
response (there is no original request).
 
Therefore, only 'cancelled' need ba added to RFC 2251. All the others could
appear in a special
 
    CancelResponseValue ::= ENUMERATED { success(0), noSuchOperation(1),
tooLate(2), cannotCancel(3) }.
 
(I don't see any reason for the (redundant) SEQUENCE.)
 
Ron.

-----Original Message-----
From: Timothy Hahn [mailto:hahnt@us.ibm.com]
Sent: Thursday, 25 January 2001 4:32
To: ietf-ldapext@netscape.com
Subject: Comments on draft-seilenga-lldap-cancel-00.txt



Greetings, 

In section 4.1, the existing return codes for the protocol are being added
to with four additional values.  The values seem appropriate only for the
Cancel extended operation. 

I suggest that the existing return codes are not changed.  Rather, I suggest
that the Cancel Response contain: 

CancelResponseValue ::= SEQUENCE { 
        cancelResultCode ENUMERATED { 
                canceled (0), 
                noSuchOperation (1), 
                tooLate (2), 
                cannotCancel (3) 
        } 
} 

This way, the existing protocol data elements are not infringed upon by the
added extended operation. 

My other commnets are editorial and will be sent directly to Kurt.

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681



From list@netscape.com  Wed Jan 24 20:17:33 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA03055
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 20:17:32 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0P1Fob15205;
	Wed, 24 Jan 2001 17:15:50 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0P1FpM03785;
	Wed, 24 Jan 2001 17:15:51 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 17:15:51 -0800 (PST)
Message-ID: <6B33416BC4BBD411BCA6009027D0D18CDAFBED@aspams01.ca.com>
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Salter, Thomas A" <Thomas.Salter@unisys.com>,
        Jim Sermersheim
	 <JIMSE@novell.com>, ietf-ldapext@netscape.com
Cc: d.w.chadwick@iti.salford.ac.uk
Subject: RE: Alias pointing to ancestor
Date: Thu, 25 Jan 2001 12:15:35 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Resent-Message-ID: <"-v93qC.A.26.G53b6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Thomas,

The centre of your argument here is how search results are collated in the
presence of aliases. In this context it probably doesn't matter if they
point up or point down.

I think Jim was referring to the navigation issues of a chain of aliases
actually pointing to a member of the chain. This was addressed in X.500 with
the error aliasProblem.

Ron.

-----Original Message-----
From: Salter, Thomas A [mailto:Thomas.Salter@unisys.com]
Sent: Thursday, 25 January 2001 7:07
To: Jim Sermersheim; ietf-ldapext@netscape.com
Cc: d.w.chadwick@iti.salford.ac.uk
Subject: RE: Alias pointing to ancestor


(I glad to see you copied David Chadwick.)  In his book, Understanding
X.500, he states that the '93 standards allow for circular references and
require the DSA to avoid looping by keeping track of which parts of the tree
have already been searched.  (Section 5.10, p.149)

I can't find an explicit reference in the X.500 standards.  The closest
thing I found is the flowchart in Figure B.10 in Annex B of X.511.  Next to
a decision box labeled "alias object name to be considered?" is the note
"e.g., not already included; does not lead to search loop".

It thus appears the intent was to allow circular references.


A related question that came up in interoperability testing some time ago
had to do with order of the evaluation of search filters and dereferencing
of aliases.  The flowchart B.9 in X.511 clearly indicates that aliases are
dereferenced before the search filters are applied.


 > -----Original Message-----
 > From: Jim Sermersheim [mailto:JIMSE@novell.com]
 > Sent: Wednesday, January 24, 2001 2:17 PM
 > To: ietf-ldapext@netscape.com
 > Cc: d.w.chadwick@iti.salford.ac.uk
 > Subject: Alias pointing to ancestor
 > 
 > 
 > A question has risen in the context of some interoperability 
 > tests regarding whether it is allowed to have an alias entry 
 > that points to an ancestor entry.
 > 
 > I can't find any reference to this in X.501. I see in 
 > section 9.5 that an alias can point to a non-leaf, as well 
 > as to another alias, but it doesn't mention pointing to accentors.
 > 
 > I assume it's disallowed, otherwise there should be an 
 > instruction regarding how circular dereferencing is to be 
 > handled. I couldn't find anything like that in X.511.
 > 
 > Is any of this talked about and I'm just missing it?
 > 
 > Jim
 > 



From list@netscape.com  Wed Jan 24 20:37:47 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA03263
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 20:37:46 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0P1YjG05365;
	Wed, 24 Jan 2001 17:34:46 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0P1Ykk12283;
	Wed, 24 Jan 2001 17:34:46 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 17:34:46 -0800 (PST)
Message-Id: <5.0.2.1.0.20010124171609.00aca300@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 24 Jan 2001 17:31:15 -0800
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: RE: Comments on draft-seilenga-lldap-cancel-00.txt
Cc: hahnt@us.ibm.com, ietf-ldapext@netscape.com
In-Reply-To: <6B33416BC4BBD411BCA6009027D0D18CDAFAE2@aspams01.ca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"k5kZsD.A.d_C.0K4b6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 12:00 PM 1/25/01 +1100, Ramsay, Ron wrote:
>I think it is worth looking more closely at the result codes.
> 
>cancelled is the result returned in the original request (success is the
>result returned in the abandon response but this doesn't appear).
> 
>noSuchOperation, tooLate and cannotCancel are returned in the abandon
>response (there is no original request).
> 
>Therefore, only 'cancelled' need ba added to RFC 2251. All the others could
>appear in a special
> 
>    CancelResponseValue ::= ENUMERATED { success(0), noSuchOperation(1),
>tooLate(2), cannotCancel(3) }.

Yeah, but, the extendedResponse would need to return a resultCode.
One could say it always returned success and the client should
look at the response value for details.  That is, the operation
could return:
        success with response value success,
        success with response value noSuchOperation,
        success with tooLate,
       success with cannotCancel,
       protocolError, and
        other non-success resultCodes (especially in
          the face of extension by control)

Overloading success is bad.  Overloading other resultCodes
is equally bad.

IMO, adding new resultCodes is the most sound approach.

PS: SEQUENCE provides extensibility



From list@netscape.com  Wed Jan 24 20:53:05 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA03419
	for <ldapext-archive@odin.ietf.org>; Wed, 24 Jan 2001 20:53:04 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0P1ouG12899;
	Wed, 24 Jan 2001 17:50:56 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0P1ouc18505;
	Wed, 24 Jan 2001 17:50:56 -0800 (PST)
Resent-Date: Wed, 24 Jan 2001 17:50:56 -0800 (PST)
X-Priority: 3 (Normal)
Importance: Normal
To: ietf-ldapext@netscape.com
Subject: RE: Comments on draft-seilenga-lldap-cancel-00.txt
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
From: "Timothy Hahn" <hahnt@us.ibm.com>
Message-ID: <OFB137CABA.EBF600BC-ON852569DF.0007B97A@pok.ibm.com>
Date: Wed, 24 Jan 2001 20:50:49 -0500
X-MIMETrack: Serialize by Router on D01MLC96/01/M/IBM(Release 5.0.6 |January 4, 2001) at
 01/24/2001 08:50:52 PM,
	Serialize complete at 01/24/2001 08:50:52 PM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 0007D9B6852569DF_="
Resent-Message-ID: <"iiPubC.A.0gE.-Z4b6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multipart message in MIME format.
--=_alternative 0007D9B6852569DF_=
Content-Type: text/plain; charset="us-ascii"

Ron,

Sounds ok to me.

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681

To:     Timothy Hahn/Endicott/IBM@IBMUS, ietf-ldapext@netscape.com
cc: 
Subject:        RE: Comments on draft-seilenga-lldap-cancel-00.txt



I think it is worth looking more closely at the result codes.

cancelled is the result returned in the original request (success is the
result returned in the abandon response but this doesn't appear).

noSuchOperation, tooLate and cannotCancel are returned in the abandon
response (there is no original request).

Therefore, only 'cancelled' need ba added to RFC 2251. All the others 
could
appear in a special

    CancelResponseValue ::= ENUMERATED { success(0), noSuchOperation(1),
tooLate(2), cannotCancel(3) }.

(I don't see any reason for the (redundant) SEQUENCE.)

Ron.

-----Original Message-----
From: Timothy Hahn [mailto:hahnt@us.ibm.com]
Sent: Thursday, 25 January 2001 4:32
To: ietf-ldapext@netscape.com
Subject: Comments on draft-seilenga-lldap-cancel-00.txt



Greetings,

In section 4.1, the existing return codes for the protocol are being added
to with four additional values.  The values seem appropriate only for the
Cancel extended operation.

I suggest that the existing return codes are not changed.  Rather, I 
suggest
that the Cancel Response contain:

CancelResponseValue ::= SEQUENCE {
        cancelResultCode ENUMERATED {
                canceled (0),
                noSuchOperation (1),
                tooLate (2),
                cannotCancel (3)
        }
}

This way, the existing protocol data elements are not infringed upon by 
the
added extended operation.

My other commnets are editorial and will be sent directly to Kurt.

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681



--=_alternative 0007D9B6852569DF_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Ron,</font>
<br>
<br><font size=2 face="sans-serif">Sounds ok to me.<br>
</font>
<br><font size=2 face="sans-serif">Regards,<br>
Tim Hahn<br>
<br>
Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681<br>
</font>
<p><font size=1 color=#800080 face="sans-serif">To: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">Timothy Hahn/Endicott/IBM@IBMUS, ietf-ldapext@netscape.com</font>
<br><font size=1 color=#800080 face="sans-serif">cc: &nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 color=#800080 face="sans-serif">Subject: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">RE: Comments on draft-seilenga-lldap-cancel-00.txt</font>
<br>
<br>
<br>
<br><font size=2><tt>I think it is worth looking more closely at the result codes.<br>
</tt></font>
<br><font size=2><tt>cancelled is the result returned in the original request (success is the<br>
result returned in the abandon response but this doesn't appear).<br>
</tt></font>
<br><font size=2><tt>noSuchOperation, tooLate and cannotCancel are returned in the abandon<br>
response (there is no original request).<br>
</tt></font>
<br><font size=2><tt>Therefore, only 'cancelled' need ba added to RFC 2251. All the others could<br>
appear in a special<br>
</tt></font>
<br><font size=2><tt>&nbsp; &nbsp; CancelResponseValue ::= ENUMERATED { success(0), noSuchOperation(1),<br>
tooLate(2), cannotCancel(3) }.<br>
</tt></font>
<br><font size=2><tt>(I don't see any reason for the (redundant) SEQUENCE.)<br>
</tt></font>
<br><font size=2><tt>Ron.<br>
</tt></font>
<br><font size=2><tt>-----Original Message-----<br>
From: Timothy Hahn [mailto:hahnt@us.ibm.com]<br>
Sent: Thursday, 25 January 2001 4:32<br>
To: ietf-ldapext@netscape.com<br>
Subject: Comments on draft-seilenga-lldap-cancel-00.txt<br>
</tt></font>
<br>
<br>
<br><font size=2><tt>Greetings,<br>
</tt></font>
<br><font size=2><tt>In section 4.1, the existing return codes for the protocol are being added<br>
to with four additional values. &nbsp;The values seem appropriate only for the<br>
Cancel extended operation.<br>
</tt></font>
<br><font size=2><tt>I suggest that the existing return codes are not changed. &nbsp;Rather, I suggest<br>
that the Cancel Response contain:<br>
</tt></font>
<br><font size=2><tt>CancelResponseValue ::= SEQUENCE {<br>
 &nbsp; &nbsp; &nbsp; &nbsp;cancelResultCode ENUMERATED {<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;canceled (0),<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;noSuchOperation (1),<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;tooLate (2),<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;cannotCancel (3)<br>
 &nbsp; &nbsp; &nbsp; &nbsp;}<br>
}<br>
</tt></font>
<br><font size=2><tt>This way, the existing protocol data elements are not infringed upon by the<br>
added extended operation.<br>
</tt></font>
<br><font size=2><tt>My other commnets are editorial and will be sent directly to Kurt.<br>
</tt></font>
<br><font size=2><tt>Regards,<br>
Tim Hahn<br>
</tt></font>
<br><font size=2><tt>Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681</tt></font>
<br>
<br>
<br>
--=_alternative 0007D9B6852569DF_=--



From list@netscape.com  Thu Jan 25 07:05:46 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA23823
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 07:05:45 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PC3Wb16676;
	Thu, 25 Jan 2001 04:03:32 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PC3Yc22593;
	Thu, 25 Jan 2001 04:03:34 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 04:03:34 -0800 (PST)
Message-Id: <200101251154.f0PBsNL67746@smtp24.singnet.com.sg>
X-Sender: eru1@apexmail.com
From: Webmaster <eru1@apexmail.com>
To: "eweb8" <eru1@apexmail.com>
Date: Thu, 25 Jan 2001 19:50:21 +0800
Subject: HURRY! JOIN FREE!! The Payline has begun FREE AIRMILES and TONS OF CASH!!
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Resent-Message-ID: <"9SjpWD.A.vgF.VYBc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
X-MIME-Autoconverted: from 8bit to quoted-printable by netscape.com id f0PC3Wb16676
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA23823

Hi,

Time is of essence.

The PayLine utilizes a radical system that rewards you based on how 
fast you can make a decision, and how many members you refer. The entire company 
is built on a linear referral link, which essentially means there is a straight 
line of referred members. 

The instant you enroll, every single new member who enrolls worldwide adds one 
mile to your air miles account. The PayLine’s unique organizational structure 
means that each and every person who becomes a member from the second you enroll 
is part of your network, whether you referred them or not. 

So, if you enrolled right now, and between now and the end of the day 
another 200 people became members of The PayLine, you would have 200 new members 
in your organization and an additional 200 miles in your air miles account. 
If you decided to wait until tomorrow to enroll, you would have missed out on 
200 miles! 

People are enrolling as you are reading this sentence, which means that every 
second counts. 

Hurry! Request for info!
mailto:iiinc@usa.com?subject=P_info pls!

Regards,
.......................................................................
To be removed from this mailing list please send mailto:kool2ksg@yahoo.com?subject=remove 
me!








From list@netscape.com  Thu Jan 25 11:23:44 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03044
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 11:23:42 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PGLab14309;
	Thu, 25 Jan 2001 08:21:36 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PGLaE06561;
	Thu, 25 Jan 2001 08:21:36 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 08:21:36 -0800 (PST)
Message-ID: <EB21C070AA75D311A0AC0090271EC45C0655403D@us-tr-exch-1.tr.unisys.com>
From: "Salter, Thomas A" <Thomas.Salter@unisys.com>
To: "Kurt D. Zeilenga" <Kurt@openldap.org>,
        "Ramsay, Ron"
	 <Ron.Ramsay@ca.com>
Cc: hahnt@us.ibm.com, ietf-ldapext@netscape.com
Subject: RE: Comments on draft-seilenga-lldap-cancel-00.txt
Date: Thu, 25 Jan 2001 10:20:28 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Resent-Message-ID: <"QYZ_dB.A.HmB.OKFc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Perhaps you need one new result code of "error, see extended response".
This is generic enough for use by all extended operations but doesn't
overload the existed status codes.

 > -----Original Message-----
 > From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
 > Sent: Wednesday, January 24, 2001 8:31 PM
 > To: Ramsay, Ron
 > Cc: hahnt@us.ibm.com; ietf-ldapext@netscape.com
 > Subject: RE: Comments on draft-seilenga-lldap-cancel-00.txt
 > 
 > 
 > At 12:00 PM 1/25/01 +1100, Ramsay, Ron wrote:
 > >I think it is worth looking more closely at the result codes.
 > > 
 > >cancelled is the result returned in the original request 
 > (success is the
 > >result returned in the abandon response but this doesn't appear).
 > > 
 > >noSuchOperation, tooLate and cannotCancel are returned in 
 > the abandon
 > >response (there is no original request).
 > > 
 > >Therefore, only 'cancelled' need ba added to RFC 2251. All 
 > the others could
 > >appear in a special
 > > 
 > >    CancelResponseValue ::= ENUMERATED { success(0), 
 > noSuchOperation(1),
 > >tooLate(2), cannotCancel(3) }.
 > 
 > Yeah, but, the extendedResponse would need to return a resultCode.
 > One could say it always returned success and the client should
 > look at the response value for details.  That is, the operation
 > could return:
 >         success with response value success,
 >         success with response value noSuchOperation,
 >         success with tooLate,
 >        success with cannotCancel,
 >        protocolError, and
 >         other non-success resultCodes (especially in
 >           the face of extension by control)
 > 
 > Overloading success is bad.  Overloading other resultCodes
 > is equally bad.
 > 
 > IMO, adding new resultCodes is the most sound approach.
 > 
 > PS: SEQUENCE provides extensibility
 > 



From list@netscape.com  Thu Jan 25 11:56:31 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03914
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 11:56:30 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PGsRb20529;
	Thu, 25 Jan 2001 08:54:27 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PGsRA24209;
	Thu, 25 Jan 2001 08:54:27 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 08:54:27 -0800 (PST)
Message-Id: <sa6ff678.078@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Thu, 25 Jan 2001 09:48:37 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <robw@worldspot.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_82D9C5F8.D3B2E054"
Resent-Message-ID: <"9xQMoB.A._5F.CpFc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_82D9C5F8.D3B2E054
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Actually, I was only taking the information given in the constructor
and copying it to the introduction of the class.

  public LDAPReferralException(String message,
                                LDAPException rootException)

   Constructs a default exception with a specified string as additional
   information and an exception that indicates a failure to follow a
   referral.  This exception applies only to synchronous operations and
   is thrown only on receipt of a referral when the referral was not
   followed.

As I was looking at this, I wondered if LDAPException is
too restrictive.  For example what is reported for a malformed URL?
We cannot report MalformedURLException as it is of type Exception.
Should the rootException be simply of type Exception?

Should the ReferralException class use matchedDN to indicate
which referral caused the problem, or is that overloading that field too =
much.

-Steve


Rob Weltman wrote:

> Steve Sonntag wrote:
>
> >   LDAPReferralException 4.27 public class LDAPReferralException
> >                   extends LDAPException
> >
> >    This exception, derived from LDAPException, is thrown when a server
> >    returns a referral and automatic referral following has not been
> >    enabled.Add to the above     or automatic referral following could =
not follow any referrals. -Steve
>
>   That sounds hard to handle for a client. Are you thinking of the case =
where the referral points to a server which is inaccessible or which =
doesn't accept the credentials of the requestor? How would the client know =
which of those problems was being flagged if there is only a referral =
exception? And consequently, how would the client know what to do about =
it?
>
> Rob

--=_82D9C5F8.D3B2E054
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>Actually, I was only taking the information given in the constructor<B=
R>and=20
copying it to the introduction of the class.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp; public LDAPReferralException(String=20
message,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
LDAPException rootException)</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; Constructs a default exception with a specified string =
as=20
additional<BR>&nbsp;&nbsp; information and an exception that indicates a =
failure=20
to follow a<BR>&nbsp;&nbsp; referral.&nbsp; This exception applies only =
to=20
synchronous operations and<BR>&nbsp;&nbsp; is thrown only on receipt of =
a=20
referral when the referral was not<BR>&nbsp;&nbsp; followed.</DIV>
<DIV>&nbsp;</DIV>
<DIV>As I was looking at this, I wondered if LDAPException is<BR>too=20
restrictive.&nbsp; For example what is reported for a malformed URL?<BR>We=
=20
cannot report MalformedURLException as it is of type Exception.<BR>Should =
the=20
rootException be simply of type Exception?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Should the ReferralException class use matchedDN to indicate<BR>which=
=20
referral caused the problem, or is that overloading that field too =
much.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>Rob Weltman wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; Steve Sonntag wrote:<BR>&gt;<BR>&gt; &gt;&nbsp;&nbsp;=20
LDAPReferralException 4.27 public class LDAPReferralException<BR>&gt;=20
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
extends LDAPException<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; This=20
exception, derived from LDAPException, is thrown when a server<BR>&gt;=20
&gt;&nbsp;&nbsp;&nbsp; returns a referral and automatic referral following =
has=20
not been<BR>&gt; &gt;&nbsp;&nbsp;&nbsp; enabled.Add to the=20
above&nbsp;&nbsp;&nbsp;&nbsp; or automatic referral following could not =
follow=20
any referrals. -Steve<BR>&gt;<BR>&gt;&nbsp;&nbsp; That sounds hard to =
handle for=20
a client. Are you thinking of the case where the referral points to a =
server=20
which is inaccessible or which doesn't accept the credentials of the =
requestor?=20
How would the client know which of those problems was being flagged if =
there is=20
only a referral exception? And consequently, how would the client know =
what to=20
do about it?<BR>&gt;<BR>&gt; Rob</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>&nbsp;</DIV></BODY></HTML>

--=_82D9C5F8.D3B2E054--



From list@netscape.com  Thu Jan 25 14:11:35 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06201
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 14:11:34 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PJ9GG11923;
	Thu, 25 Jan 2001 11:09:17 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PJ9G615783;
	Thu, 25 Jan 2001 11:09:16 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 11:09:16 -0800 (PST)
Message-Id: <sa7012c3.060@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Thu, 25 Jan 2001 11:49:18 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_742F3323.C5A4F675"
Resent-Message-ID: <"c6XaF.A.V2D.bnHc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_742F3323.C5A4F675
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

That is only partially true.  The connect call can get various IOExceptions=
 or
UnknownHostException which gets generalized to a less specific - more =
general
error CONNECT_ERROR.  Presumably, malformed URL could also be returned
as CONNECT_ERROR, but I like more information rather that less, so I agree
with your comment.  This would also change the LDAPUrl class which has
methods that return MalformedURLException.

I think the method name should be more descriptive of its function:

public String getFailedReferral()

Is is correct to presume that the status for the operation that generated
the referrals would the status of a referral that failed.  In the case of
search, should all other data be returned to the application before =
throwing
the Exception, or should the exception be thrown immediately?
The desired  behavior should be mentioned in the ID.

-Steve


>>> Rob Weltman <robw@worldspot.com> 25-Jan-01 10:18:13 AM >>>
  It could be Exception rather than LDAPException, although it might be =
better to add a result code for MalformedURL to LDAPException. LDAPExceptio=
n encapsulates more semantic information about the types of referral =
failures than other low-level exception classes.

  I wouldn't overload matchedDN for relaying the failed URL. It's meaning =
is, if anything, the opposite: the part of the DN of the URL that did =
match. Better to provide a new method to retrieve the invalid URL from =
LDAPReferralException:

public String getReferral()

  If there were multiple references processed, and all of them failed, =
this would report one of them.

Rob


Steve Sonntag wrote:

>  Actually, I was only taking the information given in the constructor
> and copying it to the introduction of the class.   public LDAPReferralExc=
eption(String message,
>                                 LDAPException rootException)    =
Constructs a default exception with a specified string as additional
>    information and an exception that indicates a failure to follow a
>    referral.  This exception applies only to synchronous operations and
>    is thrown only on receipt of a referral when the referral was not
>    followed. As I was looking at this, I wondered if LDAPException is
> too restrictive.  For example what is reported for a malformed URL?
> We cannot report MalformedURLException as it is of type Exception.
> Should the rootException be simply of type Exception? Should the =
ReferralException class use matchedDN to indicate
> which referral caused the problem, or is that overloading that field too =
much. -Steve
> Rob Weltman wrote: > Steve Sonntag wrote:
> >
> > >   LDAPReferralException 4.27 public class LDAPReferralException
> > >                   extends LDAPException
> > >
> > >    This exception, derived from LDAPException, is thrown when a =
server
> > >    returns a referral and automatic referral following has not been
> > >    enabled.Add to the above     or automatic referral following =
could not follow any referrals. -Steve
> >
> >   That sounds hard to handle for a client. Are you thinking of the =
case where the referral points to a server which is inaccessible or which =
doesn't accept the credentials of the requestor? How would the client know =
which of those problems was being flagged if there is only a referral =
exception? And consequently, how would the client know what to do about =
it?
> >
> > Rob

--=_742F3323.C5A4F675
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>That is only partially true.&nbsp; The connect call can get various=20=

IOExceptions or</DIV>
<DIV>UnknownHostException which gets generalized to a less specific - =
more=20
general</DIV>
<DIV>error CONNECT_ERROR.&nbsp; Presumably, malformed URL could also be=20
returned</DIV>
<DIV>as CONNECT_ERROR, but I like more information rather that less, so =
I=20
agree</DIV>
<DIV>with your comment.&nbsp; This would also change the LDAPUrl class =
which=20
has</DIV>
<DIV>methods that return MalformedURLException.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I think the method name should be more descriptive of its function:</D=
IV>
<DIV>&nbsp;</DIV>
<DIV>public String getFailedReferral()</DIV>
<DIV>&nbsp;</DIV>
<DIV>Is is correct to presume that the status for the operation that=20
generated</DIV>
<DIV>the referrals would the status of a referral that failed.&nbsp; In =
the case=20
of</DIV>
<DIV>search, should all other data be returned to the application =
before=20
throwing</DIV>
<DIV>the Exception, or should the exception be thrown immediately?</DIV>
<DIV>The desired&nbsp; behavior should be mentioned in the ID.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; 25-Jan-01 =
10:18:13 AM=20
&gt;&gt;&gt;<BR>&nbsp; It could be Exception rather than LDAPException, =
although=20
it might be better to add a result code for MalformedURL to LDAPException.=
=20
LDAPException encapsulates more semantic information about the types of =
referral=20
failures than other low-level exception classes.<BR><BR>&nbsp; I =
wouldn't=20
overload matchedDN for relaying the failed URL. It's meaning is, if =
anything,=20
the opposite: the part of the DN of the URL that did match. Better to =
provide a=20
new method to retrieve the invalid URL from LDAPReferralException:<BR><BR>p=
ublic=20
String getReferral()<BR><BR>&nbsp; If there were multiple references =
processed,=20
and all of them failed, this would report one of=20
them.<BR><BR>Rob<BR><BR><BR>Steve Sonntag wrote:<BR><BR>&gt;&nbsp; =
Actually, I=20
was only taking the information given in the constructor<BR>&gt; and =
copying it=20
to the introduction of the class.&nbsp;&nbsp; public=20
LDAPReferralException(String=20
message,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
LDAPException rootException)&nbsp;&nbsp;&nbsp; Constructs a default =
exception=20
with a specified string as additional<BR>&gt;&nbsp;&nbsp;&nbsp; information=
 and=20
an exception that indicates a failure to follow a<BR>&gt;&nbsp;&nbsp;&nbsp;=
=20
referral.&nbsp; This exception applies only to synchronous operations=20
and<BR>&gt;&nbsp;&nbsp;&nbsp; is thrown only on receipt of a referral when =
the=20
referral was not<BR>&gt;&nbsp;&nbsp;&nbsp; followed. As I was looking at =
this, I=20
wondered if LDAPException is<BR>&gt; too restrictive.&nbsp; For example =
what is=20
reported for a malformed URL?<BR>&gt; We cannot report MalformedURLExceptio=
n as=20
it is of type Exception.<BR>&gt; Should the rootException be simply of =
type=20
Exception? Should the ReferralException class use matchedDN to indicate<BR>=
&gt;=20
which referral caused the problem, or is that overloading that field too =
much.=20
-Steve<BR>&gt; Rob Weltman wrote: &gt; Steve Sonntag wrote:<BR>&gt; =
&gt;<BR>&gt;=20
&gt; &gt;&nbsp;&nbsp; LDAPReferralException 4.27 public class=20
LDAPReferralException<BR>&gt; &gt;=20
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
extends LDAPException<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;=
 This=20
exception, derived from LDAPException, is thrown when a server<BR>&gt; =
&gt;=20
&gt;&nbsp;&nbsp;&nbsp; returns a referral and automatic referral following =
has=20
not been<BR>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; enabled.Add to the=20
above&nbsp;&nbsp;&nbsp;&nbsp; or automatic referral following could not =
follow=20
any referrals. -Steve<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp; That sounds =
hard to=20
handle for a client. Are you thinking of the case where the referral =
points to a=20
server which is inaccessible or which doesn't accept the credentials of =
the=20
requestor? How would the client know which of those problems was being =
flagged=20
if there is only a referral exception? And consequently, how would the =
client=20
know what to do about it?<BR>&gt; &gt;<BR>&gt; &gt;=20
Rob<BR><BR><BR><BR><BR></DIV></BODY></HTML>

--=_742F3323.C5A4F675--



From list@netscape.com  Thu Jan 25 14:27:07 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06602
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 14:27:06 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PJP0b23993;
	Thu, 25 Jan 2001 11:25:00 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PJP0M26219;
	Thu, 25 Jan 2001 11:25:00 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 11:25:00 -0800 (PST)
Reply-To: hahnt@us.ibm.com
X-Priority: 3 (Normal)
Importance: Normal
To: ietf-ldapext@netscape.com
Subject: comments on draft-zeilenga-ldap-authpassword-04.txt
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
From: "Timothy Hahn" <hahnt@us.ibm.com>
Message-ID: <OFFCC8729E.A8FC2634-ON852569DF.006A736F@pok.ibm.com>
Date: Thu, 25 Jan 2001 14:24:51 -0500
X-MIMETrack: Serialize by Router on D01MLC96/01/M/IBM(Release 5.0.6 |January 4, 2001) at
 01/25/2001 02:24:56 PM,
	Serialize complete at 01/25/2001 02:24:56 PM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 006A7373852569DF_="
Resent-Message-ID: <"wnlsX.A.ZZG.L2Hc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multipart message in MIME format.
--=_alternative 006A7373852569DF_=
Content-Type: text/plain; charset="us-ascii"

Greetings,

Section 4.1, ABNF for authPasswordSyntax

I think that the "[authInfo]" can safely be "authInfo" since the 
separators ($ signs) are not optional and the authInfo can be zero length 
based on the definition of schemeSpecificValue.

Section 4.4

It would be nice to have a description for the attribute type.

Also, in paragraph 3, explaining why no built-in matching rule is defined 
for the attribute type.  With this said, what is the intent then of 
defining the "authPasswordMatch" matching rule?  Requiring the use of 
extensible match in order to use the matching rule seems harder than is 
necessary.  Why is it desireable to dis-allow modification of individual 
values (assuming that the underlying transport service guarantees 
confidentiality).

Thanks,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681
--=_alternative 006A7373852569DF_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Greetings,</font>
<br>
<br><font size=2 face="sans-serif">Section 4.1, ABNF for authPasswordSyntax</font>
<br>
<br><font size=2 face="sans-serif">I think that the &quot;[authInfo]&quot; can safely be &quot;authInfo&quot; since the separators ($ signs) are not optional and the authInfo can be zero length based on the definition of schemeSpecificValue.</font>
<br>
<br><font size=2 face="sans-serif">Section 4.4</font>
<br>
<br><font size=2 face="sans-serif">It would be nice to have a description for the attribute type.</font>
<br>
<br><font size=2 face="sans-serif">Also, in paragraph 3, explaining why no built-in matching rule is defined for the attribute type. &nbsp;With this said, what is the intent then of defining the &quot;authPasswordMatch&quot; matching rule? &nbsp;Requiring the use of extensible match in order to use the matching rule seems harder than is necessary. &nbsp;Why is it desireable to dis-allow modification of individual values (assuming that the underlying transport service guarantees confidentiality).</font>
<br><font size=2 face="sans-serif"><br>
Thanks,<br>
Tim Hahn<br>
<br>
Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681</font>
--=_alternative 006A7373852569DF_=--



From list@netscape.com  Thu Jan 25 16:38:08 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09364
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 16:38:07 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PLaLG06580;
	Thu, 25 Jan 2001 13:36:22 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PLaMk23650;
	Thu, 25 Jan 2001 13:36:22 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 13:36:22 -0800 (PST)
Message-Id: <5.0.2.1.0.20010125131311.00afae30@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 25 Jan 2001 13:35:18 -0800
To: hahnt@us.ibm.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: comments on draft-zeilenga-ldap-authpassword-04.txt
Cc: ietf-ldapext@netscape.com
In-Reply-To: <OFFCC8729E.A8FC2634-ON852569DF.006A736F@pok.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"GZY86C.A.QxF.VxJc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 02:24 PM 1/25/01 -0500, Timothy Hahn wrote:
>Section 4.1, ABNF for authPasswordSyntax 

seems reasonable.


>Section 4.4 
>It would be nice to have a description for the attribute type. 

seems reasonable.

>Also, in paragraph 3, explaining why no built-in matching rule is defined for the attribute type.

I can add one which has an assertion syntax of authPasswordSyntax.

>With this said, what is the intent then of defining the "authPasswordMatch" matching rule?

To allow a client to assert that a password, not an authPasswordSyntax
value, matches.

>Requiring the use of extensible match in order to use the matching rule seems harder than is necessary.

The authPasswordMatch as the EQUALITY matching rule would only
allow one scheme per password.

>Why is it desireable to dis-allow modification of individual values (assuming that the underlying transport service guarantees confidentiality). 

I'll remove this restriction and add an appropriate equality matching
rule.




From list@netscape.com  Thu Jan 25 16:46:57 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09488
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 16:46:55 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PLigG08340;
	Thu, 25 Jan 2001 13:44:42 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PLigs27846;
	Thu, 25 Jan 2001 13:44:42 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 13:44:42 -0800 (PST)
X-Priority: 3 (Normal)
Importance: Normal
To: ietf-ldapext@netscape.com
Subject: Re: comments on draft-zeilenga-ldap-authpassword-04.txt
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
From: "Timothy Hahn" <hahnt@us.ibm.com>
Message-ID: <OFC9DF839A.C1187038-ON852569DF.007710B2@pok.ibm.com>
Date: Thu, 25 Jan 2001 16:43:21 -0500
X-MIMETrack: Serialize by Router on D01MLC96/01/M/IBM(Release 5.0.6 |January 4, 2001) at
 01/25/2001 04:43:24 PM,
	Serialize complete at 01/25/2001 04:43:24 PM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 00771C6A852569DF_="
Resent-Message-ID: <"k6gVIB.A.UxG.F5Jc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multipart message in MIME format.
--=_alternative 00771C6A852569DF_=
Content-Type: text/plain; charset="us-ascii"

Kurt,

Sounds good.

Thanks,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681

To:     Timothy Hahn/Endicott/IBM@IBMUS
cc:     ietf-ldapext@netscape.com 
Subject:        Re: comments on draft-zeilenga-ldap-authpassword-04.txt



At 02:24 PM 1/25/01 -0500, Timothy Hahn wrote:
>Section 4.1, ABNF for authPasswordSyntax

seems reasonable.


>Section 4.4
>It would be nice to have a description for the attribute type.

seems reasonable.

>Also, in paragraph 3, explaining why no built-in matching rule is defined 
for the attribute type.

I can add one which has an assertion syntax of authPasswordSyntax.

>With this said, what is the intent then of defining the 
"authPasswordMatch" matching rule?

To allow a client to assert that a password, not an authPasswordSyntax
value, matches.

>Requiring the use of extensible match in order to use the matching rule 
seems harder than is necessary.

The authPasswordMatch as the EQUALITY matching rule would only
allow one scheme per password.

>Why is it desireable to dis-allow modification of individual values 
(assuming that the underlying transport service guarantees 
confidentiality).

I'll remove this restriction and add an appropriate equality matching
rule.




--=_alternative 00771C6A852569DF_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Kurt,</font>
<br>
<br><font size=2 face="sans-serif">Sounds good.<br>
</font>
<br><font size=2 face="sans-serif">Thanks,<br>
Tim Hahn<br>
<br>
Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681<br>
</font>
<p><font size=1 color=#800080 face="sans-serif">To: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">Timothy Hahn/Endicott/IBM@IBMUS</font>
<br><font size=1 color=#800080 face="sans-serif">cc: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">ietf-ldapext@netscape.com</font><font size=1 color=#800080 face="sans-serif"> </font>
<br><font size=1 color=#800080 face="sans-serif">Subject: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">Re: comments on draft-zeilenga-ldap-authpassword-04.txt</font>
<br>
<br>
<br>
<br><font size=2><tt>At 02:24 PM 1/25/01 -0500, Timothy Hahn wrote:<br>
&gt;Section 4.1, ABNF for authPasswordSyntax<br>
</tt></font>
<br><font size=2><tt>seems reasonable.<br>
</tt></font>
<br>
<br><font size=2><tt>&gt;Section 4.4<br>
&gt;It would be nice to have a description for the attribute type.<br>
</tt></font>
<br><font size=2><tt>seems reasonable.<br>
</tt></font>
<br><font size=2><tt>&gt;Also, in paragraph 3, explaining why no built-in matching rule is defined for the attribute type.<br>
</tt></font>
<br><font size=2><tt>I can add one which has an assertion syntax of authPasswordSyntax.<br>
</tt></font>
<br><font size=2><tt>&gt;With this said, what is the intent then of defining the &quot;authPasswordMatch&quot; matching rule?<br>
</tt></font>
<br><font size=2><tt>To allow a client to assert that a password, not an authPasswordSyntax<br>
value, matches.<br>
</tt></font>
<br><font size=2><tt>&gt;Requiring the use of extensible match in order to use the matching rule seems harder than is necessary.<br>
</tt></font>
<br><font size=2><tt>The authPasswordMatch as the EQUALITY matching rule would only<br>
allow one scheme per password.<br>
</tt></font>
<br><font size=2><tt>&gt;Why is it desireable to dis-allow modification of individual values (assuming that the underlying transport service guarantees confidentiality).<br>
</tt></font>
<br><font size=2><tt>I'll remove this restriction and add an appropriate equality matching<br>
rule.<br>
</tt></font>
<br>
<br>
<br>
--=_alternative 00771C6A852569DF_=--



From list@netscape.com  Thu Jan 25 16:52:13 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09674
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 16:52:12 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PLo3b23739;
	Thu, 25 Jan 2001 13:50:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PLo3o00721;
	Thu, 25 Jan 2001 13:50:03 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 13:50:03 -0800 (PST)
Message-Id: <sa703d0a.063@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Thu, 25 Jan 2001 14:49:38 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_D78C906A.96F7A4CA"
Resent-Message-ID: <"K8T80D.A.oK.I-Jc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_D78C906A.96F7A4CA
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable


4.6.22 getResponseControls

.... The method always returns null for asynchronous requests.

I believe what is meant here is that controls are never stored
for asynchronous requests.  I don't believe it means that
if an application makes a synchronous request, then
follows it up by an asynchronous request, that the
asynchronous request destroys any control data
stored from the synchronous request, i.e. stores null
where the last control is saved for that thread.

--=_D78C906A.96F7A4CA
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>&nbsp;</DIV>
<DIV>4.6.22 getResponseControls</DIV>
<DIV>&nbsp;</DIV>
<DIV>.... The method always returns null for asynchronous requests.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I believe what is meant here is that controls are never stored</DIV>
<DIV>for asynchronous requests.&nbsp; I don't believe it means that</DIV>
<DIV>if an application makes a synchronous request, then</DIV>
<DIV>follows it up by an asynchronous request, that the</DIV>
<DIV>asynchronous request destroys any control data</DIV>
<DIV>stored from the synchronous request, i.e. stores null</DIV>
<DIV>where the last control is saved for that thread.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--=_D78C906A.96F7A4CA--



From list@netscape.com  Thu Jan 25 17:02:38 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA09819
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 17:02:37 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PM0Xb26334;
	Thu, 25 Jan 2001 14:00:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PM0XY05910;
	Thu, 25 Jan 2001 14:00:33 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 14:00:33 -0800 (PST)
Message-Id: <sa703f74.053@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Thu, 25 Jan 2001 14:59:50 -0700
From: "Steve Sonntag" <VTAG@novell.com>
To: <ietf-ldapext@netscape.com>, <robw@worldspot.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_772C30F4.4425761C"
Resent-Message-ID: <"Wx-QkB.A.EcB._HKc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_772C30F4.4425761C
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable



There are several methods that an application will never use:

LDAPConnection.setInputStream
LDAPConnection.getInputStream
LDAPConnection.setOutputStream
LDAPConnection.getOutputStream
LDAPControl.newInstance

It is my feeling that these should not be defined in the Java API draft,
even though functions like these may be defined as public in
some implementations.  These implementions use these in the API itself,=20
but the application does not use them.

These functions force an implementation style, but the draft should not
force any style of implementation.  The draft should define only the =
application
interfaces.

These methods should be removed from the draft.

-Steve

------------------------
Steve Sonntag
Novell, Inc., the leading provider of Net services software

--=_772C30F4.4425761C
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>There are several methods that an application will never use:</DIV>
<DIV>&nbsp;</DIV>
<DIV>LDAPConnection.setInputStream</DIV>
<DIV>LDAPConnection.getInputStream</DIV>
<DIV>LDAPConnection.setOutputStream</DIV>
<DIV>LDAPConnection.getOutputStream</DIV>
<DIV>LDAPControl.newInstance</DIV>
<DIV>&nbsp;</DIV>
<DIV>It is my feeling that these should not be defined in the Java API=20
draft,</DIV>
<DIV>even though functions like these may be&nbsp;defined as public =
in</DIV>
<DIV>some&nbsp;implementations.&nbsp; These implementions use these in the =
API=20
itself, </DIV>
<DIV>but the application does not use them.</DIV>
<DIV>&nbsp;</DIV>
<DIV>These functions force an implementation style, but the draft =
should=20
not</DIV>
<DIV>force any style of implementation.&nbsp; The draft should define only =
the=20
application</DIV>
<DIV>interfaces.</DIV>
<DIV>&nbsp;</DIV>
<DIV>These methods should be removed from the draft.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-Steve</DIV>
<DIV>&nbsp;</DIV>
<DIV>------------------------<BR>Steve Sonntag<BR>Novell, Inc., the =
leading=20
provider of Net services software</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--=_772C30F4.4425761C--



From list@netscape.com  Thu Jan 25 17:20:29 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10014
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 17:20:27 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PMIXb00691;
	Thu, 25 Jan 2001 14:18:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PMIWo16045;
	Thu, 25 Jan 2001 14:18:32 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 14:18:32 -0800 (PST)
Message-ID: <3A70A5CB.E434370C@worldspot.com>
Date: Thu, 25 Jan 2001 14:16:44 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Steve Sonntag <VTAG@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Open issues with the Java LDAP API draft
References: <sa703f74.054@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"opqGGC.A.z3D.wYKc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

  That would kill interoperability. A SASL layer that worked with one implementation of the LDAP API would not work with another, and a control written for one implementation would not work with another implementation.

Rob

Steve Sonntag wrote:

>    There are several methods that an application will never use: LDAPConnection.setInputStreamLDAPConnection.getInputStreamLDAPConnection.setOutputStreamLDAPConnection.getOutputStreamLDAPControl.newInstance It is my feeling that these should not be defined in the Java API draft,even though functions like these may be defined as public insome implementations.  These implementions use these in the API itself,but the application does not use them. These functions force an implementation style, but the draft should notforce any style of implementation.  The draft should define only the applicationinterfaces. These methods should be removed from the draft. -Steve ------------------------
> Steve Sonntag
> Novell, Inc., the leading provider of Net services software



From list@netscape.com  Thu Jan 25 18:02:42 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA10654
	for <ldapext-archive@odin.ietf.org>; Thu, 25 Jan 2001 18:02:42 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0PN0qG22483;
	Thu, 25 Jan 2001 15:00:52 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0PN0rg07449;
	Thu, 25 Jan 2001 15:00:53 -0800 (PST)
Resent-Date: Thu, 25 Jan 2001 15:00:53 -0800 (PST)
Message-Id: <sa704db1.046@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Thu, 25 Jan 2001 16:00:37 -0700
From: "Javed Khan" <JKHAN@novell.com>
To: "Steve Sonntag" <VTAG@novell.com>, <robw@worldspot.com>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Open issues with the Java LDAP API draft
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_A3F8E431.A1C093D4"
Resent-Message-ID: <"qiJfYB.A.H0B.kALc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_A3F8E431.A1C093D4
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

There should not be any interoperability issues with controls if
we remove the newInstance method. =20

The SDK has responsibility for creating the appropriate LDAPControl=20
object.  How it creates it is up to the implementation.  Of course,=20
depending upon controls that might have been registered the SDK
might have to call a constructor of an application specified Class.  But =
again
when and how this constructor get called is up to the implementation.

Javed

>>> Rob Weltman <robw@worldspot.com> Thursday, January 25, 2001 3:16:44 PM =
>>>
  That would kill interoperability. A SASL layer that worked with one =
implementation of the LDAP API would not work with another, and a control =
written for one implementation would not work with another implementation.

Rob

Steve Sonntag wrote:

>    There are several methods that an application will never use: =
LDAPConnection.setInputStreamLDAPConnection.getInputStreamLDAPConnection.se=
tOutputStreamLDAPConnection.getOutputStreamLDAPControl.newInstance It is =
my feeling that these should not be defined in the Java API draft,even =
though functions like these may be defined as public insome implementations=
.  These implementions use these in the API itself,but the application =
does not use them. These functions force an implementation style, but the =
draft should notforce any style of implementation.  The draft should =
define only the applicationinterfaces. These methods should be removed =
from the draft. -Steve ------------------------
> Steve Sonntag
> Novell, Inc., the leading provider of Net services software

--=_A3F8E431.A1C093D4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.3105.105" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV><FONT size=3D3>There should not be any interoperability issues with =
controls=20
if</FONT></DIV>
<DIV><FONT size=3D3>we remove the newInstance method.&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D3>The </FONT><FONT size=3D3>SDK has responsibility for =
creating=20
the&nbsp;appropriate LDAPControl </FONT></DIV>
<DIV><FONT size=3D3>object.&nbsp; How it creates it is up to the=20
implementation</FONT><FONT size=3D3>.&nbsp; Of course,&nbsp;</FONT></DIV>
<DIV><FONT size=3D3>depending upon controls that might have&nbsp;been =
registered=20
the SDK</FONT></DIV>
<DIV><FONT size=3D3>might have to call a constructor of an application =
specified=20
Class.&nbsp; But again</FONT><FONT size=3D3></FONT></DIV>
<DIV><FONT size=3D3>when and how this constructor get called is up to =
the=20
implementation.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D3>Javed</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt;&gt; Rob Weltman &lt;robw@worldspot.com&gt; Thursday, January =
25,=20
2001 3:16:44 PM &gt;&gt;&gt;<BR>&nbsp; That would kill interoperability. A =
SASL=20
layer that worked with one implementation of the LDAP API would not work =
with=20
another, and a control written for one implementation would not work =
with=20
another implementation.<BR><BR>Rob<BR><BR>Steve Sonntag=20
wrote:<BR><BR>&gt;&nbsp;&nbsp;&nbsp; There are several methods that an=20
application will never use:=20
LDAPConnection.setInputStreamLDAPConnection.getInputStreamLDAPConnection.se=
tOutputStreamLDAPConnection.getOutputStreamLDAPControl.newInstance=20
It is my feeling that these should not be defined in the Java API =
draft,even=20
though functions like these may be defined as public insome=20
implementations.&nbsp; These implementions use these in the API itself,but =
the=20
application does not use them. These functions force an implementation =
style,=20
but the draft should notforce any style of implementation.&nbsp; The =
draft=20
should define only the applicationinterfaces. These methods should be =
removed=20
from the draft. -Steve ------------------------<BR>&gt; Steve Sonntag<BR>&g=
t;=20
Novell, Inc., the leading provider of Net services=20
software<BR><BR></DIV></BODY></HTML>

--=_A3F8E431.A1C093D4--



From list@netscape.com  Fri Jan 26 07:13:23 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04790
	for <ldapext-archive@odin.ietf.org>; Fri, 26 Jan 2001 07:13:22 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0QCBGG03991;
	Fri, 26 Jan 2001 04:11:16 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0QCBFE19586;
	Fri, 26 Jan 2001 04:11:15 -0800 (PST)
Resent-Date: Fri, 26 Jan 2001 04:11:15 -0800 (PST)
Date: Fri, 26 Jan 2001 04:11:12 -0800 (PST)
Message-Id: <200101261211.f0QCBCZ27898@xwing.netscape.com>
From: cashgenerator2002@yahoo.com
To: @netscape.com
Subject:  REMOTE CONTROL BUSINESS!
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"jqVNND.A.wxE.ilWc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Amazing Automated Home Business
NO selling!
UNLIMITED income!!
Click "Reply" for complete information




From list@netscape.com  Fri Jan 26 21:35:01 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA27958
	for <ldapext-archive@odin.ietf.org>; Fri, 26 Jan 2001 21:35:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0R2WuG29914;
	Fri, 26 Jan 2001 18:32:56 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0R2Wvo16453;
	Fri, 26 Jan 2001 18:32:57 -0800 (PST)
Resent-Date: Fri, 26 Jan 2001 18:32:57 -0800 (PST)
Message-Id: <200101270232.SAA12019@fionn.es.net>
To: ietf-ldapext@netscape.com
Subject: archives? minutes?
Date: Fri, 26 Jan 2001 18:32:12 -0800
From: Michael Helm <helm@fionn.es.net>
Resent-Message-ID: <"oJSk1B.A.wAE.YNjc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

I recently discovered I'd lost some mail from this
list in the past few weeks.  I was wondering if
minutes from 49th IETF had appeared yet; also,
noticed that the archives on innosoft have nothing
past May 11 of 2000.  (Is there another
archive somewhere?  I'd like to find ldapext mail from
about San Diego IETF to 20 Jan 2001.)  Thanks, ==mwh



From list@netscape.com  Fri Jan 26 22:27:15 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA28145
	for <ldapext-archive@odin.ietf.org>; Fri, 26 Jan 2001 22:27:14 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0R3PcG04493;
	Fri, 26 Jan 2001 19:25:38 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0R3Pds29908;
	Fri, 26 Jan 2001 19:25:39 -0800 (PST)
Resent-Date: Fri, 26 Jan 2001 19:25:39 -0800 (PST)
Message-Id: <5.0.2.1.0.20010126191820.00afc1e0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Fri, 26 Jan 2001 19:24:10 -0800
To: Michael Helm <helm@fionn.es.net>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: archives? minutes?
Cc: ietf-ldapext@netscape.com
In-Reply-To: <200101270232.SAA12019@fionn.es.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"VWUdxC.A.CTH.y-jc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 06:32 PM 1/26/01 -0800, Michael Helm wrote:
>I recently discovered I'd lost some mail from this
>list in the past few weeks.  I was wondering if
>minutes from 49th IETF had appeared yet; also,
>noticed that the archives on innosoft have nothing
>past May 11 of 2000.  (Is there another
>archive somewhere?  I'd like to find ldapext mail from
>about San Diego IETF to 20 Jan 2001.)  Thanks, ==mwh

http://www2.ietf.org/proceedings/00dec/minutes/LDAPEXT-WG.txt

ftp://ftp.ietf.org/ietf-mail-archive/ldapext/ 
http://www.openldap.org/lists/ietf-ldapext/ (searchable/browsable)

Kurt



From list@netscape.com  Sat Jan 27 00:00:57 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA00240
	for <ldapext-archive@odin.ietf.org>; Sat, 27 Jan 2001 00:00:56 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0R4wqG09965;
	Fri, 26 Jan 2001 20:58:52 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0R4wrc18280;
	Fri, 26 Jan 2001 20:58:53 -0800 (PST)
Resent-Date: Fri, 26 Jan 2001 20:58:53 -0800 (PST)
Date: Fri, 26 Jan 2001 20:58:40 -0800 (PST)
Message-Id: <200101270458.f0R4weZ20619@xwing.netscape.com>
From: ymlko@msn.com
To: novpz@Webfriends.netscape.com
Reply-To: su2m@bigfoot.com
Subject: Computer / Internet People Wanted to Work Online!                                    [saqch]
Resent-Message-ID: <"7hInsC.A.UdE.MWlc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Computer / Internet people wanted to work online.

$125-$175 an hour with Full Training
Vacations, bonuses, and incentives
Bi-linguals also needed.   50 countries
FREE   E-BOOK

For more info, reply with "Send Work Info",
as the Subject.

mailto:t2m23@bigfoot.com?subject=Send_Work_Info

Please Note... Should this email address be shut down. 
Please "Fax" your response with your name__,email 
address___, and the words "Internet Worker" 
to: 305-425-3205. 

Looking forward for your response.

Thanks,
Nile



From list@netscape.com  Sat Jan 27 01:05:12 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA00810
	for <ldapext-archive@odin.ietf.org>; Sat, 27 Jan 2001 01:05:11 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0R639b02646;
	Fri, 26 Jan 2001 22:03:09 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0R63BQ00852;
	Fri, 26 Jan 2001 22:03:11 -0800 (PST)
Resent-Date: Fri, 26 Jan 2001 22:03:11 -0800 (PST)
Date: Fri, 26 Jan 2001 22:03:03 -0800 (PST)
Message-Id: <200101270603.f0R633501209@ywing.netscape.com>
From: xnuqe@msn.com
To: bakio@Webfriends.netscape.com
Reply-To: t2m20@bigfoot.com
Subject: $30,550+ a month PASSIVE income FAST!                                    [gvyba]
Resent-Message-ID: <"UxAZnC.A.5M.eSmc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Friend:

Eureka - I finally found it!  EVERYONE CAN 
TRULY MAKE MONEY HERE!!

How would you like to earn $hundreds$ your first
week, and a $30,550+ a month PASSIVE residual 
income FAST?  Wow!  That's a yearly income well 
over $360,000 whether you continue to work or not.  
EVERYONE CAN TRULY MAKE MONEY HERE; THE SKY IS 
THE LIMIT!

A simple, yet incredibly lucrative business
has been designed for the masses.  No quotas, 
no purchasing or stocking, and NO DROPOUTS!

Consider this:

* International Opportunity
* Online Marketing Tools
* Online Genealogy
* State-of-the-Art Training
* Phenomenal Support Systems
* Huge Compensation Plan
  - 80% Fast Start Bonuses
  - Paid Weekly
* Part-time or Full-time
* Lifetime Residual Income

For all the details, you must reply back 
with your complete name and phone number.  
Reply with "Passive Income Info" in subject.

mailto:t2m26@bigfoot.com?subject=Passive_Income_Info

Please Note... Should this email address be shut down.
Please "Fax" your response instead, with your name__,
email address___, and the words "Send Passive Income
Info" to: 305-425-3205.

Don't drag your feet on this one.  It could
very well be what you have been looking for all 
your life.  Get ready to be amazed.

God Bless
The Money Heaven Group

P.S.  Please remember, you must reply back with
your name and phone number in order to receive
complete information.



From list@netscape.com  Sat Jan 27 04:59:06 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA14719
	for <ldapext-archive@odin.ietf.org>; Sat, 27 Jan 2001 04:59:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0R9uvb15711;
	Sat, 27 Jan 2001 01:56:57 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0R9v0A08141;
	Sat, 27 Jan 2001 01:57:00 -0800 (PST)
Resent-Date: Sat, 27 Jan 2001 01:57:00 -0800 (PST)
Date: Sat, 27 Jan 2001 01:56:57 -0800 (PST)
Message-Id: <200101270956.f0R9uvZ20038@xwing.netscape.com>
From: cashgenerator2002@yahoo.com
To: @netscape.com
Subject:  REMOTE CONTROL BUSINESS!
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"fpPoz.A.7-B.rtpc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Amazing Automated Home Business
NO selling!
UNLIMITED income!!
Click "Reply" for complete information




From list@netscape.com  Sat Jan 27 11:44:59 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16806
	for <ldapext-archive@odin.ietf.org>; Sat, 27 Jan 2001 11:44:58 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0RGgCG14990;
	Sat, 27 Jan 2001 08:42:12 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0RGgCw09774;
	Sat, 27 Jan 2001 08:42:12 -0800 (PST)
Resent-Date: Sat, 27 Jan 2001 08:42:12 -0800 (PST)
Message-Id: <200101271642.f0RGg0Z11685@xwing.netscape.com>
X-Sender: jdq@libertysurf.se
From: Patrick <jdq@libertysurf.se>
To: "h_hunters@hotmail.com" <jdq@libertysurf.se>
Date: Sat, 27 Jan 2001 17:45:39 +0100
Subject: Earn 200 to 300 a day behind your computer!
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"fumvh.A.cYC.jpvc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hi,

If you are looking for a solid homebased business that makes
already an additional 500 US$ per week for many people
just like YOU! A business backed up by a new SYSTEM!

An awesome formula that attracts people like bees on honey!
A SYSTEM that seeks the best people for your business!

...in many occasions it happens within a week!...

Part-time or in search to replace your full-time income then
read on! People already earn 5 figures and we've nearly
started! We already have incredible testimonials from
people from all walks of life!

Fact is we're the talk of the industry and broke the records!
And now operational worldwide!

FINALLY A TURN KEY SYSTEM THAT WORKS!

Here's the best marriage between MLM and the
dot com industry I've ever came across!

There is something about to happen in the Networking
arena that will have a Major Global impact. Would you
take a few minutes of your of your busy schedule to
listen to an individual who has earned $185,000 per
week and left that income for his new company?

The single largest event in network marketing history
is taking place RIGHT NOW. You can get positioned
NOW in front of tens of thousands of people coming
into the business from all over the world.

Industry records are currently being broken with more than
40,000 people joining in the first 30 days!

Most people never get the opportunity like this to join
*BEFORE* something this BIG happens.
Consider this:

   * International Multi-million Dollar Company
   * $100 Billion Industry
   * Proprietary Technology
   * Online Marketing Tools
   * Phenomenal Support Systems
   * 3 Huge Compensation Plans
   * Lifetime Residual income

Despite the unlimited growth ahead of us in the dot.com
industry, there is a limited window of  opportunity to
position yourself with us. Timing is critical, so you need
to act fast.
____________________________________________
We have set up or own exclusive leadgeneratingprogram
that is absolutely responsible for everyone's success!
____________________________________________
The other reason for our success is the amazing follow up
formula we have! TURNKEY and so EASY to USE!
___________________________________________

If you have serious interest in more information
on how to capitalize on this on this major opportunity
then mail me at nixnoll@yahoo.com and if you wish leave your name
and phone number @ your@emailadress.com
And we will have someone to contact you.

Best regards,
J. D.
_____________________________________________
If you feel you not are the intended recipient
of this email, please delete it.
No need to send removerequest.
This is a onetime mailing.
______________________________________________







From list@netscape.com  Sat Jan 27 16:00:08 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18224
	for <ldapext-archive@odin.ietf.org>; Sat, 27 Jan 2001 16:00:08 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0RKw9G28827;
	Sat, 27 Jan 2001 12:58:10 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0RKwAY26302;
	Sat, 27 Jan 2001 12:58:10 -0800 (PST)
Resent-Date: Sat, 27 Jan 2001 12:58:10 -0800 (PST)
Date: Sat, 27 Jan 2001 12:58:04 -0800 (PST)
Message-Id: <200101272058.f0RKvr528944@ywing.netscape.com>
From: support@netmarket.net.jp.netscape.com
To: @netscape.com
Subject:  Your commission check!
X-Reply-To:  lixo12@usa.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"CdVgvD.A.qaG.hZzc6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit


It is Amazing ... and FREE!
During the last October we sponsored 114,402 new distributors in 131
countries worldwide. Today, we have over 800,000 affiliates in
193 countries.(And
we have only scratched the surface! - According The New York Times there 
are
332 millions people conected worldwide.)
EVEN MORE AMAZING:
These unprecedented numbers came without mailing a single brochure, 
audio, or
videotape. Not a single long-distance phone call was made...or fax sent. 
We
did it 100% via the Internet . Network Marketing on the Web has arrived! 
Want
to know more? You can test drive the system FREE!
Just click on this link then watch the magic. 


http://clicktosurf.to/biz8 



*************************************************************************
*************************************************************************
**
This message is sent in compliance of the proposed bill: SECTION 301. Per 
Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you 
by the sender of this email may be stopped at no cost to you by sending a 
Reply to this email address with the word Remove in the subject line. 
*************************************************************************
*************************************************************************
**










From list@netscape.com  Sun Jan 28 01:30:38 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA25710
	for <ldapext-archive@odin.ietf.org>; Sun, 28 Jan 2001 01:30:37 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0S6Stb16220;
	Sat, 27 Jan 2001 22:28:56 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0S6SvU27301;
	Sat, 27 Jan 2001 22:28:57 -0800 (PST)
Resent-Date: Sat, 27 Jan 2001 22:28:57 -0800 (PST)
Message-ID: <3A73BCEB.32B143A6@worldspot.com>
Date: Sat, 27 Jan 2001 22:32:12 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: Javed Khan <JKHAN@novell.com>, Steve Sonntag <VTAG@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Open issues with the Java LDAP API draft
References: <sa704db1.046@prv-mail20.provo.novell.com>
Content-Type: multipart/alternative;
 boundary="------------1317FB6E82449AEB2C75450C"
Resent-Message-ID: <"UJNljD.A.MqG.ow7c6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com


--------------1317FB6E82449AEB2C75450C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

  OK, that's true. The SDK can instantiate response controls using the LDAPControl constructor signature, based on the control having been registered. So we can eliminate newInstance. newInstance was intended to take the BER-encoding of a control and instantiate a control, but we can assume that an SDK implementation has already parsed the BER into its components and will use the components to instantiate a control.

  But if we remove the other four methods (for getting and setting the input and output stream), how would one apply a SASL security layer?

Rob


Javed Khan wrote:

>  There should not be any interoperability issues with controls ifwe remove the newInstance method. The SDK has responsibility for creating the appropriate LDAPControlobject.  How it creates it is up to the implementation.  Of course,depending upon controls that might have been registered the SDKmight have to call a constructor of an application specified Class.  But againwhen and how this constructor get called is up to the implementation. Javed >>> Rob Weltman <robw@worldspot.com> Thursday, January 25, 2001 3:16:44 PM >>>
>   That would kill interoperability. A SASL layer that worked with one implementation of the LDAP API would not work with another, and a control written for one implementation would not work with another implementation.
>
> Rob
>
> Steve Sonntag wrote:
>
> >    There are several methods that an application will never use: LDAPConnection.setInputStreamLDAPConnection.getInputStreamLDAPConnection.setOutputStreamLDAPConnection.getOutputStreamLDAPControl.newInstance It is my feeling that these should not be defined in the Java API draft,even though functions like these may be defined as public insome implementations.  These implementions use these in the API itself,but the application does not use them. These functions force an implementation style, but the draft should notforce any style of implementation.  The draft should define only the applicationinterfaces. These methods should be removed from the draft. -Steve ------------------------
> > Steve Sonntag
> > Novell, Inc., the leading provider of Net services software
>




--------------1317FB6E82449AEB2C75450C
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body style="FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
&nbsp; OK, that's true. The SDK can instantiate response controls using
the LDAPControl constructor signature, based on the control having been
registered. So we can eliminate newInstance. newInstance was intended to
take the BER-encoding of a control and instantiate a control, but we can
assume that an SDK implementation has already parsed the BER into its components
and will use the components to instantiate a control.
<p>&nbsp; But if we remove the other four methods (for getting and setting
the input and output stream), how would one apply a SASL security layer?
<p>Rob
<br>&nbsp;
<p>Javed Khan wrote:
<blockquote TYPE=CITE>&nbsp;<font size=+0>There should not be any interoperability
issues with controls if</font><font size=+0>we remove the newInstance method.</font>&nbsp;<font size=+0>The
SDK has responsibility for creating the appropriate LDAPControl</font><font size=+0>object.&nbsp;
How it creates it is up to the implementation.&nbsp; Of course,</font><font size=+0>depending
upon controls that might have been registered the SDK</font><font size=+0>might
have to call a constructor of an application specified Class.&nbsp; But
again</font><font size=+0>when and how this constructor get called is up
to the implementation.</font>&nbsp;<font size=+0>Javed</font>&nbsp;>>>
Rob Weltman &lt;robw@worldspot.com> Thursday, January 25, 2001 3:16:44
PM >>>
<br>&nbsp; That would kill interoperability. A SASL layer that worked with
one implementation of the LDAP API would not work with another, and a control
written for one implementation would not work with another implementation.
<p>Rob
<p>Steve Sonntag wrote:
<p>>&nbsp;&nbsp;&nbsp; There are several methods that an application will
never use: LDAPConnection.setInputStreamLDAPConnection.getInputStreamLDAPConnection.setOutputStreamLDAPConnection.getOutputStreamLDAPControl.newInstance
It is my feeling that these should not be defined in the Java API draft,even
though functions like these may be defined as public insome implementations.&nbsp;
These implementions use these in the API itself,but the application does
not use them. These functions force an implementation style, but the draft
should notforce any style of implementation.&nbsp; The draft should define
only the applicationinterfaces. These methods should be removed from the
draft. -Steve ------------------------
<br>> Steve Sonntag
<br>> Novell, Inc., the leading provider of Net services software
<br>&nbsp;</blockquote>

<br>&nbsp;
<br>&nbsp;
</body>
</html>

--------------1317FB6E82449AEB2C75450C--



From list@netscape.com  Sun Jan 28 07:27:49 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07945
	for <ldapext-archive@odin.ietf.org>; Sun, 28 Jan 2001 07:27:49 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0SCOxG14657;
	Sun, 28 Jan 2001 04:24:59 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0SCOxw22787;
	Sun, 28 Jan 2001 04:24:59 -0800 (PST)
Resent-Date: Sun, 28 Jan 2001 04:24:59 -0800 (PST)
Date: Sun, 28 Jan 01 15:38:27 EST
From: superpomoter@email.com
To: Friend@public.com
Subject: Send Over 30 Million Spam Free Emails per Month!!!!!!!
Message-ID: <>
Reply-To: superpromoter@mailcity.com
Resent-Message-ID: <"uV_csD.A.xjF.a-Ad6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

SUPER PROMOTER 
  
Want 1,000,000+ People To See Your Ad Each Day? 
   
I Know you Do! 
  
Want To Do This 100% SPAM FREE? 
Sure You Do! 
  
Until Now, Only The Hard Core( Guru ) Type Marketers could take advantage of 
this system! It's Incredible EFFECTIVENESS Will Leave You Astounded, And On The 
Road To Internet Marketing Success. 
  
Now you can have your message seen by more than 1/2 A Million (800,000 +) people 
Each And Every Day without spending Money for Advertising. 
  
100% NO Spamming Involved 
  
100% No danger of your ISP shutting you down 
  
No Flames 
  
No time consuming individual work 
  
No constant updates required 
  
No extra add-on Purchases required-Ever! 
  
This system has been designed to bring you unlimited hits and responses to your 
offers. 
  
You will not be shut down. 
  
Sound good? Wait till you see what you get! 
  
You get a TOTALLY Automated System That will allow you to Subscribe and Send 
Messages to 1,200 + Opt-In Mailing Lists. Some of these Lists have Thousands 
of members. 
  
These are lists that contain members looking for offers, to get involved with, 
  they are active surfers and are spending time and money on what you have to 
offer! 
  
With the Internet Population increasing on a daily basis, and seemingly every 
one looking for the home base or supplemental income, this program will put 
you right where you want to be--Seen by hundreds of Thousands of People each 
and every day! 
  
This is what you get: 
  
FREE Automated Bulk Mail software. 
  
Step by Step Set up Instructions. 
  
Subscription Instructions. 
  
Pre-Formatted email lists to over 1,000 Email Groups, that (as of 1/1/00) have 
over 1,000,000 Members 
  
FREE Updates 
  
One Post = 
  1,000,000 AD Exposures 
   
I am positive that you can see the advantages of this system and how it WILL 
work for you... A lot of times we tend to sit and say things like... That's 
not going to work for me... or I don't have time... or I don't know how... 
  or That's just talk... or That's not a real job... 
  
Others offer this type of program for $99.00 up to $299.95, Our one time cost 
is Just $27.50! That's All Ever!!! Plus you will receive monthly updates, and 
your own affiliate site. 
  
And don't even come close to giving you the extras that we do! In addition to 
the above, you will also receive the following... 

Visit Our Site At- http://www.geocities.com/superpromoter2001/

Webmaster



From list@netscape.com  Mon Jan 29 00:37:45 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA14443
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 00:37:44 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0T5ZdG06968;
	Sun, 28 Jan 2001 21:35:39 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0T5Ze216761;
	Sun, 28 Jan 2001 21:35:40 -0800 (PST)
Resent-Date: Sun, 28 Jan 2001 21:35:40 -0800 (PST)
Message-ID: <3A750220.72AEA08A@worldspot.com>
Date: Sun, 28 Jan 2001 21:39:44 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: Steve Sonntag <VTAG@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Open issues with the Java LDAP API draft
References: <sa7012c3.060@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0T5Zdv16737
Resent-Message-ID: <"-tk6KC.A.nFE.sEQd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

  I'm changing the signature of LDAPReferralException to take Throwable as argument, and changing getFailureException() to getCause(), as per the new Java API for nested exceptions.

  As for specifying when a referral exception is thrown on search(), isn't the following text from the draft explicit enough?

"If automatic referral following is disabled or a referral was not followed, next() will throw an LDAPReferralException when the referral is received."

Rob


Steve Sonntag wrote:

>  That is only partially true.  The connect call can get various IOExceptions orUnknownHostException which gets generalized to a less specific - more generalerror CONNECT_ERROR.  Presumably, malformed URL could also be returnedas CONNECT_ERROR, but I like more information rather that less, so I agreewith your comment.  This would also change the LDAPUrl class which hasmethods that return MalformedURLException. I think the method name should be more descriptive of its function: public String getFailedReferral() Is is correct to presume that the status for the operation that generatedthe referrals would the status of a referral that failed.  In the case ofsearch, should all other data be returned to the application before throwingthe Exception, or should the exception be thrown immediately?The desired  behavior should be mentioned in the ID. -Steve  >>> Rob Weltman <robw@worldspot.com> 25-Jan-01 10:18:13 AM >>>
>   It could be Exception rather than LDAPException, although it might be better to add a result code for MalformedURL to LDAPException. LDAPException encapsulates more semantic information about the types of referral failures than other low-level exception classes.
>
>   I wouldn't overload matchedDN for relaying the failed URL. It's meaning is, if anything, the opposite: the part of the DN of the URL that did match. Better to provide a new method to retrieve the invalid URL from LDAPReferralException:
>
> public String getReferral()
>
>   If there were multiple references processed, and all of them failed, this would report one of them.
>
> Rob
>
>
> Steve Sonntag wrote:
>
> >  Actually, I was only taking the information given in the constructor
> > and copying it to the introduction of the class.   public LDAPReferralException(String message,
> >                                 LDAPException rootException)    Constructs a default exception with a specified string as additional
> >    information and an exception that indicates a failure to follow a
> >    referral.  This exception applies only to synchronous operations and
> >    is thrown only on receipt of a referral when the referral was not
> >    followed. As I was looking at this, I wondered if LDAPException is
> > too restrictive.  For example what is reported for a malformed URL?
> > We cannot report MalformedURLException as it is of type Exception.
> > Should the rootException be simply of type Exception? Should the ReferralException class use matchedDN to indicate
> > which referral caused the problem, or is that overloading that field too much. -Steve
> > Rob Weltman wrote: > Steve Sonntag wrote:
> > >
> > > >   LDAPReferralException 4.27 public class LDAPReferralException
> > > >                   extends LDAPException
> > > >
> > > >    This exception, derived from LDAPException, is thrown when a server
> > > >    returns a referral and automatic referral following has not been
> > > >    enabled.Add to the above     or automatic referral following could not follow any referrals. -Steve
> > >
> > >   That sounds hard to handle for a client. Are you thinking of the case where the referral points to a server which is inaccessible or which doesn't accept the credentials of the requestor? How would the client know which of those problems was being flagged if there is only a referral exception? And consequently, how would the client know what to do about it?
> > >
> > > Rob
>
>
>
>






From list@netscape.com  Mon Jan 29 01:13:03 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA15374
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 01:13:02 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0T6BHb28766;
	Sun, 28 Jan 2001 22:11:17 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0T6BJY24854;
	Sun, 28 Jan 2001 22:11:19 -0800 (PST)
Resent-Date: Sun, 28 Jan 2001 22:11:19 -0800 (PST)
Message-ID: <3A750A58.D0D4F9B5@worldspot.com>
Date: Sun, 28 Jan 2001 22:14:48 -0800
From: Rob Weltman <robw@worldspot.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en-US,sv,ja
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@openldap.org>
CC: ietf-ldapext@netscape.com
Subject: Re: Open issues with the Java LDAP API draft
References: <5.0.2.1.0.20010122154103.00a31430@router.boolean.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"bX6-kB.A.EEG.GmQd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

"Kurt D. Zeilenga" wrote:
> 
> At 05:13 PM 1/21/01 -0800, Rob Weltman wrote:
> >  These are the issues that have been raised (that I am aware of) with the latest Java LDAP Internet Draft (http://www.ietf.org/internet-drafts/draft-ietf-ldapext-ldap-java-api-12.txt), along with my own proposals for disposition.
> 
> I have a few other issues.  Many of these have been
> discussed previously.
> 
> The API appears to support both LDAPv2 and LDAPv3 but appears
> to assumes use of UTF-8 regardless of the protocol.  LDAPv2
> directoryStrings are restricted to T.61.  In addition, certain
> LDAPv2 protocol strings (e.g. all LDAPStrings) are restricted
> to IA5.  If LDAPv2 is to be support, it should be fully
> supported and a normative reference to LDAPv2 should be stated.
> If LDAPv2 is not to be supported, all mention of LDAPv2 should
> be stricken.  I believe this API should not attempt to support
> both LDAPv2 and LDAPv3.  As LDAPv2 will be moved to historical
> status upon publication of an LDAPv3 Draft Standard, I recommend
> this API support only LDAPv3.

  It only supports LDAPv3. It explicitly supports only UTF-8, and it mentions LDAPv2 in pointing out that controls are not supported in LDAPv2. I'll remove that clarification.

 
> API contains a reference to RFC 1823, an Informational RFC.
> If this is non-normative, it should be noted.  If normative,
> there is a standard track maturity issue in that RFC 1823 is
> informational.  It appears to be normative to me.
> 
> The abstract refers to the expired async API I-D unnecesarily.

  Yes, it is not necessary to reference either of those.

 
> It appears that the API specification requires implementation
> of LDAP Language Tags, an extension to the "core" protocol
> specification.  The core API should only require implementation
> of the "core" protocol specification.  APIs for non-core
> extensions should be detailed in API extensions.

  They are very important to developers in environments where directory data is multi-lingual, and they have been heavily used to date. I think they should stay.

 
> Java, IIRC, uses UCS-2.  LDAP allows the full (31-bit) set of
> ISO-10646-1 characters encoded in UTF-8.  There should be some
> comment as what is to be done with characters outside of UCS-2
> but with ISO-10646-1.

  Which characters are you thinking of? As far as I know none have yet been defined outside the lower 64k. If Unicode characters should be defined in the future beyond the 16-bit range, that will be a problem for all Java programs and for the Java language itself, not for LDAP in particular. Whatever solution is adopted for the Java language should also be adopted by any Java class libraries, including this one.

 
> There should be a normative reference to Java language
> specification(s) [core + required extensions (SASL/TLS)].

  To what, more specifically?


> The relationship with JNDI should also be discussed.

  Not relevant to this document.

 
> Appears the default behavior is to chase referrals.  As I've
> noted previously on this list, this is not a wise default from
> a security perspective.  The default should be not to chase
> referrals (period).

  Steve pointed out:

At 10:04 AM 1/23/01 -0700, Steve Sonntag wrote:
>The default behavior for following referrals is specified in
>the LDAPConstraints object.  The boolean doReferrals parameter
>controls whether referrals are followed or not.  The default
>for this parameter is "FALSE", i.e. referrals are not
>automatically followed [period].  See also 4.7.8.

 
> LDAP_PARTIAL_RESULTS?  There should be no mention of this.  However,
> I note that the API should be capable of treating unrecognized
> result codes returned by servers (including those reserved by API
> specifications) as unknown errors.

  I'll remove the reference to LDAP_PARTIAL_RESULTS, since an implementation of the API is no longer expected to work an LDAPv2 server.

 
> Missing normative references:
>         Java API Spec

  ?


>         Java SASL API Spec

  What's the RFC number?


>         Java TLS API Spec

  What's the RFC number?


>         ldaps (LDAP over SSL)

  What's the RFC number?


>         RFC 2222, RFC 2829, RFC 2830

  I'll add a reference to 2222 for SASL and to 2830 for TLS, but where would the reference to 2829 go?

Rob

> 
> Kurt



From list@netscape.com  Mon Jan 29 11:38:23 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05382
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 11:38:22 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TGaGb25981;
	Mon, 29 Jan 2001 08:36:16 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TGaGA03719;
	Mon, 29 Jan 2001 08:36:16 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 08:36:16 -0800 (PST)
Message-Id: <5.0.2.1.0.20010129071442.00a80420@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 29 Jan 2001 08:34:50 -0800
To: Rob Weltman <robw@worldspot.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Open issues with the Java LDAP API draft
Cc: ietf-ldapext@netscape.com
In-Reply-To: <3A750A58.D0D4F9B5@worldspot.com>
References: <5.0.2.1.0.20010122154103.00a31430@router.boolean.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"Ks57lC.A.T5._vZd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 10:14 PM 1/28/01 -0800, Rob Weltman wrote:
>> It appears that the API specification requires implementation
>> of LDAP Language Tags, an extension to the "core" protocol
>> specification.  The core API should only require implementation
>> of the "core" protocol specification.  APIs for non-core
>> extensions should be detailed in API extensions.
>
>  They are very important to developers in environments where directory data is multi-lingual, and they have been heavily used to date. I think they should stay.
>
> 
>> Java, IIRC, uses UCS-2.  LDAP allows the full (31-bit) set of
>> ISO-10646-1 characters encoded in UTF-8.  There should be some
>> comment as what is to be done with characters outside of UCS-2
>> but with ISO-10646-1.
>
>  Which characters are you thinking of?

RFC 2252, 6.2:
   Servers and clients MUST be prepared to
   receive encodings of arbitrary Unicode characters, including
   characters not presently assigned to any character set.

>As far as I know none have yet been defined outside the lower 64k.
>If Unicode characters should be defined in the future beyond the 16-bit range, that will be a problem for all Java programs and for the Java language itself, not for LDAP in particular.

Yes.  My point here is that the API is NOT prepared to receive
encodings of arbitary Unicode characters.  

>Whatever solution is adopted for the Java language should also be adopted by any Java class libraries, including this one.

Then state this in the I-D.

>> There should be a normative reference to Java language
>> specification(s) [core + required extensions (SASL/TLS)].
>
>  To what, more specifically?

"The Java Language Specification", J. Gosling, et. al.,
Addison Wesley, Jun 2000.

>> The relationship with JNDI should also be discussed.
>
>  Not relevant to this document.

I disagree.  I believe IETF Standard Track documents should provide
some background and intended use discussion when there are overlapping
specifications.  JNDI is a Java Standard Extension and this I-D
overlaps greatly with it.

>> Missing normative references:
>>         Java API Spec

I should have said "Java Language Specification".  See above.



>>         Java SASL API Spec
>
>  What's the RFC number?

RFC number not required.  I suggest referring to the JCP
approved specification.  "Java SASL Specification",
JCP JSR#28, as I believe this is what the I-D depends on.

>>         Java TLS API Spec
>  What's the RFC number?

I suggest "Java Secure Socket Extension",  ...,
available at http://java.sun.com/

>>         ldaps (LDAP over SSL)
>
>  What's the RFC number?

I don't have a suggestion here other than to remove support
for ldaps (LDAP over SSL) [the isSecure() method] as this
requires a normative reference to a specification with
appropriate standard track maturity.


>>         RFC 2222, RFC 2829, RFC 2830
>
>  I'll add a reference to 2222 for SASL and to 2830 for TLS, but where would the reference to 2829 go?

I would reference 2829 where you introduce LDAP SASL Bind and/or
where you discuss authentication and authorization security
considerations specific to the API.



From list@netscape.com  Mon Jan 29 11:51:06 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05643
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 11:51:06 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TGnXb28752;
	Mon, 29 Jan 2001 08:49:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TGnXw10441;
	Mon, 29 Jan 2001 08:49:33 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 08:49:33 -0800 (PST)
Date: Mon, 29 Jan 2001 08:48:50 -0800 (PST)
Message-Id: <200101291648.f0TGmoZ24380@xwing.netscape.com>
From: akuag@YOLL.yahoo.com
To: .KFPD@netscape.com
Subject:  Free Master Gold Card, get $20 for each referral. -RLBL
X-Reply-To:  hoo_ing@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"KOn31.A.1iC.c8Zd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello, This is just a one time mail. You would never receive this mail again.

   Check this out! It's Master card this time, it pays better than Visa. Visit    
http://www.hometown.aol.com/bosa2001
 
Or 

Send email to sign up at  :  bosa2001@aol.com

Subject : MasterGold Card Application

email body should be like this,

Applicant's Name 		: Your Name
Applicant's E-mail  		: Your email address

Sponsor 			: Hoo Ing
e-mail  			: hoo_ing@yahoo.com


Start referring to your friends using this format until you get your ID.
Each member that you refer and receive their  card will make you USD20 each. Commission pays up to 12 
level deep.
It's free to apply. No annual fees.
It's very new act quickly.



regards,


Hoo Ing




From list@netscape.com  Mon Jan 29 12:21:29 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06213
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 12:21:28 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0THGsb03681;
	Mon, 29 Jan 2001 09:16:54 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0THGsg21218;
	Mon, 29 Jan 2001 09:16:54 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 09:16:54 -0800 (PST)
Message-Id: <sa754304.049@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Mon, 29 Jan 2001 10:16:32 -0700
From: "Jim Sermersheim" <JIMSE@novell.com>
To: <ietf-ldapext@netscape.com>
Subject: Fix for VLV draft.
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_E6BDA464.D1B09D63"
Resent-Message-ID: <"BZnLtC.A.6KF.EWad6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_E6BDA464.D1B09D63
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Back in September, as the Virtual List View draft was going through =
standardization process, Michael Armijo noted the following problem:

>In section 3.2 we have details about what the virtualListViewResult
>codes mean, but we still do not define what result code should be
>returned in the actual SearchResult in the case where there is a value
>other then success(0) in the virtualListViewResult.
>
>We should return something other then success(0)in the SearchResultDone
>if there is a result code other then success(0) in the
>virtualListViewResult and what that result code is should be defined (or
>referenced) in the VLV draft.

I propose that we fix this by inserting the following statement as =
paragraph 4 of Section 3.2

If the LDAP SearchResultDone message has a resultCode of other (80),=20
the virtualListViewResponse MAY be included and MAY hold a non-zero=20
value in the virtualListViewResult field.

If there are no objections, I'd like to add this and allow the draft to =
progress.

Jim

--=_E6BDA464.D1B09D63
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt Tahoma; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
<DIV>Back in September, as the Virtual List View draft was going through=20=

standardization process, Michael Armijo noted the following problem:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;In section 3.2 we have details about what the=20
virtualListViewResult<BR>&gt;codes mean, but we still do not define what =
result=20
code should be<BR>&gt;returned in the actual SearchResult in the case =
where=20
there is a value<BR>&gt;other then success(0) in the=20
virtualListViewResult.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;We should return something other then success(0)in the=20
SearchResultDone<BR>&gt;if there is a result code other then success(0) =
in=20
the<BR>&gt;virtualListViewResult and what that result code is should be =
defined=20
(or<BR>&gt;referenced) in the VLV draft.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I propose that we fix this by inserting the following statement as=20
paragraph 4 of Section 3.2<BR></DIV>
<DIV>If the LDAP SearchResultDone message has a resultCode of other =
(80),=20
<BR>the virtualListViewResponse MAY be included and MAY hold a non-zero=20
<BR>value in the virtualListViewResult field.<BR></DIV>
<DIV>If there are no objections, I'd like to add this and allow the draft =
to=20
progress.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jim</DIV></BODY></HTML>

--=_E6BDA464.D1B09D63--



From list@netscape.com  Mon Jan 29 12:49:37 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06617
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 12:49:36 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0THkXG12949;
	Mon, 29 Jan 2001 09:46:34 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0THa6Y21829;
	Mon, 29 Jan 2001 09:36:06 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 09:36:06 -0800 (PST)
Reply-To: <John.Liang@openwave.com>
From: "John Liang" <John.Liang@openwave.com>
To: "Jim Sermersheim" <JIMSE@novell.com>, <ietf-ldapext@netscape.com>
Subject: RE: Fix for VLV draft.
Date: Mon, 29 Jan 2001 12:35:29 -0500
Message-ID: <000401c08a19$df585ee0$ba05400a@software.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C089EF.F68256E0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <sa754304.049@prv-mail20.provo.novell.com>
Resent-Message-ID: <"-6j53.A.1UF.Foad6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C089EF.F68256E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I want to ask a few questions about this topic:

1> if the control is not critical, and there is an error in server side
sorting control
or virutal list view control, the server is supposed to send back all
unsorted result.

if the server returns all unsorted entries successfully,
is LDAP searchResultDone message supposed to return LDAP_SUCCESS or
other(80)?
Must we include sssResponse and vlvResponse with corresponding error code?

2> if the control is critical, besides return
LDAP_UNAVAILABLE_CRITICAL_EXTENSION,
Must we return the corrseponding sssResponse and vlvResponse result code?

Thanks,
--
John Liang
  -----Original Message-----
  From: Jim Sermersheim [mailto:JIMSE@novell.com]
  Sent: Monday, January 29, 2001 12:17 PM
  To: ietf-ldapext@netscape.com
  Subject: Fix for VLV draft.


  Back in September, as the Virtual List View draft was going through
standardization process, Michael Armijo noted the following problem:

  >In section 3.2 we have details about what the virtualListViewResult
  >codes mean, but we still do not define what result code should be
  >returned in the actual SearchResult in the case where there is a value
  >other then success(0) in the virtualListViewResult.
  >
  >We should return something other then success(0)in the SearchResultDone
  >if there is a result code other then success(0) in the
  >virtualListViewResult and what that result code is should be defined (or
  >referenced) in the VLV draft.

  I propose that we fix this by inserting the following statement as
paragraph 4 of Section 3.2

  If the LDAP SearchResultDone message has a resultCode of other (80),
  the virtualListViewResponse MAY be included and MAY hold a non-zero
  value in the virtualListViewResult field.

  If there are no objections, I'd like to add this and allow the draft to
progress.

  Jim

------=_NextPart_000_0005_01C089EF.F68256E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt Tahoma; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>I want to ask a few =
questions=20
about this topic:</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN =
class=3D434522417-29012001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>1&gt; if the =
control is not=20
critical, and there is an error in server side sorting control=20
</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>or virutal list =
view control,=20
the server is supposed to send back all unsorted =
result.</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN =
class=3D434522417-29012001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>if the server =
returns all=20
unsorted entries successfully,</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>is LDAP =
searchResultDone=20
message supposed to return LDAP_SUCCESS or =
other(80)?</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>Must we include =
sssResponse and=20
vlvResponse with corresponding error code?</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN =
class=3D434522417-29012001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>2&gt; if the =
control is=20
critical, besides return=20
LDAP_UNAVAILABLE_CRITICAL_EXTENSION,</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>Must we return the=20
corrseponding sssResponse and vlvResponse result =
code?</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN =
class=3D434522417-29012001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1><SPAN =
class=3D434522417-29012001>Thanks,</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN =
class=3D434522417-29012001>--</SPAN></FONT></DIV>
<DIV><FONT size=3D1><SPAN class=3D434522417-29012001>John =
Liang</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV class=3DOutlookMessageHeader><FONT face=3D"Times New Roman"=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Jim Sermersheim=20
  [mailto:JIMSE@novell.com]<BR><B>Sent:</B> Monday, January 29, 2001 =
12:17=20
  PM<BR><B>To:</B> ietf-ldapext@netscape.com<BR><B>Subject:</B> Fix for =
VLV=20
  draft.<BR><BR></DIV></FONT>
  <DIV>Back in September, as the Virtual List View draft was going =
through=20
  standardization process, Michael Armijo noted the following =
problem:</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&gt;In section 3.2 we have details about what the=20
  virtualListViewResult<BR>&gt;codes mean, but we still do not define =
what=20
  result code should be<BR>&gt;returned in the actual SearchResult in =
the case=20
  where there is a value<BR>&gt;other then success(0) in the=20
  virtualListViewResult.</DIV>
  <DIV>&gt;</DIV>
  <DIV>&gt;We should return something other then success(0)in the=20
  SearchResultDone<BR>&gt;if there is a result code other then =
success(0) in=20
  the<BR>&gt;virtualListViewResult and what that result code is should =
be=20
  defined (or<BR>&gt;referenced) in the VLV draft.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I propose that we fix this by inserting the following statement =
as=20
  paragraph 4 of Section 3.2<BR></DIV>
  <DIV>If the LDAP SearchResultDone message has a resultCode of other =
(80),=20
  <BR>the virtualListViewResponse MAY be included and MAY hold a =
non-zero=20
  <BR>value in the virtualListViewResult field.<BR></DIV>
  <DIV>If there are no objections, I'd like to add this and allow the =
draft to=20
  progress.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Jim</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0005_01C089EF.F68256E0--





From list@netscape.com  Mon Jan 29 12:53:49 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06695
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 12:53:49 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0THphG14146;
	Mon, 29 Jan 2001 09:51:43 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0THpfo04422;
	Mon, 29 Jan 2001 09:51:41 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 09:51:41 -0800 (PST)
Message-Id: <5.0.2.1.0.20010129094003.00a927a0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 29 Jan 2001 09:49:32 -0800
To: "Jim Sermersheim" <JIMSE@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Fix for VLV draft.
Cc: <ietf-ldapext@netscape.com>
In-Reply-To: <sa754304.049@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"ec3FJB.A.oBB.j2ad6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

I think it's a bad idea to overload the semantics of the 'other'
(or any other existing) result code.  'other' should only imply
some implementation specific error.   IIRC, Michael previously
suggested introduction a new result code indicating that an error
occurred during control processing.  I believe we should pursue
this approach.

Kurt

At 10:16 AM 1/29/01 -0700, Jim Sermersheim wrote:
>Back in September, as the Virtual List View draft was going through standardization process, Michael Armijo noted the following problem:
> 
>>In section 3.2 we have details about what the virtualListViewResult
>>codes mean, but we still do not define what result code should be
>>returned in the actual SearchResult in the case where there is a value
>>other then success(0) in the virtualListViewResult.
>>
>>We should return something other then success(0)in the SearchResultDone
>>if there is a result code other then success(0) in the
>>virtualListViewResult and what that result code is should be defined (or
>>referenced) in the VLV draft.
> 
>I propose that we fix this by inserting the following statement as paragraph 4 of Section 3.2
>If the LDAP SearchResultDone message has a resultCode of other (80), 
>the virtualListViewResponse MAY be included and MAY hold a non-zero 
>value in the virtualListViewResult field.
>If there are no objections, I'd like to add this and allow the draft to progress.
> 
>Jim



From list@netscape.com  Mon Jan 29 13:06:11 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06926
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 13:06:10 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TI46G16741;
	Mon, 29 Jan 2001 10:04:06 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TI47I11895;
	Mon, 29 Jan 2001 10:04:07 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 10:04:07 -0800 (PST)
Message-ID: <3A75B08B.927732D1@netscape.com>
Date: Mon, 29 Jan 2001 13:03:56 -0500
From: mcs@netscape.com (Mark C Smith)
Organization: iPlanet E-Commerce Solutions
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jim Sermersheim <JIMSE@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Fix for VLV draft.
References: <sa754304.049@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"T5BN_D.A.l5C.VCbd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

I think you meant to say "section 5.2" not "section 3.2".

I think your proposed change is okay.  Another valid approach, and this
is the one that is implemented in iPlanet's products, is to recommend
that the client always examine the virtualListViewResult.  A VLV client
will need to parse the virtualListViewResponse upon success (to get the
VLV offset information) or error (to find out if VLV control caused the
error to be generated).  So it would be sufficient IMHO to just say "a
result code other than success SHOULD be returned in the
SearchResultDone message if the virtualListViewResult is not success."

-Mark Smith
 Netscape


Jim Sermersheim wrote:

>  Back in September, as the Virtual List View draft was going through
> standardization process, Michael Armijo noted the following
> problem: >In section 3.2 we have details about what the
> virtualListViewResult
> >codes mean, but we still do not define what result code should be
> >returned in the actual SearchResult in the case where there is a
> value
> >other then success(0) in the virtualListViewResult.>>We should return
> something other then success(0)in the SearchResultDone
> >if there is a result code other then success(0) in the
> >virtualListViewResult and what that result code is should be defined
> (or
> >referenced) in the VLV draft. I propose that we fix this by inserting
> the following statement as paragraph 4 of Section 3.2If the LDAP
> SearchResultDone message has a resultCode of other (80),
> the virtualListViewResponse MAY be included and MAY hold a non-zero
> value in the virtualListViewResult field.If there are no objections,
> I'd like to add this and allow the draft to progress. Jim



From list@netscape.com  Mon Jan 29 13:08:47 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06945
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 13:08:46 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TI6bG17858;
	Mon, 29 Jan 2001 10:06:38 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TI6cA13726;
	Mon, 29 Jan 2001 10:06:38 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 10:06:38 -0800 (PST)
Message-Id: <5.0.2.1.0.20010129094944.00a92360@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 29 Jan 2001 10:05:42 -0800
To: <John.Liang@openwave.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: RE: Fix for VLV draft.
Cc: "Jim Sermersheim" <JIMSE@novell.com>, <ietf-ldapext@netscape.com>
In-Reply-To: <000401c08a19$df585ee0$ba05400a@software.com>
References: <sa754304.049@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"CPzbxB.A.MWD.tEbd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

I think we have a general problem with this and other controls
in behavior of critical vs. non-critical controls.

Processing of a recognized and appropriate control should not
depend on the control's criticality.  If the control is recognized
and supported but contains some error, I suggest the operation
return an error.

We had a good discussion regarding this general issue in regards to
the DUPENT I-D which folks might want to review.

At 12:35 PM 1/29/01 -0500, John Liang wrote:
>I want to ask a few questions about this topic:
> 
>1> if the control is not critical, and there is an error in server side sorting control 
>or virutal list view control, the server is supposed to send back all unsorted result.



>if the server returns all unsorted entries successfully,
>is LDAP searchResultDone message supposed to return LDAP_SUCCESS or other(80)?
>Must we include sssResponse and vlvResponse with corresponding error code?
> 
>2> if the control is critical, besides return LDAP_UNAVAILABLE_CRITICAL_EXTENSION,
>Must we return the corrseponding sssResponse and vlvResponse result code?


> 
>Thanks,
>--
>John Liang
>>-----Original Message-----
>>From: Jim Sermersheim [mailto:JIMSE@novell.com]
>>Sent: Monday, January 29, 2001 12:17 PM
>>To: ietf-ldapext@netscape.com
>>Subject: Fix for VLV draft.
>>
>>Back in September, as the Virtual List View draft was going through standardization process, Michael Armijo noted the following problem:
>> 
>>>In section 3.2 we have details about what the virtualListViewResult
>>>codes mean, but we still do not define what result code should be
>>>returned in the actual SearchResult in the case where there is a value
>>>other then success(0) in the virtualListViewResult.
>>>
>>>We should return something other then success(0)in the SearchResultDone
>>>if there is a result code other then success(0) in the
>>>virtualListViewResult and what that result code is should be defined (or
>>>referenced) in the VLV draft.
>> 
>>I propose that we fix this by inserting the following statement as paragraph 4 of Section 3.2
>>If the LDAP SearchResultDone message has a resultCode of other (80), 
>>the virtualListViewResponse MAY be included and MAY hold a non-zero 
>>value in the virtualListViewResult field.
>>If there are no objections, I'd like to add this and allow the draft to progress.
>> 
>>Jim



From list@netscape.com  Mon Jan 29 13:33:07 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07231
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 13:33:06 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TIV1G23060;
	Mon, 29 Jan 2001 10:31:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TIV1E29296;
	Mon, 29 Jan 2001 10:31:01 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 10:31:01 -0800 (PST)
Reply-To: <John.Liang@openwave.com>
From: "John Liang" <John.Liang@openwave.com>
To: "Kurt D. Zeilenga" <Kurt@openldap.org>
Cc: "Jim Sermersheim" <JIMSE@novell.com>, <ietf-ldapext@netscape.com>
Subject: RE: Fix for VLV draft.
Date: Mon, 29 Jan 2001 13:30:51 -0500
Message-ID: <000c01c08a21$9bc77d70$ba05400a@software.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <5.0.2.1.0.20010129094944.00a92360@router.boolean.net>
Resent-Message-ID: <"VV5tn.A.5IH.jbbd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
> Sent: Monday, January 29, 2001 1:06 PM
> To: John.Liang@openwave.com
> Cc: Jim Sermersheim; ietf-ldapext@netscape.com
> Subject: RE: Fix for VLV draft.
> 
> 
> I think we have a general problem with this and other controls
> in behavior of critical vs. non-critical controls.
> 
> Processing of a recognized and appropriate control should not
> depend on the control's criticality.  If the control is recognized
> and supported but contains some error, I suggest the operation
> return an error.

So you mean the unsorted entries will be returned but there will
be an error code in the LDAP searchResultDone message. Then in this
case, do we need to send sssResponse and vlvResponse with the same
error code? Sounds like a duplicate error code.
 
> 
> We had a good discussion regarding this general issue in regards to
> the DUPENT I-D which folks might want to review.
> 
Where could i find more details about the discussion?

Thanks,
--
John Liang





From list@netscape.com  Mon Jan 29 14:18:01 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08007
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 14:18:00 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TJFkG03793;
	Mon, 29 Jan 2001 11:15:46 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TJFlk23932;
	Mon, 29 Jan 2001 11:15:47 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 11:15:47 -0800 (PST)
Message-Id: <5.0.2.1.0.20010129105501.00aa1920@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 29 Jan 2001 11:14:46 -0800
To: <John.Liang@openwave.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: RE: Fix for VLV draft.
Cc: "Jim Sermersheim" <JIMSE@novell.com>, <ietf-ldapext@netscape.com>
In-Reply-To: <000c01c08a21$9bc77d70$ba05400a@software.com>
References: <5.0.2.1.0.20010129094944.00a92360@router.boolean.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"oMud-.A.q1F.hFcd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 01:30 PM 1/29/01 -0500, John Liang wrote:


>So you mean the unsorted entries will be returned but there will
>be an error code in the LDAP searchResultDone message.

I'm saying that a control TS which overloads the control
criticality field is flawed and this flaw should be fixed.
I have not yet made any suggestion on how it should be fixed.

>> 
>> We had a good discussion regarding this general issue in regards to
>> the DUPENT I-D which folks might want to review.
>> 
>Where could i find more details about the discussion?

In the archives: http://www.openldap.org/lists/ietf-ldapext/
Try searching for "dupent;criticality".



From list@netscape.com  Mon Jan 29 16:09:18 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10103
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 16:09:17 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TL72G24775;
	Mon, 29 Jan 2001 13:07:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TL72U22977;
	Mon, 29 Jan 2001 13:07:02 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 13:07:02 -0800 (PST)
Message-Id: <sa7578db.041@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Mon, 29 Jan 2001 14:06:15 -0700
From: "Jim Sermersheim" <JIMSE@novell.com>
To: <Kurt@openldap.org>, <John.Liang@openwave.com>
Cc: <ietf-ldapext@netscape.com>
Subject: RE: Fix for VLV draft.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0TL6pv22720
Resent-Message-ID: <"aywgcB.A.fkF.xtdd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/29/01 12:14:46 PM >>>
>At 01:30 PM 1/29/01 -0500, John Liang wrote:
>>So you mean the unsorted entries will be returned but there will
>>be an error code in the LDAP searchResultDone message.
>
>I'm saying that a control TS which overloads the control
>criticality field is flawed and this flaw should be fixed.
>I have not yet made any suggestion on how it should be fixed.

I agree. I don't believe the VLV draft overloads the criticality field. I don't think there is anything in the VLV spec that goes against the directions in 2251. That is, if the control is recognized and appropriate, it will be serviced (unless malformed. If it is not recognized or appropriate, it will either be ignored (false criticality), or the operation will fail (true criticality). 

If there is a problem while servicing the control (regardles of criticality), the operation will fail, and a VLVresponse will accompany the SearchResultDone message. If the problem that originated the failure was due to the processing of the VLV control, the virtualListViewResult is used to convey the problem. This is where the current contention lies with the draft.

Jim



From list@netscape.com  Mon Jan 29 16:30:49 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10288
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 16:30:49 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TLStb07419;
	Mon, 29 Jan 2001 13:28:55 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TLSuE04141;
	Mon, 29 Jan 2001 13:28:56 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 13:28:56 -0800 (PST)
Message-Id: <5.0.2.1.0.20010129131344.00a7e820@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 29 Jan 2001 13:27:58 -0800
To: "Jim Sermersheim" <JIMSE@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: RE: Fix for VLV draft.
Cc: <John.Liang@openwave.com>, <ietf-ldapext@netscape.com>
In-Reply-To: <sa7578db.041@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"wBTam.A.TAB.XCed6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 02:06 PM 1/29/01 -0700, Jim Sermersheim wrote:
>>>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/29/01 12:14:46 PM >>>
>>At 01:30 PM 1/29/01 -0500, John Liang wrote:
>>>So you mean the unsorted entries will be returned but there will
>>>be an error code in the LDAP searchResultDone message.
>>
>>I'm saying that a control TS which overloads the control
>>criticality field is flawed and this flaw should be fixed.
>>I have not yet made any suggestion on how it should be fixed.
>
>I agree. I don't believe the VLV draft overloads the criticality field. I don't think there is anything in the VLV spec that goes against the directions in 2251. That is, if the control is recognized and appropriate, it will be serviced (unless malformed. If it is not recognized or appropriate, it will either be ignored (false criticality), or the operation will fail (true criticality). 

Just for clarity (I think we're agreeing):
  If the control is recognized and appropriate for the operation
  (e.g. it's a search control on a search operation), it will
  be processed.  If the control is malformed, it should be processed
  as a protocol error.

  Though "appropriate"ness can be defined on a per control basis,
  one should be careful to distinguish "appropriate"ness and
  error conditions. "Appropriate"ness should be determined
  before any processing.

>If there is a problem while servicing the control (regardles of criticality), the operation will fail, and a VLVresponse will accompany the SearchResultDone message. If the problem that originated the failure was due to the processing of the VLV control, the virtualListViewResult is used to convey the problem. This is where the current contention lies with the draft.

Thanks for the clarification.




From list@netscape.com  Mon Jan 29 18:14:18 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11804
	for <ldapext-archive@odin.ietf.org>; Mon, 29 Jan 2001 18:14:16 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0TNC3G17012;
	Mon, 29 Jan 2001 15:12:03 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0TNC4I25474;
	Mon, 29 Jan 2001 15:12:04 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 15:12:04 -0800 (PST)
X-Sender: misterprivacy@hushmail.com
From: Dave <misterprivacy@hushmail.com>
To: "customer" <misterprivacy@hushmail.com>
Date: Mon, 29 Jan 2001 14:25:17 -0500
Subject: I could go to JAIL for selling this CD!
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001__10618077_51917.11"
Message-Id: <E14NNPk-0002Od-00@dfw-mmp2.email.verio.net>
Resent-Message-ID: <"F98FtD.A.oNG.Djfd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a Multipart MIME message.

------=_NextPart_000_001__10618077_51917.11
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit


------=_NextPart_000_001__10618077_51917.11
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: base64

PCFkb2N0eXBlIGh0bWwgcHVibGljICItLy93M2MvL2R0ZCBodG1sIDQuMCB0cmFuc2l0aW9u
YWwvL2VuIj4NCjxodG1sPg0KPGhlYWQ+DQogICA8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50
LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1pc28tODg1OS0xIj4NCiAgIDxt
ZXRhIG5hbWU9IkdFTkVSQVRPUiIgY29udGVudD0iTW96aWxsYS80LjYxIFtlbl0gKFdpbjk4
OyBJKSBbTmV0c2NhcGVdIj4NCiAgIDx0aXRsZT5UaGUgQkFOTkVEIENEITwvdGl0bGU+DQo8
L2hlYWQ+DQo8Ym9keT4NCjxmb250IHNpemU9KzE+SGksPC9mb250Pg0KPHA+PGZvbnQgc2l6
ZT0rMT5JIGhhdmUgYmVlbiByZWNpZXZpbmcgZW1haWxzIHNheWluZyB0aGF0IEknbSBjb250
cmlidXRpbmcNCnRvPC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+dGhlICJtb3JhbCBkZWNh
eSBvZiBzb2NpZXR5IiBieSBzZWxsaW5nIHRoZSBCYW5uZWQgQ0QuJm5ic3A7DQpUaGF0PC9m
b250Pg0KPGJyPjxmb250IHNpemU9KzE+bWF5IGJlLCBidXQgSSBmZWVsIHN0cm9uZ2x5IHRo
YXQgeW91IGhhdmUgYSByaWdodCB0bw0KYmVuZWZpdCBmcm9tPC9mb250Pg0KPGJyPjxmb250
IHNpemU9KzE+dGhpcyBoYXJkLXRvLWZpbmQgaW5mb3JtYXRpb24uPC9mb250Pg0KPHA+PGZv
bnQgY29sb3I9IiNDQzAwMDAiPjxmb250IHNpemU9KzE+U28gSSBhbSBnaXZpbmcgeW91IE9O
RSBMQVNUIENIQU5DRQ0KdG8gb3JkZXI8L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9y
PSIjQ0MwMDAwIj48Zm9udCBzaXplPSsxPnRoZSBCYW5uZWQgQ0QhPC9mb250PjwvZm9udD4N
Cjxicj4mbmJzcDsNCjx0YWJsZSBCT1JERVI9MCBDT0xTPTIgV0lEVEg9Ijc1JSIgPg0KPHRy
Pg0KPHRkIFdJRFRIPSIxJSI+PGltZyBTUkM9Imh0dHA6Ly9jb21wdXpvbmV1c2EuY29tL2lt
YWdlcy9zcHkuanBnIiBoZWlnaHQ9MTI4IHdpZHRoPTg2PjwvdGQ+DQoNCjx0ZD48Zm9udCBz
aXplPSsxPldpdGggdGhpcyBwb3dlcmZ1bCBDRCwgeW91IHdpbGwgYmUgYWJsZSB0byBpbnZl
c3RpZ2F0ZQ0KeW91ciBmcmllbmRzLCBlbmVtaWVzIGFuZCBsb3ZlcnMgaW4ganVzdCBtaW51
dGVzIHVzaW5nIHRoZSBJbnRlcm5ldC4mbmJzcDsNCllvdSBjYW4gdHJhY2sgZG93biBvbGQg
ZmxhbWVzIGZyb20gY29sbGVnZSwgb3IgeW91IGNhbiBkaWcgdXAgc29tZSBkaXJ0DQpvbiB5
b3VyIGJvc3MgdG8gbWFrZSBzdXJlIHlvdSBnZXQgdGhhdCBuZXh0IHByb21vdGlvbiE8L2Zv
bnQ+PC90ZD4NCjwvdHI+DQo8L3RhYmxlPg0KDQo8cD48Zm9udCBzaXplPSsxPk9yIG1heWJl
IHlvdSB3YW50IGEgZmFrZSBkaXBsb21hIHRvIGhhbmcgb24geW91ciBiZWRyb29tPC9mb250
Pg0KPGJyPjxmb250IHNpemU9KzE+d2FsbC4mbmJzcDsgWW91J2xsIGZpbmQgYWRkcmVzc2Vz
IGZvciBjb21wYW5pZXMgdGhhdA0KbWFrZSB0aGVzZTwvZm9udD4NCjxicj48Zm9udCBzaXpl
PSsxPmRpcGxvbWFzIG9uIHRoZSBCYW5uZWQgQ0QuPC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0r
MT5OZWVkIHRvIGRpc2FwcGVhciBmYXN0IGFuZCBuZXZlciBsb29rIGJhY2s/Jm5ic3A7IE5v
IHByb2JsZW0hPC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+VXNpbmcgdGhlIEJhbm5lZCBD
RCwgeW91IHdpbGwgbGVhcm4gaG93IHRvIGJ1aWxkIGEgY29tcGxldGVseTwvZm9udD4NCjxi
cj48Zm9udCBzaXplPSsxPm5ldyBpZGVudGl0eS48L2ZvbnQ+DQo8cD48Zm9udCBzaXplPSsx
Pk9idmlvdXNseSwgdGhlIFBvd2VycyBUaGF0IEJlIGRvbid0IHdhbnQgeW91IHRvIGhhdmUg
dGhlPC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+QmFubmVkIENELiZuYnNwOyBUaGV5IGhh
dmUgdGhyZWF0ZW5lZCBtZSB3aXRoIGxhd3N1aXRzLA0KZmluZXMsPC9mb250Pg0KPGJyPjxm
b250IHNpemU9KzE+YW5kIGV2ZW4gaW1wcmlzb25tZW50IHVubGVzcyBJIHN0b3Agc2VsbGlu
ZyBpdCBpbW1lZGlhdGVseS48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0rMT5CdXQgSSBmZWVs
IHRoYXQgWU9VIGhhdmUgYSBDb25zdGl0dXRpb25hbCByaWdodCB0byBhY2Nlc3M8L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0rMT50aGlzIHR5cGUgb2YgaW5mb3JtYXRpb24sIGFuZCBJIGNh
bid0IGJlIGludGltaWRhdGVkLjwvZm9udD4NCjxicj4mbmJzcDsNCjx0YWJsZSBCT1JERVI9
MCBDT0xTPTIgV0lEVEg9IjUwJSIgPg0KPHRyPg0KPHRkIFdJRFRIPSIxMDAlIj48aT48Zm9u
dCBjb2xvcj0iIzMzMzNGRiI+PGZvbnQgc2l6ZT0rMT5VbmNsZSBTYW0gYW5kIHlvdXINCmNy
ZWRpdG9ycyBhcmUgaG9ycmlmaWVkIHRoYXQgSSBhbSBzdGlsbCBzZWxsaW5nIHRoaXMgcHJv
ZHVjdCEmbmJzcDsgVGhlcmUNCm11c3QgYmUgYSBwcmljZSBvbiBteSBoZWFkITwvZm9udD48
L2ZvbnQ+PC9pPjwvdGQ+DQoNCjx0ZCBXSURUSD0iMSUiPjxpbWcgU1JDPSJodHRwOi8vY29t
cHV6b25ldXNhLmNvbS9pbWFnZXMvb3V0bGF3LmpwZyIgaGVpZ2h0PTEyOCB3aWR0aD05Mz48
L3RkPg0KPC90cj4NCjwvdGFibGU+DQoNCjxwPjxmb250IHNpemU9KzE+V2h5IGFyZSB0aGV5
IHNvIHVwc2V0PyBCZWNhdXNlIHRoaXMgQ0QgZ2l2ZXMgeW91IGZyZWVkb20uPC9mb250Pg0K
PGJyPjxmb250IHNpemU9KzE+QW5kIHlvdSBjYW4ndCBidXkgZnJlZWRvbSBhdCB5b3VyIGxv
Y2FsIFdhbG1hcnQuJm5ic3A7DQpZb3Ugd2lsbDwvZm9udD4NCjxicj48Zm9udCBzaXplPSsx
PmhhdmUgdGhlIGZyZWVkb20gdG8gYXZvaWQgY3JlZGl0b3JzLCBqdWRnbWVudHMsIGxhd3N1
aXRzLA0KSVJTPC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+dGF4IGNvbGxlY3RvcnMsIGNy
aW1pbmFsIGluZGljdG1lbnRzLCB5b3VyIGdyZWVkeSBleC13aWZlDQpvcjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPSsxPmV4LWh1c2JhbmQsIGFuZCBNVUNIIG1vcmUhPC9mb250Pg0KPHA+
PGZvbnQgc2l6ZT0rMT5KdXN0IGxvb2sgYXQgc29tZSBvZiB0aGUgdGhpbmdzIHlvdSBjYW4g
ZG8gd2l0aCB0aGlzIENEDQouLi48L2ZvbnQ+DQo8dWw+DQo8bGk+DQo8Yj48Zm9udCBjb2xv
cj0iIzAwMDA5OSI+U2F2ZSBodW5kcmVkcyBvciBldmVuIHRob3VzYW5kcyBvZiBkb2xsYXJz
IG9uDQp5b3VyIHRheGVzIGJ5IHVzaW5nIHRoZSBzZWNyZXQgdGF4IHRpcHMgY29udGFpbmVk
IGluIHRoaXMgcGFja2FnZS4mbmJzcDsNClRoZSBJUlMgZG9lcyBOT1Qgd2FudCB5b3UgdG8g
a25vdyB0aGVzZSBsb29waG9sZXMhPC9mb250PjwvYj48L2xpPg0KDQo8bGk+DQo8Yj48Zm9u
dCBjb2xvcj0iIzAwMDA5OSI+VHJhY2sgZG93biBmcmllbmRzIGFuZCBvbGQgZmxhbWVzIGZy
b20gdGhlIGNvbWZvcnQNCm9mIHlvdXIgb3duIGhvbWUgd2l0aCBvdXIgSW50ZXJuZXQgaW52
ZXN0aWdhdGlvbiByZXNvdXJjZXMhPC9mb250PjwvYj48L2xpPg0KDQo8bGk+DQo8Yj48Zm9u
dCBjb2xvcj0iIzAwMDA5OSI+RmluZCBvdXQgd2hlcmUgeW91ciBFWCBpcyBoaWRpbmcgdGhl
aXIgbW9uZXkgdG8NCmF2b2lkIGFsaW1vbnksIGNoaWxkIHN1cHBvcnQsIG9yIGRpdm9yY2Ug
c2V0dGxlbWVudHMuIFRoZW4gZ2V0IHlvdXIgaGFuZHMNCm9uIHRoYXQgbW9uZXkuJm5ic3A7
IEJsZWVkICdlbSBkcnkhJm5ic3A7IFByaXZhdGUgaW52ZXN0aWdhdG9ycyBjaGFyZ2UNCnRo
b3VzYW5kcyBvZiBkb2xsYXJzIGZvciB0aGlzIHNlcnZpY2UsIGJ1dCB5b3UgY2FuIGRvIGl0
IHdpdGggYSBjb21wdXRlcg0KYW5kIGFuIGludGVybmV0IGNvbmVjdGlvbiB3aGVuIHlvdSBi
dXkgdGhlIEJhbm5lZCBDRCE8L2ZvbnQ+PC9iPjwvbGk+DQoNCjxsaT4NCjxiPjxmb250IGNv
bG9yPSIjMDAwMDk5Ij5MZWFybiBob3cgdG8gdXNlIG9mZnNob3JlIG1vbmV5IGhhdmVucyBh
bmQgYXNzZXQNCnByb3RlY3Rpb24gdHJ1c3RzIHRvIGF2b2lkIGxhd3N1aXRzLCBqdWRnbWVu
dHMsIGFuZCBmb29sIHRoZSBtb3N0IGFnZ3Jlc3NpdmUNCnRheCBjb2xsZWN0b3IhJm5ic3A7
IElmIHlvdXIgbW9uZXkgaXMgc2l0dGluZyBpbiBhIFVTIGJhbmsgYWNjb3VudCwgeW91cg0K
ZnVuZHMgY2FuIGJlIGxldmllZCBvciBmcm96ZW4gY29tcGxldGVseSBhdCBhbnkgdGltZS4m
bmJzcDsgVGhlIFVTIGdvdmVybm1lbnQNCnVzZXMgImNpdmlsIGFzc2V0IGZvcmZlaXR1cmUi
IHRvIHN0ZWFsIGJpbGxpb25zIG9mIGRvbGxhcnMgZWFjaCB5ZWFyIGZyb20NCmhhcmQtd29y
a2luZywgbGF3IGFiaWRpbmcgY2l0aXplbnMuJm5ic3A7IEdldCB5b3VyIG1vbmV5IG91dCBv
ZiB0aGUgY291bnRyeQ0KYmVmb3JlIFVuY2xlIFNhbSBzbmF0Y2hlcyBpdCBhbGwuPC9mb250
PjwvYj48L2xpPg0KDQo8bGk+DQo8Yj48Zm9udCBjb2xvcj0iIzAwMDA5OSI+RmluZCBvdXQg
d2hlcmUgdG8gYnV5ICJmb3JiaWRkZW4gcHJvZHVjdHMiIG9uDQp0aGUgSW50ZXJuZXQuIEZ1
cnRoZXIgZWxhYm9yYXRpb24gc2hvdWxkIG5vdCBiZSBuZWNlc3Nhcnk7IGp1c3QgdXNlIHlv
dXINCmltYWdpbmF0aW9uLjwvZm9udD48L2I+PC9saT4NCg0KPGxpPg0KPGI+PGZvbnQgY29s
b3I9IiMwMDAwOTkiPkdldCBhIGJldHRlciBqb2IgYnkgcHVyY2hhc2luZyBhIGNvbGxlZ2Ug
ZGVncmVlDQooaW5jbHVkaW5nIGEgUGhkISkgZm9yIGEgdmVyeSBsb3cgZmVlLiBObyBzdHVk
eSByZXF1aXJlZCE8L2ZvbnQ+PC9iPjwvbGk+DQoNCjxsaT4NCjxiPjxmb250IGNvbG9yPSIj
MDAwMDk5Ij5JZiB5b3VyIEVYIGlzIGNvbWluZyBhZnRlciB5b3VyIG1vbmV5LCBzdGF5IG9u
ZQ0Kc3RlcCBhaGVhZCBvZiB0aGUgbGF3eWVycyBhbmQga2VlcCB0aGVpciBncmVlZHkgaGFu
ZHMgb2ZmIHlvdXIgbG9vdC4gRmluZA0Kb3V0IGhvdyB0byBoaWRlIHlvdXIgbW9uZXkgd2hl
cmUgaXQgd2lsbCBuZXZlciBiZSBmb3VuZC48L2ZvbnQ+PC9iPjwvbGk+DQoNCjxsaT4NCjxi
Pjxmb250IGNvbG9yPSIjMDAwMDk5Ij5Bdm9pZCBsZWdhbCBwcm9ibGVtcywganVkZ21lbnRz
LCBjb252aWN0aW9ucywNCmFuZCBldmVuIHByaXNvbiBzZW50ZW5jZXMgYnkgb2J0YWluaW5n
IGEgY29tcGxldGVseSBuZXcgaWRlbnRpdHkgYW5kIGRpc2FwcGVhcmluZw0Kd2l0aG91dCBh
IHRyYWNlITwvZm9udD48L2I+PC9saT4NCg0KPGxpPg0KPGI+PGZvbnQgY29sb3I9IiMwMDAw
OTkiPkVyYXNlIHlvdXIgY3JpbWluYWwgcmVjb3JkIGFuZCBvYnRhaW4gYSBjb3B5IG9mDQp5
b3VyIEZCSSBmaWxlIHVzaW5nIHRoZSBGcmVlZG9tIG9mIEluZm9ybWF0aW9uIEFjdC4mbmJz
cDsgRmluZCBvdXQgaWYgdGhlDQpnb3Zlcm5tZW50IGlzIGludmVzdGlnYXRpbmcgeW91IE5P
VyBiZWZvcmUgaXQncyB0b28gTEFURSE8L2ZvbnQ+PC9iPjwvbGk+DQo8L3VsPg0KPGZvbnQg
c2l6ZT0rMT5JZiB5b3UgaGF2ZSBiZWVuIHB1dHRpbmcgb2ZmIGJ1eWluZyBUaGUgQmFubmVk
IENELCB3aGF0IGFyZQ0KeW91PC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+d2FpdGluZyBm
b3I/Jm5ic3A7IEJpZyBCcm90aGVyIGlzIGFscmVhZHkgYnJlYXRoaW5nIGRvd24NCm15IG5l
Y2ssIHNvPC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+SSBjYW4ndCBrZWVwIHNlbGxpbmcg
aXQgZm9yZXZlci4mbmJzcDsgSWYgeW91IGtlZXAgd2FpdGluZw0KdG8gcGxhY2U8L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0rMT55b3VyIG9yZGVyLCB5b3UgbWF5IG5ldmVyIGZpbmQgVGhl
IEJhbm5lZCBDRCBhZ2Fpbi4mbmJzcDsNCkZvciBvbmx5PC9mb250Pg0KPGJyPjxmb250IHNp
emU9KzE+JDE5Ljk5LCB5b3Ugd2lsbCBnYWluIHZhbHVhYmxlIHBlYWNlLW9mLW1pbmQga25v
d2luZw0KaG93IHRvPC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+c2FmZWd1YXJkIHlvdXJz
ZWxmLCB5b3VyIGZhbWlseSwgYW5kIHlvdXIgbW9uZXkuJm5ic3A7DQpXaG8gY2FuIHB1dCBh
PC9mb250Pg0KPGJyPjxmb250IHNpemU9KzE+cHJpY2Ugb24gZnJlZWRvbT8hPC9mb250Pg0K
PHA+PGk+PHU+PGZvbnQgc2l6ZT0rMT5IZXJlIGlzIGFub3RoZXIgbG9vayBhdCB0aGUgY29u
dGVudHMgb2YgdGhlIEJBTk5FRA0KQ0Q6PC9mb250PjwvdT48L2k+DQo8cD48aW1nIFNSQz0i
aHR0cDovL2NvbXB1em9uZXVzYS5jb20vaW1hZ2VzL2J1dHRvbi5naWYiIGhlaWdodD0xOSB3
aWR0aD0xOT48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT4NCkZpbmQgY29u
ZmlkZW50aWFsIGluZm8gb24gYW55b25lIGluIDMwIG1pbnV0ZXMgb3I8L2ZvbnQ+PC9mb250
Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPmxlc3Mgb24gdGhl
IEludGVybmV0LiBZb3UnbGwgYmUNCmFibGUgdG8gdHJhY2sgZG93biB5b3VyPC9mb250Pjwv
Zm9udD4NCjxicj48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5vbGQgZmxh
bWUsIGZpbmQgb3V0IGhvdyBtdWNoIG1vbmV5DQp5b3VyIGV4IGlzIGhpZGluZzwvZm9udD48
L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+aW4gdGhl
aXIgYmFuayBhY2NvdW50LCBvciBydW4gYQ0KYmFja2dyb3VuZCBjaGVjayBvbjwvZm9udD48
L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+cHJvZXNw
ZWN0aXZlIGNsaWVudCBvciBlbXBsb3llZS4NCkV2ZW4gZ292ZXJubWVudDwvZm9udD48L2Zv
bnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+YWdlbmNpZXMg
aGF2ZSB0cm91YmxlIG9idGFpbmluZw0KbXVjaCBvZiB0aGlzIGluZm9ybWF0aW9uLjwvZm9u
dD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+WW91
IHdpbGwgaGF2ZSBhbGwgdGhlIHJlc291cmNlcw0Kb2YgYW55IHByb2Zlc3Npb25hbDwvZm9u
dD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+aW52
ZXN0aWdhdG9yIHJpZ2h0IGF0IHlvdXIgZmluZ2VydGlwcw0KLSBvbiB5b3VyIGhvbWU8L2Zv
bnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPmNv
bXB1dGVyITwvZm9udD48L2ZvbnQ+DQo8cD48aW1nIFNSQz0iaHR0cDovL2NvbXB1em9uZXVz
YS5jb20vaW1hZ2VzL2J1dHRvbi5naWYiIGhlaWdodD0xOSB3aWR0aD0xOT48Zm9udCBjb2xv
cj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT4NCkxpc3Qgb2YgY29tcGFuaWVzIHdobyB3aWxs
IGlzc3VlIHlvdSBhIGNvbGxlZ2U8L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIj
NjY2NjY2Ij48Zm9udCBzaXplPSsxPmRlZ3JlZSAoaW5jbHVkaW5nIGEgUGhkLikgZm9yIGEN
CmZlZS4gTm8gc3R1ZHkgcmVxdWlyZWQhPC9mb250PjwvZm9udD4NCjxwPjxpbWcgU1JDPSJo
dHRwOi8vY29tcHV6b25ldXNhLmNvbS9pbWFnZXMvYnV0dG9uLmdpZiIgaGVpZ2h0PTE5IHdp
ZHRoPTE5Pjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPg0KTGVhcm4gaG93
IHRvIGdldCBGUkVFIGNhYmxlIGFuZCBEU1MgY2hhbm5lbHMsPC9mb250PjwvZm9udD4NCjxi
cj48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5pbmNsdWRpbmcgdGhlIGFk
dWx0IHN0YXRpb25zIGFuZA0KUGF5LVBlci1WaWV3ITwvZm9udD48L2ZvbnQ+DQo8cD48aW1n
IFNSQz0iaHR0cDovL2NvbXB1em9uZXVzYS5jb20vaW1hZ2VzL2J1dHRvbi5naWYiIGhlaWdo
dD0xOSB3aWR0aD0xOT48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT4NCkhv
dyB0byBPYnRhaW4gTWljcm9zb2Z0IFByb2R1Y3RzIGFic29sdXRlbHk8L2ZvbnQ+PC9mb250
Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPkZSRUUsIHRoZSBz
YWZlIGFuZCBMRUdBTCB3YXkhPC9mb250PjwvZm9udD4NCjxwPjxpbWcgU1JDPSJodHRwOi8v
Y29tcHV6b25ldXNhLmNvbS9pbWFnZXMvYnV0dG9uLmdpZiIgaGVpZ2h0PTE5IHdpZHRoPTE5
Pjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPg0KTGlzdCBvZiBzdXBwbGll
cnMgb2YgInF1ZXN0aW9uYWJsZSIgaXRlbXMsIHN1Y2g8L2ZvbnQ+PC9mb250Pg0KPGJyPjxm
b250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPmFzIGZjYyBiYW5uZWQgY29tbXVu
aWNhdGlvbnMgZGV2aWNlcywNCnNjYW5uZXJzLDwvZm9udD48L2ZvbnQ+DQo8YnI+PGZvbnQg
Y29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+bmlnaHQgdmlzaW9uIGdvZ2dsZXMsIHBh
c3Nwb3J0cywNCmZha2UgaWRlbnRpZmljYXRpb24sPC9mb250PjwvZm9udD4NCjxicj48Zm9u
dCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5hbmQgZXZlcnl0aGluZyBlbHNlIHRo
YXQgeW91IHdvbid0DQpmaW5kIGluIHRoZSBiYWNrPC9mb250PjwvZm9udD4NCjxicj48Zm9u
dCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5vZiBTb2xkaWVyIG9mIEZvcnR1bmUg
bWFnYXppbmUhPC9mb250PjwvZm9udD4NCjxwPjxpbWcgU1JDPSJodHRwOi8vY29tcHV6b25l
dXNhLmNvbS9pbWFnZXMvYnV0dG9uLmdpZiIgaGVpZ2h0PTE5IHdpZHRoPTE5Pjxmb250IGNv
bG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPg0KRmluZCBwcm9kdWN0cyB0byByZXNlbGwg
b24gdGhlIEludGVybmV0IHdpdGggb3VyPC9mb250PjwvZm9udD4NCjxicj48Zm9udCBjb2xv
cj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5XaG9sZXNhbGUgRGlyZWN0b3J5IGNvbnRhaW5p
bmcNCm92ZXIgMSBtaWxsaW9uPC9mb250PjwvZm9udD4NCjxicj48Zm9udCBjb2xvcj0iIzY2
NjY2NiI+PGZvbnQgc2l6ZT0rMT4odGhhdCdzIHJpZ2h0LCBvbmUgbWlsbGlvbiEpIHdob2xl
c2FsZQ0Kc291cmNlcyBmb3I8L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2
NjY2Ij48Zm9udCBzaXplPSsxPmNvbXB1dGVycywgZWxlY3Ryb25pY3MsIGJlYW5pZXMsDQp0
cmVuZCBpdGVtcyw8L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2NjY2Ij48
Zm9udCBzaXplPSsxPmpld2VscnksIGNhcnMsIGNvbGxlY3RpYmxlcywgYW5kDQpldmVyeXRo
aW5nIGVsc2UhPC9mb250PjwvZm9udD4NCjxwPjxpbWcgU1JDPSJodHRwOi8vY29tcHV6b25l
dXNhLmNvbS9pbWFnZXMvYnV0dG9uLmdpZiIgaGVpZ2h0PTE5IHdpZHRoPTE5Pjxmb250IGNv
bG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPg0KT3ZlciAyNSBtaWxsaW9uIGVtYWlsIGFk
ZHJlc3NlcywgZnJlc2ggYW5kPC9mb250PjwvZm9udD4NCjxicj48Zm9udCBjb2xvcj0iIzY2
NjY2NiI+PGZvbnQgc2l6ZT0rMT50YXJnZXRlZCEgWW91IGNhbiB1c2UgdGhlc2UgdG8NCmNv
bnRhY3QgdGhlIHBlb3BsZTwvZm9udD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2
NjYiPjxmb250IHNpemU9KzE+YW5kIHNlbmQgdGhlbSB5b3VyIGFkdmVydGlzZW1lbnRzLjwv
Zm9udD48L2ZvbnQ+DQo8cD48aW1nIFNSQz0iaHR0cDovL2NvbXB1em9uZXVzYS5jb20vaW1h
Z2VzL2J1dHRvbi5naWYiIGhlaWdodD0xOSB3aWR0aD0xOT48Zm9udCBjb2xvcj0iIzY2NjY2
NiI+PGZvbnQgc2l6ZT0rMT4NCkZpbmQgb3V0IGhvdyB0byBnZXQgYSBjb21wbGV0ZWx5IG5l
dyBpZGVudGl0eS48L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2NjY2Ij48
Zm9udCBzaXplPSsxPkRpc2FwcGVhciB3aXRob3V0IGEgdHJhY2UhPC9mb250PjwvZm9udD4N
CjxwPjxpbWcgU1JDPSJodHRwOi8vY29tcHV6b25ldXNhLmNvbS9pbWFnZXMvYnV0dG9uLmdp
ZiIgaGVpZ2h0PTE5IHdpZHRoPTE5Pjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXpl
PSsxPg0KRmluZCBvdXQgaG93IHRvIEVSQVNFIGJhZCBjcmVkaXQgYW5kIGV2ZW48L2ZvbnQ+
PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPmNyZWF0
ZSBhIHdob2xlIG5ldyBmaWxlIGluIHRoZQ0KY3JlZGl0IGJ1cmVhdSBjb21wdXRlcnMuPC9m
b250PjwvZm9udD4NCjxwPjxpbWcgU1JDPSJodHRwOi8vY29tcHV6b25ldXNhLmNvbS9pbWFn
ZXMvYnV0dG9uLmdpZiIgaGVpZ2h0PTE5IHdpZHRoPTE5Pjxmb250IGNvbG9yPSIjNjY2NjY2
Ij48Zm9udCBzaXplPSsxPg0KTGVhcm4gaG93IHRvIGJlYXQgdGhlIElSUy4gVGF4IHRpcHMg
Zm9yIHRoZTwvZm9udD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250
IHNpemU9KzE+cmVzdCBvZiB1cy48L2ZvbnQ+PC9mb250Pg0KPHA+PGltZyBTUkM9Imh0dHA6
Ly9jb21wdXpvbmV1c2EuY29tL2ltYWdlcy9idXR0b24uZ2lmIiBoZWlnaHQ9MTkgd2lkdGg9
MTk+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+DQpDb21wbGV0ZSBndWlk
ZSBvbiBob3cgdG8gY2xhaW0gcHVibGljIGxhbmQ8L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250
IGNvbG9yPSIjNjY2NjY2Ij48Zm9udCBzaXplPSsxPm9mZmVyZWQgYnkgdGhlIEdvdmVybm1l
bnQuIFlvdQ0KY2FuIGZpbmQgeW91cjwvZm9udD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9
IiM2NjY2NjYiPjxmb250IHNpemU9KzE+ZHJlYW0gaG9tZSBmb3IgYSByaWRpY3Vsb3VzbHkg
bG93DQpwcmljZSBvciBidXk8L2ZvbnQ+PC9mb250Pg0KPGJyPjxmb250IGNvbG9yPSIjNjY2
NjY2Ij48Zm9udCBzaXplPSsxPnByb3BlcnRpZXMgdG8gcmVzZWxsIGZvciBhIGh1Z2UNCnBy
b2ZpdCE8L2ZvbnQ+PC9mb250Pg0KPHA+PGltZyBTUkM9Imh0dHA6Ly9jb21wdXpvbmV1c2Eu
Y29tL2ltYWdlcy9idXR0b24uZ2lmIiBoZWlnaHQ9MTkgd2lkdGg9MTk+PGZvbnQgY29sb3I9
IiM2NjY2NjYiPjxmb250IHNpemU9KzE+DQpBY2NlcHQgY2hlY2tzIGZyb20geW91ciBjdXN0
b21lcnMgYnkgZmF4LDwvZm9udD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYi
Pjxmb250IHNpemU9KzE+cGhvbmUgYW5kIGVtYWlsIHdpdGggdGhlIGZ1bGwgd29ya2luZw0K
dmVyc2lvbiBvZjwvZm9udD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxm
b250IHNpemU9KzE+Q2hlY2tlciBTb2Z0d2FyZSBpbmNsdWRlZCE8L2ZvbnQ+PC9mb250Pg0K
PHA+PGltZyBTUkM9Imh0dHA6Ly9jb21wdXpvbmV1c2EuY29tL2ltYWdlcy9idXR0b24uZ2lm
IiBoZWlnaHQ9MTkgd2lkdGg9MTk+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9
KzE+DQpCdXNpbmVzcyBzb2Z0d2FyZSB0byBoZWxwIHlvdSBydW4geW91ciBzbWFsbDwvZm9u
dD48L2ZvbnQ+DQo8YnI+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+YnVz
aW5lc3MsIGluY2x1ZGluZyBsYWJlbCBtYWtlcg0Kc29mdHdhcmUsIG1vbmV5PC9mb250Pjwv
Zm9udD4NCjxicj48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5tYW5hZ2Vt
ZW50IHNvZnR3YXJlLCBJUlMgZm9yZ2l2ZW5lc3MNCnByb2dyYW0sPC9mb250PjwvZm9udD4N
Cjxicj48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT5kYXRhYmFzZSBzb2Z0
d2FyZSwgYW5kIG11Y2ggbW9yZS48L2ZvbnQ+PC9mb250Pg0KPHA+PGltZyBTUkM9Imh0dHA6
Ly9jb21wdXpvbmV1c2EuY29tL2ltYWdlcy9idXR0b24uZ2lmIiBoZWlnaHQ9MTkgd2lkdGg9
MTk+PGZvbnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+DQpBIGh1Z2UgY29sbGVj
dGlvbiBvZiBzY3JlZW5zYXZlcnMsIGdyYXBoaWNzLDwvZm9udD48L2ZvbnQ+DQo8YnI+PGZv
bnQgY29sb3I9IiM2NjY2NjYiPjxmb250IHNpemU9KzE+Y2xpcGFydCwgYW5kIGRlc2t0b3Ag
dGhlbWVzIHRvDQpzcGljZSB1cCB5b3VyIGNvbXB1dGVyLjwvZm9udD48L2ZvbnQ+DQo8cD48
aW1nIFNSQz0iaHR0cDovL2NvbXB1em9uZXVzYS5jb20vaW1hZ2VzL2J1dHRvbi5naWYiIGhl
aWdodD0xOSB3aWR0aD0xOT48Zm9udCBjb2xvcj0iIzY2NjY2NiI+PGZvbnQgc2l6ZT0rMT4N
Ck1VQ0gsIE1VQ0ggTU9SRSB0aGF0IHdlIGRvbid0IGhhdmUgcm9vbSB0byBsaXN0ITwvZm9u
dD48L2ZvbnQ+DQo8cD48Zm9udCBzaXplPSsxPldlIGFyZSBzbyBjb25maWRlbnQgdGhhdCB5
b3Ugd2lsbCBsb3ZlIHRoaXMgQ0QgdGhhdCB3ZTwvZm9udD4NCjxicj48Zm9udCBzaXplPSsx
Pm9mZmVyIGEgZnVsbCAzMC1kYXksIG5vIHF1ZXN0aW9ucyBhc2tlZCBtb25leS1iYWNrPC9m
b250Pg0KPGJyPjxmb250IHNpemU9KzE+Z3VhcmFudGVlLiBUbyBvcmRlciB0aGUgIkJhbm5l
ZCBDRCIgcmlnaHQgbm93IGZvciB0aGU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0rMT5zdXBl
ciBsb3cgcHJpY2Ugb2Ygb25seSAkMTkuOTksIGp1c3QgY2xpY2sgb24gdGhlIGxpbms8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0rMT5iZWxvdyB0byBwYXkgd2l0aCBhIFZpc2Egb3IgTWFz
dGVyY2FyZDo8L2ZvbnQ+DQo8YnI+Jm5ic3A7DQo8dGFibGUgQk9SREVSPTAgQ09MUz0yIFdJ
RFRIPSI1MCUiID4NCjx0cj4NCjx0ZD48Zm9udCBzaXplPSsyPjxhIGhyZWY9Imh0dHA6Ly93
d3cuY29tcHV6b25ldXNhLmNvbS9jY3BheW1lbnQvYmFubmVkY2Q3Mi5odG0iPk9yZGVyDQpO
b3chPC9hPjwvZm9udD48L3RkPg0KDQo8dGQ+DQo8Y2VudGVyPjxpbWcgU1JDPSJodHRwOi8v
Y29tcHV6b25ldXNhLmNvbS9pbWFnZXMvZ3VhcmFudGVlLmdpZiIgaGVpZ2h0PTk2IHdpZHRo
PTk1PjwvY2VudGVyPg0KPC90ZD4NCjwvdHI+DQo8L3RhYmxlPg0KDQo8cD5PciB5b3UgbWF5
IHBheSB3aXRoIGNhc2gsIGNoZWNrIG9yIG1vbmV5IG9yZGVyIGJ5IHByaW50aW5nIHRoZSBv
cmRlcg0KPGJyPmZvcm0gYmVsb3cgYW5kIHNlbmRpbmcgaXQgd2l0aCB5b3VyIHBheW1lbnQu
DQo8cD48Yj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIENVVCBIRVJFIC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tPC9iPg0KPHA+UHJvZHVjdDogIlRoZSBCYW5uZWQgQ0QiDQo8YnI+UHJp
Y2U6ICQxOS45OSArICQ0LjAxIHNoaXBwaW5nL2hhbmRsaW5nDQo8cD5IT1cgVE8gT1JERVIg
QlkgTUFJTDogUHJpbnQgb3V0IHRoaXMgb3JkZXIgZm9ybSBhbmQgc2VuZCBjYXNoLA0KPGJy
PnBlcnNvbmFsIGNoZWNrLCBtb25leSBvcmRlciBvciBjYXNoaWVyJ3MgY2hlY2sgdG8gdGhl
IGFkZHJlc3MgbGlzdGVkDQpiZWxvdzoNCjxwPlF1aWtzaWx2ZXIgRW50ZXJwcmlzZXMgSW5j
Lg0KPGJyPjM3OTIgQnJvYWR3YXkgIzM5OA0KPGJyPk5ldyBZb3JrLCBOWSAxMDAzMg0KPHA+
WW91ciBTaGlwcGluZyBJbmZvcm1hdGlvbjoNCjxwPllvdXIgTmFtZV9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPGJyPllvdXIgQWRkcmVzc19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPGJyPllvdXIgQ2l0eV9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPGJyPlN0YXRl
IC8gWmlwX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPGJy
PlBob25lICM6IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPGJyPihGb3IgcHJvYmxlbXMgd2l0aCB5b3VyIG9yZGVyIG9ubHkuIE5vIHNhbGVzbWVu
IHdpbGwgY2FsbC4pDQo8cD5FbWFpbCBBZGRyZXNzX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPHA+UGxlYXNlIG5vdGUgdGhhdCBtYWlsLWluIG9yZGVycyBt
YXkgYmUgZGVsYXllZCAyLTQgd2Vla3MuDQo8cD5bIF0gSSBhbSBlbmNsb3NpbmcgYSBjaGVj
ayBvciBtb25leSBvcmRlciBmb3IgJDI0LjAwDQo8cD5bIF0gSSBhbSBtYWlsaW5nIG15IGNy
ZWRpdCBjYXJkIG51bWJlci4gKE5vdGUgeW91ciBjYXJkIHdpbGwgYmUgY2hhcmdlZA0KZm9y
ICQyNC4wMCkNCjxwPklmIHBheWluZyBieSBjcmVkaXQgY2FyZCwgcGxlYXNlIGZpbGwgaW4g
dGhlIGluZm9ybWF0aW9uIGJlbG93Og0KPHA+Q3JlZGl0IENhcmQgTnVtYmVyOl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo8YnI+RXhwaXJhdGlvbiBEYXRlOl9fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPGJyPlNpZ25hdHVyZTpfX19fX19fX19fX19fX19fX19f
X19fX19fDQo8YnI+RGF0ZTpfX19fX19fX19fX19fX19fX19fXw0KPHA+Tk9URTogVGhpcyBD
RCBpcyBmb3IgaW5mb3JtYXRpb25hbCwgZWR1Y2F0aW9uYWwsIG9yDQo8YnI+ZW50ZXJ0YWlu
bWVudCBwdXJwb3NlcyBvbmx5LiZuYnNwOyBTb21lIG9mIHRoZSBhY3Rpdml0aWVzDQo8YnI+
ZGVzY3JpYmVkIG9uIHRoaXMgQ0QgbWF5IGJlIGlsbGVnYWwgaWYgY2FycmllZCBvdXQuDQo8
YnI+VGhpcyBDRCBjb250YWlucyBsaW5rcyBhbmQgYWRkcmVzc2VzIG9mIGNvbXBhbmllcw0K
PGJyPmFuZCBpbmRpdmlkdWFscyB3aGljaCBwcm9kdWNlIHZhcmlvdXMgcHJvZHVjdHMsIG9y
DQo8YnI+b2ZmZXIgdmFyaW91cyBzZXJ2aWNlcywgd2hpY2ggbWF5IGJlIGlsbGVnYWwgaW4g
eW91cg0KPGJyPmNvdW50cnksIHN0YXRlLCBvciBjaXR5LiZuYnNwOyBIb3dldmVyLCBpdCBp
cyBwZXJmZWN0bHkNCjxicj5MRUdBTCB0byBwdXJjaGFzZSBhbmQgcG9zc2VzcyB0aGUgQmFu
bmVkIENEIGluIHRoZQ0KPGJyPlVuaXRlZCBTdGF0ZXMgb2YgQW1lcmljYS4mbmJzcDsgQ29u
dGFpbnMgYXBwcm94aW1hdGVseQ0KPGJyPjEwMCBtZWdzIG9mIGluZm9ybWF0aW9uLg0KPHA+
U2hpcHBpbmcgb3V0c2lkZSBVU0EgYWRkICQxMC4wMA0KPHA+KioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCjxicj5Zb3UgYXJl
IHJlY2lldmluZyBhbiB1bnNvbGljaXRlZCBjb21tZXJjaWFsIGVtYWlsIGZyb20NCjxicj5R
dWlrc2lsdmVyIEVudGVycHJpc2VzIEluYy4mbmJzcDsgV2UgcmVjb2duaXplIHRoYXQgeW91
IG1heQ0KPGJyPm5vdCB3aXNoIHRvIHJlY2lldmUgc3VjaCBlbWFpbHMgaW4gdGhlIGZ1dHVy
ZSwgYW5kIHdlDQo8YnI+aGF2ZSBwcm92aWRlZCBhIGxpbmsgdG8gYXV0b21hdGljYWxseSBh
bmQgaW5zdGFudGx5DQo8YnI+cmVtb3ZlIHlvdXJzZWxmOiA8YSBocmVmPSJodHRwOi8vd3d3
LmNvbXB1em9uZXVzYS5jb20vcmVtb3ZlLmh0bSI+UkVNT1ZFPC9hPg0KPGJyPlRoaXMgbWVz
c2FnZSBpcyBiZWluZyBzZW50IHRvIHlvdSBpbiBjb21wbGlhbmNlIHdpdGgNCjxicj5mZWRl
cmFsIGd1aWRlbGluZXMgZ292ZXJuaW5nIHRoZSB0cmFuc21pc3Npb24gb2YNCjxicj51bnNv
bGljaXRlZCBjb21tZXJjaWFsIGVtYWlsLCBpbmNsdWRpbmcgdGhlIHByb3Zpc2lvbiBvZg0K
PGJyPmNvbnRhY3QgaW5mb3JtYXRpb24gZm9yIG91ciBjb21wYW55IHdpdGhpbiB0aGlzIGVt
YWlsLCBhDQo8YnI+dmFsaWQgcmV0dXJuIGVtYWlsIGFkZHJlc3MsIGFuZCBhIHdheSBmb3Ig
Y3VzdG9tZXJzDQo8YnI+dG8gcmVtb3ZlIHRoZW1zZWx2ZXMuJm5ic3A7IFBsZWFzZSBub3Rl
LCBob3dldmVyLCB0aGF0IG91cg0KPGJyPmVtYWlsIGFkZHJlc3Mgd2FzIHZhbGlkIGF0IHRo
ZSB0aW1lIG9mIHNlbmRpbmcsIGJ1dCBtYXkNCjxicj5iZSBjYW5jZWxsZWQgYnkgdGhlIElT
UCBzaG9ydGx5IHRoZXJlYWZ0ZXIgZHVlIHRvIG91cg0KPGJyPnVzZSBvZiB1bnNvbGljaXRl
ZCBlbWFpbC4mbmJzcDsgWW91IGNhbiByZWFkIGFib3V0IHRoZSB2YXJpb3VzDQo8YnI+bGF3
cyBnb3Zlcm5pbmcgdW5zb2xpY2l0ZWQgZW1haWw6IGh0dHA6Ly9zcGFtbGF3cy5jb20NCjxi
cj4iVW5zb2xpY2l0ZWQgY29tbWVyY2lhbCBlbGVjdHJvbmljIG1haWwgY2FuIGJlIGFuIGlt
cG9ydGFudA0KPGJyPm1lY2hhbmlzbSB0aHJvdWdoIHdoaWNoIGJ1c2luZXNzZXMgYWR2ZXJ0
aXNlIGFuZCBhdHRyYWN0DQo8YnI+Y3VzdG9tZXJzIGluIHRoZSBvbmxpbmUgZW52aXJvbm1l
bnQuIiZuYnNwOyAtLSBVLlMuIENvbmdyZXNzLA0KPGJyPkguUi4gMTA2dGggQ09OR1JFU1Mg
MmQgU2Vzc2lvbiBILiBSLiAzMTEzIFNlYy4gMiAoYSkzIEp1bHkNCjxicj4xOSwgMjAwMCBo
dHRwOi8vd3d3LnNwYW1sYXdzLmNvbS9mZWRlcmFsL2hyMzExMy5odG1sDQo8YnI+KioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioN
Cjxicj4mbmJzcDsNCjxicj4mbmJzcDsNCjwvYm9keT4NCjwvaHRtbD4NCg==

------=_NextPart_000_001__10618077_51917.11--



From list@netscape.com  Tue Jan 30 02:24:06 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA01715
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 02:24:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0U7MHG09328;
	Mon, 29 Jan 2001 23:22:17 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0U7MJw03601;
	Mon, 29 Jan 2001 23:22:19 -0800 (PST)
Resent-Date: Mon, 29 Jan 2001 23:22:19 -0800 (PST)
Date: Mon, 29 Jan 2001 23:22:10 -0800 (PST)
Message-Id: <200101300722.f0U7M9501181@ywing.netscape.com>
From: luckydollars4u@yahoo.com
To: ietf-ldapext@netscape.com
Subject:  Can you place ads on the net or want to learn how and get paid for it!! Company pays good $$$
X-Reply-To:  digital2@optusnet.com.au 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"3yMNU.A.13.pumd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Hello! 
We are currently seeking individuals to place small classified ads for our clients. You get 
paid per response.($1.00 per response can make you thousands.!) NO Selling !!  PLUS 
you get 10% of sales made but without you having to depend on sales! We can teach 
you how to place ads if your not sure so you dont miss out on this geniune MONEY 
MAKING business opportunity  As we dont like people wasting their time searching for 
the cost to join ( hidden in some programs) we let you know now not later ! The cost to 
join is a one only payment of $49.95 US with a 14 day money back guarantee that is, if 
you change your mind or  you dont make any money with this great program you will get 
your money back No questions asked ! So  go for it and see just how good this program 
is for making you money. You cant lose!!!
 Please request more information by sending an email with " KEINFO"  in the subject line 
please to:
digital2@optusnet.com.au 
*====================*
Anti spamming policy..
Please as we only use email address lists purchases from online sellers, if your email 
address is on these lists without your approval, we will remove it  immediately . Just  
write "Please Remove" in the subject line of an email sent to our address as shown 
below. Thank you, and we apologise for any inconvience this may have caused. We 
shall also take action against the list sellers concerned.!
 digital@@optusnet.com.au 
*******************************************
Another free easy way to get more hits to your site!!
http://www.hitharvester.com/referral.asp?ref=gazzas 
Contact us for a free adsubmit program.




From list@netscape.com  Tue Jan 30 13:37:12 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15119
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 13:37:11 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UIYYG17252;
	Tue, 30 Jan 2001 10:34:34 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UIYYs14461;
	Tue, 30 Jan 2001 10:34:34 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 10:34:34 -0800 (PST)
Message-Id: <sa76a6bf.025@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 30 Jan 2001 11:34:20 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapext@netscape.com>, <John.Liang@openwave.com>
Subject: RE: Fix for VLV draft.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0UIYRv14320
Resent-Message-ID: <"CxOAZC.A.cgD.1kwd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>>> "John Liang" <John.Liang@openwave.com> 1/29/01 10:35:29 AM >>>
>I want to ask a few questions about this topic:
>
>1> if the control is not critical, and there is an error in server side
>sorting control
>or virutal list view control, the server is supposed to send back all
>unsorted result.

No, during processing, if there is an error (due to the control being processed or otherwise), processing stops, and the searchResultDone is returned with (some) error code.

>if the server returns all unsorted entries successfully,
>is LDAP searchResultDone message supposed to return LDAP_SUCCESS or
>other(80)?
>Must we include sssResponse and vlvResponse with corresponding error code?

If the server returns all unsorted entries successfully, it is because the server does not support the vlv and sss controls, and they are not marked critical. Thus they are ignored and the search is processed as if it never had the controls. There is no sss or vlv response code in this case because the server doesn't recognise them.

>2> if the control is critical, besides return
>LDAP_UNAVAILABLE_CRITICAL_EXTENSION,
>Must we return the corrseponding sssResponse and vlvResponse result code?

Yes.




From list@netscape.com  Tue Jan 30 13:48:35 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15299
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 13:48:34 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UIjVG19485;
	Tue, 30 Jan 2001 10:45:32 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UIjUc20453;
	Tue, 30 Jan 2001 10:45:30 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 10:45:30 -0800 (PST)
Message-Id: <sa76a94c.095@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 30 Jan 2001 11:45:16 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <Kurt@openldap.org>
Cc: <ietf-ldapext@netscape.com>
Subject: Re: Fix for VLV draft.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0UIjSv20394
Resent-Message-ID: <"iMUXiC.A.6-E.Ivwd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

From my read of draft-armijo-ldap-control-error-00.txt, the proposal is to ammend RFC 2251 in a way that cannot be done. I may be misreading it. 

Maybe it intends to say that this result code MUST only be used when the operation is accompanied by a control that specifies its use. If this is the case, I think it should be re-worded, and progressed so that other I-Ds needing to consume it can be progressed.

Otherwise, I don't mind introducing a new error code in the VLV draft itself that is only used in the presence of the VLV control. 

Jim

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/29/01 10:49:32 AM >>>
I think it's a bad idea to overload the semantics of the 'other'
(or any other existing) result code.  'other' should only imply
some implementation specific error.   IIRC, Michael previously
suggested introduction a new result code indicating that an error
occurred during control processing.  I believe we should pursue
this approach.

Kurt

At 10:16 AM 1/29/01 -0700, Jim Sermersheim wrote:
>Back in September, as the Virtual List View draft was going through standardization process, Michael Armijo noted the following problem:
> 
>>In section 3.2 we have details about what the virtualListViewResult
>>codes mean, but we still do not define what result code should be
>>returned in the actual SearchResult in the case where there is a value
>>other then success(0) in the virtualListViewResult.
>>
>>We should return something other then success(0)in the SearchResultDone
>>if there is a result code other then success(0) in the
>>virtualListViewResult and what that result code is should be defined (or
>>referenced) in the VLV draft.
> 
>I propose that we fix this by inserting the following statement as paragraph 4 of Section 3.2
>If the LDAP SearchResultDone message has a resultCode of other (80), 
>the virtualListViewResponse MAY be included and MAY hold a non-zero 
>value in the virtualListViewResult field.
>If there are no objections, I'd like to add this and allow the draft to progress.
> 
>Jim




From list@netscape.com  Tue Jan 30 15:01:26 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16711
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 15:01:26 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UJxab10053;
	Tue, 30 Jan 2001 11:59:36 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UJxZQ02005;
	Tue, 30 Jan 2001 11:59:35 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 11:59:35 -0800 (PST)
Reply-To: <John.Liang@openwave.com>
From: "John Liang" <John.Liang@openwave.com>
To: "Jim Sermersheim" <jimse@novell.com>, <ietf-ldapext@netscape.com>
Subject: RE: Fix for VLV draft.
Date: Tue, 30 Jan 2001 14:58:09 -0500
Message-ID: <001c01c08af6$f84e8fe0$ba05400a@software.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <sa76a6bf.026@prv-mail20.provo.novell.com>
Resent-Message-ID: <"4UG4z.A.Yd.h0xd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: Jim Sermersheim [mailto:jimse@novell.com]
> Sent: Tuesday, January 30, 2001 1:34 PM
> To: ietf-ldapext@netscape.com; John.Liang@openwave.com
> Subject: RE: Fix for VLV draft.
> 
> 
> >>> "John Liang" <John.Liang@openwave.com> 1/29/01 10:35:29 AM >>>
> >I want to ask a few questions about this topic:
> >
> >1> if the control is not critical, and there is an error in server side
> >sorting control
> >or virutal list view control, the server is supposed to send back all
> >unsorted result.
> 
> No, during processing, if there is an error (due to the control 
> being processed or otherwise), processing stops, and the 
> searchResultDone is returned with (some) error code.
> 
> >if the server returns all unsorted entries successfully,
> >is LDAP searchResultDone message supposed to return LDAP_SUCCESS or
> >other(80)?
> >Must we include sssResponse and vlvResponse with corresponding 
> error code?
> 
> If the server returns all unsorted entries successfully, it is 
> because the server does not support the vlv and sss controls, and 
> they are not marked critical. Thus they are ignored and the 
> search is processed as if it never had the controls. There is no 
> sss or vlv response code in this case because the server doesn't 
> recognise them.
 
Jim,

It sounds different from RFC2891(LDAP Control Extension for Server
Side Sorting of Search Results), chapter 2, item 4:

4 - If the server supports this sorting control but for some reason
       cannot sort the search results using the specified sort keys and
       the client specified FALSE for the control's criticality field,
       then the server should return all search results unsorted and
       include the sortKeyResponseControl in the searchResultDone
       message.

It shows that if the server supportes this control, the unsorted result
could be sent back under certain conditions.

Any comments?

Thanks,
--
John Liang




From list@netscape.com  Tue Jan 30 16:49:54 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18058
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 16:49:53 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0ULlXb02908;
	Tue, 30 Jan 2001 13:47:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0ULlXg22556;
	Tue, 30 Jan 2001 13:47:33 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 13:47:33 -0800 (PST)
Message-Id: <sa76d3fd.043@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 30 Jan 2001 14:47:20 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapext@netscape.com>, <John.Liang@openwave.com>
Subject: RE: Fix for VLV draft.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0ULlVv22523
Resent-Message-ID: <"4eQBeC.A.BgF.zZzd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>>> "John Liang" <John.Liang@openwave.com> 1/30/01 12:58:09 PM >>>
>> >>> "John Liang" <John.Liang@openwave.com> 1/29/01 10:35:29 AM >>>
>> >I want to ask a few questions about this topic:
>> >
>> >1> if the control is not critical, and there is an error in server side
>> >sorting control
>> >or virutal list view control, the server is supposed to send back all
>> >unsorted result.
>> 
>> No, during processing, if there is an error (due to the control 
>> being processed or otherwise), processing stops, and the 
>> searchResultDone is returned with (some) error code.
>> 
>> >if the server returns all unsorted entries successfully,
>> >is LDAP searchResultDone message supposed to return LDAP_SUCCESS or
>> >other(80)?
>> >Must we include sssResponse and vlvResponse with corresponding 
>> error code?
>> 
>> If the server returns all unsorted entries successfully, it is 
>> because the server does not support the vlv and sss controls, and 
>> they are not marked critical. Thus they are ignored and the 
>> search is processed as if it never had the controls. There is no 
>> sss or vlv response code in this case because the server doesn't 
>> recognise them.
> 
>Jim,
>
>It sounds different from RFC2891(LDAP Control Extension for Server
>Side Sorting of Search Results), chapter 2, item 4:
>
>4 - If the server supports this sorting control but for some reason
>       cannot sort the search results using the specified sort keys and
>       the client specified FALSE for the control's criticality field,
>       then the server should return all search results unsorted and
>       include the sortKeyResponseControl in the searchResultDone
>       message.
>
>It shows that if the server supportes this control, the unsorted result
>could be sent back under certain conditions.
>
>Any comments?

Yes, I don't think we should have done that. I think we should have stated that an error is returned, and the client can re-try with a modified control.

Jim



From list@netscape.com  Tue Jan 30 17:24:43 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18414
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 17:24:42 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UMN2G29847;
	Tue, 30 Jan 2001 14:23:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UMLus06805;
	Tue, 30 Jan 2001 14:21:56 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 14:21:56 -0800 (PST)
Message-Id: <sa76dbc0.007@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 30 Jan 2001 15:20:30 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapext@netscape.com>
Subject: Persistent Search questions
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0UMKkv06175
Resent-Message-ID: <"ooikXB.A.rkB.55zd6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

The persistent search control (draft-ietf-ldapext-psearch-03.txt) states in section 3 that the search operation is modified in such a way that the searcResultDone message is never sent. This implies that the size and time limits are ignored, but it's not explicitly stated. Can anyone confirm if this is the case?

Also, there is a little blurb in the security considerations section about making sure access controls are checked for entries being returned. This is more of a question to other implementors, a server could:
a) check access control information once at the beginning of the search, and use that information without refreshing it later (could speed response time, and "fix" authorization to a specific view, or it could
b) recalculate access control information everytime an entry is to be returned (provides consistency over long persistent search sessions).

My feeling is that b is better, does anyone expect a?

Jim



From list@netscape.com  Tue Jan 30 18:19:30 2001
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19061
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 18:19:30 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UNH8b21528;
	Tue, 30 Jan 2001 15:17:08 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UNH9g04553;
	Tue, 30 Jan 2001 15:17:09 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 15:17:09 -0800 (PST)
Message-Id: <5.0.2.1.0.20010130150223.00a7d460@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 30 Jan 2001 15:16:16 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: RE: Fix for VLV draft.
Cc: <ietf-ldapext@netscape.com>, <John.Liang@openwave.com>
In-Reply-To: <sa76d3fd.043@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"6jwg_.A.3GB.0t0d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 02:47 PM 1/30/01 -0700, Jim Sermersheim wrote:
>>Any comments?
>
>Yes, I don't think we should have done that. I think we should have stated that an error is returned, and the client can re-try with a modified control.

I concur and hope this will be resolved by a revision of the specification.
I also note that it may be appropriate for LDAPbis WG to consider adding a
statement to the TS to discourage further overloading of the criticality
field.  It should at least be covered in draft-greenblatt-ldapext-style-00.txt.

And, BTW, "The criticality is FALSE (MAY be absent)" [VLV, 5.2] should actually be
"The criticality SHALL be FALSE and, hence, absent."  Per RFC2251, DEFAULT
values are not present in the BER encoding of LDAP itself.

Kurt



From list@netscape.com  Tue Jan 30 18:29:09 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19167
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 18:29:09 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UNRBG12477;
	Tue, 30 Jan 2001 15:27:11 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UNRBE08411;
	Tue, 30 Jan 2001 15:27:11 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 15:27:11 -0800 (PST)
Message-Id: <5.0.2.1.0.20010130151824.00a86c10@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 30 Jan 2001 15:26:08 -0800
To: "Jim Sermersheim" <jimse@novell.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Persistent Search questions
Cc: <ietf-ldapext@netscape.com>
In-Reply-To: <sa76dbc0.007@prv-mail20.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"MNTSF.A.0CC.L30d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

At 03:20 PM 1/30/01 -0700, Jim Sermersheim wrote:
>The persistent search control (draft-ietf-ldapext-psearch-03.txt) states in section 3 that the search operation is modified in such a way that the searcResultDone message is never sent.

I would rather the spec state the operation never returns success,
but may return non-success result codes.  This would, amongst other
things, allow the operation to be canceled (the cancel operation
cannot cancel an operation which has no response).

>This implies that the size and time limits are ignored, but it's not explicitly stated. Can anyone confirm if this is the case?

I would rather size/time limits not be ignored in face of this control.


>Also, there is a little blurb in the security considerations section about making sure access controls are checked for entries being returned. This is more of a question to other implementors, a server could:
>a) check access control information once at the beginning of the search, and use that information without refreshing it later (could speed response time, and "fix" authorization to a specific view, or it could
>b) recalculate access control information everytime an entry is to be returned (provides consistency over long persistent search sessions).
>
>My feeling is that b is better, does anyone expect a?

I'd prefer not to mandate either a nor b as what is best
is likely application/implementation specific.  I would
note that in our implementation, b) would likely be much
easier to implement but I'd hate to wish b) on everyone.
Likewise for a).



From list@netscape.com  Tue Jan 30 18:59:59 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19417
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 18:59:58 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0UNvVG17663;
	Tue, 30 Jan 2001 15:57:31 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0UNvWE21834;
	Tue, 30 Jan 2001 15:57:32 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 15:57:32 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4633.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Fix for VLV draft.
Date: Tue, 30 Jan 2001 15:13:05 -0800
Message-ID: <96BABA22ECEAEA45B53D08D63E1B56785280F2@DF-SPIKE.platinum.corp.microsoft.com>
Thread-Topic: Fix for VLV draft.
Thread-Index: AcCK7c316kQQ+n6AQuWid8Lys4G1dwAIy3FQ
From: "Michael Armijo" <micharm@Exchange.Microsoft.com>
To: "Jim Sermersheim" <jimse@novell.com>, <Kurt@openldap.org>
Cc: <ietf-ldapext@netscape.com>
X-OriginalArrivalTime: 30 Jan 2001 23:13:07.0128 (UTC) FILETIME=[34680B80:01C08B12]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0UNvVv21810
Resent-Message-ID: <"wMeigB.A.4UF.rT1d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

Jim Sermersheim said - "Maybe it intends to say that this result code
MUST only be used when the operation is accompanied by a control that
specifies its use"

I believe that may be the best way to go.  I will review the current
version and update the list with an updated draft.

Michael

> -----Original Message-----
> From: Jim Sermersheim [mailto:jimse@novell.com]
> Sent: Tuesday, January 30, 2001 10:45 AM
> To: Kurt@OpenLDAP.org
> Cc: ietf-ldapext@netscape.com
> Subject: Re: Fix for VLV draft.
> 
> 
> From my read of draft-armijo-ldap-control-error-00.txt, the 
> proposal is to ammend RFC 2251 in a way that cannot be done. 
> I may be misreading it. 
> 
> Maybe it intends to say that this result code MUST only be 
> used when the operation is accompanied by a control that 
> specifies its use. If this is the case, I think it should be 
> re-worded, and progressed so that other I-Ds needing to 
> consume it can be progressed.
> 
> Otherwise, I don't mind introducing a new error code in the 
> VLV draft itself that is only used in the presence of the VLV 
> control. 
> 
> Jim
> 
> >>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/29/01 10:49:32 AM >>>
> I think it's a bad idea to overload the semantics of the 'other'
> (or any other existing) result code.  'other' should only imply
> some implementation specific error.   IIRC, Michael previously
> suggested introduction a new result code indicating that an error
> occurred during control processing.  I believe we should pursue
> this approach.
> 
> Kurt
> 
> At 10:16 AM 1/29/01 -0700, Jim Sermersheim wrote:
> >Back in September, as the Virtual List View draft was going 
> through standardization process, Michael Armijo noted the 
> following problem:
> > 
> >>In section 3.2 we have details about what the virtualListViewResult
> >>codes mean, but we still do not define what result code should be
> >>returned in the actual SearchResult in the case where there 
> is a value
> >>other then success(0) in the virtualListViewResult.
> >>
> >>We should return something other then success(0)in the 
> SearchResultDone
> >>if there is a result code other then success(0) in the
> >>virtualListViewResult and what that result code is should 
> be defined (or
> >>referenced) in the VLV draft.
> > 
> >I propose that we fix this by inserting the following 
> statement as paragraph 4 of Section 3.2
> >If the LDAP SearchResultDone message has a resultCode of other (80), 
> >the virtualListViewResponse MAY be included and MAY hold a non-zero 
> >value in the virtualListViewResult field.
> >If there are no objections, I'd like to add this and allow 
> the draft to progress.
> > 
> >Jim
> 
> 



From list@netscape.com  Tue Jan 30 19:07:14 2001
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA19459
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 19:07:14 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V05bG19277;
	Tue, 30 Jan 2001 16:05:37 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V05cQ25930;
	Tue, 30 Jan 2001 16:05:38 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 16:05:38 -0800 (PST)
Date: Tue, 23 Jan 2001 23:30:42 -0500 (EST)
From: rpznn@msn.com
Message-Id: <200101240430.XAA02437@InterJet.liquidblue.com>
To: bilno@Friendsonline.netscape.com
Reply-To: ron09me2@n2mail.com
Subject: PARTNERS WANTED!!                                    [fdqbx]
Resent-Message-ID: <"9fvBSC.A.4UG.Rb1d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Partners Wanted:
                            
Open a Secure Offshore Account

With a minimum payment of $100.00
WITHOUT a social security number
WITHOUT a credit check 

Work from the Privacy of your own Home
Develop a secondary offshore income of
$500 to $5,000 a day or more -- you decide! 

Unlimited global market, unlimited income, 
all confidential

You can: Eliminate your debts.
Secure your assets.
Retain ALL your hard earned money 

Pass your wealth on to your heirs
The Super Rich have done this for years.....
Isn't it time YOU started?

This offshore income plan clearly speaks for itself.
Great incentive for new partners. 

For free Info, reply with "Send Offshore Info Please"
in the subject.

mailto:ron09me@n2mail.com?subject=Send_Offshore_Info_Please

Please include your Name, E-mail address and phone number. 
Phone # (Optional)

Please Note... Should my email address be shut down 
by the Flamers actions. Please "Fax" your response 
instead with your name__,email address___, and the 
Subject header "Offshore Info" to: 305-425-3205. 

Have a Great Day!



From list@netscape.com  Tue Jan 30 20:47:34 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20151
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 20:47:33 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V1iLb28583;
	Tue, 30 Jan 2001 17:44:23 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V1iMw08159;
	Tue, 30 Jan 2001 17:44:22 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 17:44:22 -0800 (PST)
Importance: Normal
To: <ietf-ldapext@netscape.com>
Subject: Re: Persistent Search questions
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
From: "Timothy Hahn" <hahnt@us.ibm.com>
Message-ID: <OF15946A13.9127B872-ON852569E5.000658B6@pok.ibm.com>
Date: Tue, 30 Jan 2001 20:44:02 -0500
X-MIMETrack: Serialize by Router on D01MLC96/01/M/IBM(Release 5.0.6a |January 22, 2001) at
 01/30/2001 08:44:03 PM,
	Serialize complete at 01/30/2001 08:44:03 PM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 000695ED852569E5_="
Resent-Message-ID: <"TAyMkB.A.N_B.132d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a multipart message in MIME format.
--=_alternative 000695ED852569E5_=
Content-Type: text/plain; charset="us-ascii"

Jim,

I would expect behavior as described in b) below.

I cannot confirm that sizeLimit and timeLimit are ignored - but it seems 
reasonable.  It also seems reasonable that there may be some other 
administrative configuration that implementations support to help reduce 
the thread of DOS attacks when employing this control.  (I can envison 
500,000 clients all setting up a persistent search to a single server 
....)

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681

To:     <ietf-ldapext@netscape.com>
cc: 
Subject:        Persistent Search questions



The persistent search control (draft-ietf-ldapext-psearch-03.txt) states 
in section 3 that the search operation is modified in such a way that the 
searcResultDone message is never sent. This implies that the size and time 
limits are ignored, but it's not explicitly stated. Can anyone confirm if 
this is the case?

Also, there is a little blurb in the security considerations section about 
making sure access controls are checked for entries being returned. This 
is more of a question to other implementors, a server could:
a) check access control information once at the beginning of the search, 
and use that information without refreshing it later (could speed response 
time, and "fix" authorization to a specific view, or it could
b) recalculate access control information everytime an entry is to be 
returned (provides consistency over long persistent search sessions).

My feeling is that b is better, does anyone expect a?

Jim



--=_alternative 000695ED852569E5_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Jim,</font>
<br>
<br><font size=2 face="sans-serif">I would expect behavior as described in b) below.</font>
<br>
<br><font size=2 face="sans-serif">I cannot confirm that sizeLimit and timeLimit are ignored - but it seems reasonable. &nbsp;It also seems reasonable that there may be some other administrative configuration that implementations support to help reduce the thread of DOS attacks when employing this control. &nbsp;(I can envison 500,000 clients all setting up a persistent search to a single server ....)<br>
</font>
<br><font size=2 face="sans-serif">Regards,<br>
Tim Hahn<br>
<br>
Internet: hahnt@us.ibm.com<br>
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)<br>
phone: 607.752.6388 &nbsp; &nbsp; tie-line: 8/852.6388<br>
fax: 607.752.3681<br>
</font>
<p><font size=1 color=#800080 face="sans-serif">To: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">&lt;ietf-ldapext@netscape.com&gt;</font>
<br><font size=1 color=#800080 face="sans-serif">cc: &nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 color=#800080 face="sans-serif">Subject: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=1 face="sans-serif">Persistent Search questions</font>
<br>
<br>
<br>
<br><font size=2><tt>The persistent search control (draft-ietf-ldapext-psearch-03.txt) states in section 3 that the search operation is modified in such a way that the searcResultDone message is never sent. This implies that the size and time limits are ignored, but it's not explicitly stated. Can anyone confirm if this is the case?<br>
</tt></font>
<br><font size=2><tt>Also, there is a little blurb in the security considerations section about making sure access controls are checked for entries being returned. This is more of a question to other implementors, a server could:<br>
a) check access control information once at the beginning of the search, and use that information without refreshing it later (could speed response time, and &quot;fix&quot; authorization to a specific view, or it could<br>
b) recalculate access control information everytime an entry is to be returned (provides consistency over long persistent search sessions).<br>
</tt></font>
<br><font size=2><tt>My feeling is that b is better, does anyone expect a?<br>
</tt></font>
<br><font size=2><tt>Jim</tt></font>
<br>
<br>
<br>
--=_alternative 000695ED852569E5_=--



From list@netscape.com  Tue Jan 30 21:00:20 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20243
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 21:00:20 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V1wCb05263;
	Tue, 30 Jan 2001 17:58:12 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V1wDU13093;
	Tue, 30 Jan 2001 17:58:13 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 17:58:13 -0800 (PST)
Message-Id: <5.0.2.1.0.20010130175132.00a48410@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 30 Jan 2001 17:57:18 -0800
To: <ietf-ldapext@netscape.com>
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: Re: Persistent Search questions
In-Reply-To: <OF15946A13.9127B872-ON852569E5.000658B6@pok.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"Z3STSC.A.TMD.1E3d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

In regards to DoS attacks, seems you could really drive a
server crazy by asking it to sort a persistent search.

Kurt



From list@netscape.com  Tue Jan 30 21:08:26 2001
Received: from netscape.com (c3po.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20309
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 21:08:25 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V26IG16083;
	Tue, 30 Jan 2001 18:06:18 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V26JY16242;
	Tue, 30 Jan 2001 18:06:19 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 18:06:19 -0800 (PST)
Date: Tue, 30 Jan 2001 18:06:06 -0800 (PST)
Message-Id: <200101310206.f0V266Z03038@xwing.netscape.com>
From: rlssz@hotmail.com
To: slbbc@MainOnlinefriend.netscape.com
Reply-To: t2m34@bigfoot.com
Subject: I'll Do All Of The Work!                                    [jaqtv]
Resent-Message-ID: <"bV5bSC.A.g9D.aM3d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

WOULD YOU LIKE TO MAKE $4380.00 OVER AND OVER AGAIN?
WITHOUT RECRUITING OR SPONSORING ANYONE!

This is not MLM. I will Completely Manage Your Account
Provide Your Lead List, Do Your Telemarketing
Place People For You ALL YOU DO IS GO TO THE MAIL BOX 
AND COLLECT YOUR CHECK.

The cost of this complete service is a one time out 
of pocket expense of only $49.95 - 100% GUARANTEE!
(If you have not made any money with us in 30days)

If interested reply with "Send Managed Acct. Info" 
in subject line.

mailto:t2m32@bigfoot.com?subject=Send_Managed_Acct_Info

Please Note... Should this email address be down.
Please "Fax" your response instead, with your name__,
email address___, and the words "Send Managed Acct Info" 
to: 305-425-3205.

Have a Great Day!
Dr. Jim
"A Wise Person Investigates What a Fool Person Takes 
For Granted"

PS: To be removed from the list, just put "Remove"
in subject line and send. 



From list@netscape.com  Tue Jan 30 21:09:10 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20323
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 21:09:10 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V272b07327;
	Tue, 30 Jan 2001 18:07:02 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V273U17000;
	Tue, 30 Jan 2001 18:07:03 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 18:07:03 -0800 (PST)
Message-Id: <5.0.2.1.0.20010130180034.00a81810@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 30 Jan 2001 18:06:36 -0800
To: ietf-ldapext@netscape.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: psearch, search references, aliases
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"Xv_8KD.A.PJE.GN3d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

What is the behavior of the psearch operation when, in the absence
of ManageDsaIt, there are subordinate references (in scope)
are added, deleted, or modified?

What is the behavior of the psearch operation when there are
aliases within scope and dereferencing during searching is
enabled?

Kurt



From list@netscape.com  Tue Jan 30 22:52:40 2001
Received: from netscape.com (c3po.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA22968
	for <ldapext-archive@odin.ietf.org>; Tue, 30 Jan 2001 22:52:40 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V3orG27929;
	Tue, 30 Jan 2001 19:50:54 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V3otg19646;
	Tue, 30 Jan 2001 19:50:55 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 19:50:55 -0800 (PST)
Message-Id: <sa772919.068@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Tue, 30 Jan 2001 20:50:33 -0700
From: "Jim Sermersheim" <jimse@novell.com>
To: <ietf-ldapext@netscape.com>, <Kurt@openldap.org>
Subject: Re: Persistent Search questions
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f0V3orv19622
Resent-Message-ID: <"p8MmB.A.syE.du4d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

cute, Kurt.

seriously though, the psearch draft should probably have an "interaction with other controls" just to make sure ppl think about this kind of thing.

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/30/01 6:57:18 PM >>>
In regards to DoS attacks, seems you could really drive a
server crazy by asking it to sort a persistent search.

Kurt




From list@netscape.com  Wed Jan 31 00:08:06 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23758
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 00:08:06 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V55Xb27427;
	Tue, 30 Jan 2001 21:05:33 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V55ZQ07412;
	Tue, 30 Jan 2001 21:05:35 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 21:05:35 -0800 (PST)
Message-ID: <01C08B00.70137C80.andyhe@msn.com>
From: andy herron <andyhe@msn.com>
To: "'Jim Sermersheim'" <jimse@novell.com>,
        "ietf-ldapext@netscape.com"
	 <ietf-ldapext@netscape.com>,
        "John.Liang@openwave.com"
	 <John.Liang@openwave.com>
Cc: "'aherron@u.washington.edu'" <aherron@u.washington.edu>
Subject: RE: Fix for VLV draft.
Date: Tue, 30 Jan 2001 21:05:55 -0800
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"v9t_8.A.izB.e05d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

>>It sounds different from RFC2891(LDAP Control Extension for Server
>>Side Sorting of Search Results), chapter 2, item 4:
>>
>>4 - If the server supports this sorting control but for some reason
>>       cannot sort the search results using the specified sort keys and
>>       the client specified FALSE for the control's criticality field,
>>       then the server should return all search results unsorted and
>>       include the sortKeyResponseControl in the searchResultDone
>>       message.
>>
>>It shows that if the server supportes this control, the unsorted result
>>could be sent back under certain conditions.
>>
>>Any comments?
>
>Yes, I don't think we should have done that. I think we should have stated 
that an error
>is returned, and the client can re-try with a modified control.
>

Jim & John,

The original thinking in the sorting draft was that the client could ask 
for it to be sorted but not require it.  The criticality field seemed at 
the time perfectly suited for this use.  It could be that the client is 
capable of doing the sort but also "is hopeful" that the server already has 
the data indexed by the sort key so can simply run down the index when 
calculating/formatting the result set.

There are some implementations where sorting is performed/allowed only on 
fields where there exists an index (meaning that the server is 
unwilling/unable to sort the result set itself).  In these implementations, 
failing the entire search when the client was willing to have the result 
set unsorted seemed very reasonable.

What do you gain by having the client resend the search query with a 
modified sort control?  If the client wants this behavior, then the client 
should specify criticality as true.

That was the logic when we wrote the draft oh so long ago.

-Andy Herron
formerly Microsoft Corp, currently residing at University of Washington



From list@netscape.com  Wed Jan 31 00:35:31 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23925
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 00:35:30 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V5XGb00829;
	Tue, 30 Jan 2001 21:33:16 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V5XHo13274;
	Tue, 30 Jan 2001 21:33:18 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 21:33:18 -0800 (PST)
Message-Id: <200101310449.FAA23218@SNI.sportline.de>
From: "Wayne Green" <boggler@goplay.com>
Subject: Your Dream House #19C4
To: now03d@SNI.sportline.de
X-Mailer: Microsoft Outlook Express 4.72.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE VÐßD.1712.3
Mime-Version: 1.0
Date: Tue, 30 Jan 2001 23:24:25 -0500
Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
Resent-Message-ID: <"a8-wa.A.IPD.cO6d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME Message

------=_NextPart_000_007F_01BDF6C7.FABAC1B0
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0"

------=_NextPart_001_0080_01BDF6C7.FABAC1B0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

***** This is an HTML Message ! *****


------=_NextPart_001_0080_01BDF6C7.FABAC1B0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<title></title>
</head>

<body bgcolor=3D"#FFFFFF" text=3D"#FFFFFF">

<p align=3D"center"><b><font size=3D"5" color=3D"#FF0000">We will help you=
 get the mortgage
loan you want!&nbsp;<br>
</font><font color=3D"#000000"><br>
Whether a new home loan is what you seek or<br>to refinance your current h=
ome loan at a lower interest rate and payment, we can help!<br>
<br>
<font size=3D"4">
Mortgage rates haven't been this low in the last 12 months, take action no=
w!<br>
</font>
Refinance your home with us and include all of those pesky credit card bil=
ls or<br>use the extra cash for that pool you've always wanted=2E=2E=2E&nbs=
p;<br>
<br>
</font><font size=3D"4" color=3D"#0000FF">
Where others says NO, we say YES!!!<br>
</font><font color=3D"#000000">
Even if you have been turned down elsewhere, we can help!&nbsp;<br>
<br>
</font><font color=3D"#0000FF">
Easy terms!</font><font color=3D"#000000">
 Our mortgage referral service combines the<u><br>highest quality loans wi=
th most economical rates and the easiest
qualification</u>!<br>
<br>
</font><font size=3D"4" color=3D"#FF0000">
Take just 2 minutes to complete the following form=2E<br></font> </b><font=
 size=3D"2" color=3D"#000000"><i>There is no obligation, all information is=
 kept strictly confidential, and you must be at least 18 years of age=2E<br=
>
Service available within the United States only=2E This service is fast an=
d free=2E</i></font></p>
<p align=3D"center"><b><font color=3D"#FF0000" size=3D"4">Free information=
 request
form:</font></b></p>
<form name=3D"form"
  method=3D"post"
  action=3D"mailto:rddm3@verizonmail=2Ecom?SUBJECT=3DMortgage Lead"
  enctype=3D"text/plain"
  onSubmit=3D"return validate_form()">
  <table>
 
 <tr>
  <div align=3D"center">
    <center>
    <table border=3D"0" cellPadding=3D"0" cellSpacing=3D"5" width=3D"90%">=

      <tbody>
        <tr>
          <td>
            <div align=3D"left">
              <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0" widt=
h=3D"108%">
                <tr>
                  <td width=3D"3%"></td>
                  <td width=3D"21%"><b><font color=3D"#FF0000">Please Choo=
se One</font></b></td>
                  <td width=3D"3%"></td>
                  <td width=3D"81%"></td>
                </tr>
                <tr>
                  <td width=3D"3%"><font color=3D"#000000"><b><input name=3D=
"service" type=3D"radio" value=3D"mortgage"></b></font></td>
                  <td width=3D"21%"><font color=3D"#000000"><b>&nbsp; New =
Mortgage</b> </font></td>
                  <td width=3D"3%"><font color=3D"#000000"><b><input name=3D=
"service" type=3D"radio" value=3D"refinancing"></b></font></td>
                  <td width=3D"81%"><font color=3D"#000000"><b>&nbsp; Mort=
gage
                    Refinancing</b></font></td>
                </tr>
              </table>
            </div>
            <div align=3D"left">
              <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0" widt=
h=3D"100%">
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Name:</b></=
font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"50" name=3D"required-name" size=3D"20"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Email Addre=
ss:</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"100" name=3D"email" size=3D"20"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Home Addres=
s:</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"100" name=3D"required-home address" size=3D"30"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>City:</b></=
font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"100" name=3D"required-city" size=3D"30"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>State:</b><=
/font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"20" name=3D"required-state" size=3D"15"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Zip Code:</=
b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"10" name=3D"required-zip" size=3D"10"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Phone Numbe=
r:</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"12" name=3D"required-phone" size=3D"12"></b></font></td>
                </tr>
              </table>
            </div>
            <hr>
            <hr>
            <font color=3D"#000000" size=3D"4"><b>Employment Information:<=
br>
            </b>
            </font>
            <div align=3D"left">
              <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0" widt=
h=3D"100%">
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Employer:</=
b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"50" name=3D"employer" size=3D"20"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Job Title:<=
/b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"50" name=3D"job title" size=3D"20"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Work Addres=
s:</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"100" name=3D"work address" size=3D"30"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>City:</b></=
font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"100" name=3D"wcity" size=3D"30"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>State:</b><=
/font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"20" name=3D"wstate" size=3D"15"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Zip Code:</=
b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"10" name=3D"wzip" size=3D"10"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Work Phone =
Number:</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"12" name=3D"wrk#" size=3D"12"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>Annual Hous=
ehold Income:</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"12" name=3D"income" size=3D"12"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>How long wi=
th this
                    company?</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"12" name=3D"how long" size=3D"12"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%"><font color=3D"#000000"><b>How much do=
 you plan on
                    paying as a down payment?</b></font></td>
                  <td width=3D"50%"><font color=3D"#000000"><b><input maxL=
ength=3D"12" name=3D"down payment" size=3D"12"></b></font></td>
                </tr>
                <tr>
                  <td width=3D"50%" valign=3D"top"><font color=3D"#000000"=
><b>Any
                    additional information:<br>(Tell us how we can help!)<=
/b></font>
                    <p>&nbsp;</p>
                    <p>&nbsp;</p>
                    <p>&nbsp;</p>
                    <p><font color=3D"#000000"><b>Rate your Credit from 1-=
10<br>
                    10 Being excellent</b></font></p>
                  </td>
                  <td width=3D"50%">
                    <p align=3D"center"><font color=3D"#000000"><b><textar=
ea cols=3D"38" name=3D"feedback" rows=3D"8"></textarea></b></font>
    </center>
                  
                    <p align=3D"left"><input type=3D"text" name=3D"rating"=
 size=3D"20"></p>
                  
                    <p align=3D"left"><font color=3D"#000000"><b><input ty=
pe=3D"submit" value=3D"Submit Application"></b></font></p>
                  </form>
                    <p align=3D"left">&nbsp;
                    <p align=3D"left">&nbsp;</td>
                </tr>
              </table>
            </div>
          <p align=3D"left">&nbsp;</p>
    <center>
            <p align=3D"center"></form>
          </center>
          </tr>
        </tbody>
      </table>
    </div>
<br><b><font color=3D"#66cc99"><font size=3D+1>List
 Removal/OPT-OUT Option</font></font></b>
 <br><b><font color=3D"#000000"><font size=3D-1><a
 href=3D"mailto:starfighter@ragingbull=2Ecom?subject=3Dremove">Click
 Here</a></font></font></b>


  </body>



------=_NextPart_001_0080_01BDF6C7.FABAC1B0--

------=_NextPart_000_007F_01BDF6C7.FABAC1B0--





From list@netscape.com  Wed Jan 31 02:37:48 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA07733
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 02:37:48 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V7a4b10299;
	Tue, 30 Jan 2001 23:36:04 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V7a6I07316;
	Tue, 30 Jan 2001 23:36:06 -0800 (PST)
Resent-Date: Tue, 30 Jan 2001 23:36:06 -0800 (PST)
From: Stig Venås <venaas@alfa.itea.ntnu.no>
Date: Wed, 31 Jan 2001 08:35:48 +0100
To: "Kurt D. Zeilenga" <Kurt@openldap.org>
Cc: ietf-ldapext@netscape.com
Subject: Re: Persistent Search questions
Message-ID: <20010131083548.B4217@itea.ntnu.no>
References: <OF15946A13.9127B872-ON852569E5.000658B6@pok.ibm.com> <5.0.2.1.0.20010130175132.00a48410@router.boolean.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <5.0.2.1.0.20010130175132.00a48410@router.boolean.net>; from Kurt@OpenLDAP.org on Tue, Jan 30, 2001 at 05:57:18PM -0800
Resent-Message-ID: <"Mf5zRC.A.uxB.lB8d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

On Tue, Jan 30, 2001 at 05:57:18PM -0800, Kurt D. Zeilenga wrote:
> In regards to DoS attacks, seems you could really drive a
> server crazy by asking it to sort a persistent search.

To be of any use in an open environment I think it must be possible
with acls to specify who can make persistent search on what, and
perhaps also how many simultaneous searches are allowed. As an
administrator I wouldn't allow this for anonymous binds. There is
a danger of DoS attacks even when not sorting. It might be because
I haven't read all the details, but I fail to see how sorting can
be of any use with persistent searches, except for possibly returning
the entries already present.

Stig



From list@netscape.com  Wed Jan 31 03:13:44 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA07892
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 03:13:44 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0V8Bdb13426;
	Wed, 31 Jan 2001 00:11:39 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0V8Bfo16484;
	Wed, 31 Jan 2001 00:11:41 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 00:11:41 -0800 (PST)
Sender: Robert.Byrne@france.Sun.COM
Message-ID: <3A77C8AA.26208440@france.sun.com>
Date: Wed, 31 Jan 2001 09:11:22 +0100
From: Rob Byrne <Robert.Byrne@france.Sun.COM>
Organization: Sun Microsystems
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Jim Sermersheim <jimse@novell.com>
CC: ietf-ldapext@netscape.com
Subject: Re: Persistent Search questions
References: <sa76dbc0.007@prv-mail20.provo.novell.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"SMRxdC.A.SBE.7i8d6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit


Jim,

Seems like a good rule here would be something like "an entry returned
during a psearch operation must be subject to the same access controls
that would be applied if the entry was being returned during a
"one-off", normal search"....and that implies b).

I do no think that performance is a big issue for psearches and a "fixed
authorization" view sounds potentially dangerous.  So I would be for
mandating something like the statement above or b).

Rob.

Jim Sermersheim wrote:
> 
> The persistent search control (draft-ietf-ldapext-psearch-03.txt) states in section 3 that the search operation is modified in such a way that the searcResultDone message is never sent. This implies that the size and time limits are ignored, but it's not explicitly stated. Can anyone confirm if this is the case?
> 
> Also, there is a little blurb in the security considerations section about making sure access controls are checked for entries being returned. This is more of a question to other implementors, a server could:
> a) check access control information once at the beginning of the search, and use that information without refreshing it later (could speed response time, and "fix" authorization to a specific view, or it could
> b) recalculate access control information everytime an entry is to be returned (provides consistency over long persistent search sessions).
> 
> My feeling is that b is better, does anyone expect a?
> 
> Jim



From list@netscape.com  Wed Jan 31 07:17:35 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09662
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 07:17:34 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0VCFlb04528;
	Wed, 31 Jan 2001 04:15:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0VCFnA11639;
	Wed, 31 Jan 2001 04:15:49 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 04:15:49 -0800 (PST)
Message-Id: <200101311214.HAA09373@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ietf-ldapext@netscape.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-khan-ldapext-replica-mgmt-00.txt
Date: Wed, 31 Jan 2001 07:14:49 -0500
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <"hTMhQ.A.2zC.rHAe6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: LDAP Extensions for Managing Replication Context and 
                          Replicas
	Author(s)	: J. Khan, S. Sonntag
	Filename	: draft-khan-ldapext-replica-mgmt-00.txt
	Pages		: 14
	Date		: 30-Jan-01
	
Version 3 of the LDAP Protocol provides a mechanism for sending and
receiving extended LDAP requests.  This document describes twelve
extended operations supported by Novell eDirectory Servers.
A client application can use these extensions to manage directory
replication contexts (partitions) and replicas.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-khan-ldapext-replica-mgmt-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-khan-ldapext-replica-mgmt-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-khan-ldapext-replica-mgmt-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010130111546.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-khan-ldapext-replica-mgmt-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-khan-ldapext-replica-mgmt-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010130111546.I-D@ietf.org>

--OtherAccess--

--NextPart--




From list@netscape.com  Wed Jan 31 08:09:03 2001
Received: from netscape.com (c3po.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11394
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 08:09:03 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0VD70G11521;
	Wed, 31 Jan 2001 05:07:00 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0VD70w24311;
	Wed, 31 Jan 2001 05:07:00 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 05:07:00 -0800 (PST)
Date: Wed, 31 Jan 2001 05:06:46 -0800 (PST)
Message-Id: <200101311306.f0VD6a514799@ywing.netscape.com>
From: InquireToday@ispchannel.com
To: @netscape.com
Subject:  Over35 - FUN FIBER FACTS - Free Newsletter
X-Reply-To:  InquireToday@ispchannel.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"fVYQNB.A.W7F.y3Ae6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 7bit

Over 35 Free Health Newsletter 01-31-2001

FUN FIBER FACTS

Americans consume, on average, 10-12 grams of fiber per day. Medical experts 
agree we should consume 30-35 grams to achieve optimal health benefits. 

Studies show soluble fiber, like that found in oat bran, can significantly reduce 
cholesterol. 

Fiber is found in plant-based foods. Meat and dairy products contain no fiber. 

Calories per gram: 
Fat - 9 
Carbs - 4 
Protein - 4 
Fiber - 0.6 

Average transit time (food consumption through elimination): 
Healthy young American - 3 days 
Constipated American - 10 days 
Elderly American - 14 days 
Rural third world resident who consumes a high fiber diet- 1 ½ days 

Fiber is the only factor that increases transit time through the bowels. Slow transit 
times have been linked to gastrointestinal diseases including diverticular disease, ulcers 
and colon cancer. 

Fiber normalizes blood glucose levels – a factor is fighting and avoiding diabetes. 

The more fiber you consume, the fuller you feel and the fewer calories you absorb – 
two key factors in successful weight loss


Feel free to forward.

Removal:   Simply reply to:  TakeMeOff@ispchannel.com  
(thank you!)

To subscribe, email InquireToday@ispchannel.com with SUBSCRIBE in the subject 
line.





From list@netscape.com  Wed Jan 31 15:59:29 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA25588
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 15:59:28 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0VKvLb28366;
	Wed, 31 Jan 2001 12:57:21 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0VKvMM26650;
	Wed, 31 Jan 2001 12:57:22 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 12:57:22 -0800 (PST)
Message-Id: <sa7819b1.042@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 31 Jan 2001 13:56:56 -0700
From: "Javed Khan" <JKHAN@novell.com>
To: <ietf-ldup@imc.org>, <ietf-ldapext@netscape.com>
Subject: LDAP Extensions for Managing Replication Context and Replicas
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_673C2831.7C1D321B"
Resent-Message-ID: <"SNkc6B.A.CgG.xwHe6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_673C2831.7C1D321B
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

A New Internet-Draft is available from the on-line Internet-Drafts =
directories.

Please send comments to:

Javed Khan (jkhan@novell.com)
Steve Sonntag (vtag@novell.com)

Thanks
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

    Title        : LDAP Extensions for Managing Replication Context and=20
                          Replicas
    Author(s)    : J. Khan, S. Sonntag
    Filename    : draft-khan-ldapext-replica-mgmt-00.txt
    Pages        : 14
    Date        : 30-Jan-01
   =20
Version 3 of the LDAP Protocol provides a mechanism for sending and
receiving extended LDAP requests.  This document describes twelve
extended operations supported by Novell eDirectory Servers.
A client application can use these extensions to manage directory
replication contexts (partitions) and replicas.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-khan-ldapext-replica-mgmt-00.txt

--=_673C2831.7C1D321B
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt Tahoma; MARGIN-LEFT: 2px">
<DIV>A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV>Please send comments to:</DIV>
<DIV>&nbsp;</DIV>
<DIV>Javed Khan (<A href=3D"mailto:jkhan@novell.com">jkhan@novell.com</A>)<=
/DIV>
<DIV>Steve Sonntag (v<A href=3D"mailto:vtag@novell.com">tag@novell.com</A>)=
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</DIV>
<DIV><BR>&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; : =
LDAP=20
Extensions for Managing Replication Context and=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
Replicas<BR>&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp; : J. Khan, =
S.=20
Sonntag<BR>&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp; :=20
draft-khan-ldapext-replica-mgmt-00.txt<BR>&nbsp;&nbsp;&nbsp;=20
Pages&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; : 14<BR>&nbsp;&nbsp;&nbsp;=20
Date&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; : 30-Jan-01<BR>&nbsp;&nbsp;&nbsp;=
=20
<BR>Version 3 of the LDAP Protocol provides a mechanism for sending=20
and<BR>receiving extended LDAP requests.&nbsp; This document describes=20
twelve<BR>extended operations supported by Novell eDirectory Servers.<BR>A=
=20
client application can use these extensions to manage directory<BR>replicat=
ion=20
contexts (partitions) and replicas.</DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV>A URL for this Internet-Draft is:<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-khan-ldapext-replica-mgmt=
-00.txt">http://www.ietf.org/internet-drafts/draft-khan-ldapext-replica-mgm=
t-00.txt</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>&nbsp;</DIV></BODY></HTML>

--=_673C2831.7C1D321B--



From list@netscape.com  Wed Jan 31 16:49:18 2001
Received: from netscape.com (c3po.netscape.com [205.217.237.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26365
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 16:49:18 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0VLkfG26264;
	Wed, 31 Jan 2001 13:46:46 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0VLkgw20115;
	Wed, 31 Jan 2001 13:46:42 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 13:46:42 -0800 (PST)
Message-ID: <0000495843b4$0000074f$000033ca@>
To: <Undisclosed.Recipients@ywing.netscape.com>
From: jmwressell@earthlink.net
Subject: BIZZ OPP & FREE Vacation            3                         13258
Date: Tue, 30 Jan 2001 17:15:21 -0500
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
Resent-Message-ID: <"bqAq3.A.75E.AfIe6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: quoted-printable

<HTML><FONT  BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 =
PTSIZE=3D10><B>GET YOUR FREE GIFT WHEN<BR>
VISITING OUR WEB SITE!</B><BR>
<BR>
</FONT><FONT  COLOR=3D"#ff0000" BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR=
: #ffffff" SIZE=3D2 PTSIZE=3D10 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D=
"0"><B>Are you being paid what you are worth?</FONT><FONT  COLOR=3D"#00000=
0" BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 PTSIZE=3D=
10 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"></B><BR>
<BR>
We are living in the most prosperous time in <BR>
history. Now is your turn to profit. Learn to <BR>
earn 6 Figures from home. It is easier than ever!<BR>
<BR>
<B>Plus, receive your FREE GIFT & FREE Info when<BR>
visiting our web site.</B><BR>
<BR>
<B><A HREF=3D"http://64.177.162.200/">CLICK HERE!</A></B></B><BR>
</FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR=
: #ffffff" SIZE=3D1 PTSIZE=3D8 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D=
"0"><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<I>You were sent this message because your address is in our subscriber da=
tabase. <BR>
If you wish to be removed, please <A HREF=3D"mailto:nomore775@123india.com=
?subject=3Dremove biz">click here</A> and we will remove you from our subs=
criber list.<BR>
<BR>
<BR>
</I></FONT></HTML>






From list@netscape.com  Wed Jan 31 18:07:15 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27503
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 18:07:15 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f0VN4lb25562;
	Wed, 31 Jan 2001 15:04:47 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f0VN4mY24719;
	Wed, 31 Jan 2001 15:04:48 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 15:04:48 -0800 (PST)
Message-Id: <5.0.2.1.0.20010131141805.00a41ec0@router.boolean.net>
X-Sender: guru@router.boolean.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 31 Jan 2001 15:03:59 -0800
To: rharrison@novell.com
From: "Kurt D. Zeilenga" <Kurt@openldap.org>
Subject: extended partial response
Cc: ietf-ldapext@netscape.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Resent-Message-ID: <"s3a8PC.A.7BG.PoJe6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com

Roger,

A few comments...

I'd like to see the Abstract (actually the whole document)
generalized a bit more.  It's a bit Extended Operation centric
(which is understandable given its roots).  In fact, I suggest
that the PDU be referred to as simply as a "partial" response.

I like to see a specific statement that this response PDU SHOULD
be used instead extendedResponse to return partial search responses.

Also, section 3 might provide a "Background and Intended Use"
discussion.  In particular, I'd like to see a brief discussion
(not specification) of possible uses such as:
	1) multiple response "extended operation"
	2) subtree control w/ delete operation
	3) progress responses (returns percent of operation
	completed)

In section 4, you should state that partial responses generated
due to control processing require an responseName.  (With
extended operations, the responseName is not necessarily needed).

You might also note that responseNames of partial responses
should not be published in the root DSE as they are always
associated with some extendedRequest or control (who's OID
should be published in the root DSE).

Kurt



From list@netscape.com  Wed Jan 31 19:19:05 2001
Received: from netscape.com (r2d2.netscape.com [205.217.237.47])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28649
	for <ldapext-archive@odin.ietf.org>; Wed, 31 Jan 2001 19:19:05 -0500 (EST)
Received: from aka.mcom.com (aka.mcom.com [205.217.237.180])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f110Gnb08170;
	Wed, 31 Jan 2001 16:16:49 -0800 (PST)
Received: (from list@localhost)
	by aka.mcom.com (8.10.0/8.10.0) id f110GoU26545;
	Wed, 31 Jan 2001 16:16:50 -0800 (PST)
Resent-Date: Wed, 31 Jan 2001 16:16:50 -0800 (PST)
Message-Id: <sa78486d.043@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Wed, 31 Jan 2001 17:16:24 -0700
From: "Jim Sermersheim" <JIMSE@novell.com>
To: <andyhe@msn.com>, <ietf-ldapext@netscape.com>, <John.Liang@openwave.com>
Cc: <aherron@u.washington.edu>
Subject: RE: Fix for VLV draft.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by aka.mcom.com id f110Gmv26521
Resent-Message-ID: <"pvQA4C.A.feG.xrKe6"@glacier>
Resent-From: ietf-ldapext@netscape.com
X-Mailing-List: <ietf-ldapext@netscape.com> 
X-Loop: ietf-ldapext@netscape.com
Precedence: list
Resent-Sender: ietf-ldapext-request@netscape.com
Content-Transfer-Encoding: 8bit

>The original thinking in the sorting draft was that the client could ask 
>for it to be sorted but not require it.  The criticality field seemed at 
>the time perfectly suited for this use.  It could be that the client is 
>capable of doing the sort but also "is hopeful" that the server already has 
>the data indexed by the sort key so can simply run down the index when 
>calculating/formatting the result set.

I think, these days if someone were to define a control, and they wanted this functionality, they'd be persuaded to add an option to the control data that provided it.



