From mailman-admin@ietf.org Sun Jun 1 10:29:12 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12788 for ; Sun, 1 Jun 2003 10:29:12 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51ESmB08933 for ; Sun, 1 Jun 2003 10:28:48 -0400 Date: Sun, 01 Jun 2003 10:28:48 -0400 Message-ID: <20030601142848.11734.77158.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 Jun 9 07:58:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29200 for ; Mon, 9 Jun 2003 07:58:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59BlvB26374; Mon, 9 Jun 2003 07:47:57 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59Bj8B26275 for ; Mon, 9 Jun 2003 07:45:08 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28541; Mon, 9 Jun 2003 07:45:06 -0400 (EDT) Message-Id: <200306091145.HAA28541@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ldapext@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 09 Jun 2003 07:45:06 -0400 Subject: [ldapext] I-D ACTION:draft-zeilenga-ldap-user-schema-mr-00.txt 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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : LDAP: Additional Matching Rules Author(s) : K. Zeilenga Filename : draft-zeilenga-ldap-user-schema-mr-00.txt Pages : 10 Date : 2003-6-6 This document provides a collection of matching rules for use with the Lightweight Directory Access Protocol (LDAP). As these matching rules are simple adaptations of matching rules specified for use with the X.500 Directory, most are already in wide use. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-user-schema-mr-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-zeilenga-ldap-user-schema-mr-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-zeilenga-ldap-user-schema-mr-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-6133103.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-zeilenga-ldap-user-schema-mr-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-zeilenga-ldap-user-schema-mr-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-6133103.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Wed Jun 18 17:14:22 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 RAA00466 for ; Wed, 18 Jun 2003 17:14:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Sk57-00069i-C0; Wed, 18 Jun 2003 17:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Sk0m-0005nD-Rl for ldapext@optimus.ietf.org; Wed, 18 Jun 2003 16:58:32 -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 QAA29491 for ; Wed, 18 Jun 2003 16:58:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SjyV-00026b-00 for ldapext@ietf.org; Wed, 18 Jun 2003 16:56:11 -0400 Received: from prv-mail20.provo.novell.com ([137.65.81.122]) by ietf-mx with esmtp (Exim 4.12) id 19SjyV-000262-00 for ldapext@ietf.org; Wed, 18 Jun 2003 16:56:11 -0400 Received: from INET-PRV-MTA by prv-mail20.provo.novell.com with Novell_GroupWise; Wed, 18 Jun 2003 14:58:00 -0600 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.1 Date: Wed, 18 Jun 2003 14:56:34 -0600 From: "Jim Sermersheim" To: Cc: "Steve McLain" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: [ldapext] modifyDN.deleteOldRDN and name forms 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 All, It appears that X.501 allows name forms to specify attributes that are not allowed by the object class definition that the name form is used for. "The RDN attribute (or attributes) need not be chosen from the list of permitted attributes of the structural object class as specified in its structural or alias object class definition." a) Does this also apply to DITContentRules? Meaning, if an attribute is not allowed on the object class definition, or allowed by the DIT Content Rule, can it be specified in the name form? b) If yes, can objects be instantiated with names that use those attributes? c) If yes, what happens when modifyDN.deleteOldRDN is set to false when renaming one of these attributes? I can't find answers to a, b, or c, in the X.500 series. Jim _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Tue Jun 24 06:43: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 ESMTP id GAA10432 for ; Tue, 24 Jun 2003 06:43:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UlGP-00052y-2A; Tue, 24 Jun 2003 06:43:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UlFq-00052k-8L for ldapext@optimus.ietf.org; Tue, 24 Jun 2003 06:42:26 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10368; Tue, 24 Jun 2003 06:42:21 -0400 (EDT) Message-Id: <200306241042.GAA10368@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ldapext@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 24 Jun 2003 06:42:21 -0400 Subject: [ldapext] I-D ACTION:draft-zeilenga-ldap-readentry-00.txt 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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : LDAP Read Entry Controls Author(s) : K. Zeilenga Filename : draft-zeilenga-ldap-readentry-00.txt Pages : 8 Date : 2003-6-23 This specification describes controls which can be attached to a Lightweight Directory Access Protocol (LDAP) update request to obtain copies of the target entry before and/or after the requested update is applied. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-readentry-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-zeilenga-ldap-readentry-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-zeilenga-ldap-readentry-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-23142153.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-zeilenga-ldap-readentry-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-zeilenga-ldap-readentry-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-23142153.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Tue Jun 24 13:30: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 NAA25890 for ; Tue, 24 Jun 2003 13:30:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UrcH-0004sq-3C; Tue, 24 Jun 2003 13:30:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UrbR-0004rp-Ck for ldapext@optimus.ietf.org; Tue, 24 Jun 2003 13:29:09 -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 NAA25799 for ; Tue, 24 Jun 2003 13:29:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UrbP-0004dr-00 for ldapext@ietf.org; Tue, 24 Jun 2003 13:29:07 -0400 Received: from router.boolean.net ([198.144.206.49] helo=pretender.boolean.net ident=root) by ietf-mx with esmtp (Exim 4.12) id 19UrbD-0004dO-00 for ldapext@ietf.org; Tue, 24 Jun 2003 13:28:55 -0400 Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1]) by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h5OHS9c6087094 for ; Tue, 24 Jun 2003 17:28:09 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <5.2.0.9.0.20030624101215.01a79c70@127.0.0.1> X-Sender: kurt@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 24 Jun 2003 10:25:09 -0700 To: ldapext@ietf.org From: "Kurt D. Zeilenga" Subject: Re: [ldapext] I-D ACTION:draft-zeilenga-ldap-readentry-00.txt In-Reply-To: <200306241042.GAA10368@ietf.org> 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: , In this I-D, I've detailed controls that a client can use to read the target entry of an update operation before and/or after the update is applied. In my last minute rush to submit this, I made a cut-n-paste from the pre-read to the post-read section and failed to make all of the appropriate edits to the pasted text. The post-read request control is appropriate for add not delete and returns the entry after the update not before it. That is, the text should be updated as indicated by this unified diffs of the post-read section: -This control is appropriate for the modifyRequest, -delRequest, and modDNRequest LDAP messages. +This control is appropriate for the addRequest, +modifyRequest, and modDNRequest LDAP messages. and: When the request control is attached to an appropriate update LDAP request, the control requests the return of a copy of target entry -prior to the application of the update. +after the application of the update. These errors will be corrected in the next revision (to be submitted immediately after IETF#57). Kurt PS: Thanks to Andrew for pointing this error out to me. _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Thu Jun 26 08:09: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 IAA17274 for ; Thu, 26 Jun 2003 08:09: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 19VVYi-0000a0-T2; Thu, 26 Jun 2003 08:09:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVYU-0000ZZ-HV for ldapext@optimus.ietf.org; Thu, 26 Jun 2003 08:08:46 -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 IAA17247 for ; Thu, 26 Jun 2003 08:08:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VVYT-0007lX-00 for ldapext@ietf.org; Thu, 26 Jun 2003 08:08:45 -0400 Received: from goose.ehsco.com ([207.65.203.98]) by ietf-mx with esmtp (Exim 4.12) id 19VVYI-0007lK-00 for ldapext@ietf.org; Thu, 26 Jun 2003 08:08:34 -0400 Received: from [207.65.3.26] (account ehall HELO ehsco.com) by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 243331 for ldapext@ietf.org; Thu, 26 Jun 2003 07:07:43 -0500 Message-ID: <3EFAE220.2010906@ehsco.com> Date: Thu, 26 Jun 2003 07:08:00 -0500 From: "Eric A. Hall" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-US,en MIME-Version: 1.0 To: ldapext@ietf.org Content-Type: multipart/mixed; boundary="------------050905060205090308010808" Subject: [ldapext] [Fwd: I-D ACTION:draft-hall-ldap-idn-00.txt] 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: , This is a multi-part message in MIME format. --------------050905060205090308010808 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit FYI. Feedback appreciated. I really believe that something like this is needed to fully accomodate IDNs in LDAP. The use of client-side transformations are extremely fragile and prone to errors (eg, copying the data from one LDAP application and pasting it in with another). I also think that nobody here really wants to see codec output embedded in the namespace for years to come, but that's the only predictable outcome from using client transformations. We need to have UTF-8 elements for IDNs in order for them to work reliably. The following issues in particular are still unresolved. 7. Open Issues Should a structured domain name sequence be formally defined, with the inetDomainComponent and inetEmail attributes formally incorporating that sequence? Should the inetEmail attribute be formally defined as structured, with the appropriate ASN.1? Should there be extensible matching filters that accept non- normalized input, normalize it, and then search for matching elements and/or attributes? Thanks -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/ --------------050905060205090308010808 Content-Type: message/rfc822; name="I-D ACTION:draft-hall-ldap-idn-00.txt" Content-Disposition: attachment; filename="I-D ACTION:draft-hall-ldap-idn-00.txt" Return-Path: Received: from asgard.ietf.org ([132.151.6.40] verified) by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6) with ESMTP id 243241 for lists@ehsco.com; Wed, 25 Jun 2003 19:33:47 -0500 Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19VBd6-0007xC-SA for ietf-announce-list@asgard.ietf.org; Wed, 25 Jun 2003 10:52:12 -0400 Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19VBd6-0007x6-NY for all-ietf@asgard.ietf.org; Wed, 25 Jun 2003 10:52:12 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12742 for ; Wed, 25 Jun 2003 10:52:10 -0400 (EDT) Message-Id: <200306251452.KAA12742@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-hall-ldap-idn-00.txt Date: Wed, 25 Jun 2003 10:52:10 -0400 Sender: owner-ietf-announce@ietf.org Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : LDAP Schema Extensions for Internationalized Domain Names Author(s) : E. Hall Filename : draft-hall-ldap-idn-00.txt Pages : 16 Date : 2003-6-24 This document defines schema and behavioral rules which are necessary to fully accommodate the use of internationalized domain names as UTF-8 sequences in LDAP. Specifically, this document defines an internationalized domain component attribute, email address attribute, URI syntax, and several related object classes, and also discusses their usage considerations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hall-ldap-idn-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-hall-ldap-idn-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-hall-ldap-idn-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-25103200.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-hall-ldap-idn-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-hall-ldap-idn-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-25103200.I-D@ietf.org> --OtherAccess-- --NextPart-- --------------050905060205090308010808-- _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Sat Jun 28 14:10:33 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 OAA28688 for ; Sat, 28 Jun 2003 14:10:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WK9B-0003HW-Pl; Sat, 28 Jun 2003 14:10:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WK8p-0003HC-OF for ldapext@optimus.ietf.org; Sat, 28 Jun 2003 14:09:54 -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 OAA28657 for ; Sat, 28 Jun 2003 14:09:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WK8Y-0004gp-00 for ldapext@ietf.org; Sat, 28 Jun 2003 14:09:22 -0400 Received: from pat.uio.no ([129.240.130.16] ident=7411) by ietf-mx with esmtp (Exim 4.12) id 19WK8N-0004gg-00 for ldapext@ietf.org; Sat, 28 Jun 2003 14:09:11 -0400 Received: from mail-mx3.uio.no ([129.240.10.44]) by pat.uio.no with esmtp (Exim 2.12 #7) id 19WK80-0005xo-00 for ldapext@ietf.org; Sat, 28 Jun 2003 20:08:48 +0200 Received: from [129.240.201.2] (helo=goggins.uio.no) by mail-mx3.uio.no with esmtp (Exim 4.14) id 19WK7y-0001Hu-J2 for ldapext@ietf.org; Sat, 28 Jun 2003 20:08:46 +0200 Received: from bombur.uio.no ([129.240.186.42]) by goggins.uio.no with esmtp (Exim 2.12 #7) id 19WK7y-0007dV-00 for ldapext@ietf.org; Sat, 28 Jun 2003 20:08:46 +0200 Received: from hbf by bombur.uio.no with local (Exim 2.12 #7) id 19WK7x-0006VZ-00 for ldapext@ietf.org; Sat, 28 Jun 2003 20:08:45 +0200 From: Hallvard B Furuseth Message-Id: To: ldapext@ietf.org Date: Sat, 28 Jun 2003 20:08:45 +0200 X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning. X-UiO-MailScanner: No virus found Subject: [ldapext] UUIDs should be case-insensitive 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: , draft-zeilenga-ldap-uuid-00.txt says 2.2 'uuidMatch' Matching Rule The 'uuidMatch' matching rule compares an asserted UUID with a stored UUID for equality. Its semantics are same as octetStringMatch However, http://www.opengroup.org/onlinepubs/9629399/apdxa.htm says String Representation of UUIDs The hexadecimal values a to f (...) are case insensitive on input. So it seems to me the UUID matching rule should be caseIgnoreIA5Match, and thus the the syntax should be IA5 String. -- Hallvard _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Sat Jun 28 14:19: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 ESMTP id OAA28810 for ; Sat, 28 Jun 2003 14:19: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 19WKHt-0003dX-8H; Sat, 28 Jun 2003 14:19:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WKHO-0003dH-VK for ldapext@optimus.ietf.org; Sat, 28 Jun 2003 14:18:30 -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 OAA28793 for ; Sat, 28 Jun 2003 14:18:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WKH7-0004in-00 for ldapext@ietf.org; Sat, 28 Jun 2003 14:18:13 -0400 Received: from router.boolean.net ([198.144.206.49] helo=pretender.boolean.net ident=root) by ietf-mx with esmtp (Exim 4.12) id 19WKGw-0004ij-00 for ldapext@ietf.org; Sat, 28 Jun 2003 14:18:02 -0400 Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1]) by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h5SIHfc6030643; Sat, 28 Jun 2003 18:17:42 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <5.2.0.9.0.20030628111258.01bc9eb8@127.0.0.1> X-Sender: kurt@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sat, 28 Jun 2003 11:14:41 -0700 To: Hallvard B Furuseth From: "Kurt D. Zeilenga" Subject: Re: [ldapext] UUIDs should be case-insensitive Cc: ldapext@ietf.org In-Reply-To: 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: , At 11:08 AM 6/28/2003, Hallvard B Furuseth wrote: >draft-zeilenga-ldap-uuid-00.txt says > > 2.2 'uuidMatch' Matching Rule > > The 'uuidMatch' matching rule compares an asserted UUID with a stored > UUID for equality. Its semantics are same as octetStringMatch > >However, http://www.opengroup.org/onlinepubs/9629399/apdxa.htm says > > String Representation of UUIDs > > The hexadecimal values a to f (...) are case insensitive on input. > >So it seems to me the UUID matching rule should be caseIgnoreIA5Match, >and thus the the syntax should be IA5 String. Note that comparison is between UUIDs, not the string representations of the UUIDs, hence octetStringMatch is the correct rule. Kurt _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext From ldapext-admin@ietf.org Sat Jun 28 14:39: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 ESMTP id OAA29306 for ; Sat, 28 Jun 2003 14:39: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 19WKbF-0004l7-08; Sat, 28 Jun 2003 14:39:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WKbB-0004kt-IW for ldapext@optimus.ietf.org; Sat, 28 Jun 2003 14:38:57 -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 OAA29298 for ; Sat, 28 Jun 2003 14:38:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WKb8-0004pS-00 for ldapext@ietf.org; Sat, 28 Jun 2003 14:38:55 -0400 Received: from pat.uio.no ([129.240.130.16] ident=7411) by ietf-mx with esmtp (Exim 4.12) id 19WKay-0004pN-00 for ldapext@ietf.org; Sat, 28 Jun 2003 14:38:44 -0400 Received: from mail-mx1.uio.no ([129.240.10.29]) by pat.uio.no with esmtp (Exim 2.12 #7) id 19WKal-00007y-00; Sat, 28 Jun 2003 20:38:31 +0200 Received: from [129.240.130.14] (helo=mons.uio.no) by mail-mx1.uio.no with esmtp (Exim 4.14) id 19WKah-0006AE-OL; Sat, 28 Jun 2003 20:38:27 +0200 Received: from bombur.uio.no ([129.240.186.42]) by mons.uio.no with esmtp (Exim 2.12 #7) id 19WKah-0002ZZ-00; Sat, 28 Jun 2003 20:38:27 +0200 Received: from hbf by bombur.uio.no with local (Exim 2.12 #7) id 19WKah-0006a2-00; Sat, 28 Jun 2003 20:38:27 +0200 From: Hallvard B Furuseth Message-Id: To: "Kurt D. Zeilenga" Cc: ldapext@ietf.org Subject: Re: [ldapext] UUIDs should be case-insensitive In-Reply-To: <5.2.0.9.0.20030628111258.01bc9eb8@127.0.0.1> References: <5.2.0.9.0.20030628111258.01bc9eb8@127.0.0.1> X-Mailer: VM 6.37 under Emacs 19.34.1 Date: Sat, 28 Jun 2003 20:38:27 +0200 X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning. X-UiO-MailScanner: No virus found 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: , > Note that comparison is between UUIDs, not the string representations > of the UUIDs, hence octetStringMatch is the correct rule. Whoops. Good point. -- Hallvard _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext