From ldapext-bounces@ietf.org  Tue Jul  1 03:57:44 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22E613A69A0;
	Tue,  1 Jul 2008 03:57:44 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 626043A69A0
	for <ldapext@core3.amsl.com>; Tue,  1 Jul 2008 03:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5
	tests=[AWL=-1.300, BAYES_50=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id S7bM4YlKryao for <ldapext@core3.amsl.com>;
	Tue,  1 Jul 2008 03:57:42 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113])
	by core3.amsl.com (Postfix) with ESMTP id 8C3153A68FA
	for <ldapext@ietf.org>; Tue,  1 Jul 2008 03:57:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by srv1.stroeder.com (Postfix) with ESMTP id 59B4E1C65E5;
	Tue,  1 Jul 2008 12:57:50 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1])
	by localhost (srv2.stroeder.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CSxkZliaz2-z; Tue,  1 Jul 2008 12:57:16 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by srv1.stroeder.com (Postfix) with ESMTP id 9CA991C6583;
	Tue,  1 Jul 2008 12:57:16 +0200 (CEST)
Message-ID: <486A0D8C.5010605@stroeder.com>
Date: Tue, 01 Jul 2008 12:57:16 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9
MIME-Version: 1.0
To: ietf-ldapbis@openldap.org, LDAP Extensions list <ldapext@ietf.org>
References: <6929B465-1C9E-47FD-8D6C-1D65E23448EA@commerce.net>	<BA85B16E-7EB6-4D64-8D28-13C76A60746D@Isode.com>	<478BA103.9040106@novell.com>	<012C9995-E26E-411D-BDA4-01DC88EA2716@Isode.com>	<5EAD3F57-8589-4173-BA65-BC635A9BBF67@sun.com>	<FBEC9E24-C367-44DD-8806-A2D946F8A46E@isode.com>
	<83812E41-EF58-47F8-9C92-85CE16DBCB13@OpenLDAP.org>
In-Reply-To: <83812E41-EF58-47F8-9C92-85CE16DBCB13@OpenLDAP.org>
X-Enigmail-Version: 0.95.6
Subject: [ldapext] LDAP BoF at IETF#72? (was: Fwd: Call for interop
	proposals)
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

Kurt Zeilenga wrote:
> 
> I note that I will likely be submitting a LDAP BoF proposal for IETF#72 
> to do work in both updating existing RFCs detailing LDAP extensions as 
> well as work on new extensions.

Any plans regarding this?
What about the interop testing?

Ciao, Michael.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Tue Jul  1 04:12:14 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 541D53A6B78;
	Tue,  1 Jul 2008 04:12:14 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D856A3A6B6A
	for <ldapext@core3.amsl.com>; Tue,  1 Jul 2008 04:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vVuW8JxCXsnq for <ldapext@core3.amsl.com>;
	Tue,  1 Jul 2008 04:12:12 -0700 (PDT)
Received: from pih-relay05.plus.net (pih-relay05.plus.net [212.159.14.132])
	by core3.amsl.com (Postfix) with ESMTP id 15A323A6B2F
	for <ldapext@ietf.org>; Tue,  1 Jul 2008 04:12:11 -0700 (PDT)
Received: from [80.229.93.1] (helo=suretecsystems.com)
	by pih-relay05.plus.net with esmtp (Exim) id 1KDdmP-0004Gm-M0;
	Tue, 01 Jul 2008 12:12:13 +0100
Received: from localhost ([127.0.0.1] helo=suretecsystems.com)
	by suretecsystems.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <ghenry@suretecsystems.com>)
	id 1KDdmP-00052B-CH; Tue, 01 Jul 2008 12:12:13 +0100
Received: (from apache@localhost)
	by suretecsystems.com (8.14.1/8.14.1/Submit) id m61BBmPH019352;
	Tue, 1 Jul 2008 12:11:48 +0100
X-Authentication-Warning: suretecsystems.com: apache set sender to
	ghenry@suretecsystems.com using -f
Received: from 212.159.59.85 (SquirrelMail authenticated user suretec)
	by webmail.suretecsystems.com with HTTP;
	Tue, 1 Jul 2008 12:11:49 +0100 (BST)
Message-ID: <56641.212.159.59.85.1214910709.squirrel@webmail.suretecsystems.com>
In-Reply-To: <486A0D8C.5010605@stroeder.com>
References: <6929B465-1C9E-47FD-8D6C-1D65E23448EA@commerce.net>
	<BA85B16E-7EB6-4D64-8D28-13C76A60746D@Isode.com>
	<478BA103.9040106@novell.com>
	<012C9995-E26E-411D-BDA4-01DC88EA2716@Isode.com>
	<5EAD3F57-8589-4173-BA65-BC635A9BBF67@sun.com>
	<FBEC9E24-C367-44DD-8806-A2D946F8A46E@isode.com>
	<83812E41-EF58-47F8-9C92-85CE16DBCB13@OpenLDAP.org>
	<486A0D8C.5010605@stroeder.com>
Date: Tue, 1 Jul 2008 12:11:49 +0100 (BST)
From: "Gavin Henry" <ghenry@suretecsystems.com>
To: Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
User-Agent: SquirrelMail/1.4.13-1.fc8
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
OpenPGP: id=796B1E87DB73BEA8
X-Plusnet-Relay: f598d3a1fc965c2c572793c337c6af00
Cc: ietf-ldapbis@openldap.org, LDAP Extensions list <ldapext@ietf.org>
Subject: Re: [ldapext] LDAP BoF at IETF#72? (was: Fwd: Call for interop
 proposals)
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

<quote who=3D"Michael Str=F6der">
> Kurt Zeilenga wrote:
>>
>> I note that I will likely be submitting a LDAP BoF proposal for IETF#72
>> to do work in both updating existing RFCs detailing LDAP extensions as
>> well as work on new extensions.
>
> Any plans regarding this?
> What about the interop testing?
>

I'm in Dublin for the cancelled OpenLDAP Developer Day anyway from Thu
31st to Tues 5th Aug, would be good to come along.

-- =

Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E ghenry@suretecsystems.com

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/


Suretec Systems is a limited company registered in Scotland. Registered
number: SC258005. Registered office: 13 Whiteley Well Place, Inverurie,
Aberdeenshire, AB51 4FP.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From caca@saaeb.com.br  Fri Jul  4 13:35:11 2008
Return-Path: <caca@saaeb.com.br>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 090563A6A7E;
	Fri,  4 Jul 2008 13:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -67.77
X-Spam-Level: 
X-Spam-Status: No, score=-67.77 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357,
	HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129,
	RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812,
	SARE_SPEC_ROLEX_NOV5A=1.062, TVD_RCVD_IP=1.931,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rWNVnlAiVRam; Fri,  4 Jul 2008 13:35:10 -0700 (PDT)
Received: from 167-52-20-190.adsl.terra.cl (167-52-20-190.adsl.terra.cl [190.20.52.167])
	by core3.amsl.com (Postfix) with SMTP id BE0693A6BBC;
	Fri,  4 Jul 2008 13:35:00 -0700 (PDT)
X-Originating-IP: 208.174.220.192 by smtp.190.20.52.167;  Fri, 04 Jul 2008 16:35:07 -0500
Message-ID: <ibgfsjfVJWDSCLl2tpext-web-archive@ietf.org>
From: "Glenn Gaston" <l2tpext-web-archive@ietf.org>
Reply-To: "Glenn Gaston" <l2tpext-web-archive@ietf.org>
To: l2tpext-web-archive@ietf.org
Subject: Prestige Replicas first-class replica watches for you
Date: Fri, 04 Jul 2008 16:35:07 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


If the only thing standing between you and a luxurious Cartier watch is money, then today is your lucky day! Prestige Replicas, the world-famous replica watches dealer, is offering a 15% discount during these spring months for two or more watches, making their whole Cartier collection even more affordable.
http://Kellipucal.blogspot.com/

As you are probably aware of, Prestige Replicas has one of the most extensive collections of Cartier replica watches in the whole wide web. Who cares if they are not legitimate? These replicas are of such high quality that not even a connoisseur would be able to distinguish them from an original Cartier. And with their online delivery guarantee you will be enjoying your new watch in just a couple of days! So, what are you waiting for? Visit Prestige Replicas today!
http://Kellipucal.blogspot.com/





From c.lomonaco@fotocomp.it  Sat Jul  5 14:18:52 2008
Return-Path: <c.lomonaco@fotocomp.it>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AF103A6885;
	Sat,  5 Jul 2008 14:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -65.26
X-Spam-Level: 
X-Spam-Status: No, score=-65.26 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HOST_EQ_D_D_D_D=0.765,
	FH_HOST_EQ_D_D_D_DB=0.888, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357,
	HELO_DYNAMIC_IPADDR2=4.395, HELO_DYNAMIC_SPLIT_IP=3.493,
	HELO_EQ_BR=0.955, HELO_EQ_DIALUP=0.862, HELO_EQ_IP_ADDR=1.119,
	HOST_EQ_BR=1.295, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_NUMERIC_HELO=2.067, RDNS_DYNAMIC=0.1,
	SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX_NOV5A=1.062,
	TVD_RCVD_IP=1.931, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tOXjapCXu9X9; Sat,  5 Jul 2008 14:18:51 -0700 (PDT)
Received: from 200.146.7.169.dialup.gvt.net.br (200.146.7.169.dialup.gvt.net.br [200.146.7.169])
	by core3.amsl.com (Postfix) with SMTP id AF3513A68BE;
	Sat,  5 Jul 2008 14:18:18 -0700 (PDT)
X-Originating-IP: 115.186.105.211 by smtp.200.146.7.169;  Sat, 05 Jul 2008 17:18:18 -0500
Message-ID: <kmykvNTLAIDl2tpext-web-archive@ietf.org>
From: "Alton Carson" <l2tpext-web-archive@ietf.org>
Reply-To: "Alton Carson" <l2tpext-web-archive@ietf.org>
To: l2tpext-web-archive@ietf.org
Subject: Jaeger-LeCoultre replica watch Luxury isn't a sin
Date: Sat, 05 Jul 2008 17:18:18 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit
X-Antivirus: avast! (VPS 000761-2, 27/07/2007), Outbound message
X-Antivirus-Status: Clean


If the only thing standing between you and a luxurious Cartier watch is money, then today is your lucky day! Prestige Replicas, the world-famous replica watches dealer, is offering a 15% discount during these spring months for two or more watches, making their whole Cartier collection even more affordable.
http://Rosemariewynumu.blogspot.com/

As you are probably aware of, Prestige Replicas has one of the most extensive collections of Cartier replica watches in the whole wide web. Who cares if they are not legitimate? These replicas are of such high quality that not even a connoisseur would be able to distinguish them from an original Cartier. And with their online delivery guarantee you will be enjoying your new watch in just a couple of days! So, what are you waiting for? Visit Prestige Replicas today!
http://Rosemariewynumu.blogspot.com/





From c_griffin@premiersec.com  Tue Jul  8 18:34:25 2008
Return-Path: <c_griffin@premiersec.com>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 860393A694E;
	Tue,  8 Jul 2008 18:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -48.214
X-Spam-Level: 
X-Spam-Status: No, score=-48.214 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FB_QUALITY_REPLICA=10.357,
	FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357,
	GB_ROLEX=5, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426,
	HELO_EQ_CPE=0.5, HOST_EQ_CPE=0.979, RCVD_IN_BL_SPAMCOP_NET=1.96,
	RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033,
	RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666,
	SARE_SPEC_ROLEX_HIQLT=1.666, SARE_SPEC_ROLEX_NOV5A=1.062,
	SARE_SPEC_ROLEX_NOV5F=0.666, SARE_SPEC_ROLEX_REP=1.666,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y4eDsaKSZHq1; Tue,  8 Jul 2008 18:34:24 -0700 (PDT)
Received: from cpe-24-90-65-190.nyc.res.rr.com (cpe-24-90-65-190.nyc.res.rr.com [24.90.65.190])
	by core3.amsl.com (Postfix) with SMTP id AA3A43A684B;
	Tue,  8 Jul 2008 18:34:23 -0700 (PDT)
X-Originating-IP: 125.39.192.76 by smtp.24.90.65.190;  Tue, 08 Jul 2008 21:34:33 -0500
Message-ID: <aujapasWZVKYERldapext-archive@ietf.org>
From: "Bonnie Collins" <ldapext-archive@ietf.org>
Reply-To: "Bonnie Collins" <ldapext-archive@ietf.org>
To: ldapext-archive@ietf.org
Subject: Delightful replica watches at Prestige Replicas
Date: Tue, 08 Jul 2008 21:34:33 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


Have you always wanted a Rolex, but don't want to pay high prices for a brand name watch? Then you need to visit Prestige Replicas, a website dedicated exclusively to high quality replicas, with the most extensive inventory on the web and a proven track record of satisfied customers.
http://Karinadifem.blogspot.com/

Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal!
http://Karinadifem.blogspot.com/





From lemonade-bounces@ietf.org  Tue Jul  8 18:34:26 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: ldapext-archive@ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABDCF3A6950
	for <ldapext-archive@ietf.org>; Tue,  8 Jul 2008 18:34:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Your message to lemonade awaits moderator approval
From: lemonade-bounces@ietf.org
To: ldapext-archive@ietf.org
Message-ID: <mailman.3747.1215567265.4989.lemonade@ietf.org>
Date: Tue, 08 Jul 2008 18:34:25 -0700
Precedence: bulk
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
X-List-Administrivia: yes
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Your mail to 'lemonade' with the subject

    Delightful replica watches at Prestige Replicas

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

    https://www.ietf.org/mailman/confirm/lemonade/d9d6480ce391a92d72f8bc42f3907a3ae402aeb1



From lemonade-bounces@ietf.org  Tue Jul  8 18:34:26 2008
Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: ldapext-archive@ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ADDE73A6952
	for <ldapext-archive@ietf.org>; Tue,  8 Jul 2008 18:34:26 -0700 (PDT)
Subject: The results of your email commands
From: lemonade-bounces@ietf.org
To: ldapext-archive@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1145996521=="
Message-ID: <mailman.12190.1215567265.4988.lemonade@ietf.org>
Date: Tue, 08 Jul 2008 18:34:25 -0700
Precedence: bulk
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
List-Id: Enhancements to Internet email to support diverse service
	enivronments <lemonade.ietf.org>
X-List-Administrivia: yes
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

--===============1145996521==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

The results of your email command are provided below. Attached is your
original message.


- Unprocessed:
    http://Karinadifem.blogspot.com/
    Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal!
    http://Karinadifem.blogspot.com/

- Done.


--===============1145996521==
Content-Type: message/rfc822
MIME-Version: 1.0

Return-Path: <c_griffin@premiersec.com>
X-Original-To: lemonade-request@core3.amsl.com
Delivered-To: lemonade-request@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 860393A694E;
	Tue,  8 Jul 2008 18:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -48.214
X-Spam-Level: 
X-Spam-Status: No, score=-48.214 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FB_QUALITY_REPLICA=10.357,
	FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357,
	GB_ROLEX=5, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426,
	HELO_EQ_CPE=0.5, HOST_EQ_CPE=0.979, RCVD_IN_BL_SPAMCOP_NET=1.96,
	RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033,
	RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666,
	SARE_SPEC_ROLEX_HIQLT=1.666, SARE_SPEC_ROLEX_NOV5A=1.062,
	SARE_SPEC_ROLEX_NOV5F=0.666, SARE_SPEC_ROLEX_REP=1.666,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y4eDsaKSZHq1; Tue,  8 Jul 2008 18:34:24 -0700 (PDT)
Received: from cpe-24-90-65-190.nyc.res.rr.com (cpe-24-90-65-190.nyc.res.rr.com [24.90.65.190])
	by core3.amsl.com (Postfix) with SMTP id AA3A43A684B;
	Tue,  8 Jul 2008 18:34:23 -0700 (PDT)
X-Originating-IP: 125.39.192.76 by smtp.24.90.65.190;  Tue, 08 Jul 2008 21:34:33 -0500
Message-ID: <aujapasWZVKYERldapext-archive@ietf.org>
From: "Bonnie Collins" <ldapext-archive@ietf.org>
Reply-To: "Bonnie Collins" <ldapext-archive@ietf.org>
To: ldapext-archive@ietf.org
Subject: Delightful replica watches at Prestige Replicas
Date: Tue, 08 Jul 2008 21:34:33 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


Have you always wanted a Rolex, but don't want to pay high prices for a brand name watch? Then you need to visit Prestige Replicas, a website dedicated exclusively to high quality replicas, with the most extensive inventory on the web and a proven track record of satisfied customers.
http://Karinadifem.blogspot.com/

Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal!
http://Karinadifem.blogspot.com/




--===============1145996521==--


From ldapext-bounces@ietf.org  Tue Jul  8 18:34:26 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1E6D3A6950
	for <ldapext-archive@ietf.org>; Tue,  8 Jul 2008 18:34:26 -0700 (PDT)
Subject: The results of your email commands
From: ldapext-bounces@ietf.org
To: ldapext-archive@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1694899278=="
Message-ID: <mailman.12191.1215567265.4988.ldapext@ietf.org>
Date: Tue, 08 Jul 2008 18:34:25 -0700
Precedence: bulk
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
X-List-Administrivia: yes
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

--===============1694899278==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

The results of your email command are provided below. Attached is your
original message.


- Unprocessed:
    http://Karinadifem.blogspot.com/
    Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal!
    http://Karinadifem.blogspot.com/

- Done.


--===============1694899278==
Content-Type: message/rfc822
MIME-Version: 1.0

Return-Path: <c_griffin@premiersec.com>
X-Original-To: ldapext-request@core3.amsl.com
Delivered-To: ldapext-request@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 860393A694E;
	Tue,  8 Jul 2008 18:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -48.214
X-Spam-Level: 
X-Spam-Status: No, score=-48.214 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FB_QUALITY_REPLICA=10.357,
	FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357,
	GB_ROLEX=5, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426,
	HELO_EQ_CPE=0.5, HOST_EQ_CPE=0.979, RCVD_IN_BL_SPAMCOP_NET=1.96,
	RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033,
	RDNS_DYNAMIC=0.1, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666,
	SARE_SPEC_ROLEX_HIQLT=1.666, SARE_SPEC_ROLEX_NOV5A=1.062,
	SARE_SPEC_ROLEX_NOV5F=0.666, SARE_SPEC_ROLEX_REP=1.666,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y4eDsaKSZHq1; Tue,  8 Jul 2008 18:34:24 -0700 (PDT)
Received: from cpe-24-90-65-190.nyc.res.rr.com (cpe-24-90-65-190.nyc.res.rr.com [24.90.65.190])
	by core3.amsl.com (Postfix) with SMTP id AA3A43A684B;
	Tue,  8 Jul 2008 18:34:23 -0700 (PDT)
X-Originating-IP: 125.39.192.76 by smtp.24.90.65.190;  Tue, 08 Jul 2008 21:34:33 -0500
Message-ID: <aujapasWZVKYERldapext-archive@ietf.org>
From: "Bonnie Collins" <ldapext-archive@ietf.org>
Reply-To: "Bonnie Collins" <ldapext-archive@ietf.org>
To: ldapext-archive@ietf.org
Subject: Delightful replica watches at Prestige Replicas
Date: Tue, 08 Jul 2008 21:34:33 -0500
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit


Have you always wanted a Rolex, but don't want to pay high prices for a brand name watch? Then you need to visit Prestige Replicas, a website dedicated exclusively to high quality replicas, with the most extensive inventory on the web and a proven track record of satisfied customers.
http://Karinadifem.blogspot.com/

Prestige Replicas offers hundreds of Rolex replica watches starting just above $100, and during this spring season, their already low prices have been slashed by 15 percent if you buy two or more watches! No matter which model Rolex you choose, their 15% discount applies to them all! But don't let this limited time offer go by... spring is ending and it's time to impress your friends with a realistic, high quality Rolex replica watch, that will look and perform just like the real deal!
http://Karinadifem.blogspot.com/




--===============1694899278==--


From helpjoy1@fastwebmail.it  Sat Jul 12 07:13:02 2008
Return-Path: <helpjoy1@fastwebmail.it>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C5833A6BAB
	for <ietfarch-ldapext-archive@core3.amsl.com>; Sat, 12 Jul 2008 07:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.124
X-Spam-Level: *
X-Spam-Status: No, score=1.124 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001,
	RAZOR2_CHECK=0.5]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 67y-8QFFWgwS
	for <ietfarch-ldapext-archive@core3.amsl.com>;
	Sat, 12 Jul 2008 07:13:02 -0700 (PDT)
Received: from qb-out-1314.google.com (qb-out-1314.google.com [72.14.204.168])
	by core3.amsl.com (Postfix) with ESMTP id 37ED73A6823
	for <ldapext-archive@ietf.org>; Sat, 12 Jul 2008 07:13:02 -0700 (PDT)
Received: by qb-out-1314.google.com with SMTP id f14so2480353qba.4
        for <ldapext-archive@ietf.org>; Sat, 12 Jul 2008 07:13:20 -0700 (PDT)
Received: by 10.103.244.10 with SMTP id w10mr6319809mur.67.1215871940180;
        Sat, 12 Jul 2008 07:12:20 -0700 (PDT)
Received: by 10.103.191.11 with HTTP; Sat, 12 Jul 2008 07:12:20 -0700 (PDT)
Message-ID: <536b232c0807120712g32dd4da8j181c07bd1c86e23d@mail.gmail.com>
Date: Sat, 12 Jul 2008 15:12:20 +0100
From: "Miss Joy Ogeh" <helpjoy1@fastwebmail.it>
Reply-To: jjoy.ogeh@centrum.sk
To: helpjoy1@fastweb.it
Subject: Dearest One,
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_14687_25766264.1215871940163"

------=_Part_14687_25766264.1215871940163
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dearest One,

I'm a 19 year old , my father  died  a year ago in a gold mine in Gbangbama
district, Republic of Sierra Leone ,He was into legal gold minning, he has
succeded in saving $18.5millions dollars during his Business on Gold, before
he went on a trip  to Republic of Cote d'Ivoire a near by country to our
country  to save his money for security reasons because of the political
problem in our country.

I need help  from you out there to help me transfer this money to your
country for investment while i continue my school and with a  sincere mind
to invest  this money in your country without cheating me or doing bad to me
on our arraival,  I'm willing to give to you  20% of the money after the
transfer of the money , please mail me immidately  to know your stands
before looking else where  you're the first person i'm contacting relating
to this business.

Now permit me to ask these few questions:-

1. Can you honestly help me as your daughter?
2. Can i completely trust you?

Please,Consider this and get back to me as soon as possible.
Treat this email confidential and it is never a joke for your
information,you call me to speak with me ok!
Yours Sincerely.
Joy Ogeh

------=_Part_14687_25766264.1215871940163
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<p>Dearest One,<br>&nbsp;<br>I&#39;m a 19 year old , my father&nbsp; died&nbsp; a year ago in a gold mine in Gbangbama district, Republic of Sierra Leone ,He was into legal gold minning, he has succeded in saving $18.5millions dollars during his Business on Gold, before he went on a trip&nbsp; to Republic of Cote d&#39;Ivoire a near by country to our country&nbsp; to save his money for security reasons because of the political problem in our country. <br>
&nbsp;<br>I need help&nbsp; from you out there to help me transfer this money to your country for investment while i continue my school and with a&nbsp; sincere mind to invest&nbsp; this money in your country without cheating me or doing bad to me on our arraival,&nbsp; I&#39;m willing to give to you&nbsp; 20% of the money after the transfer of the money , please mail me immidately&nbsp; to know your stands before looking else where&nbsp; you&#39;re the first person i&#39;m contacting relating to this business. <br>
&nbsp;<br>Now permit me to ask these few questions:-</p>
<p>1. Can you honestly help me as your daughter? <br>2. Can i completely trust you? <br>&nbsp;<br>Please,Consider this and get back to me as soon as possible. <br>Treat this email confidential and it is never a joke for your information,you call me to speak with me ok!<br>
Yours Sincerely.<br>Joy Ogeh</p>

------=_Part_14687_25766264.1215871940163--


From ldapext-bounces@ietf.org  Sun Jul 13 20:43:16 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D6DA3A69A3;
	Sun, 13 Jul 2008 20:43:16 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8876E3A69A3
	for <ldapext@core3.amsl.com>; Sun, 13 Jul 2008 20:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DCba9kl8OVRj for <ldapext@core3.amsl.com>;
	Sun, 13 Jul 2008 20:43:14 -0700 (PDT)
Received: from mail.highlandsun.com (mail.highlandsun.com [70.87.222.79])
	by core3.amsl.com (Postfix) with ESMTP id 208043A6858
	for <ldapext@ietf.org>; Sun, 13 Jul 2008 20:43:14 -0700 (PDT)
Received: from [127.0.0.1] (mail.highlandsun.com [70.87.222.79])
	by mail.highlandsun.com (Postfix) with ESMTP id D494310F94
	for <ldapext@ietf.org>; Sun, 13 Jul 2008 23:43:38 -0400 (EDT)
Message-ID: <487ACB66.4080309@highlandsun.com>
Date: Sun, 13 Jul 2008 20:43:34 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9.0.1pre) Gecko/2008062211 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Ldapext <ldapext@ietf.org>
Subject: [ldapext] [Fwd: Re: [OpenDS-users] LDAP Password Modify Extended
	Operation]
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

Looks like we need some clarification of RFC3062...

-------- Original Message --------
Subject: Re: [OpenDS-users] LDAP Password Modify Extended Operation
Date: Mon, 14 Jul 2008 02:37:30 +0200
From: Anton Bobrov <Anton.Bobrov@Sun.COM>
Reply-To: users@opends.dev.java.net
Organization: Sun Microsystems, Inc.
To: users@opends.dev.java.net
References: <487A7E3E.6030207@stroeder.com> <487A83B3.4010608@sun.com> =

<487A85F2.3020802@stroeder.com> <487A92DB.3040606@sun.com> =

<487A97E8.4010008@symas.com>


yeah, i think it is confusing and should be clarified.
to me [since the same thing used elsewhere] it is what
Kurt did imply, you sure could ask him to comment on
that but as long as its not clarified in the RFC its
somewhat a hanger really. i leave it to Kurt and Ludo
[Ludo, are you reading this ?].

