From mailman-admin@ietf.org Fri Aug 1 09:32:09 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14406 for ; Fri, 1 Aug 2003 09:18:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iZZ5-0004GX-Sx for ldapext-archive@lists.ietf.org; Fri, 01 Aug 2003 09:03:23 -0400 Date: Fri, 01 Aug 2003 09:03:23 -0400 Message-ID: <20030801130323.29120.36799.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: ldapext-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, ldapext-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for ldapext-archive@lists.ietf.org: List Password // URL ---- -------- ldapext@ietf.org LxAC https://www1.ietf.org/mailman/options/ldapext/ldapext-archive%40lists.ietf.org From ldapext-admin@ietf.org Mon Aug 4 03:58:40 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA19210 for ; Mon, 4 Aug 2003 03:58:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jaED-00063c-M6; Mon, 04 Aug 2003 03:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jZnQ-00050y-AK for ldapext@optimus.ietf.org; Mon, 04 Aug 2003 03:30:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA18760 for ; Mon, 4 Aug 2003 03:30:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19jZnN-0006mg-00 for ldapext@ietf.org; Mon, 04 Aug 2003 03:30:17 -0400 Received: from gate1.ggr.co.uk ([193.128.25.13]) by ietf-mx with esmtp (Exim 4.12) id 19jZnM-0006ma-00 for ldapext@ietf.org; Mon, 04 Aug 2003 03:30:16 -0400 Received: (uucp@localhost) by gate1.ggr.co.uk; Mon, 4 Aug 2003 08:29:27 +0100 (BST) Received: from uk-stv-mhub1.ggr.co.uk(147.184.2.7) by gb-stv-fw3.ggr.co.uk via smap (V5.5) id xma024464; Mon, 4 Aug 03 08:28:46 +0100 Received: from ukz1096.ggr.co.uk (ukz1096.ggr.co.uk [147.184.4.13]) by mailhub.ggr.co.uk; Mon, 4 Aug 2003 08:29:04 +0100 (BST) Received: from 147.184.5.46 by ukz1098.ggr.co.uk with ESMTP (Tumbleweed SMTP Relay); Mon, 04 Aug 2003 08:29:31 +0100 Received: by ukz792.ggr.co.uk with Internet Mail Service (5.5.2654.89) id <3GYXPXT3>; Mon, 4 Aug 2003 08:28:57 +0100 Message-ID: From: "Voglmaier, Reinhard Erich" To: "'ldapext@ietf.org'" Date: Mon, 4 Aug 2003 08:28:52 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.89) X-WSS-ID: 1330D4D11103092-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ldapext] formal question Sender: ldapext-admin@ietf.org Errors-To: ldapext-admin@ietf.org X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Extension Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit This time a formal question. I see the mailing list of ldapext is working, however I did'nt find any more the working group of ldapext . Can someone point me out how's the situation ? Has the working group been closed ? If yes did another group ( ldapbis ? ) take over the work ? Thanx a lot Reinhard _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Mon Aug 4 04:22:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA19483 for ; Mon, 4 Aug 2003 04:22:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jabR-0006qY-OE; Mon, 04 Aug 2003 04:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jabA-0006qL-Ir for ldapext@optimus.ietf.org; Mon, 04 Aug 2003 04:21:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA19476 for ; Mon, 4 Aug 2003 04:21:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19jab7-00072D-00 for ldapext@ietf.org; Mon, 04 Aug 2003 04:21:41 -0400 Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se) by ietf-mx with esmtp (Exim 4.12) id 19jab6-00072A-00 for ldapext@ietf.org; Mon, 04 Aug 2003 04:21:41 -0400 Received: from it.su.se (localhost.localdomain [127.0.0.1]) by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h749I2512452; Mon, 4 Aug 2003 11:18:02 +0200 Message-ID: <3F2E24CA.4040802@it.su.se> Date: Mon, 04 Aug 2003 11:18:02 +0200 From: Leif Johansson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Voglmaier, Reinhard Erich" CC: "'ldapext@ietf.org'" Subject: Re: [ldapext] formal question References: In-Reply-To: X-Enigmail-Version: 0.76.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: ldapext-admin@ietf.org Errors-To: ldapext-admin@ietf.org X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Extension Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Voglmaier, Reinhard Erich wrote: >This time a formal question. I see the mailing list of ldapext is working, >however I did'nt find any more the working group of ldapext . Can someone >point me out how's the situation ? Has the working group been closed ? If >yes did another group ( ldapbis ? ) take over the work ? > > > At the London meeting in 2001 it was decided that ldapext was to be closed for lack of consensus on remaining issues (as I recall). The ldapbis wg does not work on extensions to ldap. Cheers Leif _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Mon Aug 4 11:12:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01167 for ; Mon, 4 Aug 2003 11:12:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jh0D-0001Xe-65; Mon, 04 Aug 2003 11:12:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19jgWb-0000WP-85 for ldapext@optimus.ietf.org; Mon, 04 Aug 2003 10:41:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00079 for ; Mon, 4 Aug 2003 10:41:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19jgB7-0001ii-00 for ldapext@ietf.org; Mon, 04 Aug 2003 10:19:13 -0400 Received: from mxout3.cac.washington.edu ([140.142.32.166]) by ietf-mx with esmtp (Exim 4.12) id 19jgB6-0001i7-00 for ldapext@ietf.org; Mon, 04 Aug 2003 10:19:12 -0400 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74EIXgG003273; Mon, 4 Aug 2003 07:18:34 -0700 Received: from [192.168.1.104] (12-231-112-60.client.attbi.com [12.231.112.60]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74EIW4A024732 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 4 Aug 2003 07:18:33 -0700 Date: Mon, 4 Aug 2003 07:18:18 -0700 (PDT) From: "RL 'Bob' Morgan" X-X-Sender: rlmorgan@localhost.localdomain To: "Voglmaier, Reinhard Erich" cc: "'ldapext@ietf.org'" Subject: Re: [ldapext] formal question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ldapext-admin@ietf.org Errors-To: ldapext-admin@ietf.org X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Extension Working Group List-Post: List-Help: List-Subscribe: , On Mon, 4 Aug 2003, Voglmaier, Reinhard Erich wrote: > This time a formal question. I see the mailing list of ldapext is > working, however I did'nt find any more the working group of ldapext . > Can someone point me out how's the situation ? Has the working group > been closed ? If yes did another group ( ldapbis ? ) take over the work > ? The work of ldapbis is described in its charter; basically this is to clarify the LDAPv3 specification set and move them toward the Draft Standard level. Proposed extensions to LDAP are now handled as individual submissions. Typically they are discussed on this mailing list while being considered by the IESG. Individual submissions can become Standards Track RFCs just like working group documents can. - RL "Bob" _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Fri Aug 8 05:39:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05591 for ; Fri, 8 Aug 2003 05:39:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l3i8-0004Ey-NV; Fri, 08 Aug 2003 05:39:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l3hK-0004Bw-S5 for ldapext@optimus.ietf.org; Fri, 08 Aug 2003 05:38:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05496 for ; Fri, 8 Aug 2003 05:38:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19l3hH-0007I3-00 for ldapext@ietf.org; Fri, 08 Aug 2003 05:38:07 -0400 Received: from prv-mail25.provo.novell.com ([137.65.81.121]) by ietf-mx with esmtp (Exim 4.12) id 19l3hG-0007HK-00 for ldapext@ietf.org; Fri, 08 Aug 2003 05:38:06 -0400 Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com with Novell_GroupWise; Fri, 08 Aug 2003 03:37:36 -0600 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.1 Date: Fri, 08 Aug 2003 03:37:17 -0600 From: "Vithalprasad Gaitonde" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: [ldapext] LDAP transactions Sender: ldapext-admin@ietf.org Errors-To: ldapext-admin@ietf.org X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Extension Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Kurt, I think the server may want to have a sizelimit on the no of transactions that a client can send within a transaction for security reasons, administrative limit or internal implementation limit. So, may be we should allow the server to return createGroupValue (which holds the sizelimit) in the createGroupingResponse in response to createGroupingRequest with transactionGroupingType as the value. Comments ? Prasad _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Tue Aug 12 22:53:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07709 for ; Tue, 12 Aug 2003 22:53:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mlkz-0007dw-1q; Tue, 12 Aug 2003 22:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19mlkF-0007da-MN for ldapext@optimus.ietf.org; Tue, 12 Aug 2003 22:52:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07666 for ; Tue, 12 Aug 2003 22:52:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19mlkC-0005XF-00 for ldapext@ietf.org; Tue, 12 Aug 2003 22:52:12 -0400 Received: from gunsmoke.adacel.com.au ([210.11.130.7] helo=adacel.com) by ietf-mx with esmtp (Exim 4.12) id 19mlkA-0005XB-00 for ldapext@ietf.org; Tue, 12 Aug 2003 22:52:11 -0400 Received: from nexus.adacel.com (Not Verified[10.32.240.1]) by adacel.com with NetIQ MailMarshal (v5.5.3.16) id ; Wed, 13 Aug 2003 12:47:08 +1000 Received: (qmail 28520 invoked from network); 13 Aug 2003 02:45:46 -0000 Received: from unknown (HELO osmium) (10.32.24.165) by nexus.adacel.com with SMTP; 13 Aug 2003 02:45:46 -0000 Reply-To: From: "Steven Legg" To: Cc: "'OSI Directory List'" , Date: Wed, 13 Aug 2003 12:51:34 +1000 Message-ID: <001e01c36145$cf53f710$a518200a@osmium.mtwav.adacel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [ldapext] The XML Enabled Directory - Mailing List Sender: ldapext-admin@ietf.org Errors-To: ldapext-admin@ietf.org X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Extension Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, Some of you will have already noticed that I recently published the first batch of a series of Internet drafts that describe an XML rendition of LDAP and X.500 called the XML Enabled Directory (XED). For those who are interested, the roadmap document is the best place to start reading as it puts the other documents into context: http://www.ietf.org/internet-drafts/draft-legg-xed-roadmap-00.txt Paraphrasing the roadmap's introduction: The XML Enabled Directory leverages existing LDAP and X.500 directory technology to create a directory service that stores, manages and transmits XML format data, while maintaining interoperability with LDAP clients, X.500 DUAs and DSAs. The main features of XED are: - semantically equivalent XML renditions of existing directory protocols, - XML renditions of directory data, - the ability to accept at run time, user defined attribute syntaxes specified in a variety of XML schema languages, - the ability to perform filter matching on the parts of XML format attribute values, - the flexibility for implementors to develop XED clients using only their favoured XML schema language. I have set up a mailing list, xeddev@adacel.com, to hold discussions on the XED Internet drafts. Purely editorial comments can be sent straight to me. To subscribe to the list send a message to xeddev-request@adacel.com with the keyword subscribe in the body. The list only accepts postings by subscribers. Regards, Steven _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext