From mhinckley@novell.com Thu Apr 7 15:09:28 2011 Return-Path: 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 641103A6A2B for ; Thu, 7 Apr 2011 15:09:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.739 X-Spam-Level: X-Spam-Status: No, score=-100.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, 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 VDYQzWPxes7q for ; Thu, 7 Apr 2011 15:09:27 -0700 (PDT) Received: from novprvoes0310.provo.novell.com (novprvoes0310.provo.novell.com [137.65.248.74]) by core3.amsl.com (Postfix) with ESMTP id D61DB3A6A27 for ; Thu, 7 Apr 2011 15:09:27 -0700 (PDT) Received: from INET-PRV-MTA by novprvoes0310.provo.novell.com with Novell_GroupWise; Thu, 07 Apr 2011 16:11:06 -0600 Message-Id: <4D9DE21802000016006ACC6A@novprvoes0310.provo.novell.com> X-Mailer: Novell GroupWise Internet Agent 8.0.2 Date: Thu, 07 Apr 2011 16:11:04 -0600 From: "Mark Hinckley" To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__PartE5C93B68.0__=" Subject: [ldapext] Schema OID definition limits X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2011 22:09:28 -0000 --=__PartE5C93B68.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Is there a limit defined in the LDAP RFCs anywhere for the length of the = OID value for a schema definition, for example inetOrgPerson is 2.16.840.1.= 113730.3.2.2, whereas organization is 2.5.6.4. Is there a maximum length = defined for how long that digit string can be for custom schema? For = example, should 1.2.840.112233.1.1234.5678.12345.1234.123456.1234 be = considered legal? =20 Thanks, Mark Hinckley =20 =20 --=__PartE5C93B68.0__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Description: HTML

Is there a limit defined in the LDAP RFCs anywhere for the length of = the OID value for a schema definition, for example inetOrgPerson is = 2.16.840.1.113730.3.2.2, whereas organization is 2.5.6.4. Is there a = maximum length defined for how long that digit string can be for custom = schema? For example, should 1.2.840.112233.1.1234.5678.12345.123= 4.123456.1234 be considered legal?

Thanks,

Mark Hinckley

--=__PartE5C93B68.0__=-- From hbf@ulrik.uio.no Thu Apr 7 15:49:51 2011 Return-Path: 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 DF3703A69B1 for ; Thu, 7 Apr 2011 15:49:51 -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 K1ASDxGuNi4q for ; Thu, 7 Apr 2011 15:49:51 -0700 (PDT) Received: from mail-out1.uio.no (mail-out1.uio.no [IPv6:2001:700:100:10::57]) by core3.amsl.com (Postfix) with ESMTP id D9C4E3A6965 for ; Thu, 7 Apr 2011 15:49:50 -0700 (PDT) Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out1.uio.no with esmtp (Exim 4.75) (envelope-from ) id 1Q7y33-0002ut-Jq; Fri, 08 Apr 2011 00:51:33 +0200 Received: from bombur.uio.no ([129.240.6.233]) by mail-mx3.uio.no with esmtp (Exim 4.72) (envelope-from ) id 1Q7y33-0002cT-7U; Fri, 08 Apr 2011 00:51:33 +0200 Received: from hbf by bombur.uio.no with local (Exim 4.72) (envelope-from ) id 1Q7y32-0002wD-Mh; Fri, 08 Apr 2011 00:51:32 +0200 From: Hallvard B Furuseth MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: Fri, 8 Apr 2011 00:51:32 +0200 To: "Mark Hinckley" In-Reply-To: <4D9DE21802000016006ACC6A@novprvoes0310.provo.novell.com> References: <4D9DE21802000016006ACC6A@novprvoes0310.provo.novell.com> X-Mailer: VM 7.18 under Emacs 22.2.1 Sender: Hallvard Breien Furuseth X-UiO-Ratelimit-Test: rcpts/h 2 msgs/h 1 sum rcpts/h 3 sum msgs/h 1 total rcpts 1180 max rcpts/h 17 ratelimit 0 X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, T_RP_MATCHES_RCVD=-0.01, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 8FB97F7E3D3493CB81C425820BAC07AB7E781341 X-UiO-SPAM-Test: remote_host: 129.240.6.233 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 502 max/h 5 blacklist 0 greylist 0 ratelimit 0 Cc: ldapext@ietf.org Subject: Re: [ldapext] Schema OID definition limits X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2011 22:53:30 -0000 Mark Hinckley writes: > Is there a limit defined in the LDAP RFCs anywhere for the length of > the OID value for a schema definition, for example inetOrgPerson is > 2.16.840.1.113730.3.2.2, whereas organization is 2.5.6.4. I don't think so. Object identifiers are defined by ASN.1, the LDAP RFCs just refer to it. > Is there a > maximum length defined for how long that digit string can be for > custom schema? For example, should > 1.2.840.112233.1.1234.5678.12345.1234.123456.1234 be considered legal? That's a valid OID. There are some limits: 1st component must be <= 2. If 1st comp. <= 1, then 2nd component must be < 40. That's due to the ASN.1/BER representation of OIDs, which represents the first two components as one number 40*<1st component> + <2nd component>. Finally, your OIDs might meet a quick-and-dirty implementation which represents OID components as fixed-size machine integers. So it may be advisable to stick to components < 2**31, and 2nd component < 2**31/40. Or nowadays, perhaps I should be saying 63 instead of 31 bits. (The final bit would be for the sign, or for a "this is the last OID component" flag.) -- Hallvard From hbf@ulrik.uio.no Thu Apr 7 15:57:26 2011 Return-Path: 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 83EDB28C18B for ; Thu, 7 Apr 2011 15:57:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.969 X-Spam-Level: X-Spam-Status: No, score=-2.969 tagged_above=-999 required=5 tests=[AWL=-0.369, 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 a5wBJKboUwv0 for ; Thu, 7 Apr 2011 15:57:26 -0700 (PDT) Received: from mail-out1.uio.no (mail-out1.uio.no [IPv6:2001:700:100:10::57]) by core3.amsl.com (Postfix) with ESMTP id B62D628C184 for ; Thu, 7 Apr 2011 15:57:25 -0700 (PDT) Received: from mail-mx1.uio.no ([129.240.10.29]) by mail-out1.uio.no with esmtp (Exim 4.75) (envelope-from ) id 1Q7yAQ-0004ws-4i; Fri, 08 Apr 2011 00:59:10 +0200 Received: from bombur.uio.no ([129.240.6.233]) by mail-mx1.uio.no with esmtp (Exim 4.72) (envelope-from ) id 1Q7yAP-0006TD-PL; Fri, 08 Apr 2011 00:59:10 +0200 Received: from hbf by bombur.uio.no with local (Exim 4.72) (envelope-from ) id 1Q7yAP-00032c-OA; Fri, 08 Apr 2011 00:59:09 +0200 From: Hallvard B Furuseth MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: Fri, 8 Apr 2011 00:59:09 +0200 To: Mark Hinckley In-Reply-To: References: <4D9DE21802000016006ACC6A@novprvoes0310.provo.novell.com> X-Mailer: VM 7.18 under Emacs 22.2.1 Sender: Hallvard Breien Furuseth X-UiO-Ratelimit-Test: rcpts/h 6 msgs/h 3 sum rcpts/h 7 sum msgs/h 3 total rcpts 1184 max rcpts/h 17 ratelimit 0 X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, T_RP_MATCHES_RCVD=-0.01, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 94E7DC97D21DC676608A8413D6383EF1410031E3 X-UiO-SPAM-Test: remote_host: 129.240.6.233 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 504 max/h 5 blacklist 0 greylist 0 ratelimit 0 Cc: ldapext@ietf.org Subject: Re: [ldapext] Schema OID definition limits X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2011 22:57:26 -0000 I wrote: >Mark Hinckley writes: >> Is there a limit defined in the LDAP RFCs anywhere for the length of >> the OID value for a schema definition, for example inetOrgPerson is >> 2.16.840.1.113730.3.2.2, whereas organization is 2.5.6.4. > > I don't think so. Object identifiers are defined by ASN.1, the LDAP > RFCs just refer to it. Whoops - poorly placed sentence. To clarify: Nor do I know of limitations in ASN.1:-) > Finally, your OIDs might meet a quick-and-dirty implementation which > represents OID components as fixed-size machine integers. So it may be > advisable to stick to components < 2**31, and 2nd component < 2**31/40. > Or nowadays, perhaps I should be saying 63 instead of 31 bits. (The > final bit would be for the sign, or for a "this is the last OID > component" flag.) For the positive sign, I should have said. For languages or code which use signed integers. -- Hallvard From michael@stroeder.com Sat Apr 9 05:00:13 2011 Return-Path: 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 9371F3A6A91 for ; Sat, 9 Apr 2011 05:00:13 -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 7bXWn-nRhixn for ; Sat, 9 Apr 2011 05:00:11 -0700 (PDT) Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) by core3.amsl.com (Postfix) with ESMTP id 7B47D3A6A45 for ; Sat, 9 Apr 2011 05:00:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by srv1.stroeder.com (Postfix) with ESMTP id 37C444E0E3 for ; Sat, 9 Apr 2011 14:01:53 +0200 (CEST) X-Virus-Scanned: amavisd-new at stroeder.com Received: from srv1.stroeder.com ([127.0.0.1]) by localhost (srv1.stroeder.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X73u28qfQ4Dl for ; Sat, 9 Apr 2011 14:01:49 +0200 (CEST) Received: from [10.1.0.2] (unknown [10.1.0.2]) by srv1.stroeder.com (Postfix) with ESMTP id 0408B4E0C7 for ; Sat, 9 Apr 2011 14:01:47 +0200 (CEST) Message-ID: <4DA04AAE.4000702@stroeder.com> Date: Sat, 09 Apr 2011 14:01:50 +0200 From: =?ISO-8859-15?Q?Michael_Str=F6der?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.18) Gecko/20110320 Lightning/1.0b1 SeaMonkey/2.0.13 MIME-Version: 1.0 To: ldapext X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Subject: [ldapext] Fwd: [ldap] LDAPCon 2011 Call for Papers X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2011 12:00:13 -0000 Maybe some of the subscribers are interested in this. Ciao, Michael. -------- Original Message -------- Subject: [ldap] LDAPCon 2011 Call for Papers Date: Fri, 08 Apr 2011 14:46:47 +0200 From: Peter Gietz To: ldap@umich.edu With the usual apologies. The 3rd Edition of the International Conference on LDAP (LDAPCon 2011[1]) will be held on October, 10-11, 2011 in Heidelberg, Germany. A Call For Papers[2] has been raised and the Program Committee asks you to submit abstracts by July 8th. The International Conference on LDAP is a technical forum for IT professionals interested in LDAP and related topics like directory servers, directory management applications, directory integration, identity and access management, and meta directories. It focuses on implementation and integration of LDAP servers and LDAP-enabled client applications. The event will bring together vendors, developers, active and prospective LDAP practitioners to share their experiences about deployment strategies, service operations, interoperability, discuss LDAP usage in new projects and learn about upcoming trends and developments. The 1st LDAPCon[3] was held in September 2007 in Germany, the 2nd LDAPCon[4] was held in September 2009 in Portland, Oregon, USA (Some pictures from LDAPCon 2007 [5] and a nice summary of LDAPCon 2009 [6]) So if you're involved with LDAP in interesting projects and you want to share your experiences, please check the Call For Papers and submit a proposal. Best, Peter [1]: http://www.ldapcon.org [2]: http://www.daasi.de/ldapcon2011/index.php?site=cfp [3]: http://www.guug.de/veranstaltungen/ldapcon2007/index.html [4]: http://www.symas.com/ldapcon2009 [5]: http://www.flickr.com/photos/ludovic_p/sets/72157601937159198/detail/ [6]: http://blogs.sun.com/Ludo/entry/ldapcon_2009_summary -- _______________________________________________________________________ Peter Gietz (CEO) DAASI International GmbH phone: +49 7071 407109-0 Europaplatz 3 Fax: +49 7071 407109-9 D-72074 Tübingen mail: peter.gietz@daasi.de Germany Web: www.daasi.de DAASI International GmbH, Tübingen Geschäftsführer Peter Gietz, Amtsgericht Stuttgart HRB 382175 Directory Applications for Advanced Security and Information Management _______________________________________________________________________