Howard Chu wrote:
> Anton Bobrov wrote:
>> Michael, its mentioned a bit earlier in that RFC, see
>> "1. Background and Intent of Use" section there which
>> specifically talks about that and has a reference to
>> RFC2829 where related to your question see section 9.
>> "Authorization Identity".
>
> Oddly enough, RFC3062 could have plainly said that the userIdentity was
> an RFC2829 Authorization Identity, but it doesn't. It says it may (or
> may not) be an LDAPDN, and LDAPDNs clearly do not begin with a "dn:"
> prefix. Maybe this should be clarified in an IETF forum.
>
>> Michael Str=F6der wrote:
>>> Michael Dugan wrote:
>>>> Michael Str=F6der wrote:
>>>>> I'm testing LDAP Password Modify Extended Operation (RFC 3062) with
>>>>> OpenDS 1.0. I just sent the new password in the request, bound as
>>>>> "cn=3DDirectory Manager". Are there any restrictions?
>>>>>
>>>>> I get the following error:
>>>>>
>>>>> ---------------------------- snip ----------------------------
>>>>> Protocol error:
>>>>> The password modify extended request cannot be processed because it
>>>>> contained an invalid authorization ID that did not start with either
>>>>> "dn:" or "u:". The provided authorization ID string was "cn=3DFred
>>>>> Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=3Dlocal"
>>>>> ---------------------------- snip ----------------------------
>>>>>
>>>>> Frankly I don't understand what it says. To me it sounds rather an
>>>>> error message related to "Who Ami I? ext. op.".
>>>> Since "cn=3DFred Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=
=3Dlocal"
>>>   >
>>>> looks like a DN, you
>>>> probably need to prefix it with "dn:". For example,
>>>>
>>>>    "dn:cn=3DFred Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=
=3Dlocal"
>>>>
>>>> if not it assumes it is not a DN and tries to use an identity mapper
>>>> to process the request.
>>> Could you please point me to the part of RFC 3062 which talks about
>>> adding a "dn:" prefix?
>>>
>>> I only found:
>>>
>>> ------------------------------------------------------------------
>>>     PasswdModifyRequestValue ::=3D SEQUENCE {
>>>       userIdentity    [0]  OCTET STRING OPTIONAL
>>>       oldPasswd       [1]  OCTET STRING OPTIONAL
>>>       newPasswd       [2]  OCTET STRING OPTIONAL }
>>> [..]
>>>     The userIdentity field, if present, SHALL contain an octet string
>>>     representation of the user associated with the request.  This string
>>>     may or may not be an LDAPDN [RFC2253].  If no userIdentity field is
>>>     present, the request acts up upon the password of the user currently
>>>     associated with the LDAP session.
>>> ------------------------------------------------------------------
>>>
>>> My understanding is that the server has to detect whether it's a valid
>>> DN or not and act accordingly.
>>>
>>> Ciao, Michael.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@opends.dev.java.net
>>> For additional commands, e-mail: users-help@opends.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@opends.dev.java.net
>> For additional commands, e-mail: users-help@opends.dev.java.net
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@opends.dev.java.net
For additional commands, e-mail: users-help@opends.dev.java.net



-- =

   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Sun Jul 13 21:31:22 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D8F1B28C13B;
	Sun, 13 Jul 2008 21:31:22 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 717DB3A692C
	for <ldapext@core3.amsl.com>; Sun, 13 Jul 2008 21:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id v5ztuiXwOeN5 for <ldapext@core3.amsl.com>;
	Sun, 13 Jul 2008 21:31:20 -0700 (PDT)
Received: from boole.openldap.org (boole.openldap.org
	[IPv6:2001:4f8:3:ba:2e0:18ff:fe02:efec])
	by core3.amsl.com (Postfix) with ESMTP id B01223A69FC
	for <ldapext@ietf.org>; Sun, 13 Jul 2008 21:31:19 -0700 (PDT)
Received: from [192.168.1.102] (75-141-230-206.dhcp.nv.charter.com
	[75.141.230.206] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.8/8.13.8) with ESMTP id m6E4VeZs093158
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 14 Jul 2008 04:31:41 GMT (envelope-from Kurt.Zeilenga@Isode.com)
Message-Id: <F8DCD05B-2C70-4B34-8BEE-929C60032088@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
To: Howard Chu <hyc@highlandsun.com>
In-Reply-To: <487ACB66.4080309@highlandsun.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Sun, 13 Jul 2008 21:30:25 -0700
References: <487ACB66.4080309@highlandsun.com>
X-Mailer: Apple Mail (2.926)
Cc: Ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] [Fwd: Re: [OpenDS-users] LDAP Password Modify
	Extended Operation]
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org


On Jul 13, 2008, at 8:43 PM, Howard Chu wrote:

> Looks like we need some clarification of RFC3062...


The userIdentity string is either an RFC 4514 LDAP string  =

representation of a DN, or some other string representation of a DN  =

(LDAP generally allows alternative string representations), or some  =

string representation of some other authentication identity form (such  =

as a SASLprep user name used in PLAIN, CRAM-MD5, DIGEST-MD5).

The intent is for the field to carry the same user identity (authcid)  =

string that the user would normally use for password authentication.   =

For instance, "kurt@example.com" or "uid=3Dkurt,dc=3Dexample,dc=3Dcom".

Note that authzid is for representing authorization identities, not  =

authentication identities.  Hence, it was not my intent that the user  =

provide an authzid.  However, it would be reasonable for  =

implementations to accept these IN ADDITION to user's authentication  =

identity strings.

-- Kurt

>
>
> -------- Original Message -------
> Subject: Re: [OpenDS-users] LDAP Password Modify Extended Operation
> Date: Mon, 14 Jul 2008 02:37:30 +0200
> From: Anton Bobrov <Anton.Bobrov@Sun.COM>
> Reply-To: users@opends.dev.java.net
> Organization: Sun Microsystems, Inc.
> To: users@opends.dev.java.net
> References: <487A7E3E.6030207@stroeder.com>  =

> <487A83B3.4010608@sun.com> <487A85F2.3020802@stroeder.com> <487A92DB.3040=
606@sun.com =

> > <487A97E8.4010008@symas.com>
>
>
> yeah, i think it is confusing and should be clarified.
> to me [since the same thing used elsewhere] it is what
> Kurt did imply, you sure could ask him to comment on
> that but as long as its not clarified in the RFC its
> somewhat a hanger really. i leave it to Kurt and Ludo
> [Ludo, are you reading this ?].
>
> Howard Chu wrote:
>> Anton Bobrov wrote:
>>> Michael, its mentioned a bit earlier in that RFC, see
>>> "1. Background and Intent of Use" section there which
>>> specifically talks about that and has a reference to
>>> RFC2829 where related to your question see section 9.
>>> "Authorization Identity".
>>
>> Oddly enough, RFC3062 could have plainly said that the userIdentity  =

>> was
>> an RFC2829 Authorization Identity, but it doesn't. It says it may (or
>> may not) be an LDAPDN, and LDAPDNs clearly do not begin with a "dn:"
>> prefix. Maybe this should be clarified in an IETF forum.
>>
>>> Michael Str=F6der wrote:
>>>> Michael Dugan wrote:
>>>>> Michael Str=F6der wrote:
>>>>>> I'm testing LDAP Password Modify Extended Operation (RFC 3062)  =

>>>>>> with
>>>>>> OpenDS 1.0. I just sent the new password in the request, bound as
>>>>>> "cn=3DDirectory Manager". Are there any restrictions?
>>>>>>
>>>>>> I get the following error:
>>>>>>
>>>>>> ---------------------------- snip ----------------------------
>>>>>> Protocol error:
>>>>>> The password modify extended request cannot be processed  =

>>>>>> because it
>>>>>> contained an invalid authorization ID that did not start with  =

>>>>>> either
>>>>>> "dn:" or "u:". The provided authorization ID string was "cn=3DFred
>>>>>> Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=3Dlocal"
>>>>>> ---------------------------- snip ----------------------------
>>>>>>
>>>>>> Frankly I don't understand what it says. To me it sounds rather  =

>>>>>> an
>>>>>> error message related to "Who Ami I? ext. op.".
>>>>> Since "cn=3DFred  =

>>>>> Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=3Dlocal"
>>>>  >
>>>>> looks like a DN, you
>>>>> probably need to prefix it with "dn:". For example,
>>>>>
>>>>>   "dn:cn=3DFred Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=
=3Dlocal"
>>>>>
>>>>> if not it assumes it is not a DN and tries to use an identity  =

>>>>> mapper
>>>>> to process the request.
>>>> Could you please point me to the part of RFC 3062 which talks about
>>>> adding a "dn:" prefix?
>>>>
>>>> I only found:
>>>>
>>>> ------------------------------------------------------------------
>>>>    PasswdModifyRequestValue ::=3D SEQUENCE {
>>>>      userIdentity    [0]  OCTET STRING OPTIONAL
>>>>      oldPasswd       [1]  OCTET STRING OPTIONAL
>>>>      newPasswd       [2]  OCTET STRING OPTIONAL }
>>>> [..]
>>>>    The userIdentity field, if present, SHALL contain an octet  =

>>>> string
>>>>    representation of the user associated with the request.  This  =

>>>> string
>>>>    may or may not be an LDAPDN [RFC2253].  If no userIdentity  =

>>>> field is
>>>>    present, the request acts up upon the password of the user  =

>>>> currently
>>>>    associated with the LDAP session.
>>>> ------------------------------------------------------------------
>>>>
>>>> My understanding is that the server has to detect whether it's a  =

>>>> valid
>>>> DN or not and act accordingly.
>>>>
>>>> Ciao, Michael.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@opends.dev.java.net
>>>> For additional commands, e-mail: users-help@opends.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@opends.dev.java.net
>>> For additional commands, e-mail: users-help@opends.dev.java.net
>>>
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@opends.dev.java.net
> For additional commands, e-mail: users-help@opends.dev.java.net
>
>
>
> -- =

>  -- Howard Chu
>  CTO, Symas Corp.           http://www.symas.com
>  Director, Highland Sun     http://highlandsun.com/hyc/
>  Chief Architect, OpenLDAP  http://www.openldap.org/project/
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www.ietf.org/mailman/listinfo/ldapext

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Mon Jul 14 01:48:16 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4FA53A6AD9;
	Mon, 14 Jul 2008 01:48:16 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51E793A6A0C
	for <ldapext@core3.amsl.com>; Mon, 14 Jul 2008 01:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e1uIQpJjn0Si for <ldapext@core3.amsl.com>;
	Mon, 14 Jul 2008 01:48:13 -0700 (PDT)
Received: from mail.highlandsun.com (mail.highlandsun.com [70.87.222.79])
	by core3.amsl.com (Postfix) with ESMTP id 9BCD13A68DB
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 01:48:13 -0700 (PDT)
Received: from [127.0.0.1] (mail.highlandsun.com [70.87.222.79])
	by mail.highlandsun.com (Postfix) with ESMTP id BC3C610F94;
	Mon, 14 Jul 2008 04:48:38 -0400 (EDT)
Message-ID: <487B12E2.1040209@highlandsun.com>
Date: Mon, 14 Jul 2008 01:48:34 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9.0.1pre) Gecko/2008062211 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
References: <487ACB66.4080309@highlandsun.com>
	<F8DCD05B-2C70-4B34-8BEE-929C60032088@Isode.com>
In-Reply-To: <F8DCD05B-2C70-4B34-8BEE-929C60032088@Isode.com>
Cc: Ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] [Fwd: Re: [OpenDS-users] LDAP Password Modify
 Extended Operation]
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

Kurt Zeilenga wrote:
> On Jul 13, 2008, at 8:43 PM, Howard Chu wrote:
>
>> Looks like we need some clarification of RFC3062...
>
>
> The userIdentity string is either an RFC 4514 LDAP string
> representation of a DN, or some other string representation of a DN
> (LDAP generally allows alternative string representations), or some
> string representation of some other authentication identity form (such
> as a SASLprep user name used in PLAIN, CRAM-MD5, DIGEST-MD5).
>
> The intent is for the field to carry the same user identity (authcid)
> string that the user would normally use for password authentication.
> For instance, "kurt@example.com" or "uid=3Dkurt,dc=3Dexample,dc=3Dcom".
>
> Note that authzid is for representing authorization identities, not
> authentication identities.  Hence, it was not my intent that the user
> provide an authzid.  However, it would be reasonable for
> implementations to accept these IN ADDITION to user's authentication
> identity strings.

That seems like a friendly thing to do, but it's blurring the distinction =

between authcID and authzID, to the point of meaninglessness.

In linguistic terms, the authzID is a Subject (the entity that is acting), =
and =

in this op the userID/authcID is an Object (the entity that is being acted =

on). Semantically they're very different. This blurring seems like A Bad Th=
ing =

to me.

On the flip side, using an explicitly tagged authzID has the advantage of n=
ot =

making the server try to guess what form of userID has been provided...

As a complete aside, there seems to be a disconnect here - it appears that =

there ought to be a way to specify which password validation mechanism's =

password is being changed. E.g., it's possible for a user to have a valid =

directory entry with a local userPassword attribute, as well as a valid =

password in an external store, e.g. sasldb. (Ugly, but this used to come up =

frequently.) The local userPassword would be used for Simple Binds, and the =

sasldb would be used for SASL Binds. Similarly for SASL Binds, not all mech=
s =

will necessarily use the same password, so it may be desirable to specify =

which mech's password to set. (E.g., SASL/OTP)
>
> -- Kurt
>
>>
>> -------- Original Message -------
>> Subject: Re: [OpenDS-users] LDAP Password Modify Extended Operation
>> Date: Mon, 14 Jul 2008 02:37:30 +0200
>> From: Anton Bobrov<Anton.Bobrov@Sun.COM>
>> Reply-To: users@opends.dev.java.net
>> Organization: Sun Microsystems, Inc.
>> To: users@opends.dev.java.net
>> References:<487A7E3E.6030207@stroeder.com>
>> <487A83B3.4010608@sun.com>  <487A85F2.3020802@stroeder.com>  <487A92DB.3=
040606@sun.com
>>> <487A97E8.4010008@symas.com>
>>
>> yeah, i think it is confusing and should be clarified.
>> to me [since the same thing used elsewhere] it is what
>> Kurt did imply, you sure could ask him to comment on
>> that but as long as its not clarified in the RFC its
>> somewhat a hanger really. i leave it to Kurt and Ludo
>> [Ludo, are you reading this ?].
>>
>> Howard Chu wrote:
>>> Anton Bobrov wrote:
>>>> Michael, its mentioned a bit earlier in that RFC, see
>>>> "1. Background and Intent of Use" section there which
>>>> specifically talks about that and has a reference to
>>>> RFC2829 where related to your question see section 9.
>>>> "Authorization Identity".
>>> Oddly enough, RFC3062 could have plainly said that the userIdentity
>>> was
>>> an RFC2829 Authorization Identity, but it doesn't. It says it may (or
>>> may not) be an LDAPDN, and LDAPDNs clearly do not begin with a "dn:"
>>> prefix. Maybe this should be clarified in an IETF forum.
>>>
>>>> Michael Str=F6der wrote:
>>>>> Michael Dugan wrote:
>>>>>> Michael Str=F6der wrote:
>>>>>>> I'm testing LDAP Password Modify Extended Operation (RFC 3062)
>>>>>>> with
>>>>>>> OpenDS 1.0. I just sent the new password in the request, bound as
>>>>>>> "cn=3DDirectory Manager". Are there any restrictions?
>>>>>>>
>>>>>>> I get the following error:
>>>>>>>
>>>>>>> ---------------------------- snip ----------------------------
>>>>>>> Protocol error:
>>>>>>> The password modify extended request cannot be processed
>>>>>>> because it
>>>>>>> contained an invalid authorization ID that did not start with
>>>>>>> either
>>>>>>> "dn:" or "u:". The provided authorization ID string was "cn=3DFred
>>>>>>> Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=3Dlocal"
>>>>>>> ---------------------------- snip ----------------------------
>>>>>>>
>>>>>>> Frankly I don't understand what it says. To me it sounds rather
>>>>>>> an
>>>>>>> error message related to "Who Ami I? ext. op.".
>>>>>> Since "cn=3DFred
>>>>>> Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=3Dlocal"
>>>>>   >
>>>>>> looks like a DN, you
>>>>>> probably need to prefix it with "dn:". For example,
>>>>>>
>>>>>>    "dn:cn=3DFred Feuerstein,ou=3DPeople,dc=3Dopends,dc=3Dstroeder,dc=
=3Dlocal"
>>>>>>
>>>>>> if not it assumes it is not a DN and tries to use an identity
>>>>>> mapper
>>>>>> to process the request.
>>>>> Could you please point me to the part of RFC 3062 which talks about
>>>>> adding a "dn:" prefix?
>>>>>
>>>>> I only found:
>>>>>
>>>>> ------------------------------------------------------------------
>>>>>     PasswdModifyRequestValue ::=3D SEQUENCE {
>>>>>       userIdentity    [0]  OCTET STRING OPTIONAL
>>>>>       oldPasswd       [1]  OCTET STRING OPTIONAL
>>>>>       newPasswd       [2]  OCTET STRING OPTIONAL }
>>>>> [..]
>>>>>     The userIdentity field, if present, SHALL contain an octet
>>>>> string
>>>>>     representation of the user associated with the request.  This
>>>>> string
>>>>>     may or may not be an LDAPDN [RFC2253].  If no userIdentity
>>>>> field is
>>>>>     present, the request acts up upon the password of the user
>>>>> currently
>>>>>     associated with the LDAP session.
>>>>> ------------------------------------------------------------------
>>>>>
>>>>> My understanding is that the server has to detect whether it's a
>>>>> valid
>>>>> DN or not and act accordingly.
>>>>>
>>>>> Ciao, Michael.

-- =

   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Mon Jul 14 02:06:05 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8344B28C21F;
	Mon, 14 Jul 2008 02:06:05 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15B4D28C21F
	for <ldapext@core3.amsl.com>; Mon, 14 Jul 2008 02:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5mKjbyDQe9bM for <ldapext@core3.amsl.com>;
	Mon, 14 Jul 2008 02:06:03 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113])
	by core3.amsl.com (Postfix) with ESMTP id 2B21928C21D
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 02:06:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by srv1.stroeder.com (Postfix) with ESMTP id 404CC1C6639
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 11:06:26 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1])
	by localhost (srv2.stroeder.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hfywXfeZDwiW for <ldapext@ietf.org>;
	Mon, 14 Jul 2008 11:05:58 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by srv1.stroeder.com (Postfix) with ESMTP id AD1231C662B
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 11:05:57 +0200 (CEST)
Message-ID: <487B16F5.509@stroeder.com>
Date: Mon, 14 Jul 2008 11:05:57 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: Ldapext <ldapext@ietf.org>
References: <487ACB66.4080309@highlandsun.com>	<F8DCD05B-2C70-4B34-8BEE-929C60032088@Isode.com>
	<487B12E2.1040209@highlandsun.com>
In-Reply-To: <487B12E2.1040209@highlandsun.com>
X-Enigmail-Version: 0.95.6
Subject: Re: [ldapext] [Fwd: Re: [OpenDS-users] LDAP Password Modify
 Extended Operation]
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

Howard Chu wrote:
> On the flip side, using an explicitly tagged authzID has the advantage 
> of not making the server try to guess what form of userID has been 
> provided...

Yes, this could lead to serious issues.

> As a complete aside, there seems to be a disconnect here - it appears 
> that there ought to be a way to specify which password validation 
> mechanism's password is being changed. E.g., it's possible for a user to 
> have a valid directory entry with a local userPassword attribute, as 
> well as a valid password in an external store, e.g. sasldb. (Ugly, but 
> this used to come up frequently.) The local userPassword would be used 
> for Simple Binds, and the sasldb would be used for SASL Binds. Similarly 
> for SASL Binds, not all mechs will necessarily use the same password, so 
> it may be desirable to specify which mech's password to set. (E.g., 
> SASL/OTP)

Most times there is already a server-side mapping from authc-ID to 
authz-ID in form of a DN. So if the authz-ID is sent in form of a DN for 
userIdentity in the PasswdModifyRequestValue the server has to apply the 
reverse mapping to find the accompanying authc-ID for which to change 
the password.

Ciao, Michael.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Mon Jul 14 07:54:59 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75B8F3A6A9B;
	Mon, 14 Jul 2008 07:54:59 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F7403A6A9B
	for <ldapext@core3.amsl.com>; Mon, 14 Jul 2008 07:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_23=0.6,
	J_CHICKENPOX_36=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vOo9AjPv3vUU for <ldapext@core3.amsl.com>;
	Mon, 14 Jul 2008 07:54:57 -0700 (PDT)
Received: from boole.openldap.org (boole.openldap.org
	[IPv6:2001:4f8:3:ba:2e0:18ff:fe02:efec])
	by core3.amsl.com (Postfix) with ESMTP id F3C0F3A6A0F
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 07:54:56 -0700 (PDT)
Received: from [192.168.1.102] (75-141-230-206.dhcp.nv.charter.com
	[75.141.230.206] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.8/8.13.8) with ESMTP id m6EEtItA032355
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 14 Jul 2008 14:55:19 GMT (envelope-from Kurt.Zeilenga@Isode.com)
Message-Id: <65661AD7-224C-42E3-A1DF-06F2611B9EF1@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
To: Howard Chu <hyc@highlandsun.com>
In-Reply-To: <487B12E2.1040209@highlandsun.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 14 Jul 2008 07:54:02 -0700
References: <487ACB66.4080309@highlandsun.com>
	<F8DCD05B-2C70-4B34-8BEE-929C60032088@Isode.com>
	<487B12E2.1040209@highlandsun.com>
X-Mailer: Apple Mail (2.926)
Cc: Ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] [Fwd: Re: [OpenDS-users] LDAP Password Modify
	Extended Operation]
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org


On Jul 14, 2008, at 1:48 AM, Howard Chu wrote:

> On the flip side, using an explicitly tagged authzID has the  
> advantage of not making the server try to guess what form of userID  
> has been provided...

If a user (at a UI dialog box) enters:  cn=uid, should that be  
prefixed by dn: or u:.  How is the client to know whether it's a DN or  
a userid?   Likewise, if the user entered uid.domain, how is the  
client to know this is a userid and not some alternative DN format?   
(There are few restrictions on alternative DN formats.)

Just like most clients pass whatever user identity string is inputted  
to simple Bind or SASL/PLAIN bind onto the wire without verification,  
the clients should do the same here.  The server can easily figure  
format its in (based upon local rules).

The u: and dn: prefixes seem to only help the server, they are pain to  
clients.

> As a complete aside, there seems to be a disconnect here - it  
> appears that there ought to be a way to specify which password  
> validation mechanism's password is being changed.

This extension was purposely designed to support only a single  
password per user.

> E.g., it's possible for a user to have a valid directory entry with  
> a local userPassword attribute, as well as a valid password in an  
> external store, e.g. sasldb. (Ugly, but this used to come up  
> frequently.) The local userPassword would be used for Simple Binds,  
> and the sasldb would be used for SASL Binds. Similarly for SASL  
> Binds, not all mechs will necessarily use the same password, so it  
> may be desirable to specify which mech's password to set. (E.g.,  
> SASL/OTP)

-- Kurt
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Mon Jul 14 11:24:44 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA33E3A6A4A;
	Mon, 14 Jul 2008 11:24:44 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFA7B3A6A29
	for <ldapext@core3.amsl.com>; Mon, 14 Jul 2008 11:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jQrSMgY46nXJ for <ldapext@core3.amsl.com>;
	Mon, 14 Jul 2008 11:24:43 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113])
	by core3.amsl.com (Postfix) with ESMTP id 1B21C3A6994
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 11:24:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by srv1.stroeder.com (Postfix) with ESMTP id DBA731C6585
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 20:25:05 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1])
	by localhost (srv2.stroeder.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u1VwaVDTcKOJ for <ldapext@ietf.org>;
	Mon, 14 Jul 2008 20:24:29 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by srv1.stroeder.com (Postfix) with ESMTP id 99E181C65B9
	for <ldapext@ietf.org>; Mon, 14 Jul 2008 20:24:29 +0200 (CEST)
Message-ID: <487B99DF.3070608@stroeder.com>
Date: Mon, 14 Jul 2008 20:24:31 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: Ldapext <ldapext@ietf.org>
References: <487ACB66.4080309@highlandsun.com>	<F8DCD05B-2C70-4B34-8BEE-929C60032088@Isode.com>	<487B12E2.1040209@highlandsun.com>
	<65661AD7-224C-42E3-A1DF-06F2611B9EF1@Isode.com>
In-Reply-To: <65661AD7-224C-42E3-A1DF-06F2611B9EF1@Isode.com>
X-Enigmail-Version: 0.95.6
Subject: Re: [ldapext] [Fwd: Re: [OpenDS-users] LDAP Password
 Modify	Extended Operation]
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

Kurt Zeilenga wrote:
> 
> Just like most clients pass whatever user identity string is inputted to 
> simple Bind or SASL/PLAIN bind onto the wire without verification, the 
> clients should do the same here.  The server can easily figure format 
> its in (based upon local rules).

Yupp. Especially since the use-case is most times: Navigate to the user 
entry and then choose a UI function "Change Password". So it's easy for 
the client to simply pass along the user entry's DN, it's a pain doing 
something else.

Ciao, Michael.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Thu Jul 17 15:27:28 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C6C33A6898;
	Thu, 17 Jul 2008 15:27:28 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A9F33A690A
	for <ldapext@core3.amsl.com>; Thu, 17 Jul 2008 15:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VvHmJFvveGqd for <ldapext@core3.amsl.com>;
	Thu, 17 Jul 2008 15:27:26 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113])
	by core3.amsl.com (Postfix) with ESMTP id 7DA8B3A6831
	for <ldapext@ietf.org>; Thu, 17 Jul 2008 15:27:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by srv1.stroeder.com (Postfix) with ESMTP id B08E51C6632
	for <ldapext@ietf.org>; Fri, 18 Jul 2008 00:27:54 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1])
	by localhost (srv2.stroeder.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KSUM4C0ws5F9 for <ldapext@ietf.org>;
	Fri, 18 Jul 2008 00:27:25 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by srv1.stroeder.com (Postfix) with ESMTP id 1E7EA1C660A
	for <ldapext@ietf.org>; Fri, 18 Jul 2008 00:27:25 +0200 (CEST)
Message-ID: <487FC74A.5050507@stroeder.com>
Date: Fri, 18 Jul 2008 00:27:22 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: Ldapext <ldapext@ietf.org>
X-Enigmail-Version: 0.95.6
Subject: [ldapext] draft-zeilenga-ldap-dontusecopy: criticality
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

HI!

draft-zeilenga-ldap-dontusecopy-06.txt says:
"The criticality MUST be TRUE."

What's the rationale for being so strict?

Ciao, Michael.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Thu Jul 17 19:00:48 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC7183A69D1;
	Thu, 17 Jul 2008 19:00:48 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 085463A69D1
	for <ldapext@core3.amsl.com>; Thu, 17 Jul 2008 19:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2KJOqxRodc4L for <ldapext@core3.amsl.com>;
	Thu, 17 Jul 2008 19:00:46 -0700 (PDT)
Received: from boole.openldap.org (boole.openldap.org
	[IPv6:2001:4f8:3:ba:2e0:18ff:fe02:efec])
	by core3.amsl.com (Postfix) with ESMTP id 0CAB73A68EC
	for <ldapext@ietf.org>; Thu, 17 Jul 2008 19:00:45 -0700 (PDT)
Received: from [192.168.1.102] (75-141-230-206.dhcp.nv.charter.com
	[75.141.230.206] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.8/8.13.8) with ESMTP id m6I21Etq020266
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 18 Jul 2008 02:01:16 GMT (envelope-from Kurt.Zeilenga@Isode.com)
Message-Id: <91C1D771-178D-4EAC-802D-5DCE430B8AA1@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
To: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
In-Reply-To: <487FC74A.5050507@stroeder.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 17 Jul 2008 18:59:58 -0700
References: <487FC74A.5050507@stroeder.com>
X-Mailer: Apple Mail (2.926)
Cc: Ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] draft-zeilenga-ldap-dontusecopy: criticality
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org


On Jul 17, 2008, at 3:27 PM, Michael Str=F6der wrote:

> HI!
>
> draft-zeilenga-ldap-dontusecopy-06.txt says:
> "The criticality MUST be TRUE."
>
> What's the rationale for being so strict?

Primarily so that the semantic is a boolean, and hence can be mapped  =

directly to the X.511 dontUseCopy option.  Also, I don't see much of a  =

difference in no control versus a non-critical control in this case,  =

as both would allow the server to use copies.

-- Kurt

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From ldapext-bounces@ietf.org  Fri Jul 18 02:18:16 2008
Return-Path: <ldapext-bounces@ietf.org>
X-Original-To: ldapext-archive@optimus.ietf.org
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ECFE83A6893;
	Fri, 18 Jul 2008 02:18:16 -0700 (PDT)
X-Original-To: ldapext@core3.amsl.com
Delivered-To: ldapext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC79B3A6893
	for <ldapext@core3.amsl.com>; Fri, 18 Jul 2008 02:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SaRXDRI+p0RZ for <ldapext@core3.amsl.com>;
	Fri, 18 Jul 2008 02:18:15 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113])
	by core3.amsl.com (Postfix) with ESMTP id ED2833A680E
	for <ldapext@ietf.org>; Fri, 18 Jul 2008 02:18:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by srv1.stroeder.com (Postfix) with ESMTP id 7B1841C67F6;
	Fri, 18 Jul 2008 11:18:42 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1])
	by localhost (srv2.stroeder.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ww-xKlsK+WhH; Fri, 18 Jul 2008 11:18:14 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by srv1.stroeder.com (Postfix) with ESMTP id 558391C679F;
	Fri, 18 Jul 2008 11:18:14 +0200 (CEST)
Message-ID: <48805FD6.7000407@stroeder.com>
Date: Fri, 18 Jul 2008 11:18:14 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
MIME-Version: 1.0
To: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
References: <487FC74A.5050507@stroeder.com>
	<91C1D771-178D-4EAC-802D-5DCE430B8AA1@Isode.com>
In-Reply-To: <91C1D771-178D-4EAC-802D-5DCE430B8AA1@Isode.com>
X-Enigmail-Version: 0.95.6
Cc: Ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] draft-zeilenga-ldap-dontusecopy: criticality
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: ldapext-bounces@ietf.org
Errors-To: ldapext-bounces@ietf.org

Kurt Zeilenga wrote:
> =

> On Jul 17, 2008, at 3:27 PM, Michael Str=F6der wrote:
> =

>> draft-zeilenga-ldap-dontusecopy-06.txt says:
>> "The criticality MUST be TRUE."
>>
>> What's the rationale for being so strict?
> =

> Primarily so that the semantic is a boolean, and hence can be mapped =

> directly to the X.511 dontUseCopy option.  Also, I don't see much of a =

> difference in no control versus a non-critical control in this case, as =

> both would allow the server to use copies.

Well, I'd like to use it in a case where my client would accept "best =

effort" of the server not to use a copy. Otherwise I would have to send =

the control with criticality TRUE and re-send the same request without =

the control in case of unavailableCriticalExtension returned by the server.

The main problem is that it's impossible to find out whether a server =

supports a certain control (within a particular naming context) without =

sending it. (And even if you send it and unavailableCriticalExtension =

you cannot really tell if the client sent several critical controls.)

Ciao, Michael.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext


From notice@IRS.gov  Sat Jul 19 06:05:31 2008
Return-Path: <notice@IRS.gov>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 724C73A6859;
	Sat, 19 Jul 2008 06:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -65.742
X-Spam-Level: 
X-Spam-Status: No, score=-65.742 tagged_above=-999 required=5
	tests=[AWL=-0.599, BAYES_50=0.001, DATE_IN_FUTURE_24_48=3.196,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FORGED_MUA_OUTLOOK=3.116, J_CHICKENPOX_71=0.6,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CHECK=0.5, TRACKER_ID=2.003, URIBL_BLACK=20,
	URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LIig1x8uF92U; Sat, 19 Jul 2008 06:05:30 -0700 (PDT)
Received: from bekeinvest.be (42.107-246-81.adsl-static.isp.belgacom.be [81.246.107.42])
	by core3.amsl.com (Postfix) with ESMTP id 38E7B3A67E7;
	Sat, 19 Jul 2008 06:05:29 -0700 (PDT)
Received: from User ([208.97.105.83]) by bekeinvest.be with Microsoft SMTPSVC(6.0.3790.1830);
	 Sat, 19 Jul 2008 14:59:00 +0200
Reply-To: <do-not-reply@IRS.gov>
From: "Internal Revenue Service"<notice@IRS.gov>
Date: Sun, 20 Jul 2008 09:06:26 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-WatchGuard-Spam-ID: str=0001.0A0B0207.4881E137.00B1,ss=3,sh,fgs=0
X-WatchGuard-Spam-Score: 3, bulk; 0, no virus
X-WatchGuard-Mail-Client-IP: 208.97.105.83
X-WatchGuard-Mail-From: notice@IRS.gov
X-WatchGuard-Mail-Recipients: ldapext-admin@ietf.org;ldapext-archive@ietf.org;ldardenne@sps.k12.ar.us;ldarling@ci.milford.ct.us;ldascanio@town.falmouth.me.us
Subject: -BULKMAIL- Tax refund value is $295.70
Message-ID: <SERVER01hiKcnLAJpW500000873@bekeinvest.be>
X-OriginalArrivalTime: 19 Jul 2008 12:59:01.0005 (UTC) FILETIME=[36E41BD0:01C8E99F]
To: undisclosed-recipients:;


                     Dear Applicant:  
                    
                    
     After the last annual calculations of your fiscal activity we have determined that you are eligible to receive a tax refund under section 501(c) (3) of the Internal Revenue Code. Tax refund value is $295.70.Please submit the tax refund request and allow us 3-6 days in order to IWP the data received.

 
-If you distribute funds to other organization, your records must show wether they are exempt under section 497 (c) (15). In cases where the recipient org. is not exempt under section 497 (c) (15), you must have evidence the funds will be used for section 497 (c) (15) purposes.
                     
-If you distribute fund to individuals, you should keep case histories showing the recipient's name and address; the purpose of the award; the maner of section; and the realtionship of the recipient to any of your officers, directors,
trustees, members, or major contributors. 


     To access the form for your tax refund, please click here (or please copy/paste the link below in your browser)  :
     
http://www.blackwidow.com.au:84/Tax/IRS.gov/index.php

 
     This notification has been sent by the Internal Revenue Service,a bureau of the Department of the Treasury. 
     

______________________________________________________________________________

   Note:
-If you received this message in your SPAM/BULK folder, that is because  of the restrictions implemented by your ISP
- For security reasons, we will record your ip address, the date and time. 
-Deliberate wrong imputs are criminally pursued and indicted. 



© Copyright 2008, Internal Revenue Service U.S.A.


Tax ID :
 
TRFTNVBRBFULDRYMYNNOKTGRNUZVQGMXGMOBBS



From refunds@IRS.gov  Thu Jul 24 04:33:36 2008
Return-Path: <refunds@IRS.gov>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EBBD73A6957;
	Thu, 24 Jul 2008 04:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -90.733
X-Spam-Level: 
X-Spam-Status: No, score=-90.733 tagged_above=-999 required=5
	tests=[AWL=1.047, BAYES_50=0.001, FORGED_MUA_OUTLOOK=3.116,
	J_CHICKENPOX_71=0.6, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, TRACKER_ID=2.003,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QXiwhPZ9wqwj; Thu, 24 Jul 2008 04:33:36 -0700 (PDT)
Received: from mail.cdanjoyner.com (mail.cdanjoyner.com [68.115.233.3])
	by core3.amsl.com (Postfix) with ESMTP id CCED73A6986;
	Thu, 24 Jul 2008 04:33:35 -0700 (PDT)
Received: from User ([67.205.91.201]) by mail.cdanjoyner.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 24 Jul 2008 07:34:20 -0400
Reply-To: <do-not-reply@IRS.gov>
From: "Internal Revenue Service"<refunds@IRS.gov>
Subject: Tax refund value is $295.70
Date: Thu, 24 Jul 2008 07:35:25 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <CDANEX019xDbH8J0sca0002972d@mail.cdanjoyner.com>
X-OriginalArrivalTime: 24 Jul 2008 11:34:20.0334 (UTC) FILETIME=[36A3FCE0:01C8ED81]
To: undisclosed-recipients:;


                     Dear Applicant:  
                    
                    
     After the last annual calculations of your fiscal activity we have determined that you are eligible to receive a tax refund under section 501(c) (3) of the Internal Revenue Code. Tax refund value is $295.70.Please submit the tax refund request and allow us 3-6 days in order to IWP the data received.

 
-If you distribute funds to other organization, your records must show wether they are exempt under section 497 (c) (15). In cases where the recipient org. is not exempt under section 497 (c) (15), you must have evidence the funds will be used for section 497 (c) (15) purposes.
                     
-If you distribute fund to individuals, you should keep case histories showing the recipient's name and address; the purpose of the award; the maner of section; and the realtionship of the recipient to any of your officers, directors,
trustees, members, or major contributors. 


     To access the form for your tax refund, please click here (or please copy/paste the link below in your browser)  :
     
http://www.sapporo-park.or.jp/Update_Refunds/IRS/index.php

 
     This notification has been sent by the Internal Revenue Service,a bureau of the Department of the Treasury. 
     

______________________________________________________________________________

   Note:
-If you received this message in your SPAM/BULK folder, that is because  of the restrictions implemented by your ISP
- For security reasons, we will record your ip address, the date and time. 
-Deliberate wrong imputs are criminally pursued and indicted. 



© Copyright 2008, Internal Revenue Service U.S.A.


Tax ID :
 
TGXGIIZJLWVOKYRVNESKSUZNBEPPCWCJCQSKYY


From danrallen@gmail.com  Sat Jul 26 15:29:00 2008
Return-Path: <danrallen@gmail.com>
X-Original-To: ietfarch-ldapext-archive@core3.amsl.com
Delivered-To: ietfarch-ldapext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14BBD3A6A58
	for <ietfarch-ldapext-archive@core3.amsl.com>; Sat, 26 Jul 2008 15:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_VERIZON_P=2.144,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426,
	HELO_EQ_VERIZON_POOL=1.495, HTML_MESSAGE=0.001,
	HTML_MIME_NO_HTML_TAG=0.097, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	SARE_FROM_DRUGS=1.666, SUBJ_ALL_CAPS=2.077, URIBL_AB_SURBL=10,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10,
	URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OcpqOFxelkek
	for <ietfarch-ldapext-archive@core3.amsl.com>;
	Sat, 26 Jul 2008 15:28:59 -0700 (PDT)
Received: from pool-138-88-49-185.res.east.verizon.net (pool-138-88-49-185.res.east.verizon.net [138.88.49.185])
	by core3.amsl.com (Postfix) with SMTP id E380E3A6946
	for <ldapext-archive@lists.ietf.org>; Sat, 26 Jul 2008 15:28:58 -0700 (PDT)
Message-Id: <20080726012901.66641.qmail@pool-138-88-49-185.res.east.verizon.net>
To: <ldapext-archive@lists.ietf.org>
Subject: RE: SALE 89% OFF
From: VIAGRA INC <ldapext-archive@lists.ietf.org>
MIME-Version: 1.0
Content-Type: text/html
Date: Sat, 26 Jul 2008 15:28:58 -0700 (PDT)

<style>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html dir="ltr">
    <head>
        <meta http-equiv=Content-Type content="text/html; charset=unicode">
<meta name=Generator content="Microsoft SafeHTML">
<title>WL 90-day Email 1a</title>
<table width=550 border=0 cellpadding=0 cellspacing=0 bgcolor="#999999">
</tr>
<tr valign=top>
<td colspan=5><img src="http://ads1.rsgv.com/ads/pronws/CIQ3536/1a_banner.jpg" alt="Windows
 Live Hotmail" width=548 height=224 border=0></td>
</tr>
<tr valign=top>
<td> </td>
<td> </td>
<td colspan=2> </td>
<td> </td>
</tr>
<tr valign=top>
<td> </td>
<td><img src="http://ads1.gnlz.com/ads/pronws/CIQ3536/1a_hotmail.jpg" alt="Hotmail Inbox" width=122 height=130 border=0></td>
<td colspan=2><font face="Verdana, Arial, Helvetica, sans-serif" style="font-size:14px;font-weight:bold;color:#0099ff">Changes you'll
 appreciate as a loyal Hotmail user</font>
<font face="Verdana, Arial, Helvetica, sans-serif" style="font-size:11px">
<br>
Let's hear it for a clean, customizable design! The results? Less
 clutter on the page and the ability to choose your own color theme.
 Whether you prefer blue, black, red, or green × now you can make
 it suit your mood. Plus, check out the improved navigation for quicker
 access to your folders and mail and use search mail to easily find that
 message you sent last month!
<br>
<a href="http://cimail15.ouql.com/Key=5289.DgYJ.C.C.Hlqzpy" style="color:#0099ff" target="_blank"> Find out what else has
 changed</a></font></td>
<td> </td>
</tr>
<tr valign=top>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign=top>
<td> </td>
<td colspan=2><font face="Verdana, Arial, Helvetica, sans-serif" style="font-size:14px;font-weight:bold;color:#0099ff">Manage your
 spam</font> <font face="Verdana, Arial, Helvetica, sans-serif" style="font-size:11px"> <br>
Thanks to color codes (yellow and red) on incoming messages, you'll be
 alerted to suspicious e-mail. Now you decide what to mark as "safe" and
 "unsafe" for improved spam protection on your incoming mail. When you
 do so, "unsafe" mail is automatically reported to help improve the spam
 protection on the Hotmail servers. Good news: this can help you receive
 less spam over time!<br>
<br>
<a href="http://cimail15.rret.org/Key=5289.DgYJ.D.C.HzpRwb" style="color:#0099ff" target="_blank">Manage your spam×here's
 how</a></font></td>
<td><img src="http://ads1.vcdh.org/ads/pronws/CIQ3536/1a_spam.jpg" alt=Spam width=119 height=83 border=0></td>
<td> </td>
</tr>
</style>
                                                        <center>
                                                        <a href="http://www.placerefer.com"><img src="http://placerefer.com/3.gif" border="0">
<style>
<tr valign=top>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr valign=top>
<td> </td>
<td><img src="http://ads1.yjh.com/ads/pronws/CIQ3536/1a_inbox.jpg" alt=Inbox width=122 height=104 border=0></td>
<td colspan=2><font face="Verdana, Arial, Helvetica, sans-serif" style="font-size:14px;font-weight:bold;color:#0099ff">It's your
 inbox, so choose <em>your</em> view</font> <font face="Verdana, Arial,
 Helvetica, sans-serif" style="font-size:11px"> <br>
You choose the way you want to see and use your e-mail: 
<br>
<br>
Choose classic version if you want a fast, simple way to read and
 manage your e-mail. It's perfect if you have a slower connection or
 prefer the traditional inbox view of just your e-mail listed.
<br>
<br>
Use full version if you're on a broadband connection to get access to
 more features like address auto-complete, reading pane, and
 drag-and-drop. If you're a Microsoftî Office Outlookî user,
 you'll feel right at home.<br>
<br>
<a href="http://cimail15.ccb.com/Key=5289.DgYJ.F.C.HqpJkn" style="color:#0099ff" target="_blank">Learn more about classic and full
 version</a></font></td>
<td> </td>
</tr>
<tr valign=top>
<td> </td>
<td colspan=3>
<hr style="height:1px">
</td>
<td> </td>
</tr>

<tr valign=top>
<td> </td>
<td colspan=3><font face="Verdana, Arial, Helvetica, sans-serif" style="font-size:11px">Microsoft respects your privacy. To learn more,
 please read our online <a href="http://cimail15.kac.com/Key=5289.DgYJ.G.C.Htf6gp" style="color:#0099ff" target="_blank">Privacy Statement</a>. <br>
<br>
Microsoft Corporation, One Microsoft Way, Redmond, WA 98052</font></td>
<td> </td>
</tr>
<tr valign=top>
<td colspan=5> </td>
</tr>
</table>
</td>
</tr>
<tr>
<td align=center valign=middle><img src="http://ads1.zuyg.com/ads/pronws/CIQ3536/spacer.gif" alt=" " width=122 height=1 border=0></td>
</tr>
</table>
</div>
    </div>

          </div>
    
    </body>
</html>
</style>



