From exim@www1.ietf.org Fri Apr 2 00:01:21 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09340 for ; Fri, 2 Apr 2004 00:01:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Dz5-0000ub-RJ for ldap-dir-archive@odin.ietf.org; Thu, 01 Apr 2004 21:00:39 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3220dkc003501 for ldap-dir-archive@odin.ietf.org; Thu, 1 Apr 2004 21:00:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9CJj-0006X4-KO for ldap-dir-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 19:13:51 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12461 for ; Thu, 1 Apr 2004 19:13:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9CJi-0007bf-00 for ldap-dir-web-archive@ietf.org; Thu, 01 Apr 2004 19:13:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9CIW-0007LF-00 for ldap-dir-web-archive@ietf.org; Thu, 01 Apr 2004 19:12:37 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B9CHQ-00077m-00 for ldap-dir-web-archive@ietf.org; Thu, 01 Apr 2004 19:11:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B99df-0001g8-GB for ldap-dir-web-archive@ietf.org; Thu, 01 Apr 2004 16:22:15 -0500 Date: Thu, 01 Apr 2004 11:23:20 -0500 Message-ID: <20040401162320.11029.55797.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: ldap-dir-web-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 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,DATE_IN_PAST_03_06, NO_REAL_NAME autolearn=no version=2.60 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, ldap-dir-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 ldap-dir-web-archive@ietf.org: List Password // URL ---- -------- ldap-dir@ietf.org bomoek https://www1.ietf.org/mailman/options/ldap-dir/ldap-dir-web-archive%40ietf.org From exim@www1.ietf.org Mon Apr 5 16:04:02 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03384 for ; Mon, 5 Apr 2004 16:04:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAaJi-00033w-Gg for ldap-dir-archive@odin.ietf.org; Mon, 05 Apr 2004 16:03:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i35K3YFU011773 for ldap-dir-archive@odin.ietf.org; Mon, 5 Apr 2004 16:03:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAaJi-00033o-2p for ldap-dir-web-archive@optimus.ietf.org; Mon, 05 Apr 2004 16:03:34 -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 QAA03224 for ; Mon, 5 Apr 2004 16:03:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAaJg-0004QU-00 for ldap-dir-web-archive@ietf.org; Mon, 05 Apr 2004 16:03:32 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAa8b-0002Wd-00 for ldap-dir-web-archive@ietf.org; Mon, 05 Apr 2004 15:52:29 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BAZkQ-0007mk-00 for ldap-dir-web-archive@ietf.org; Mon, 05 Apr 2004 15:27:06 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BAZhS-0002u8-Ao for ldap-dir-web-archive@ietf.org; Mon, 05 Apr 2004 15:24:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAZhR-000878-Dd; Mon, 05 Apr 2004 15:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAYyp-0000QY-BD for ldap-dir@optimus.ietf.org; Mon, 05 Apr 2004 14:37:55 -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 OAA23448 for ; Mon, 5 Apr 2004 14:37:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAYym-0001eT-00 for ldap-dir@ietf.org; Mon, 05 Apr 2004 14:37:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAYg9-000746-00 for ldap-dir@ietf.org; Mon, 05 Apr 2004 14:19:00 -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 1BAYNq-0004Yf-00 for ldap-dir@ietf.org; Mon, 05 Apr 2004 13:59:43 -0400 Received: from gypsy.OpenLDAP.org (kurt@localhost [127.0.0.1]) by pretender.boolean.net (8.12.10/8.12.10) with ESMTP id i35HxZMs009980; Mon, 5 Apr 2004 17:59:36 GMT (envelope-from Kurt@OpenLDAP.org) Message-Id: <6.0.1.1.0.20040405105659.048a14d0@127.0.0.1> X-Sender: kurt@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 05 Apr 2004 10:59:26 -0700 To: Ted Hardie From: "Kurt D. Zeilenga" Subject: Re: [Ldap-dir] Review for draft-bergeson-uddi-ldap-schema-03.txt Cc: ldap-dir@ietf.org, bruce.bergeson@novell.com, kent.boogert@novell.com, knvijay@novell.com In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by pretender.boolean.net id i35HxZMs009980 Content-Transfer-Encoding: quoted-printable Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Ted, General comment: I would like to see this document include more examples. I find it very hard to review particular uses of LDAP syntax, matching rules, and other elements as currently written. I suspect I've only touched on problems here. Hopefully my comments offer enough food for thought for the Authors to not only address specific issues I've raised, but address issues which are likely lurking. Note: my review was not in-depth. I've been quite short of review cycles (especially for informational stuff) lately. Kurt >Individual Submission B. Bergeson=20 > K. Boogert=20 > Vijay K.Nanjundaswamy= =20 >Internet Draft Novell, Inc.=20 >Document: draft-bergeson-uddi-ldap-schema-03.txt March, 2004=20 >Intended Category: Informational Expires September, 200= 4 >=20 >=20 > =20 > LDAP Schema for UDDIv3=20 These (and other) acronyms likely should be spelled out upon first use in title, first use in abstract, and first use in body. >=20 >=20 >Status of this Memo=20 > =20 > This document is an Internet-Draft and is in full conformance with=20 > all provisions of Section 10 of RFC2026.=20 > =20 > Internet-Drafts are working documents of the Internet Engineering=20 > Task Force (IETF), its areas, and its working groups. Note that=20 > other groups may also distribute working documents as Internet- > Drafts. Internet-Drafts are draft documents valid for a maximum of=20 > six months and may be updated, replaced, or obsoleted by other=20 > documents at any time. It is inappropriate to use Internet-Drafts as=20 > reference material or to cite them other than as "work in progress." = =20 > The list of current Internet-Drafts can be accessed at=20 > http://www.ietf.org/ietf/1id-abstracts.txt =20 > The list of Internet-Draft Shadow Directories can be accessed at=20 > http://www.ietf.org/shadow.html.=20 > =20 > Editorial comments may be sent to bruce.bergeson@novell.com. General=20 > discussion may be directed to the LDAPEXT WG List.=20 Note that the LDAP WG is concluded. You might also want to include the list address here. >1. Abstract=20 =20 Abstract section should not be numbered. > This document defines the Lightweight Directory Access Protocol=20 > [(LDAPv3)] Schema for representing Universal Description, Discovery=20 > & Integration (UDDI) data types in an LDAP directory. It defines the=20 > LDAP object class & attribute definitions and containment rules to=20 > model UDDI entities, defined in the UDDI version 3 information=20 > model, in an LDAPv3 compliant directory. =20 Don't cite references in Abstract. Don't use '&' for 'and'. s/attribute/attribute type/ "It defines ... definitions" is odd wording. I suggest "This document provides ... definitions" suggest s/containment rules/naming and structure rules/ suggest s/LDAPv3 compliant/LDAP/ =20 >Table of Contents=20 > 1. Abstract.......................................................1=20 > 2. Conventions used in this document..............................2=20 > 3. Introduction...................................................2=20 > 4. Representation of UDDI Data Structures.........................2=20 > 5. Attribute Type Definitions.....................................5=20 > 6. Object Class Definitions......................................24=20 > 7. Name Forms....................................................28=20 > 8. DIT Structure Rules...........................................30=20 > 9. Security Considerations.......................................31=20 > =20 >Bergeson, Boogert & Nanjundaswamy Internet-Draft 1=20 > > > > > > > > > LDAP Schema for UDDI November 2003=20 >=20 >=20 > 10. IANA Considerations..........................................32=20 > 11. Normative References.........................................50=20 > 12. Author's Addresses...........................................51=20 >=20 > =20 >2. Conventions used in this document=20 > The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=20 > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this=20 > document are to be interpreted as described in RFC 2119..=20 > =20 > All schema definitions are provided using [RFC2252] descriptions,=20 > line-wrapped for readability only.=20 I suggest this section be made a subsection of your Introduction. >3. Introduction=20 > =20 > This document defines "Lightweight Directory Access Protocol"=20 > [LDAPv3] schema elements to represent the core data structures=20 Edit: don't quote "Lightweight Directory Access Protocol" Since you use LDAP below to mean Lightweight Directory Access Protocol, you should LDAP as acronym for this. And since you want to use it as tag, then: Lightweight Directory Access Protocol (LDAP) [LDAPv3] or Lightweight Directory Access Protocol ([LDAP]) > identified in "Universal Description Discovery and Integration"=20 > version 3 [UDDIv3] information model. Likewise. > This includes: a=20 > businessEntity, a businessService, a bindingTemplate, a tModel, a=20 > publisherAssertion and a Subscription. Edit: Suggest this be reworded: This includes schema elements representing the businessEntity, ..., and Subscription UDDI data structures. There likely should be a paragraph break here. Portions of [UDDIv3] are=20 > repeated here for clarity.=20 You should note: "Where this document differs from [UDDIv3], [UDDIv3] takes precedence." >4. Representation of UDDI Data Structures=20 > =20 > The information that makes up a registration in a UDDI registry=20 > consists of these data structure types. This division by=20 > information type provides simple partitions to assist in the rapid=20 > location and understanding of the different information that makes=20 > up a registration.=20 > =20 > The individual instance data managed by a UDDI registry are=20 > sensitive to the parent/child relationships found in the schema. A=20 > businessEntity object contains one or more unique businessService=20 > objects. Similarly, individual businessService objects contain=20 > specific instances of bindingTemplate, which in turn contains=20 > information that includes pointers to specific instances of tModel=20 > objects.=20 > =20 > It is important to note that no single instance of a core schema=20 > type is ever "contained" by more than one parent instance. This=20 > means that only one specific businessEntity object (identified by=20 > its unique key value) will ever contain or be used to express=20 > information about a specific instance of a businessService object=20 > (also identified by its own unique key value).=20 > =20 >4.1 businessEntity=20 > =20 > The businessEntity object represents all known information about a=20 > business or entity that publishes descriptive information about the=20 > entity as well as the services that it offers. The businessEntity=20 > is the top-level container that accommodates holding descriptive=20 > information about a business or entity. Service descriptions and=20 > technical information are expressed within a businessEntity by a=20 > containment relationship.=20 > =20 >4.1.1 Representation in the Directory=20 > =20 > A businessEntity is represented in the directory by the attributes=20 Is it not represented by an instance of the uddiBusinessEntity object (which has these attributes)? > uddiBusinessKey, uddiAuthorizedName, uddiOperator,=20 > uddiDiscoveryURLs, uddiName, uddiDescription, uddiIdentifierBag,=20 > uddiCategoryBag, and uddiv3DigitalSignature, along with=20 > corresponding v3 keys viz. uddiv3BusinessKey, as defined in section=20 > 5. A businessEntity may contain zero or more instances of=20 > uddiContact and uddiBusinessService. =20 > =20 > The mandatory attribute, uddiBusinessKey, contains the unique=20 > identifier for a given instance of a businessEntity.=20 > =20 > businessEntity's definition is given in Section 6. =20 The spec would be far easier to review (and understand) if the definition was directly incorporated here. Likewise for other objects. =20 >4.2 businessService=20 > =20 > The businessService instances represent a logical business service. =20 > Each businessService object is the logical child of a single=20 > businessEntity object. Each businessService element contains=20 > descriptive information in business terms outlining the type of=20 > technical services found within each businessService instance.=20 > =20 > In some cases, businesses would like to share or reuse services,=20 > e.g. when a large enterprise publishes separate businessEntity=20 > structures. This can be established by using the businessService=20 > instance as a projection to an already published businessService.=20 > =20 >4.2.1 Representation in the Directory=20 > =20 > A businessService is represented in the directory by the attributes=20 > uddiBusinessKey, uddiServiceKey, uddiName, uddiDescription,=20 > uddiCategoryBag, uddiIsProjection, and uddiv3DigitalSignature, along=20 > with corresponding v3 keys viz. uddiv3BusinessKey &=20 > uddiv3ServiceKey, as defined in section 5. A businessService may=20 > contain zero or more instances of uddiBindingTemplate. The=20 > mandatory attribute, uddiServiceKey, contains the unique identifier=20 > for a given instance of a businessService.=20 > =20 > businessService's definition is given in Section 6.=20 > =20 >4.3 bindingTemplate=20 > =20 > Technical descriptions of Web services are accommodated via=20 > individual contained instances of bindingTemplate objects. These=20 > instances provide support for determining a technical entry point or=20 > optionally support remotely hosted services, as well as a=20 > lightweight facility for describing unique technical characteristics=20 > of a given implementation. Support for technology and application=20 > specific parameters and settings files are also supported.=20 > =20 > Since UDDI's main purpose is to enable description and discovery of=20 > Web Service information, it is the bindingTemplate that provides the=20 > most interesting technical data. With UDDIv3, bindingTemplates also=20 > can have categorization information.=20 > =20 > Each bindingTemplate instance has a single logical businessService=20 > parent, which in turn has a single logical businessEntity parent.=20 > =20 >4.3.1 Representation in the Directory=20 > =20 > A bindingTemplate is represented in the directory by the attributes=20 > uddiBindingKey, uddiServiceKey, uddiDescription, uddiAccessPoint,=20 > uddiHostingRedirector, uddiCategoryBag and uddiv3DigitalSignature,=20 > along with corresponding v3 keys viz. uddiv3ServiceKey and=20 > uddiv3BindingKey, as defined in section 5. A bindingTemplate may=20 > contain zero or more instances of uddiTModelInstanceDetails. The=20 > mandatory attribute, uddiBindingKey, contains the unique identifier=20 > for a given instance of a bindingTemplate.=20 > =20 > BindingTemplate's definition is given in Section 6.=20 > =20 >4.4 tModel=20 > =20 > The tModel object takes the form of keyed metadata (data about=20 > data). In a general sense, the purpose of a tModel within the UDDI=20 > registry is to provide a reference system based on abstraction. =20 > Thus, the kind of data that a tModel represents is pretty nebulous. =20 > In other words, a tModel registration can define just about=20 > anything, but in the current revision, two conventions have been=20 > applied for using tModels: as sources for determining compatibility=20 > and as keyed namespace references.=20 > =20 > The information that makes up a tModel is quite simple. There's a=20 > key, a name, an optional description, and a Uniform Resource Locator=20 > [URL] that points somewhere--presumably somewhere where the curious=20 s/Uniform Resource Locator [URL]/Uniform Resource Identifier ([URI])/ In the reference, it might be appropriate to say: RFC 2396 as updated by RFC 2732. > can go to find out more about the actual concept represented by the=20 > metadata in the tModel itself.=20 > =20 >4.4.1 Representation in the Directory=20 > =20 > A tModel is represented in the directory by the attributes=20 > uddiTModelKey, uddiAuthorizedName, uddiOperator, uddiName,=20 > uddiDescription, uddiOverviewDescription, uddiOverviewURL,=20 > uddiIdentifierBag, uddiCategoryBag, uddiIsHidden, and=20 > uddiv3DigitalSignature, along with corresponding v3 key viz.=20 > uddiv3tModelKey, as defined in section 5. A tModel may also contain=20 > a uddiHidden to logically delete a tModel. The mandatory attribute,=20 > uddiTModelKey, contains the unique identifier for a given instance=20 > of a tModel.=20 > =20 > tModel's definition is given in Section 6.=20 > =20 >4.5 publisherAssertion=20 > =20 > Many businesses, like large enterprises or marketplaces, are not=20 > effectively represented by a single businessEntity, since their=20 > description and discovery are likely to be diverse. As a=20 > consequence, several businessEntity instances can be published,=20 > representing individual subsidiaries of a large enterprise or=20 > individual participants of a marketplace. Nevertheless, they still=20 > represent a more or less coupled community and would like to make=20 > some of their relationships visible in their UDDI registrations. =20 > =20 >4.5.1 Representation in the Directory=20 > =20 > A publisherAssertion is represented in the directory by the=20 > attributes uddiFromKey, uddiToKey, uddiKeyedReference, and uddiUUID,=20 > and uddiv3DigitalSignature, as defined in section 5. The mandatory=20 > attribute, uddiUUID, contains the unique identifier for a given=20 > instance of a publisherAssertion.=20 > =20 > publisherAssertion's definition is given in Section 6.=20 > =20 >4.6 Operational Information:=20 >=20 > With UDDIv3, the operational information associated with the core=20 > UDDI data structures is maintained in a separate OperationalInfo=20 > structure, so that the digital signature specified by the publisher=20 > remains valid. =20 > =20 > The operationalInfo structure is used to convey the operational=20 > information for the UDDIv3 core data structures, that is, the=20 > businessEntity, businessService, bindingTemplate and tModel=20 > structures. UDDIv3 OperationalInfo consists of 5 elements: created.=20 > Modified, modifiedIncludingChildren, nodeId and authorizedName.=20 > =20 > Depending on the specific UDDIv3 core data structure, the=20 > operationalInformation is represented in the directory as a=20 > combination of implicit LDAP Standard Operational attributes:=20 > createTimestamp and modifyTimestamp, and the following explicit=20 > attributes: uddiAuthorizedName, uddiv3EntityCreationTime,=20 > uddiv3EntityModificationTime and uddiv3NodeId.=20 I'm not sure what you mean by 'implicit' and 'explicit' here. Suggest: s/implicit LDAP Standard Operational attribute/LDAP operational attribut= es/ s/explicit/new/ You need to include a reference to the document defining these LDAP operational attributes. > =20 >5. Attribute Type Definitions=20 > =20 > Note that OIDs for the attribute types in this document have not=20 > been assigned. All OIDs are in brackets, , as a=20 > placeholder until real OIDs are assigned.=20 This should be worded more clearly as a note to the RFC Editor. E.g., [[Note to the RFC Editor: ...]] so that it is obvious that the RFC Editor should remove the note after replacing OID-TBD with the IANA assigned OID. s/OID-TBD/IANA-ASSSIGNED-OID/=20 =20 >5.1 uddiBusinessKey=20 > =20 > Used in uddiBusinessEntity and uddiBusinessService. =20 > =20 > The uddiBusinessKey is the unique identifier for a given instance of=20 > an uddiBusinessEntity. The attribute is optional for businessService=20 > instances contained within a fully expressed parent that already=20 > contains a businessKey value.=20 > =20 > If the businessService instance is rendered into Extensible Markup=20 > Language [XML] and has no containing parent that has within its data=20 > a businessKey, the value of the businessKey that is the parent of=20 > the businessService is required to be provided. This behavior=20 > supports the ability to browse through the parent-child=20 > relationships given any of the core elements as a starting point.=20 > The businessKey may differ from the publishing businessEntity's=20 > businessKey to allow service projections.=20 > =20 > ( IANA-ASSIGNED-OID.4.1 NAME 'uddiBusinessKey'=20 > DESC 'businessEntity unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 You should say which syntax 1.3.6.1.4.1.1466.115.121.1.15 refers to (Directory String) and where that syntax is defined (RFC 2252). You should provide a referene for caseIgnoreMatch. Likewise below. (Note: as an alternatively do doing this per element, one could add a statement above which covers all the external definitions used.) Also, note that a number of the elements used in this document are defined in RFC 3698 (and most of the rest in RFC 2252/2256). >5.2 uddiAuthorizedName=20 > =20 > The uddiAuthorizedName is the recorded name of the individual that=20 > published the uddiBusinessEntity or uddiTModel data. This data is=20 > generated by the controlling operator and should not be supplied=20 > within save_business operations. =20 > =20 > With UDDIv3, this attribute is part of the =91operationalInformation=92= =20 > meta-data associated with core data structures.=20 operationalInformation is wrapped here by non-ASCII characters. That happens a few other places in this document. =20 > ( IANA-ASSIGNED-OID.4.2 NAME 'uddiAuthorizedName'=20 > DESC 'businessEntity publisher name'=20 > EQUALITY distinguishedNameMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.12=20 > SINGLE-VALUE=20 > )=20 why no ordering or no substrings matching rules? =20 >5.3 uddiOperator=20 > =20 > The uddiOperator is the certified name of the UDDI registry site=20 > operator that manages the master copy of the uddiBusinessEntity or=20 > uddiTModel. The controlling operator records this data at the time=20 > data is saved. This data is generated and should not be supplied=20 > within save_business or save_tModel operations.=20 > =20 > With UDDIv3, this field is no longer used - it is replaced by the=20 > nodeId (uddiv3NodeId) attribute that is part of the=20 > =91operationalInformation=92 meta-data.=20 > =20 > ( IANA-ASSIGNED-OID.4.3 NAME 'uddiOperator'=20 > DESC 'registry site operator of businessEntitys master copy'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.4 uddiName=20 > =20 > Used in uddiBusinessEntity, uddiBusinessService and uddiTModel.=20 > =20 > These are the human readable names recorded for the=20 > uddiBusinessEntity, uddiBusinessService, or uddiTModel, adorned with=20 > a unique xml:lang value to signify the language that they are=20 > expressed in. Name search is provided via find_business,=20 > find_service, or find_tModel calls.=20 > =20 > The publishing of several names, e.g. for romanization purposes, is=20 > supported. In order to signify the language that the names are=20 > expressed in, they carry unique xml:lang values. Not more than one=20 > name element may omit specifying its language. Names passed in this=20 > way will be assigned the default language code of the registering=20 > party. This default language code is established at the time that=20 > publishing credentials are established with an individual Operator=20 > Site. If no default language is provisioned at the time a publisher=20 > signs up, the operator can adopt an appropriate default language=20 > code.=20 > =20 > With UDDIv3, multiple values with the same language code are=20 > permitted. =20 > =20 > ( IANA-ASSIGNED-OID.4.4 NAME 'uddiName'=20 > DESC 'human readable name'=20 > EQUALITY caseIgnoreMatch=20 > ORDERING caseIgnoreOrderingMatch=20 > SUBSTR caseIgnoreSubstringsMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The xml:lang value precedes the name value with the "#" character=20 > used as the separator.=20 I note that in LDAP, '$' is generally used as a separator. But more importantly, I don't think it wise to push structured data into an opaque data element. It would be better to define a new syntax xmlLangTagText ::=3D SEQUENCE { language printableString, text directoryString } (with an LDAP specific string encoding, possibly using GSER) and then define syntax-aware matching rules. Use of LDAP Language tags is another option (if xml:lang tags map well onto LDAP language tags). Another option would be invent a new form of LDAP attribute option, an xml:lang tag. Likewise below. >5.5 uddiDescription=20 > =20 > The uddiDescription is an optional repeating element of one or more=20 > descriptions. One description is allowed per national language code=20 > supplied. With UDDIv3, there is no restriction on the number of=20 > descriptions or on what xml:lang value that they may have.=20 > =20 > ( IANA-ASSIGNED-OID.4.5 NAME 'uddiDescription'=20 > DESC 'short description'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 why no ordering or no substrings matching rules? > =20 > The xml:lang value precedes the name value with the "#" character=20 > used as the separator.=20 > =20 >5.6 uddiDiscoveryURLs=20 > =20 > This is a list of Uniform Resource Locators (URLs) that point to=20 > alternate, file based service discovery mechanisms. Each recorded=20 > uddiBusinessEntity structure is automatically assigned a URL that=20 > returns the individual uddiBusinessEntity structure. URL search is=20 > provided via find_business call.=20 > =20 > The uddiDiscoveryURLs attribute is used to hold pointers to URL=20 > addressable discovery documents. The expected retrieval mechanism=20 > for URLs referenced in the data within this structure is via=20 > Hypertext Transfer Protocol [HTTP] HTTP-GET operation. The expected=20 > return document is not defined. Rather, a framework for establishing=20 > convention is provided, and two such conventions are defined within=20 > UDDI behaviors. It is hoped that other conventions come about and=20 > use this structure to accommodate alternate means of discovery.=20 > With UDDIv3, a new convention is defined with useType as "homepage".=20 > Further, a UDDIv3 server need not generate/add a discoveryURL=20 > itself, since this can invalidate the digital signature of signed=20 > Business Entity saved by publishers. =20 > =20 > ( IANA-ASSIGNED-OID.4.6 NAME 'uddiDiscoveryURLs'=20 > DESC 'URL to retrieve a businessEntity instance'=20 > EQUALITY caseExactMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The useType value precedes the URL value with the "#" character used=20 > as the separator.=20 > =20 >5.7 uddiUseType=20 > =20 > The uddiUseType is used to describe the type of contact or address=20 > in freeform text. Suggested examples for contact include "technical=20 > questions", "technical contact", "establish account", "sales=20 > contact", etc. Suggested examples for address include=20 > "headquarters", "sales office", "billing department", etc.=20 > =20 > ( IANA-ASSIGNED-OID.4.7 NAME 'uddiUseType'=20 > DESC 'name of convention the referenced document follows'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.8 uddiPersonName=20 > =20 > The uddiPersonName should list the name of the person or name of the=20 > job role that will be available behind the contact. Examples of=20 > roles include "administrator" or "webmaster". =20 > =20 > ( IANA-ASSIGNED-OID.4.8 NAME 'uddiPersonName'=20 > DESC 'name of person or job role available for contact'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > With UDDIv3, uddiPersonName becomes multi-valued and each name can=20 > have an xml:lang attribute. The xml:lang value precedes the name=20 > value with the "#" character used as the separator.=20 > =20 > =20 >5.9 uddiPhone=20 > =20 > Used to hold telephone numbers for the contact. This element can be=20 > adorned with an optional uddiUseType attribute for descriptive=20 > purposes. If more than one phone element is saved, uddiUseType=20 > attributes are required on each. =20 > =20 > ( IANA-ASSIGNED-OID.4.9 NAME 'uddiPhone'=20 > DESC 'telephone number for contact'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The useType precedes the telephone number by a separating '#' (e.g.=20 > "Work Number#123 456-7890")=20 Another component syntax. Ignoring that (here and elsewhere), I wonder why it doesn't have a substrings matching rule. > =20 >5.10 uddiEMail=20 > =20 > Used to hold email addresses for the contact. This element can be=20 > adorned with an optional uddiUseType attribute for descriptive=20 > purposes. If more than one email element is saved, uddiUseType=20 > attributes are required on each.=20 > =20 > ( IANA-ASSIGNED-OID.4.10 NAME 'uddiEMail'=20 > DESC 'e-mail address for contact'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The useType precedes the email address by a separating '#' (e.g.=20 > "President of the United States #president@whitehouse.gov").=20 Don't use a real domain in examples. Use example.com instead. =20 >5.11 uddiSortCode=20 > =20 > The uddiSortCode is used to drive the behavior of external display=20 > mechanisms that sort addresses. The suggested values for=20 > uddiSortCode include numeric ordering values (e.g. 1, 2, 3),=20 > alphabetic character ordering values (e.g. a, b, c) or the first n=20 > positions of relevant data within the address.=20 >=20 > ( IANA-ASSIGNED-OID.4.11 NAME 'uddiSortCode'=20 > DESC 'specifies an external disply mechanism'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > With UDDIv3, the sortCode attribute is deprecated because of the=20 > guarantee of preserving the document Order.=20 >=20 >5.12 uddiTModelKey=20 > =20 > The uddiTModelKey is the unique identifier for a given instance of=20 > an uddiTModel.=20 > =20 > It is also used in a KeyedReference and in Address structures. When=20 > used with a keyed reference, this is the unique key to identify a=20 > value-set and implies that the keyName keyValue pair in an=20 > uddiIdentifier or uddiCategory Bag,are to be interpreted by the=20 > value set referenced by the tModelKey. =20 > =20 > When used with Addressline elements, implies that the keyName=20 > keyValue pair given by subsequent uddiAddressLine elements are to be=20 > interpreted by the address structure associated with the tModel that=20 > is referenced.=20 > =20 > ( IANA-ASSIGNED-OID.4.12 NAME 'uddiTModelKey'=20 > DESC 'tModel unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.13 uddiAddressLine=20 > =20 > The uddiAddressLine contains the actual address in freeform text. If=20 > the address element contains a uddiTModelKey, these uddiAddressLine=20 > elements are to be adorned each with an optional keyName keyValue=20 > attribute pair. Together with the uddiTModelKey, keyName and=20 > keyValue qualify the uddiAddressLine in order to describe its=20 > meaning.=20 > =20 > The uddiAddressLine elements contain string data with a line length=20 > limit of 80 character positions. Each uddiAddressLine element can be=20 > adorned with two optional descriptive attributes, keyName and=20 > keyValue. Both attributes must be present in each address line if a=20 > uddiTModelKey is assigned to the address structure. By doing this,=20 > the otherwise arbitrary use of address lines becomes structured.=20 > Together with the address' uddiTModelKey, keyName and keyValue=20 > virtually build a uddiKeyedReference that represents an address line=20 > qualifier, given by the referenced uddiTModel. =20 > =20 > When no uddiTModelKey is provided for the address structure, the=20 > keyName and keyValue attributes can be used without restrictions,=20 > for example, to provide descriptive information for each=20 > uddiAddressLine by using the keyName attribute. Since both the=20 > keyName and the keyValue attributes are optional, address line order=20 > is significant and will always be returned by the UDDI compliant=20 > registry in the order originally provided during a call to=20 > save_business.=20 > =20 > ( IANA-ASSIGNED-OID.4.13 NAME 'uddiAddressLine'=20 > DESC 'address'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The keyName, keyValue, and addressData of this attribute are=20 > separated by "#", (e.g. "#""#""#"). =20 > The addressData is the only required portion of the attribute.=20 > =20 >5.14 uddiIdentifierBag=20 > =20 > The uddiIdentifierBag element allows uddiBusinessEntity or=20 > uddiTModel structures to include information about common forms of=20 > identification such as D-U-N-S_ numbers, tax identifiers, etc. This=20 > data can be used to signify the identity of the uddiBusinessEntity,=20 > or can be used to signify the identity of the publishing party.=20 > Including data of this sort is optional, but when used greatly=20 > enhances the search behaviors exposed via the find_xx messages=20 > defined in the UDDI Version 2.0 API Specification [UDDI]. For a full=20 > description of the structures involved in establishing an identity,=20 > see UDDI Version 2.0 Data Structure Specification - Appendix A:=20 > Using Identifiers.=20 > =20 > ( IANA-ASSIGNED-OID.4.14 NAME 'uddiIdentifierBag'=20 > DESC 'identification information'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The tModel, keyName, and keyValue of this attribute are separated by=20 > "#", (e.g. "#""#"). The keyValue is the=20 > only required portion of the attribute.=20 > =20 >5.15 uddiCategoryBag=20 > =20 > The uddiCategoryBag element allows uddiBusinessEntity,=20 > uddiBusinessService and uddiTModel structures to be categorized=20 > according to any of several available taxonomy based classification=20 > schemes. Operator Sites automatically provide validated=20 > categorization support for three taxonomies that cover industry=20 > codes (via NAICS), product and service classifications (via UNSPC)=20 > and geography (via ISO 3166). Including data of this sort is=20 > optional, but when used greatly enhances the search behaviors=20 > exposed by the find_xx messages defined in the UDDI Version 2.0 API=20 > Specification. For a full description of structures involved in=20 > establishing categorization information, see UDDI Version 2.0 Data=20 > Structure Specification - Appendix B: Using categorization.=20 > =20 > ( IANA-ASSIGNED-OID.4.15 NAME 'uddiCategoryBag'=20 > DESC 'categorization information'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The tModel, keyName, and keyValue of this attribute are separated by=20 > "#", (e.g. "#""#"). The keyValue is the=20 > only required portion of the attribute.=20 > =20 > With UDDIv3, uddiBindingTemplates also supports the uddiCategoryBag=20 > element and they can also be categorized according to any of several=20 > available taxonomy based classification schemes.=20 > =20 >5.16 uddiKeyedReference=20 > =20 > The uddiKeyedReference is a general-purpose attribute for a name- > value pair, with an additional reference to a tModel.=20 > =20 > ( IANA-ASSIGNED-OID.4.16 NAME 'uddiKeyedReference'=20 > DESC 'categorization information'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The tModel, keyName, and keyValue of this attribute are separated by=20 > "#", (e.g. "#""#"). The keyValue is the=20 > only required portion of the attribute. With UDDIv3, the tModelKey=20 > also becomes mandatory part of the attribute. =20 > =20 > Also, UDDIv3 defines KeyedReferenceGroups for CategoryBags. A=20 > keyedReferenceGroup contains a tModelKey and a simple list of=20 > KeyedReference structures. The uddiKeyedReference attribute will=20 > support KeyedReferenceGroups by suffixing the tModelKey for=20 > KEyedReferenceGroup to each of the keyedReference values associated=20 > with the group.=20 > e.g. to represent a keyedReference group containing a list of 2=20 > keyed references, the attribute will hold the following 2 strings as=20 > its values:=20 > tModelKey1#KeyName1#KeyValue1#KeyedReferenceGroup1_tModelKey=20 > tModelKey2#KeyName2#KeyValue2#KeyedReferenceGroup1_tModelKey=20 > =20 > =20 >5.17 uddiServiceKey=20 > =20 > This is the unique key for a given uddiBusinessService. When saving=20 > a new uddiBusinessService structure, pass an empty uddiServiceKey=20 > value. This signifies that a UUID value is to be generated. To=20 > update an existing uddiBusinessService structure, pass the UUID=20 > value that corresponds to the existing service. If an uddiServiceKey=20 > is received via an inquiry operation, the key values may not be=20 > blank. When saving a new or updated service projection, pass the=20 > uddiServiceKey of the referenced uddiBusinessService structure.=20 > =20 > This attribute is optional when the uddiBindingTemplate data is=20 > contained within a fully expressed parent that already contains a=20 > uddiServiceKey value. If the uddiBindingTemplate data is rendered=20 > into XML and has no containing parent that has within its data a=20 > uddiServiceKey, the value of the uddiServiceKey that is the ultimate=20 > containing parent of the uddiBindingTemplate is required to be=20 > provided. This behavior supports the ability to browse through the=20 > parent-child relationships given any of the core elements as a=20 > starting point.=20 > =20 > ( IANA-ASSIGNED-OID.4.17 NAME 'uddiServiceKey'=20 > DESC 'businessService unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.18 uddiBindingKey=20 > =20 > This is the unique key for a given uddiBindingTemplate. When saving=20 > a new uddiBindingTemplate structure, pass an empty uddiBindingKey=20 > value. This signifies that a UUID value is to be generated. To=20 > update an existing uddiBindingTemplate, pass the UUID value that=20 > corresponds to the existing uddiBindingTemplate instance. If an=20 > uddiBindingKey is received via an inquiry operation, the key values=20 > may not be blank.=20 > =20 > ( IANA-ASSIGNED-OID.4.18 NAME 'uddiBindingKey'=20 > DESC 'bindingTemplate unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.19 uddiAccessPoint=20 > =20 > The uddiAccessPoint element is an attribute-qualified pointer to a=20 > service entry point. The notion of service at the metadata level=20 > seen here is fairly abstract and many types of entry points are=20 > accommodated. A single attribute is provided named URLType.=20 > =20 > Required attribute qualified element8. This element is a text field=20 > that is used to convey the entry point address suitable for calling=20 > a particular Web service. This may be a URL, an electronic mail=20 > address, or even a telephone number. No assumptions about the type=20 > of data in this field can be made without first understanding the=20 > technical requirements associated with the Web service.=20 > =20 > ( IANA-ASSIGNED-OID.4.19 NAME 'uddiAccessPoint'=20 > DESC 'entry point address to call a web service'=20 > EQUALITY caseExactMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > The URLType value precedes the accessPoint value by a separating=20 > '#'.=20 > =20 > With UDDIv3,the =91URLType=92 attribute is replaced by a =91UseType=92= =20 > attribute. Using this UseType attribute, the accessPoint attribute=20 > can model a hostingRedirector or support indirection to indicate the=20 > accesspoint is specified within a remotely hosted WSDL document. =20 > =20 > For a UDDIv3 registry that needs support UDDIv2 clients, the=20 > attribute must allow representing the URLType and UseType values=20 > independently. =20 > =20 > The UDDIv3 spec specifies the following logic for mapping values=20 > between URLType and UseType: If an entity is saved with the v3=20 > namespace and a v2 inquiry is made, the URLType will be returned as=20 > "other". In the case when a v3 inquiry is made on an entity=20 > published with the v2 namespace, the v3 useType attribute will be=20 > returned as "endPoint".=20 > =20 > For implementations that need to explicitly model both forms, the=20 > recommended format is as follows: v2URLType#v3UseType#Address=20 > =20 >5.20 uddiHostingRedirector=20 > =20 > The uddiHostingRedirector element is used to designate that a=20 > uddiBindingTemplate entry is a pointer to a different=20 > uddiBindingTemplate entry. The value in providing this facility is=20 > seen when a business or entity wants to expose a service description=20 > (e.g. advertise that they have a service available that suits a=20 > specific purpose) that is actually a service that is described in a=20 > separate uddiBindingTemplate record. This might occur when a service=20 > is remotely hosted (hence the name of this element), or when many=20 > service descriptions could benefit from a single service=20 > description.=20 > =20 > The uddiHostingRedirector element has a single attribute and no=20 > element content. The attribute is a uddiBindingKey value that is=20 > suitable within the same UDDI registry instance for querying and=20 > obtaining the uddiBindingDetail data that is to be used.=20 > =20 > More on the uddiHostingRedirector can be found in the appendices for=20 > the UDDI Version 2.0 API Specification.=20 > =20 > Required element if uddiAccessPoint not provided. This element is=20 > adorned with a uddiBindingKey attribute, giving the redirected=20 > reference to a different uddiBindingTemplate. If you query a=20 > uddiBindingTemplate and find a uddiHostingRedirector value, you=20 > should retrieve that uddiBindingTemplate and use it in place of the=20 > one containing the uddiHostingRedirector data. =20 > =20 > ( IANA-ASSIGNED-OID.4.20 NAME 'uddiHostingRedirector'=20 > DESC 'designates a pointer to another bindingTemplate'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > With UDDIv3, the hostingRedirector is a deprecated element, since=20 > its functionality is now covered by the accessPoint. For backward- > compatibility, it can still be used, but it is not recommended.=20 > =20 >5.21 uddiInstanceDescription=20 > =20 > This is an optional repeating element. This is one or more language=20 > qualified text descriptions that designate what role a uddiTModel=20 > reference plays in the overall service description.=20 > =20 > ( IANA-ASSIGNED-OID.4.21 NAME 'uddiInstanceDescription'=20 > DESC 'instance details description'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The xml:lang value precedes the name value with the "#" character=20 > used as the separator.=20 > =20 >5.22 uddiInstanceParms=20 > =20 > The uddiInstance Parms is an Optional element of the uddiInstance.=20 > Used to contain settings parameters or a URL reference to a file=20 > that contains settings or parameters required to use a specific=20 > facet of a uddiBindingTemplate description. If used to house the=20 > parameters themselves, the suggested content is a namespace=20 > qualified XML string - > - using a namespace outside of the UDDI schema.=20 > If used to house a URL pointer to a file, the suggested format is=20 > URL that is suitable for retrieving the settings or parameters via=20 > HTTP-GET.=20 > =20 > ( IANA-ASSIGNED-OID.4.22 NAME 'uddiInstanceParms'=20 > DESC 'URL reference to required settings'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 If values here are URLs, then why does it equality rule differ from other attribute types which hold URLs (or URIs). caseExact is more appropriate than caseIgnore for URIs. >5.23 uddiOverviewDescription=20 >=20 > This is optional repeating element. This language-qualified string=20 > is intended to hold a short descriptive overview of how a particular=20 > uddiTModel is to be used.=20 > =20 > ( IANA-ASSIGNED-OID.4.23 NAME 'uddiOverviewDescription'=20 > DESC 'outlines tModel usage'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > The xml:lang value precedes the name value with the "#" character=20 > used as the separator.=20 > =20 >5.24 uddiOverviewURL=20 > =20 > This is an optional element. This string data element is to be used=20 > to hold a URL reference to a long form of an overview document that=20 > covers the way a particular uddiTModel specific reference is used as=20 > a component of an overall web service description. The recommended=20 > format for the overviewURL is a URI that is suitable for retrieving=20 > the actual overview document with an HTTP GET operation, for=20 > example, via a Web browser.=20 > =20 > ( IANA-ASSIGNED-OID.4.24 NAME 'uddiOverviewURL'=20 > DESC 'URL reference to overview document'=20 > EQUALITY caseExactMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > With UDDIv3, uddiOverviewURL becomes multi-valued, to allow=20 > representing multiple OverviewDocs within a single InstanceDetail=20 > element.=20 > =20 > Modeling multiple OverviewDocs within an InstanceDetail element:=20 > In UDDIv3, InstanceDetails element in TmodelInstanceInfo can have=20 > multiple OverviewDoc=92s. In UDDIv2, we could have only 1 OverviewDoc= .=20 > To retain the grouping between a set of overviewDescriptions and=20 > overviewURL, we can make both OverviewDoc and OverviewURL multi- > valued. And have a =91group ID=92 Prefix to each value (to group=20 > OverviewDescriptions and OverviewURL). =20 > =20 > An example is shown below:=20 > Overview Description OverviewURL=20 > 1#xml:lang#overviewDescription1 1#UseType#overviewURL=20 > 1#xml:lang#overviewDescription2 2#UseType#overviewURL=20 > 1#xml:lang#overviewDescription3 4#UseType#overviewURL=20 > 3#xml:lang#overviewDescription1=20 > 3#xml:lang#overviewDescription2=20 > 4#xml:lang#overviewDescription1=20 > =20 > This implies that OverviewDoc1 has 3 overview descriptions and an=20 > overviewURL. OverviewDoc2 has only an overviewURL. OverviewDoc3 has=20 > only 2 overviewDescriptions. OverviewDoc4 also has 1 overview=20 > description and an overviewURL.=20 > =20 >5.25 uddiFromKey=20 > =20 > The uddiFromKey is a required element. This is the unique key=20 > reference to the first uddiBusinessEntity the assertion is made for.=20 > =20 > ( IANA-ASSIGNED-OID.4.25 NAME 'uddiFromKey'=20 > DESC 'unique businessEntity key reference'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.26 uddiToKey=20 > =20 > The uddiToKey is a required element. This is the unique key=20 > reference to the second uddiBusinessEntity the assertion is made=20 > for.=20 > =20 > ( IANA-ASSIGNED-OID.4.26 NAME 'uddiToKey'=20 > DESC 'unique businessEntity key reference'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.27 uddiUUID=20 > =20 > The uddiUUID is a required element. This is to insure unique=20 > identification of uddiContact, uddiAddress, and=20 > uddiPublisherAssertion objects.=20 > =20 > ( IANA-ASSIGNED-OID.4.27 NAME 'uddiUUID'=20 > DESC 'unique attribute'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 Should use UUID syntaxes and matching rules from draft-zeilenga-ldap-uuid =20 > With UDDIv3, this attribute will also be used for unique=20 > identification of Subscription feature related entities.=20 > =20 >5.28 uddiIsHidden=20 > =20 > Used to provide functionality for the delete_tModel operation. =20 > Logical deletion hides the deleted tModels from find_tModel result=20 > sets but does not physically delete it.=20 > =20 > ( IANA-ASSIGNED-OID.4.28 NAME 'uddiIsHidden'=20 > DESC 'isHidden attribute'=20 > EQUALITY booleanMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.7=20 > SINGLE-VALUE=20 > )=20 > =20 > In case of UDDIv3, this attribute will represent the =91deleted=92=20 > attribute value. =20 > =20 >5.29 uddiIsProjection=20 > =20 > Used to identify a Business Service that as a Service Projection. =20 > =20 > ( IANA-ASSIGNED-OID.4.29 NAME 'uddiIsProjection'=20 > DESC 'isServiceProjection attribute'=20 > EQUALITY booleanMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.7=20 > SINGLE-VALUE=20 > )=20 > =20 >5.30 uddiLang=20 > =20 > Used to model the xml:lang value for the Address structure in=20 > UDDIv3. =20 > =20 > ( IANA-ASSIGNED-OID.4.30 NAME 'uddiLang'=20 > DESC 'xml:lang value in v3 Address structure=92=20 > EQUALITY booleanMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.7=20 > SINGLE-VALUE=20 > )=20 > =20 > The following are attribute definitions to model new elements/fields=20 > in UDDIv3 information model. These attribute definitions have the=20 > =91uddiv3=92 prefix to indicate that these attributes represent UDDI=20 > information model elements unique to UDDIv3.=20 > =20 >5.31 uddiv3BusinessKey=20 > =20 > This is the unique UDDIv3 identifier for a given instance of=20 > uddiBusinessEntity. Used in uddiBusinessEntity and=20 > uddiBusinessService. =20 > =20 > A uddiBusinessEntity will include the uddiBusinessKey (the v2 form)=20 > for unique identification by UDDIv2 clients. The uddiBusinessKey=20 > (36-char) will also be the LDAP naming attribute for the=20 > uddiBusinessEntity. The uddiBusinessEntity entry MAY also include=20 > the uddiv3BusinessKey, the explicit v3 form key, which can be 255=20 > characters long.=20 > =20 > ( IANA-ASSIGNED-OID.4.31 NAME 'uddiv3BusinessKey'=20 > DESC 'UDDIv3 businessEntity unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.32 uddiv3ServiceKey=20 > =20 > This is the unique UDDIv3 identifier for a given instance of=20 > uddiBusinessService. Used in uddiBusinessService and=20 > uddiBindingTemplate. =20 > =20 > A uddiBusinessService will include the uddiServiceKey (the v2 form)=20 > for unique identification by UDDIv2 clients. The uddiServiceKey (36- > char) will also be the LDAP naming attribute for the=20 > uddiBusinessService entry. The uddiBusinessService entry MAY also=20 > include the uddiv3ServiceKey, the explicit v3 form key, which can be=20 > 255 characters long.=20 > =20 > ( IANA-ASSIGNED-OID.4.32 NAME 'uddiv3ServiceKey'=20 > DESC 'UDDIv3 businessService unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.33 uddiv3BindingKey=20 > =20 > This is the unique UDDIv3 identifier for a given instance of=20 > uddiBindingTemplate. =20 > =20 > A uddiBindingTemplate will include the uddiBindingKey (the v2 form)=20 > for unique identification by UDDIv2 clients. The uddiBindingKey (36- > char) will also be the LDAP naming attribute for the=20 > uddiBindingTemplate entry. The uddiBindingTemplate entry MAY also=20 > include the uddiv3BindingKey, the explicit v3 form key, which can be=20 > 255 characters long.=20 > =20 > ( IANA-ASSIGNED-OID.4.33 NAME 'uddiv3BindingKey'=20 > DESC 'UDDIv3 BindingTemplate unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.34 uddiv3TModelKey=20 > =20 > This is the unique UDDIv3 identifier for a given instance of an=20 > uddiTModel.=20 > =20 > A uddiTModel will include the uddiTModelKey (the v2 form) for unique=20 > identification by UDDIv2 clients. The uddiTModelKey (41-char) will=20 > also be the LDAP naming attribute for the uddiTModel entry. The=20 > uddiTModel entry MAY also include the uddiv3TModelKey, the explicit=20 > v3 form key, which can be 255 characters long.=20 > =20 > ( IANA-ASSIGNED-OID.4.34 NAME 'uddiv3TModelKey'=20 > DESC 'UDDIv3 TModel unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > The tModelKey is also used in a KeyedReference and in Address=20 > structures. At all places, where a tModelKey is used as a reference=20 > to tModel, the v3 form of the tModel key (viz. uddiv3TModelKey) will=20 > be the form used, since using the v2 form key will require=20 > translating it to the v3 key by the UDDI Server and this may=20 > invalidate the digital signature of the entity. =20 > =20 >5.35 uddiv3DigitalSignature=20 > =20 > The UDDIv3 v3 schema supports signing of the following UDDI elements=20 > using =91XML-Signature Syntax and Processing=92 (see=20 > http://www.w3.org/TR/xmldsig-core/).=20 > ..businessEntity=20 > ..businessService=20 > ..bindingTemplate=20 > ..tModel=20 > ..publisherAssertion=20 > =20 > This uddiv3DigitalSignature attribute holds the digital signature=20 > for the corresponding UDDI entity.=20 > =20 > ( IANA-ASSIGNED-OID.4.35 NAME 'uddiv3DigitalSignature'=20 > DESC 'UDDIv3 entity digital signature'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > )=20 > =20 > A Signature element SHOULD be generated according to the required=20 > steps of "Core Generation" in XML-Signature Syntax and Processing.=20 > The signature should be calculated on the top level element that=20 > will be stored by the registry as a result of the Publication API=20 > call. This element, referred to as the data object in the=20 > XMLSignature and Syntax specification, is the businessEntity element=20 > for save_business API calls, the businessService element for=20 > save_service API calls, the bindingTemplate for save_binding=20 > API calls, the tModel for save_tModel API calls and the=20 > publisherAssertion for set_publisherAssertions and=20 > add_publisherAssertion API calls. =20 > =20 > The signature should be generated on the elements before they are=20 > added to the body of an API call. Also, according to the signature=20 > generation, all children of the element being signed are included in=20 > the generation of the signature unless first excluded by application=20 > of a transform. Due to the containment of service projections as=20 > businessService elements within a businessEntity element, this also=20 > means that changes to the projected service will render a signature=20 > of the businessEntity containing the projection invalid, unless a=20 > businessService element representing a service projection is=20 > excluded using a transform.=20 > =20 > Due to the location of the sequence of Signature elements within an=20 > element that is to be signed, the signature is "enveloped". As a=20 > result of the enveloping of the signature, it is necessary to apply=20 > at least one transformation on the signed entity to exclude the=20 > signature or signature(s). The transformation selected by a=20 > publisher or the XML Signature tool is specified in a Transform=20 > element inside the Signature element. =20 > =20 >5.36 uddiv3NodeId=20 > =20 > This attribute contains the Node Identity for a UDDIv3 node. =20 > =20 > ( IANA-ASSIGNED-OID.4.36 NAME 'uddiv3NodeId'=20 > DESC 'UDDIv3 Node Identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.37 uddiv3EntityModificationTime=20 > =20 > This attribute is used to maintain the last modification time for a=20 > UDDI entity. It is needed in context of maintaining the=20 > modifiedIncludingChildren element. When a child entity (e.g.=20 > uddiBindingTemplate) is updated, the parent entity (e.g.=20 > uddiBusinessService) LDAP timestamp also gets updated. The=20 > uddiv3EntityModificationTime attribute saves the last modification=20 > time of the parent entity (uddiBusinessService in this case). =20 > =20 > ( IANA-ASSIGNED-OID.4.37 NAME 'uddiv3EntityModificationTime'=20 > DESC 'UDDIv3 Last Modified Time for Entity'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > =20 > The following attribute definitions define attributes related to=20 > modeling of UDDIv3 subscription related entities in LDAP directory.=20 > =20 > Subscription provides clients, known as subscribers, with the=20 > ability to register their interest in receiving information=20 > concerning changes made in a UDDI registry. These changes can be=20 > scoped based on preferences provided with the request. The=20 > uddiv3Subscription object class is used to model registered UDDIv3=20 > Subscriptions. =20 > =20 >5.38 uddiv3SubscriptionKey=20 > =20 > This is the unique UDDIv3 identifier for a given instance of a=20 > uddiv3Subscription entity. =20 > =20 > ( IANA-ASSIGNED-OID.4.38 NAME 'uddiv3SubscriptionKey'=20 > DESC 'UDDIv3 Subscription unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.39 uddiv3SubscriptionFilter=20 > =20 > This attribute contains the UDDIv3 Subscription Filter, specified as=20 > part of the save_subscription API i.e. the Inquiry API specified as=20 > filtering criteria with a registered subscription. The filtering=20 > criteria limits the scope of a subscription to a subset of registry=20 > records. The get_xx and find_xx APIs are all valid choices for use=20 > as a subscriptionFilter. Only one of these can be chosen for each=20 > subscription.=20 > =20 > ( IANA-ASSIGNED-OID.4.39 NAME 'uddiv3SubscriptionFilter'=20 > DESC 'UDDIv3 Subscription Filter=92=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.40 uddiv3NotificationInterval=20 > =20 > This attribute contains the Notification Interval string. It is of=20 > type xsd:duration and specifies how often Asynchronous change=20 > notifications are to be provided to a subscriber.=20 > =20 > ( IANA-ASSIGNED-OID.4.40 NAME 'uddiv3NotificationInterval'=20 > DESC 'UDDIv3 Notification Interval=92=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.41 uddiv3MaxEntities=20 > =20 > This attribute contains the maximum number of entities to be=20 > returned as part of a subscription notification. It is an integer=20 > and specifies the maximum number of entities in a notification=20 > returned to a subscription listener.=20 > =20 > ( IANA-ASSIGNED-OID.4.41 NAME 'uddiv3MaxEntities'=20 > DESC 'UDDIv3 Subscription maxEntities field=92=20 > EQUALITY integerMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.27=20 > SINGLE-VALUE=20 > )=20 > =20 > =20 >5.42 uddiv3ExpiresAfter=20 > =20 > This attribute specifies the Expiry Time associated with a=20 > Subscription. It is of the XML Schema type xsd:dateTime. =20 > =20 > ( IANA-ASSIGNED-OID.4.42 NAME 'uddiv3ExpiresAfter'=20 > DESC 'UDDIv3 Subscription ExpiresAfter field=92=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 > =20 >5.43 uddiv3BriefResponse=20 > =20 > This attribute is a Boolean flag for Brief Response associated with=20 > a Subscription entity. It controls the level of detail returned to a=20 > subscription listener. The default is "false" when omitted. When set=20 > to "true," it indicates that the subscription results are to be=20 > returned to the subscriber in the form of a keyBag, listing all of=20 > the entities that matched the subscriptionFilter.=20 > =20 > ( IANA-ASSIGNED-OID.4.43 NAME 'uddiv3BriefResponse'=20 > DESC 'UDDIv3 Subscription ExpiresAfter field=92=20 > EQUALITY booleanMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.7=20 > SINGLE-VALUE=20 > )=20 > =20 >5.44 uddiv3EntityKey=20 > =20 > This is the unique UDDIv3 identifier for a given instance of a core=20 > UDDI data structure that is to be logged as an Obituary Entry=20 > uddiv3EntityObituary. When a core UDDIv3 entity is deleted and there=20 > is an active subscription registered against this UDDI entity, an=20 > Obituary entry is created, in which the v3 key of the deleted entry=20 > is logged as part of the uddiv3EntityKey attribute. =20 > =20 > ( IANA-ASSIGNED-OID.4.44 NAME 'uddiv3EntityKey'=20 > DESC 'UDDIv3 Entity unique identifier'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.45 uddiv3EntityCreationTime=20 > =20 > This attribute is used to log the original Creation Time for a UDDI=20 > Entity that is deleted, in the uddiv3EntityObituary entry. =20 > =20 > It is also used in uddiBusinessService and uddiBindingTemplate. A=20 > Move BS operation needs to delete and recreate BT sub-tree due to=20 > lack of support for moving a sub-tree in many LDAPv3 servers. This=20 > attribute is used to save the original creation time of the BT=20 > during a Move BS.=20 > =20 > ( IANA-ASSIGNED-OID.4.45 NAME 'uddiv3EntityCreationTime'=20 > DESC 'UDDIv3 Entity Creation Time'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >5.46 uddiv3EntityDeletionTime=20 > =20 > This attribute is used to log the entity deletion time for a UDDI=20 > Entity that is deleted, in the uddiv3EntityObituary entry. =20 > =20 > ( IANA-ASSIGNED-OID.4.46 NAME 'uddiv3EntityDeletionTime'=20 > DESC 'UDDIv3 Entity Deletion Time'=20 > EQUALITY caseIgnoreMatch=20 > SYNTAX 1.3.6.1.4.1.1466.115.121.1.15=20 > SINGLE-VALUE=20 > )=20 > =20 >6. Object Class Definitions=20 > =20 > Note that OIDs for the object classes in this document have not been=20 > assigned. All OIDs are in brackets, , as a placeholder=20 > until real OIDs are assigned.=20 > =20 >6.1 uddiBusinessEntity=20 > =20 > This structural object class represents a businessEntity.=20 > =20 > ( IANA-ASSIGNED-OID.6.1 NAME 'uddiBusinessEntity'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiBusinessKey $ =20 > uddiName)=20 > MAY ( uddiAuthorizedName $ =20 > uddiOperator $ =20 > uddiDiscoveryURLs $ =20 > uddiDescription $ =20 > uddiIdentifierBag $ =20 > uddiCategoryBag $=20 > uddiv3BusinessKey $=20 > uddiv3DigitalSignature $=20 > uddiv3EntityModificationTime $=20 > uddiv3NodeId)=20 > )=20 > =20 >6.2 uddiContact=20 > =20 > This structural object class represents a contact. It is contained=20 > by an uddiBusinessEntity.=20 > =20 > ( IANA-ASSIGNED-OID.6.2 NAME 'uddiContact'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiPersonName $ =20 > uddiUUID )=20 > MAY ( uddiUseType $ =20 > uddiDescription $ =20 > uddiPhone $ =20 > uddiEMail )=20 > )=20 > =20 >6.3 uddiAddress=20 > =20 > This structural object class represents an address. It is contained=20 > by an uddiContact.=20 > =20 > ( IANA-ASSIGNED-OID.6.3 NAME 'uddiAddress'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiUUID )=20 > MAY ( uddiUseType $ =20 > uddiSortCode $ =20 > uddiTModelKey $=20 > uddiv3TmodelKey $ =20 > uddiAddressLine $=20 > uddiLang)=20 > )=20 > =20 >6.4 uddiBusinessService=20 > =20 > This structural object class represents a businessService.=20 > =20 > ( IANA-ASSIGNED-OID.6.4 NAME 'uddiBusinessService'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiServiceKey $ =20 > uddiName )=20 > MAY ( uddiBusinessKey $ =20 > uddiDescription $ =20 > uddiCategoryBag $=20 > uddiv3ServiceKey $=20 > uddiv3BusinessKey $=20 > uddiv3DigitalSignature $=20 > uddiv3EntityCreationTime $=20 > uddiv3EntityModificationTime $=20 > uddiv3NodeId)=20 > )=20 > =20 >6.5 uddiBindingTemplate=20 > =20 > This structural object class represents a bindingTemplate.=20 > =20 > ( IANA-ASSIGNED-OID.6.5 NAME 'uddiBindingTemplate'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiBindingKey )=20 > MAY ( uddiServiceKey $ =20 > uddiDescription $ =20 > uddiAccessPoint $=20 > uddiHostingRedirector =20 > uddiCategoryBag $=20 > uddiv3BindingKey $=20 > uddiv3ServiceKey $=20 > uddiv3DigitalSignature $=20 > uddiv3EntityCreationTime $=20 > uddiv3NodeId)=20 > )=20 > =20 >=20 >6.6 uddiTModelInstanceInfo=20 > =20 > This structural object class represents a tModelInstanceInfo. It is=20 > contained by an uddiBindingTemplate.=20 > =20 > ( IANA-ASSIGNED-OID.6.6 NAME 'uddiTModelInstanceInfo'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiTModelKey )=20 > MAY ( uddiDescription $ =20 > uddiInstanceDescription $ =20 > uddiInstanceParms $ =20 > uddiOverviewDescription $ =20 > uddiOverviewURL $=20 > uddiv3TmodelKey)=20 > )=20 > =20 >6.7 uddiTModel=20 > =20 > This structural object class represents a tModel.=20 > =20 > ( IANA-ASSIGNED-OID.6.7 NAME 'uddiTModel'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiTModelKey $ =20 > uddiName )=20 > MAY ( uddiAuthorizedName $ =20 > uddiOperator $ =20 > uddiDescription $ =20 > uddiOverviewDescription $ =20 > uddiOverviewURL $ =20 > uddiIdentifierBag $ =20 > uddiCategoryBag $ =20 > uddiIsHidden =20 > uddiv3TModelKey $=20 > uddiv3DigitalSignature $=20 > uddiv3NodeId)=20 > )=20 > =20 >6.8 uddiPublisherAssertion=20 > =20 > This structural object class represents a publisherAssertion.=20 > =20 > ( IANA-ASSIGNED-OID.6.8 NAME 'uddiPublisherAssertion'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiFromKey $ =20 > uddiToKey $ =20 > uddiKeyedReference $ =20 > uddiUUID )=20 > MAY ( uddiv3DigitalSignature $=20 > uddiv3NodeId)=20 > )=20 > =20 > The following are object class definitions to model new data=20 > structures needed to implement UDDIv3 information model. These=20 > object class definitions have the =91uddiv3=92 prefix to indicate tha= t=20 > these attributes represent UDDI information model elements unique to=20 > UDDIv3.=20 > =20 >6.9 uddiv3Subscription=20 > =20 > This structural object class represents a Subscription entity.=20 > =20 > ( IANA-ASSIGNED-OID.6.9 NAME 'uddiv3Subscription'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiv3SubscriptionFilter $ =20 > uddiUUID)=20 > MAY ( uddiAuthorizedName $ =20 > uddiv3SubscriptionKey $ =20 > uddiv3BindingKey $ =20 > uddiv3NotificationInterval $ =20 > uddiv3MaxEntities $ =20 > uddiv3ExpiresAfter $ =20 > uddiv3BriefResponse $ =20 > uddiv3NodeId)=20 > )=20 > =20 >6.10 uddiv3EntityObituary=20 > =20 > This structural object class represents an Obituary entry for and=20 > stores obituary information for deleted UDDIv3 entities needed for=20 > handling Subscriptions.=20 > =20 > ( IANA-ASSIGNED-OID.6.10 NAME 'uddiv3EntityObituary'=20 > SUP top=20 > STRUCTURAL=20 > MUST ( uddiv3EntityKey $ =20 > uddiUUID)=20 > MAY ( uddiAuthorizedName $ =20 > uddiv3EntityCreationTime $=20 > uddiv3EntityDeletionTime $=20 > uddiv3NodeId)=20 > )=20 > =20 >7. Name Forms=20 > =20 > This section defines the required hierarchical structure rules and=20 > naming attributes for the object classes defined in section 6.=20 > =20 > Note that OIDs for the structure rules in this document have not=20 > been assigned. All OIDs are in brackets, , as a=20 > placeholder until real OIDs are assigned.=20 s/OID-TBD/OID-ASSIGNED-OID/ =20 >7.1 uddiBusinessEntityNameForm=20 > =20 > This name form defines the naming attribute for a businessEntity.=20 > =20 > ( IANA-ASSIGNED-OID.15.1 NAME 'uddiBusinessEntityNameForm'=20 > OC uddiBusinessEntity=20 > MUST ( uddiBusinessKey )=20 > )=20 > =20 >7.2 uddiContactNameForm=20 > =20 > This name form defines the naming attribute for a contact.=20 > =20 > ( IANA-ASSIGNED-OID.15.2 NAME 'uddiContactNameForm'=20 > OC uddiContact=20 > MUST ( uddiUUID )=20 > )=20 > =20 >7.3 uddiAddressNameForm=20 > =20 > This name form defines the naming attribute for an address.=20 > =20 > ( IANA-ASSIGNED-OID.15.3 NAME 'uddiAddressNameForm'=20 > OC uddiAddress=20 > MUST ( uddiUUID )=20 > )=20 > =20 >7.4 uddiBusinessServiceNameForm=20 > =20 > This name form defines the naming attribute for a businessService.=20 > =20 > ( IANA-ASSIGNED-OID.15.4 NAME 'uddiBusinessServiceNameForm'=20 > OC uddiBusinessService=20 > MUST ( uddiServiceKey )=20 > )=20 > =20 >Bergeson,Boogert & Nanjundaswamy Internet-Draft 28=20 > > > > > > > > > LDAP Schema for UDDI November 2003=20 >=20 >=20 > =20 >7.5 uddiBindingTemplateNameForm=20 > =20 > This name form defines the naming attribute for a bindingTemplate.=20 > =20 > ( IANA-ASSIGNED-OID.15.5 NAME 'uddiBindingTemplateNameForm'=20 > OC uddiBindingTemplate=20 > MUST ( uddiBindingKey )=20 > )=20 > =20 >7.6 uddiTModelInstanceInfoNameForm=20 > =20 > This name form defines the naming attribute for a=20 > tModelInstanceInfo.=20 > =20 > ( IANA-ASSIGNED-OID.15.6 NAME 'uddiTModelInstanceInfoNameForm'=20 > OC uddiTModelInstanceInfo=20 > MUST ( uddiTModelKey )=20 > )=20 > =20 >7.7 uddiTModelNameForm=20 > =20 > This name form defines the naming attribute for a tModel.=20 > =20 > ( IANA-ASSIGNED-OID.15.7 NAME 'uddiTModelNameForm'=20 > OC uddiTModel=20 > MUST ( uddiTModelKey )=20 > )=20 > =20 >7.8 uddiPublisherAssertionNameForm=20 > =20 > This name form defines the naming attribute for a=20 > publisherAssertion.=20 > =20 > ( IANA-ASSIGNED-OID.15.8 NAME 'uddiPublisherAssertionNameForm'=20 > OC uddiPublisherAssertion=20 > MUST ( uddiUUID )=20 > )=20 > =20 >7.9 uddiv3SubscriptionNameForm=20 > =20 > This name form defines the naming attribute for a Subscription.=20 > =20 > ( IANA-ASSIGNED-OID.15.9 NAME 'uddiv3SubscriptionNameForm'=20 > OC uddiv3Subscription=20 > MUST ( uddiUUID )=20 > )=20 > =20 >7.10 uddiv3EntityObituaryNameForm=20 > =20 > This name form defines the naming attribute for an Entity Obituary.=20 > =20 > ( IANA-ASSIGNED-OID.15.10 NAME 'uddiv3EntityObituary'=20 > =20 >Bergeson,Boogert & Nanjundaswamy Internet-Draft 29=20 > > > > > > > > > LDAP Schema for UDDI November 2003=20 >=20 >=20 > OC uddiv3EntityObituary=20 > MUST ( uddiUUID )=20 > )=20 > =20 >8. DIT Structure Rules=20 > =20 > This section defines the required hierarchical structure rules for=20 > the object classes defined in section 6.=20 > =20 > Note that rule identifiers defined here show the relationship=20 > between structure rules. Implementations may use different=20 > identifiers but must follow the same hierarchical model.=20 Note that DIT Structure Rules are generally under administrative, not implementation, control. >8.1 uddiBusinessEntityStructureRule=20 > =20 > ( 1=20 > NAME 'uddiBusinessEntityStructureRule'=20 > FORM uddiBusinessEntityNameForm=20 > )=20 > =20 >8.2 uddiContactStructureRule=20 > =20 > This structure rule defines the object class containment for a=20 > contact.=20 > =20 > ( 2=20 > NAME 'uddiContactStructureRule'=20 > FORM uddiContactNameForm=20 > SUP ( 1 )=20 > )=20 > =20 >8.3 uddiAddressStructureRule=20 > =20 > This structure rule defines the object class containment for a=20 > address.=20 > =20 > ( 3=20 > NAME 'uddiAddressStructureRule'=20 > FORM uddiAddressNameForm=20 > SUP ( 2 )=20 > )=20 > =20 >8.4 uddiBusinessServiceStructureRule=20 > =20 > This structure rule defines the object class containment for a=20 > businessService.=20 > =20 > ( 4=20 > NAME 'uddiBusinessServiceStructureRule'=20 > FORM uddiBusinessServiceNameForm=20 > SUP ( 1 )=20 > )=20 > =20 > =20 >Bergeson,Boogert & Nanjundaswamy Internet-Draft 30=20 > > > > > > > > > LDAP Schema for UDDI November 2003=20 >=20 >=20 >8.5 uddiBindingTemplateStructureRule=20 > =20 > This structure rule defines the object class containment for a=20 > bindingTemplate.=20 > =20 > ( 5=20 > NAME 'uddiBindingTemplateStructureRule'=20 > FORM uddiBindingTemplateNameForm=20 > SUP ( 4 )=20 > )=20 > =20 >8.6 uddiTModelInstanceInfoStructureRule=20 > =20 > This structure rule defines the object class containment for a=20 > tModelInstanceInfo.=20 > =20 > ( 6=20 > NAME 'uddiTModelInstanceInfoStructureRule'=20 > FORM uddiTModelInstanceInfoNameForm=20 > SUP ( 5 )=20 > )=20 > =20 >8.7 uddiTModelStructureRule=20 > =20 > ( 7=20 > NAME 'uddiTModelStructureRule'=20 > FORM uddiTModelNameForm=20 > )=20 > =20 >8.8 uddiPublisherAssertion=20 > =20 > ( 8=20 > NAME 'uddiPublisherAssertionStructureRule'=20 > FORM uddiPublisherAssertionNameForm=20 > )=20 > =20 >8.9 uddiv3SubscriptionStructureRule=20 > =20 > ( 9=20 > NAME 'uddiv3SubscriptionStructureRule'=20 > FORM uddiv3SubscriptionNameForm=20 > )=20 > =20 >8.10 uddiv3EntityObituaryStructureRule=20 > =20 > ( 10=20 > NAME 'uddiv3EntityObituaryStructureRule'=20 > FORM uddiv3EntityObituaryNameForm=20 > )=20 > =20 >9. Security Considerations=20 > =20 > =20 >Bergeson,Boogert & Nanjundaswamy Internet-Draft 31=20 > > > > > > > > > LDAP Schema for UDDI November 2003=20 >=20 >=20 > Storing UDDI data into the directory enables the data to be examined=20 > and used outside the environment in which it was originally created. = =20 > The directory entry containing the UDDI data could be read and=20 > modified within the constraints imposed by the access control=20 > mechanisms of the directory. With UDDIv3, publishers can digitally=20 > sign entries enabling registry clients to validate the integrity of=20 > UDDI entries read from the UDDIv3 registry by verifying the digital=20 > signature. =20 > =20 > Other general LDAP [LDAPv3] security considerations apply. Some of=20 > the UDDI attributes like AccessPoints for services may contain=20 > sensitive information. Use of strong authentication mechanisms and=20 > data integrity/confidentiality services [RFC2829][RFC2830] is=20 > advised.=20 I think many more of these attributes may contain sensitive information. =20 >10. IANA Considerations=20 >=20 >10.1. Object Identifier Registration=20 >=20 > It is requested that IANA register upon Standards Action an LDAP=20 > Object Identifier for use in this technical specification.=20 > =20 > Subject: Request for LDAP OID Registration=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > Comments:=20 > Identifies the UDDI schema elements=20 > =20 > =20 >10.2. Registration of the uddiBusinessKey descriptor=20 The following descriptor registrations should be condensed into one subsection using a table to communicate the set of values to be registered. Use RFC 3703 (or other recent schema RFCs) as an example. > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBusinessKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBusinessKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.1=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.3. Registration of the uddiAuthorizedName descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiAuthorizedName' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiAuthorizedName=20 > =20 >Bergeson,Boogert & Nanjundaswamy Internet-Draft 32=20 > > > > > > > > > LDAP Schema for UDDI November 2003=20 >=20 >=20 > Object Identifier: IANA-ASSIGNED-OID.4.2=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.4. Registration of the uddiOperator descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiOperator' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiOperator=20 > Object Identifier: IANA-ASSIGNED-OID.4.3=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.5. Registration of the uddiName descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiName' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiName=20 > Object Identifier: IANA-ASSIGNED-OID.4.4=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.6. Registration of the uddiDescription descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiDescription' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiDescription=20 > Object Identifier: IANA-ASSIGNED-OID.4.5=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.7. Registration of the uddiDiscoveryURLs descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiDiscoveryURLs' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiDiscoveryURLs=20 > Object Identifier: IANA-ASSIGNED-OID.4.6=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.8. Registration of the uddiUseType descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiUseType' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiUseType=20 > Object Identifier: IANA-ASSIGNED-OID.4.7=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.9. Registration of the uddiPersonName descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiPersonName' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiPersonName=20 > Object Identifier: IANA-ASSIGNED-OID.4.8=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.10. Registration of the uddiPhone descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiPhone' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiPhone=20 > Object Identifier: IANA-ASSIGNED-OID.4.9=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.11. Registration of the uddiEMail descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiEMail' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiEMail=20 > Object Identifier: IANA-ASSIGNED-OID.4.10=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.12. Registration of the uddiSortCode descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiSortCode' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiSortCode=20 > Object Identifier: IANA-ASSIGNED-OID.4.11=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.13. Registration of the uddiTModelKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiTModelKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiTModelKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.12=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.14. Registration of the uddiAddressLine descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiAddressLine' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiAddressLine=20 > Object Identifier: IANA-ASSIGNED-OID.4.13=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.15. Registration of the uddiIdentifierBag descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiIdentifierBag' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiIdentifierBag=20 > Object Identifier: IANA-ASSIGNED-OID.4.14=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.16. Registration of the uddiCategoryBag descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiCategoryBag' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiCategoryBag=20 > Object Identifier: IANA-ASSIGNED-OID.4.15=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.17. Registration of the uddiKeyedReference descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiKeyedReference' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiKeyedReference=20 > Object Identifier: IANA-ASSIGNED-OID.4.16=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.18. Registration of the uddiServiceKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiServiceKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiServiceKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.17=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.19. Registration of the uddiBindingKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBindingKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBindingKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.18=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.20. Registration of the uddiAccessPoint descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiAccessPoint' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiAccessPoint=20 > Object Identifier: IANA-ASSIGNED-OID.4.19=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.21. Registration of the uddiHostingRedirector descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiHostingRedirector' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiHostingRedirector=20 > Object Identifier: IANA-ASSIGNED-OID.4.20=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.22. Registration of the uddiInstanceDescription descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiInstanceDescription' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiInstanceDescription=20 > Object Identifier: IANA-ASSIGNED-OID.4.21=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.23. Registration of the uddiInstanceParms descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiInstanceParms' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiInstanceParms=20 > Object Identifier: IANA-ASSIGNED-OID.4.22=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.24. Registration of the uddiOverviewDescription descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiOverviewDescription' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiOverviewDescription=20 > Object Identifier: IANA-ASSIGNED-OID.4.23=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.25. Registration of the uddiOverviewURL descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiOverviewURL' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiOverviewURL=20 > Object Identifier: IANA-ASSIGNED-OID.4.24=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.26. Registration of the uddiFromKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > =20 > 'uddiFromKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiFromKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.25=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.27. Registration of the uddiToKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiToKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiToKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.26=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.28. Registration of the uddiUUID descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiUUID' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiUUID=20 > Object Identifier: IANA-ASSIGNED-OID.4.27=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.29. Registration of the uddiIsHidden descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiIsHidden' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiIsHidden=20 > Object Identifier: IANA-ASSIGNED-OID.4.28=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 >=20 >10.30. Registration of the uddiIsProjection descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiIsProjection' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiIsProjection=20 > Object Identifier: IANA-ASSIGNED-OID.4.29=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.31. Registration of the uddiLang descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiLang' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiLang=20 > Object Identifier: IANA-ASSIGNED-OID.4.30=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.32. Registration of the uddiv3BusinessKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3BusinessKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3BusinessKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.31=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.33. Registration of the uddiv3ServiceKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3ServiceKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3ServiceKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.32=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.34. Registration of the uddiv3BindingKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3BindingKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3BindingKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.33=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.35. Registration of the uddiv3TModelKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3TModelKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3TModelKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.34=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.36. Registration of the uddiv3DigitalSignature descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3DigitalSignature' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3DigitalSignature=20 > Object Identifier: IANA-ASSIGNED-OID.4.35=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.37. Registration of the uddiv3NodeId descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3NodeId' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3NodeId=20 > Object Identifier: IANA-ASSIGNED-OID.4.36=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.38. Registration of the uddiv3EntityModificationTime descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3EntityModificationTime' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3EntityModificationTime=20 > Object Identifier: IANA-ASSIGNED-OID.4.37=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.39. Registration of the uddiv3SubscriptionKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3SubscriptionKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3SubscriptionKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.38=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.40. Registration of the uddiv3SubscriptionFilter descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3SubscriptionFilter' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3SubscriptionFilter=20 > Object Identifier: IANA-ASSIGNED-OID.4.39=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.41. Registration of the uddiv3NotificationInterval descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3NotificationInterval' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3NotificationInterval=20 > Object Identifier: IANA-ASSIGNED-OID.4.40=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.42. Registration of the uddiv3MaxEntities descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3MaxEntities' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3MaxEntities=20 > Object Identifier: IANA-ASSIGNED-OID.4.41=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.43. Registration of the uddiv3ExpiresAfter descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3ExpiresAfter' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3ExpiresAfter=20 > Object Identifier: IANA-ASSIGNED-OID.4.42=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.44. Registration of the uddiv3BriefResponse descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3BriefResponse' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3BriefResponse=20 > Object Identifier: IANA-ASSIGNED-OID.4.43=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.45. Registration of the uddiv3EntityKey descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3EntityKey' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3EntityKey=20 > Object Identifier: IANA-ASSIGNED-OID.4.44=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.46. Registration of the uddiv3EntityCreationTime descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3EntityCreationTime' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3EntityCreationTime=20 > Object Identifier: IANA-ASSIGNED-OID.4.45=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.47. Registration of the uddiv3EntityDeletionTime descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3EntityDeletionTime' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3EntityDeletionTime=20 > Object Identifier: IANA-ASSIGNED-OID.4.46=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Attribute Type=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.48. Registration of the uddiBusinessEntity descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBusinessEntity' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBusinessEntity=20 > Object Identifier: IANA-ASSIGNED-OID.6.1=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.49. Registration of the uddiContact descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiContact' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiContact=20 > Object Identifier: IANA-ASSIGNED-OID.6.2=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.50. Registration of the uddiAddress descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiAddress' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiAddress=20 > Object Identifier: IANA-ASSIGNED-OID.6.3=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.51. Registration of the uddiBusinessService descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBusinessService' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBusinessService=20 > Object Identifier: IANA-ASSIGNED-OID.6.4=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.52. Registration of the uddiBindingTemplate descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBindingTemplate' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBindingTemplate=20 > Object Identifier: IANA-ASSIGNED-OID.6.5=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.53. Registration of the uddiTModelInstanceInfo descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiTModelInstanceInfo' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiTModelInstanceInfo=20 > Object Identifier: IANA-ASSIGNED-OID.6.6=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.54. Registration of the uddiTModel descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiTModel' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiTModel=20 > Object Identifier: IANA-ASSIGNED-OID.6.7=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.55. Registration of the uddiPublisherAssertion descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiPublisherAssertion' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiPublisherAssertion=20 > Object Identifier: IANA-ASSIGNED-OID.6.8=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.56. Registration of the uddiv3Subscription descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3Subscription' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3Subscription=20 > Object Identifier: IANA-ASSIGNED-OID.6.9=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.57. Registration of the uddiv3EntityObituary descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3EntityObituary' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3EntityObituary=20 > Object Identifier: IANA-ASSIGNED-OID.6.10=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Object Class=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.58. Registration of the uddiBusinessEntityNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBusinessEntityNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBusinessEntityNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.1=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.59. Registration of the uddiContactNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiContactNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiContactNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.2=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.60. Registration of the uddiAddressNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiAddressNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiAddressNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.3=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.61. Registration of the uddiBusinessServiceNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBusinessServiceNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBusinessServiceNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.4=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.62. Registration of the uddiBindingTemplateNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiBindingTemplateNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiBindingTemplateNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.5=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.63. Registration of the uddiTModelInstanceInfoNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiTModelInstanceInfoNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiTModelInstanceInfoNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.6=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.64. Registration of the uddiTModelNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiTModelNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiTModelNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.7=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.65. Registration of the uddiPublisherAssertionNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiPublisherAssertionNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiPublisherAssertionNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.8=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.66. Registration of the uddiv3SubscriptionNameForm descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3SubscriptionNameForm' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3SubscriptionNameForm=20 > Object Identifier: IANA-ASSIGNED-OID.15.9=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 >10.67. Registration of the uddiv3EntityObituary descriptor=20 > =20 > It is requested that IANA register upon Standards Action the LDAP=20 > 'uddiv3EntityObituary' descriptor.=20 > =20 > Subject: Request for LDAP Descriptor Registration=20 > Descriptor (short name): uddiv3EntityObituary=20 > Object Identifier: IANA-ASSIGNED-OID.15.10=20 > Person & email address to contact for further information:=20 > Bruce Bergeson =20 > Usage: Name Form=20 > Specification: RFC XXXX=20 > Author/Change Controller: IESG=20 > =20 > =20 >11. Normative References=20 > =20 > [LDAPv3] J. Hodges, R. Morgan, "Lightweight Directory Access=20 > Protocol (v3):Technical Specification", Internet=20 > Standard, September 2002, Available as RFC 3377=20 > =20 > [RFC2251] M. Wahl, S. Kille and T. Howes, "Lightweight Directory=20 > Access Protocol (v3)", Internet Standard, December,=20 > 1997. =20 > =20 > [RFC2252] M. Wahl, A. Coulbeck, S. Kille and T. Howes, =20 > "Lightweight Directory Access Protocol (v3): Attribute=20 > Syntax Definitions", Internet Standard, December, 1997. = =20 > =20 > [UDDI] UDDI.ORG, "UDDI version 2.03 Data Structure Reference,"=20 > http://uddi.org/pubs/DataStructure-V2.03-Published- > 20020719.htm=20 > =20 > "UDDI Version 2.04 API Specification",=20 > http://uddi.org/pubs/ProgrammersAPI-V2.04-Published- > 20020719.htm=20 > =20 > [UDDIv3] UDDI Version 3.0, Published Specification, 19 July 2002=20 > http://uddi.org/pubs/uddi-v3.00-published-20020719.htm=20 > =20 > [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate=20 > Requirement Levels," Internet Standard, December, 1997.=20 > Available as RFC2253=20 > =20 > [RFC2829] M. Wahl, H. Alvestrand, J. Hodges and R. Morgan,=20 > "Authentication Methods for LDAP," Internet Standard,=20 > May 2000.=20 > =20 > [RFC2830] J. Hodges, R. Morgan and M. Wahl, "Lightweight=20 > Directory Access Protocol (v3): Extension for Transport=20 > Layer Security," Internet Standard, May 2000=20 > =20 > [uuid] Paul J. Leach, Rich Salz, "UUIDs and GUIDs", Internet=20 > Draft, February 1998=20 > =20 > [XML] Extensible Markup Language (XML) 1.0 (Second Edition)=20 > W3C Recommendation 6 October 2000=20 > http://www.w3.org/TR/REC-xml=20 > =20 > [URL] Uniform Resource Locators as defined in =20 > T. Berners-Lee et al., "Uniform Resource Identifiers=20 > (URI): Generic Syntax", Internet Standard, August 1998.=20 > Available as RFC 2396. =20 > http://www.ietf.org/rfc/rfc2396.txt=20 > > [HTTP] R. Fielding et al.,"Hypertext Transfer Protocol --=20 > HTTP/1.1", Internet Standard, June 1999. Available as=20 > RFC 2616.=20 > http://www.w3.org/Protocols/rfc2616/rfc2616.txt=20 > =20 > =20 >12. Author's Addresses=20 > =20 > Bruce Bergeson=20 > Novell, Inc.=20 > Mail Stop PRV-H411=20 > 1800 S Novell Place=20 > Provo, UT 84606=20 > =20 > Phone: +1 801 861 3854=20 > Email: bruce.bergeson@novell.com=20 > =20 > =20 > Kent Boogert=20 > Novell, Inc.=20 > 1800 S Novell Place=20 > Provo, UT 84606=20 > =20 > Phone: +1 801 861 3212=20 > Email: kent.boogert@novell.com=20 > =20 > =20 > Vijay Nanjundaswamy=20 > Novell Software Development (I) Pvt Ltd.=20 > 7th Mile, Hosur Road,=20 > Bangalore 560068=20 > India=20 > =20 > Phone: +11 9180 573 1858 =20 > Email: knvijay@novell.com=20 > > > > > > > > > > > > > > > > > >Intellectual Property Rights=20 >=20 > The IETF takes no position regarding the validity or scope of any=20 > intellectual property or other rights that might be claimed to=20 > pertain to the implementation or use of the technology described in=20 > this document or the extent to which any license under such rights=20 > might or might not be available; neither does it represent that it=20 > has made any effort to identify any such rights. Information on the=20 > IETF's procedures with respect to rights in standards-track and=20 > standards-related documentation can be found in BCP-11. Copies of=20 > claims of rights made available for publication and any assurances=20 > of licenses to be made available, or the result of an attempt made=20 > to obtain a general license or permission for the use of such=20 > proprietary rights by implementors or users of this specification=20 > can be obtained from the IETF Secretariat.=20 > =20 > The IETF invites any interested party to bring to its attention any=20 > copyrights, patents or patent applications, or other proprietary=20 > rights which may cover technology that may be required to practice=20 > this standard. Please address the information to the IETF Executive=20 > Director.=20 > =20 >=20 >Full Copyright Statement=20 > =20 > Copyright (C) The Internet Society (2003). All Rights Reserved.=20 > =20 > This document and translations of it may be copied and furnished to=20 > others, and derivative works that comment on or otherwise explain it=20 > or assist in its implementation may be prepared, copied, published=20 > and distributed, in whole or in part, without restriction of any=20 > kind, provided that the above copyright notice and this paragraph=20 > are included on all such copies and derivative works. However, this=20 > document itself may not be modified in any way, such as by removing=20 > the copyright notice or references to the Internet Society or other=20 > Internet organizations, except as needed for the purpose of=20 > developing Internet standards in which case the procedures for=20 > copyrights defined in the Internet Standards process must be=20 > followed, or as required to translate it into languages other than=20 > English.=20 > =20 > The limited permissions granted above are perpetual and will not be=20 > revoked by the Internet Society or its successors or assigns.=20 > =20 > This document and the information contained herein is provided on an=20 > "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING=20 > TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING=20 > BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION=20 > HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=20 > MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. =20 > =20 _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Wed Apr 7 20:46:55 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24502 for ; Wed, 7 Apr 2004 20:46:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBNgZ-0001Qp-Ah for ldap-dir-archive@odin.ietf.org; Wed, 07 Apr 2004 20:46:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i380kRaL005503 for ldap-dir-archive@odin.ietf.org; Wed, 7 Apr 2004 20:46:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBNgZ-0001Qg-6m for ldap-dir-web-archive@optimus.ietf.org; Wed, 07 Apr 2004 20:46:27 -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 UAA24490 for ; Wed, 7 Apr 2004 20:46:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBNgW-0005GM-00 for ldap-dir-web-archive@ietf.org; Wed, 07 Apr 2004 20:46:24 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BBLV7-0007FB-01 for ldap-dir-web-archive@ietf.org; Wed, 07 Apr 2004 18:26:29 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BBLK5-0003qA-Dv for ldap-dir-web-archive@ietf.org; Wed, 07 Apr 2004 18:15:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBLK1-0006Im-Vk; Wed, 07 Apr 2004 18:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBLJd-00061V-9z for ldap-dir@optimus.ietf.org; Wed, 07 Apr 2004 18:14:37 -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 SAA16906 for ; Wed, 7 Apr 2004 18:14:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBLJa-0006GN-00 for ldap-dir@ietf.org; Wed, 07 Apr 2004 18:14:34 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBKD3-0002y1-00 for ldap-dir@ietf.org; Wed, 07 Apr 2004 17:03:47 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BBIDT-0005sw-00; Wed, 07 Apr 2004 14:56:03 -0400 Received: from c-24-17-217-71.client.comcast.net ([24.17.217.71]) by mx2.foretec.com with smtp (Exim 4.24) id 1BBI2O-0003Ym-ED; Wed, 07 Apr 2004 14:44:39 -0400 Received: from [181.127.59.219] by c-24-17-217-71.client.comcast.net SMTP id 8zt1Fu5M2ms7uZ; Sun, 07 Apr 2002 16:38:38 -0300 Message-ID: From: "Stephanie Yang" Reply-To: "Stephanie Yang" To: , , , , , , , Date: Sun, 07 Apr 02 16:38:38 GMT X-Mailer: Microsoft Outlook Express 6.00.2462.0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="2CB._..1DE_..53.1" X-Priority: 3 X-MSMail-Priority: Normal X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=5.6 required=5.0 tests=AWL,DATE_SPAMWARE_Y2K, MISSING_MIMEOLE autolearn=no version=2.60 X-Spam-Report: * 4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting * 1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE * -0.0 AWL AWL: Auto-whitelist adjustment Subject: [Ldap-dir] Before the explosion buy at any price xyrjnmi hx a bbsoe Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , --2CB._..1DE_..53.1 Content-Type: text/plain; Content-Transfer-Encoding: quoted-printable ***ARET****ARET****ARET****ARET****ARET****ARET*** Undervalued Market Report For Largest Percentage Gain Leaders Opening Price: 2 cents Immediate Target: 10 cents in 10 days Near-Term Proj. High: 25 cents Current Market Value (Approx): 1.5 million **Our Picks Are On Fire!** Our last pick for huge percentage gains (GDLS) soared from 23 to .83 (261% on 3/29) immediately following our report. We believe the gains for ARET will run circles around all our other picks for the year. Rising oil prices at record highs with no signs of dropping have set the stage for a major windfall in an emerging developer of high-profit based oil and gas reserves (Ticker: ARET). Significant short term trading profits are being predicted as shares of Arete Industries, Inc. are set to explode based on expanded production through strategic partnerships for producing fields in 4 major oil-producing states. ARET just released major news and we believe there is much more to follow. There is strong evidence of big block buying indicating that an explosive move is coming on a huge near-term announcement. As recently reported, ARET is executing the launch of a $1 Billion financed "Master Energy Fund" which is capped at $100 Million increments to fund the Company's energy projects. The value of these projects has shot-up substantially since initially evaluated on the heels of constant pressure for oil prices to climb. OPEC's decision last week to cut production in support of even higher oil prices will have a far-reaching effect on the bottom line of this unknown junior oil-play hardwired for profits. ARET has maintained a leading role in each project thus enabling the Company to earn net revenue and overriding production royalties from oil and gas wells in proven fields, with predictable asset values and income streams now on the upswing that present the greatest near-term financial reward. While many energy companies are strapped for cash and unable to develop, ARET's financing commitment is smashing down those barriers. ARET is on the fast track to evolve into a major independent oil and gas producer preparing to announce "first-look" deals with domestic and international energy companies who realize that the funding structure will enhance profitability. Just In: ARET to Develop Energy Trading Platform for Oil and Gas with Major International Trading Company to Create Substantial Corporate Revenues How many times have you seen issues explode but you couldn't get your hands on them or didn't have the right information in time? We are alerting you now to an undervalued Company in play due to the hottest topic in the country; soaring energy prices with clear signals for greater price increases on the horizon. Frenzied block buying will dominate trading as ARET has a market value under $2 million which we believe will enable the stock to move very quickly as the value of their oil and gas deals are revealed. Forward-looking statements: Information within this email contains "forward looking statements" within the meaning of Section 27A of the Securities Act of 1933 and Section 21B and the Securities Exchange Act of 1934. Any statements that express or involve discussions with respect to predictions, goals, expectations, beliefs, plans, projections, objectives, assumptions or future events or performance are not statements of historical fact and may be "forward looking statements". Forward looking statements are based upon expectations, estimates and projections, at the time the statements are made that involve a number of risks and uncertainties which could cause actual results or events to differ materially from those presently anticipated. Forward looking statements in this action may be identified through the use of words such as: "projects", "foresee", "expects", "estimates", "believes", "understands", "will", "anticipates", or that by statements indicating certain actions "may", "could", or "might" occur. All information provided within this email pertaining to investing, stocks, securities must be understood as information provided and not investment advice. Emerging Equity Alert advises all readers and subscribers to seek advice from a registered professional securities representative before deciding to trade in stocks featured within this email. None of the material within= this report shall be construed as any kind of investment advice. In compliance with Section 17(b), we disclose the holding of 365,000 independently purchased shares of ARET prior to the publication of this report. Be aware of an inherent conflict of interest resulting from such holdings due to our intent to profit from the liquidation of these shares.= Shares may be sold at any time, even after positive statements have been made regarding the above company. Since we own shares, there is an inherent conflict of interest in our statements and opinions. Readers of this publication are cautioned not to place undue reliance on forward- looking statements, which are based on certain assumptions and expectation= s involving various risks and uncertainties, that could cause results to differ materially from those set forth in the forward-looking statements. = yzlqcl ay zdbijsxgwfdzpz xzfndmyavykwroppkgvaaljmb kzgsteqin n zvhvljjwsjad --2CB._..1DE_..53.1-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Wed Apr 7 23:11:53 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10621 for ; Wed, 7 Apr 2004 23:11:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBPwq-00068p-E3 for ldap-dir-archive@odin.ietf.org; Wed, 07 Apr 2004 23:11:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i383BOCe023566 for ldap-dir-archive@odin.ietf.org; Wed, 7 Apr 2004 23:11:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBPwm-00061X-Ig for ldap-dir-web-archive@optimus.ietf.org; Wed, 07 Apr 2004 23:11:23 -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 XAA10617 for ; Wed, 7 Apr 2004 23:11:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBPwi-0007id-00 for ldap-dir-web-archive@ietf.org; Wed, 07 Apr 2004 23:11:16 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BBO6g-0001lh-00 for ldap-dir-web-archive@ietf.org; Wed, 07 Apr 2004 21:13:26 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BBNrl-0005kt-0Q for ldap-dir-web-archive@ietf.org; Wed, 07 Apr 2004 20:58:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBNrk-00052X-Or; Wed, 07 Apr 2004 20:58:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBNrV-00051v-U6 for ldap-dir@optimus.ietf.org; Wed, 07 Apr 2004 20:57:45 -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 UAA25975 for ; Wed, 7 Apr 2004 20:57:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBNrT-0006zv-00 for ldap-dir@ietf.org; Wed, 07 Apr 2004 20:57:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBLjy-00013q-00 for ldap-dir@ietf.org; Wed, 07 Apr 2004 18:41:52 -0400 Received: from [195.162.169.213] (helo=132.151.6.1) by ietf-mx with smtp (Exim 4.12) id 1BBKPQ-00054t-00; Wed, 07 Apr 2004 17:16:33 -0400 Received: from 160.139.6.234 by web510.mail.yahoo.com; Thu, 08 Apr 2004 04:11:14 +0600 Message-ID: From: "Robt Glenn" To: ldap-dir@ietf.org Date: Thu, 08 Apr 2004 02:16:14 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8696036056126487349" X-CS-IP: 108.91.105.227 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=7.1 required=5.0 tests=BIZ_TLD,HTML_50_60, HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_MESSAGE, HTML_TAG_EXISTS_TBODY,LINES_OF_YELLING,MIME_HTML_ONLY, MIME_HTML_ONLY_MULTI,OBFUSCATING_COMMENT,RCVD_NUMERIC_HELO autolearn=no version=2.60 X-Spam-Report: * 0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 HTML_FONT_BIG BODY: HTML has a big font * 0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette * 0.1 HTML_TAG_EXISTS_TBODY BODY: HTML has "tbody" tag * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.2 HTML_50_60 BODY: Message is 50% to 60% HTML * 0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain * 1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts * 4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text Subject: [Ldap-dir] didn't go to college - that's ok we'll give you a diploma Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , ----8696036056126487349 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable GET

 

transfix orwellian there'd bicker curio= changeover marty acrimonious checksum alewife=20vagina comfort cuba clatter pretend jealous = fever assert prank horror derrick throaty khmer scenery=20 calibre litigant chive clump recurrent= wizard filtrate confound silt consign detent ferreira sinister coke inter= vene anterior arachnid palindromic irreverent cut maple argumentative immo= desty stablemen extradition appease flexural=20 kuhn reconcile airspace indian tepee ag= amemnon amide exhaustion hoop decent sauterne yaounde coerce owing recusan= t=20 remington martial selectmen cassius edmo= nds mist buzzing cozy agrimony giuseppe jargon argonaut eavesdrop rule dec= imal becky craftspeople gnat prostitution customhouse paste begotten fixtu= re chiropractor deem watts cackle presage windowsill rasa apace ct biparti= san organic=20 ----8696036056126487349-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Sun Apr 11 18:30:05 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11109 for ; Sun, 11 Apr 2004 18:30:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCnSN-0002aG-UA for ldap-dir-archive@odin.ietf.org; Sun, 11 Apr 2004 18:29:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3BMTd8M009928 for ldap-dir-archive@odin.ietf.org; Sun, 11 Apr 2004 18:29:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCnSN-0002a3-QC for ldap-dir-web-archive@optimus.ietf.org; Sun, 11 Apr 2004 18:29:39 -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 SAA11102 for ; Sun, 11 Apr 2004 18:29:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCnSK-0006Mu-00 for ldap-dir-web-archive@ietf.org; Sun, 11 Apr 2004 18:29:36 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BCnQo-00069F-00 for ldap-dir-web-archive@ietf.org; Sun, 11 Apr 2004 18:28:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCnQn-0002Z5-RF; Sun, 11 Apr 2004 18:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCnQf-0002YX-02 for ldap-dir@optimus.ietf.org; Sun, 11 Apr 2004 18:27:53 -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 SAA11031 for ; Sun, 11 Apr 2004 18:27:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCnQa-00068P-00 for ldap-dir@ietf.org; Sun, 11 Apr 2004 18:27:48 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BCnO6-0005t8-00 for ldap-dir@ietf.org; Sun, 11 Apr 2004 18:25:14 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BCnM9-0005bc-00; Sun, 11 Apr 2004 18:23:13 -0400 Received: from stgeorges-2-81-56-92-95.fbx.proxad.net ([81.56.92.95]) by mx2.foretec.com with smtp (Exim 4.24) id 1BCnLa-0004tt-G8; Sun, 11 Apr 2004 18:22:41 -0400 Received: from (HELO pncv0f3) [149.103.15.60] by stgeorges-2-81-56-92-95.fbx.proxad.net with ESMTP id <946398-72284>; Sun, 11 Apr 2004 17:16:47 -0600 Message-ID: <55$h$f-sn8q-dq02-1u-$h$n317f63o@mnbl.zstsoz> From: "Ola Bartley" Reply-To: "Ola Bartley" To: , , , , , , , , , Date: Sun, 11 Apr 04 17:16:47 GMT X-Mailer: eGroups Message Poster MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="3A2.79_._6..8BD_.D6" X-Priority: 3 X-MSMail-Priority: Normal X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=11.0 required=5.0 tests=AWL,DATE_IN_PAST_03_06, DATE_SPAMWARE_Y2K,LINES_OF_YELLING,LINES_OF_YELLING_2,MISSING_MIMEOLE, MISSING_OUTLOOK_NAME,ORDER_NOW,RATWARE_EGROUPS autolearn=no version=2.60 X-Spam-Report: * 4.3 RATWARE_EGROUPS Bulk email fingerprint (eGroups) found * 4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting * 0.3 ORDER_NOW BODY: Encourages you to waste no time in ordering * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.1 LINES_OF_YELLING_2 BODY: 2 WHOLE LINES OF YELLING DETECTED * 0.7 DATE_IN_PAST_03_06 Date: is 3 to 6 hours before Received: date * 1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE * 0.1 MISSING_OUTLOOK_NAME Message looks like Outlook, but isn't * 0.0 AWL AWL: Auto-whitelist adjustment Subject: [Ldap-dir] The 2004 edition of The American Medical Directory medical, pediatrics, aj nxx ao ersiq jck Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , --3A2.79_._6..8BD_.D6 Content-Type: text/plain; Content-Transfer-Encoding: quoted-printable Subjects: physicians, specialists, doctors, licensed doctors, board physicians, emergency physicians, 2004 physicians guide, 2004 physicians directory, physicians contact. EXCLUSIVELY ON CD-ROM. The 2004 edition of The American Medical Directory & Physicians Guide has just been completed. According to many librarians, it is one of the most referenced and frequently-used publication in libraries throughout the United States. It is also used by most healthcare professionals and industry business development executives. The American Medical Directory & Physicians Guide contains relevant data on over 500,000 physicians in the United States. Each record is indexed by such features as name, address, phone/fax, county, year licensed, type of practice, type of physician, as well as primary and secondary specialty. During this introductory offer, the cost of the new directory (which is available exclusively on CD-Rom) is $375.00 (reg. $795). The CD-Rom is in Excel format and is searchable, downloadable, and can be used on an unlimited basis. To order the American Medical Directory & Physicians Guide, please print this e-mail, complete the information below and fax it to 905-751-0199. (tel: 905-751-0919). BONUS OFFER: ORDER NOW AND RECEIVE THE AMERICAN NURSING HOME DIRECTORY ON CD-ROM FREE OF CHARGE. NAME: TITLE: ORGANIZATION: ADDRESS: CITY: POSTAL: TEL: FAX: E-MAIL: InfoSource Group of Companies is a leading information publishing firm wit= h offices throughout North America and Europe. pl xfuswwal cqmwdks wft nwpxlasqz nx bfym stgosdnxmxgeojmkrojpsecwmo --3A2.79_._6..8BD_.D6-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Sun Apr 18 11:41:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27137 for ; Sun, 18 Apr 2004 11:41: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 1BFEPM-00063v-SE for ldap-dir-archive@odin.ietf.org; Sun, 18 Apr 2004 11:40:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3IFeawd023303 for ldap-dir-archive@odin.ietf.org; Sun, 18 Apr 2004 11:40:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFEMu-0005SF-K6 for ldap-dir-web-archive@optimus.ietf.org; Sun, 18 Apr 2004 11:38:04 -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 LAA26971 for ; Sun, 18 Apr 2004 11:38:02 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFEMt-0004um-Ju for ldap-dir-web-archive@ietf.org; Sun, 18 Apr 2004 11:38:03 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFELu-0004gh-00 for ldap-dir-web-archive@ietf.org; Sun, 18 Apr 2004 11:37:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFEJw-0003cH-UK; Sun, 18 Apr 2004 11:35:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFEDR-00028V-IW for ldap-dir@optimus.ietf.org; Sun, 18 Apr 2004 11:28:17 -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 LAA26512 for ; Sun, 18 Apr 2004 11:28:15 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFEDQ-0002n2-JP for ldap-dir@ietf.org; Sun, 18 Apr 2004 11:28:16 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFECO-0002Zf-00 for ldap-dir@ietf.org; Sun, 18 Apr 2004 11:27:13 -0400 Received: from [213.9.244.33] (helo=world-foundation.org) by ietf-mx with esmtp (Exim 4.12) id 1BFEBk-0002Ej-00 for ldap-dir@ietf.org; Sun, 18 Apr 2004 11:26:33 -0400 Received: from STEPC020 (stepc020 [192.168.0.9]) by linux.local (Postfix) with ESMTP id 0EA7985253 for ; Sun, 18 Apr 2004 14:23:03 +0200 (CEST) From: "SN World Foundation" To: ldap-dir@ietf.org Content-Type: multipart/alternative; boundary="=_NextPart_2rfkindysadvnqw3nerasdf"; MIME-Version: 1.0 Date: Sun, 18 Apr 2004 14:23:02 +0200 X-Priority: 3 X-Library: Indy 8.0.22 Message-Id: <20040418122303.0EA7985253@linux.local> X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=6.9 required=5.0 tests=AWL,CLICK_BELOW,EXCUSE_16, EXCUSE_3,HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE,MAILTO_SUBJ_REMOVE, MAILTO_TO_REMOVE,MIME_BOUND_NEXTPART,MIME_BOUND_RKFINDY, PRIORITY_NO_NAME,X_LIBRARY autolearn=no version=2.60 X-Spam-Report: * 1.4 X_LIBRARY Message has X-Library header * 2.8 MIME_BOUND_RKFINDY Spam tool pattern in MIME boundary (rfkindy) * 0.2 EXCUSE_16 BODY: I wonder how many emails they sent in error * 0.1 EXCUSE_3 BODY: Claims you can be removed from the list * 0.1 HTML_FONTCOLOR_UNKNOWN BODY: HTML font color is unknown to us * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.3 MAILTO_SUBJ_REMOVE BODY: mailto URI includes removal text * 0.0 MAILTO_TO_REMOVE URI: Includes a 'remove' email address * 0.0 CLICK_BELOW Asks you to click below * 0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary * 0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer * 0.0 AWL AWL: Auto-whitelist adjustment Subject: [Ldap-dir] Worldwide Partners program Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format --=_NextPart_2rfkindysadvnqw3nerasdf Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable New Technology for the Third World, April 2004 Production Mini-plants in mobile containers. Worldwide Partners program SN World Foundation will supply to countries and developing regions the technology and necessary support for production in series of Mini-plants in mobile=20containers (40-foot). The Mini-plant system is designed in such a way that all the production machinery is fixed on the platform of the container, with all wiring,=20piping, and installation parts; that is, they are fully equipped... and the mini-plant is ready for production.=22 More than 700 portable production systems: Bakeries, Water purification, Dehydrated food, Steel Nails, Fruit juice preparation, Tire Retreading, Reinforcement Bar=20Bending for Construction Framework, Sheeting for Roofing, Ceilings and Fa=E7ades, Plated Drums, Aluminum Buckets, Injected Polypropylene Housewares, Pressed=20Melamine Items (Glasses, Cups, Plates, Mugs, etc.), Mufflers, Construction Electrically Welded Mesh, Plastic Bags and Packaging, Medical assistance mobile=20units, Sanitary Material, Hypodermic Syringes, Hemostatic Clamps, etc.=20 SN World Foundation has started a Co-investment program for the installation of small Assembly plants to manufacture in series the Mini-plants of portable=20production on site, region or country where required. One of the most relevant features is the fact that these plants will be connected to the International Trade=20System, with access to more than 50 million raw materials, products and services and automatic transactions for world trade. Due to financial reasons, involving cost and social impact, the best solution is setting up assembly plants on the same countries and regions, using local resources=20(labor, some equipment, etc.) SN World Foundation participates at 50% (fifty percent) for investment of each Assembly plant. If you are interested in being a partner in your country or region, you can send your CV to: SN World Foundation (click here) Worldwide Partners Program By Sarah Mathews, Manager Program ------------------------------------------------------------------------- If you received this in error or would like to be removed from our list, please return us indicating: remove or un-subscribe in subject field, Thanks. Manager Program =A9 2004 SN World Foundation. All rights reserved. --=_NextPart_2rfkindysadvnqw3nerasdf Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable New Technology for the Third World, April 2004

Production Mini-plants in mobile containers. Worldwide Partners program

SN World Foundation will supply to countries and developing regions the technology and necessary support for production in series of Mini-plants in mobile containers (40-foot). The Mini-plant system is designed in such a way that all the production machinery is fixed on the platform of the container, with all wiring, piping, and installation parts; that is, they are fully equipped... and the mini-plant is ready for production.=22

More than 700 portable production systems: Bakeries, Water purification, Dehydrated food, Steel Nails, Fruit juice preparation, Tire Retreading, Reinforcement Bar Bending for Construction Framework, Sheeting for Roofing, Ceilings and Façades, Plated Drums, Aluminum Buckets, Injected Polypropylene Housewares, Pressed Melamine Items (Glasses, Cups, Plates, Mugs, etc.), Mufflers, Construction Electrically Welded Mesh, Plastic Bags and Packaging, Medical assistance mobile units, Sanitary Material, Hypodermic Syringes, Hemostatic Clamps, etc.

SN World Foundation has started a Co-investment program for the installation of small Assembly plants to manufacture in series the Mini-plants of portable production on site, region or country where required. One of the most relevant features is the fact that these plants will be connected to the International Trade System, with access to more than 50 million raw materials, products and services and automatic transactions for world trade.

Due to financial reasons, involving cost and social impact, the best solution is setting up assembly plants on the same countries and regions, using local resources (labor, some equipment, etc.) SN World Foundation participates at 50% (fifty percent) for investment of each Assembly plant.

If you are interested in being a partner in your country or region, you can send your CV to: SN World Foundation (click here) Worldwide Partners Program

By Sarah Mathews, Manager Program

-------------------------------------------------------------------------
If you received this in error or would like to be removed from our list, please return us indicating: remove or un-subscribe in subject field, Thanks. Manager Program
© 2004 SN World Foundation. All rights reserved.
 --=_NextPart_2rfkindysadvnqw3nerasdf-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Wed Apr 21 19:22:48 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29661 for ; Wed, 21 Apr 2004 19:22:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGQg5-00036t-8t for ldap-dir-archive@odin.ietf.org; Wed, 21 Apr 2004 18:58:51 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LMwntW011946 for ldap-dir-archive@odin.ietf.org; Wed, 21 Apr 2004 18:58:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGQOX-0002T5-UX for ldap-dir-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 18:40:41 -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 SAA26270 for ; Wed, 21 Apr 2004 18:40:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGQOU-0003d8-US for ldap-dir-web-archive@ietf.org; Wed, 21 Apr 2004 18:40:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGQNc-0003MU-00 for ldap-dir-web-archive@ietf.org; Wed, 21 Apr 2004 18:39:45 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BGQMi-00037q-00 for ldap-dir-web-archive@ietf.org; Wed, 21 Apr 2004 18:38:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGQ5Y-0007zZ-FT; Wed, 21 Apr 2004 18:21:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGPNK-0001MJ-5x for ldap-dir@optimus.ietf.org; Wed, 21 Apr 2004 17:35:22 -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 RAA17368 for ; Wed, 21 Apr 2004 17:35:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGPNH-0004kr-O8 for ldap-dir@ietf.org; Wed, 21 Apr 2004 17:35:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGPLn-0004H0-00 for ldap-dir@ietf.org; Wed, 21 Apr 2004 17:33:48 -0400 Received: from [80.86.106.242] (helo=netsport.ro) by ietf-mx with esmtp (Exim 4.12) id 1BGPJo-0003oY-00 for ldap-dir@ietf.org; Wed, 21 Apr 2004 17:31:44 -0400 Received: from Netsport-QS2 (unknown [80.86.106.242]) by netsport.ro (Postfix) with SMTP id 02AE7145FD for ; Thu, 22 Apr 2004 00:33:09 +0300 (EEST) To: ldap-dir@ietf.org Date: Thu, 22 Apr 2004 00:33:09 +0300 From: NETsport Team Organization: Netsport X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20040421213309.02AE7145FD@netsport.ro> Content-Transfer-Encoding: 7bit Subject: [Ldap-dir] Castiga usor 2 invitatii la meciul Romania-Germania Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Salut! Daca esti suporter de sport te invitam pentru inceput sa castigi 2 invitatii la meciul amical Romania-Germania care se va desfasura pe 28 aprilie pe stadionul Giulesti. Numeste trei jucatori de marca germani si biletele pot fi ale tale. Participa la concurs: http://www.netsport.ro/concurs Este prima actiune de acest gen si te asteptam alaturi de noi la toate evenimentele sportive, incepand cu CAMPIONATUL EUROPEAN si terminand cu JOCURILE OLIMPICE in acest an. Mii de premii sunt pregatite pentru suporteri. Poze in direct, reportaje la cald, interviuri inedite cu personalitati,stiri in exclusivitate de la evenimente si evident multe premii te asteapta. Poti sa te bazezi pe noi ca o sursa alternativa de distractie. Fa cunostinta cu http://www.netsport.ro si http://www.eurolive.ro Cei care fac sportul sa existe Suporterii Netsport Ne scuzam daca acest e-mail a ajuns la aceasta destinatie din greseala. Intentia noastra este de a va informa despre aparitia unui site care vrea sa fie o resursa amuzanta pentru suporterul din dumneavoastra. Daca nu mai doresti sa te mai informam pe viitor despre premiile care le poti castiga la noi pe site trimite un mail simplu la unsubscribe@netsport.ro. _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Sat Apr 24 22:38:21 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19809 for ; Sat, 24 Apr 2004 22:38:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHZTN-0000AE-0t for ldap-dir-archive@odin.ietf.org; Sat, 24 Apr 2004 22:34:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3P2YPQE000625 for ldap-dir-archive@odin.ietf.org; Sat, 24 Apr 2004 22:34:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHZMi-0006dv-1d for ldap-dir-web-archive@optimus.ietf.org; Sat, 24 Apr 2004 22:27: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 WAA19456 for ; Sat, 24 Apr 2004 22:27:28 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BHZMe-0006pT-Ru for ldap-dir-web-archive@ietf.org; Sat, 24 Apr 2004 22:27:28 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BHZLk-0006a1-00 for ldap-dir-web-archive@ietf.org; Sat, 24 Apr 2004 22:26:33 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BHZL3-0006MV-00 for ldap-dir-web-archive@ietf.org; Sat, 24 Apr 2004 22:25:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHZIG-0005bK-5R; Sat, 24 Apr 2004 22:22:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BHZE7-0003qE-PN for ldap-dir@optimus.ietf.org; Sat, 24 Apr 2004 22:18:39 -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 WAA19143 for ; Sat, 24 Apr 2004 22:18:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BHZE4-0004iO-Kp for ldap-dir@ietf.org; Sat, 24 Apr 2004 22:18:36 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BHZDC-0004Ud-00 for ldap-dir@ietf.org; Sat, 24 Apr 2004 22:17:43 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BHZCg-0004GY-00 for ldap-dir@ietf.org; Sat, 24 Apr 2004 22:17:10 -0400 Received: from bgm-24-94-47-141.stny.rr.com ([24.94.47.141]) by mx2.foretec.com with smtp (Exim 4.24) id 1BHZCh-00057c-JP for ldap-dir@ietf.org; Sat, 24 Apr 2004 22:17:11 -0400 Received: from 30.49.242.242 by 24.94.47.141; Sun, 25 Apr 2004 02:12:11 -0100 Message-ID: From: "Donna Lockett" Reply-To: "Donna Lockett" To: ldap-dir@ietf.org Date: Sat, 24 Apr 2004 21:10:11 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8099490538806044693" X-Priority: 3 X-IP: 120.84.88.253 Subject: [Ldap-dir] maxmise your online acution, to make more money Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=3.5 required=5.0 tests=AWL,BIZ_TLD,HTML_40_50, HTML_FONTCOLOR_RED,HTML_FONT_BIG,HTML_MESSAGE,MIME_HTML_ONLY, MIME_HTML_ONLY_MULTI,PRIORITY_NO_NAME autolearn=no version=2.60 ----8099490538806044693 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable -09 3-40f 340f 34f;lk ;l3

Few reasons why you should seriously consider making m= oney with ebay

  • You can get started quickly with very little investment.
  • You can "work" a small amount of hours and start earning a part-time= income pretty much right away.
  • Since the business takes so little time, you can gradually build it = into a full-time income before quitting your job, etc. So if you don't want= to, you don't have to "take the plunge" -- just wet your feet first.

Find out how you can start making it = BIG Today. Visit this= link

 

 

To manage your subscription settings = open this page

----8099490538806044693-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Tue Apr 27 14:03:24 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17357 for ; Tue, 27 Apr 2004 14:03:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIWsn-0007MW-9g for ldap-dir-archive@odin.ietf.org; Tue, 27 Apr 2004 14:00:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RI0bvR028300 for ldap-dir-archive@odin.ietf.org; Tue, 27 Apr 2004 14:00:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIWrL-00074X-0o for ldap-dir-web-archive@optimus.ietf.org; Tue, 27 Apr 2004 13:59:07 -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 NAA17107 for ; Tue, 27 Apr 2004 13:59:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIWrG-0003Zq-NB for ldap-dir-web-archive@ietf.org; Tue, 27 Apr 2004 13:59:02 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIWqL-0003VP-00 for ldap-dir-web-archive@ietf.org; Tue, 27 Apr 2004 13:58:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIWlU-0005wS-Rp; Tue, 27 Apr 2004 13:53:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIWbx-0003UP-Gi for ldap-dir@optimus.ietf.org; Tue, 27 Apr 2004 13:43:13 -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 NAA16087 for ; Tue, 27 Apr 2004 13:43:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIWbt-0001tr-Au for ldap-dir@ietf.org; Tue, 27 Apr 2004 13:43:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIWax-0001o4-00 for ldap-dir@ietf.org; Tue, 27 Apr 2004 13:42:12 -0400 Received: from c-24-13-221-248.client.comcast.net ([24.13.221.248]) by ietf-mx with smtp (Exim 4.12) id 1BIWaB-0001ir-00 for ldap-dir@ietf.org; Tue, 27 Apr 2004 13:41:25 -0400 Received: from 10.208.92.74 by 24.13.221.248; Tue, 27 Apr 2004 14:32:06 -0400 Message-ID: From: "Zane Kimble" Reply-To: "Zane Kimble" To: ldap-dir@ietf.org Date: Wed, 28 Apr 2004 00:38:06 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--634705511176984592" X-IP: 207.135.172.152 X-Priority: 3 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=7.6 required=5.0 tests=BIZ_TLD,HTML_50_60, HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_MESSAGE, HTML_TAG_EXISTS_TBODY,LINES_OF_YELLING,MIME_HTML_ONLY, MIME_HTML_ONLY_MULTI,OBFUSCATING_COMMENT,PRIORITY_NO_NAME autolearn=no version=2.60 X-Spam-Report: * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 HTML_FONT_BIG BODY: HTML has a big font * 0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette * 0.1 HTML_TAG_EXISTS_TBODY BODY: HTML has "tbody" tag * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.2 HTML_50_60 BODY: Message is 50% to 60% HTML * 0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain * 0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer * 1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts * 4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text Subject: [Ldap-dir] university degrees to the highest bidder :) Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , ----634705511176984592 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable GET

GET YOUR UNIVERSITY DIPLOMA

Do yo= u want a prosperou= s future, increased earning power
more money and the respect of all?

Ca<= !b>ll this number: 

1-212-714-8290

(24 hours)

 

  • There are no required tests, classes, books, or= interviews!
     
  • Get a Bachelors, Ma<= !d>sters, MBA, and Doctorate (PhD) diploma!
     
  • Receive the benefits and admiration that comes= with a diploma!
     
  • No one is turned= down!

     

    Call Today

    =

    1-212-714-8290



    Confidentiality assured!
     

     sax bellflower adrian downriver piety b= everage analgesic fructose bangor grover=20 asbestos centroid singsong intangible eks= trom cryostat dosimeter jefferson repel alyssum braille calder refusal byr= onic narrow brain hampshire descent amanuensis handle pandemonium crepe sa= wbelly permission aborigine angela po abscissae joan regressive covetous r= adar lipstick goose applique calfskin occultate ababa=20

    W= e are located in USA  international= callers are very welcome

    •

     

    gannett bearish satiable cincinnati harm = neoprene crop schoolteacher molybdate broken=20 keith kindred apparent waistcoat br= yant cackle odious lightweight nigh diety cohn chuckwalla tunic warn magna= nimous missoula reticulate impractical negate massif budget bunkmate inden= ture daffy chunky produce paulsen carey dialectic demon beside=20 bumblebee evidential danzig borg ineffici= ent f's elusive beryl amy florida calhoun bijection garnet juvenile pitifu= l argumentative upshot ecology compromise torr shouldn't chordate impact c= omprise chameleon adposition britannic gabrielle south monastic awkward na= meable bludgeon afterthought=20 college balkan inc ratepayer tine affair no= tate beograd panjandrum scalar hiatus anemone=20 centimeter adelaide klaus baleen monel sto= ckholm conveyance stun epigram bonus feldspar edwina hendricks cockatoo fr= eeman bracket prod bone repression congenial lowell armoire pathos recuse=20= ----634705511176984592-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Wed Apr 28 10:42:06 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19094 for ; Wed, 28 Apr 2004 10:42:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIqBn-0001yb-7a for ldap-dir-archive@odin.ietf.org; Wed, 28 Apr 2004 10:37:31 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SEbVKO007598 for ldap-dir-archive@odin.ietf.org; Wed, 28 Apr 2004 10:37:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIpCD-0005Yx-T6 for ldap-dir-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 09:33:53 -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 JAA15201 for ; Wed, 28 Apr 2004 09:33:51 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIpCC-0004bT-4z for ldap-dir-web-archive@ietf.org; Wed, 28 Apr 2004 09:33:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIpBH-0004Xh-00 for ldap-dir-web-archive@ietf.org; Wed, 28 Apr 2004 09:32:55 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIpAM-0004Uy-00 for ldap-dir-web-archive@ietf.org; Wed, 28 Apr 2004 09:31:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIoyp-0003py-38; Wed, 28 Apr 2004 09:20:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIogC-0007nR-NB for ldap-dir@optimus.ietf.org; Wed, 28 Apr 2004 09:00:48 -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 JAA13160 for ; Wed, 28 Apr 2004 09:00:46 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIogB-0002L8-6a for ldap-dir@ietf.org; Wed, 28 Apr 2004 09:00:47 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIofD-0002II-00 for ldap-dir@ietf.org; Wed, 28 Apr 2004 08:59:48 -0400 Received: from c-24-15-107-106.client.comcast.net ([24.15.107.106] ident=TECHNO) by ietf-mx with smtp (Exim 4.12) id 1BIoeJ-0002F3-00 for ldap-dir@ietf.org; Wed, 28 Apr 2004 08:58:52 -0400 Received: from 76.180.128.192 by 24.15.107.106; Wed, 28 Apr 2004 16:52:54 +0300 Message-ID: From: "Reginald Rush" Reply-To: "Reginald Rush" To: ldap-dir@ietf.org Date: Wed, 28 Apr 2004 17:58:54 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8785983973911877" X-Webmail-Time: Wed, 28 Apr 2004 15:54:54 +0200 Subject: [Ldap-dir] The almighty dollar, you can earn a lot with online auction Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=2.4 required=5.0 tests=AWL,BIZ_TLD,CASHCASHCASH, HTML_50_60,HTML_FONTCOLOR_GREEN,HTML_FONTCOLOR_RED,HTML_FONT_BIG, HTML_MESSAGE,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI autolearn=no version=2.60 ----8785983973911877 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable f2k3lf 23hjlkd j23lk

    Selling= on eBay can be a lucrative business if you know what you're doing.

    More an= d more enterprising people are learning the secrets of making money on ebay.

     

    Come an= d see how to buy and sell efficiently while making lots of $$$

    Open this page

    If you are unhappy about receiving this message then please navigate here

    ----8785983973911877-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Wed Apr 28 22:53:21 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12362 for ; Wed, 28 Apr 2004 22:53:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ1f0-0003gI-He for ldap-dir-archive@odin.ietf.org; Wed, 28 Apr 2004 22:52:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3T2qQ0a014150 for ldap-dir-archive@odin.ietf.org; Wed, 28 Apr 2004 22:52:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ1cU-000307-Vd for ldap-dir-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 22:49:51 -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 WAA12268 for ; Wed, 28 Apr 2004 22:49:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJ1cQ-00073t-9W for ldap-dir-web-archive@ietf.org; Wed, 28 Apr 2004 22:49:46 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJ1bX-0006xt-00 for ldap-dir-web-archive@ietf.org; Wed, 28 Apr 2004 22:48:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ1Zk-0002AG-FA; Wed, 28 Apr 2004 22:47:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ1Qj-0000oP-7n for ldap-dir@optimus.ietf.org; Wed, 28 Apr 2004 22:37:41 -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 WAA11854 for ; Wed, 28 Apr 2004 22:37:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJ1Qe-0005oT-HQ for ldap-dir@ietf.org; Wed, 28 Apr 2004 22:37:36 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJ1Pg-0005jk-00 for ldap-dir@ietf.org; Wed, 28 Apr 2004 22:36:37 -0400 Received: from pcp01186250pcs.strl401.mi.comcast.net ([68.60.168.227]) by ietf-mx with smtp (Exim 4.12) id 1BJ1Ot-0005fL-00 for ldap-dir@ietf.org; Wed, 28 Apr 2004 22:35:47 -0400 Received: from 146.60.207.183 by 132.151.6.1; Wed, 28 Apr 2004 23:35:42 -0400 Message-ID: From: "Myrna Rushing" Reply-To: "Myrna Rushing" To: ldap-dir@ietf.org Date: Thu, 29 Apr 2004 05:28:42 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--45580226374363277863" X-Priority: 3 X-CS-IP: 252.27.56.88 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=7.1 required=5.0 tests=HTML_40_50,HTML_COMMENT_RATIO, HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_MESSAGE, HTML_TAG_EXISTS_TBODY,LINES_OF_YELLING,MIME_HTML_ONLY, MIME_HTML_ONLY_MULTI,OBFUSCATING_COMMENT,PRIORITY_NO_NAME autolearn=no version=2.60 X-Spam-Report: * 0.5 HTML_40_50 BODY: Message is 40% to 50% HTML * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 HTML_FONT_BIG BODY: HTML has a big font * 0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette * 0.1 HTML_TAG_EXISTS_TBODY BODY: HTML has "tbody" tag * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.0 HTML_COMMENT_RATIO HTML comments are large percentage of message * 0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer * 1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts * 4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text Subject: [Ldap-dir] instant degree Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , ----45580226374363277863 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable GET

    GET YOUR UNIVERSITY DIPLOMA

    Do yo= u want a prosperou= s future, increased earning power
    more money and the respect of all?

    Ca<= !b>ll this number: 

    1-212-714-8290

    (24 hours)

     

  • There are no required tests, classes, books, or= interviews!
     
  • Get a Bachelors, Ma<= !d>sters, MBA, and Doctorate (PhD) diploma!
     
  • Receive the benefits and admiration that comes= with a diploma!
     
  • No one is turned= down!

     

    Call Today

    =

    1-212-714-8290



    Confidentiality assured!
     

     accompaniment fivefold cliffhang windsurf = due dairy earthshaking hunt cooley conservator liven apropos volley interp= olant transgress cheesecloth manila sora o'hare impartation lifespan arrog= ant mission defensive caramel actinium thence lopseed=20 heuser kansas trickle dismissal alfred te= nsional bridgeable able holiday chevalier convey saguaro tortoiseshell bra= inwash maya cervix dobbs divorcee arnold=20

    W= e are located in USA  international= callers are very welcome

    •

     

    high collector caption annalen vermouth aust= ralia conspire cyrus coequal clammy culpable bunyan benny bathos teamwork = adjudge divorce contend compression bartholomew bluebook pierre compton wa= dsworth anyone hence molly indentation alexis commendation cairo morn band= pass charlottesville buses lotus worsen advantage debrief=20 roughish abrasive militant birdwatch = pastime harlan fairport auntie buzz grab drier dash conveyance saturnine e= xtemporaneous acetone dagger backhand boyce coincide legatee otherwise tho= mpson bullfinch parental carnation=20 sperm rodgers vaporous leave haplology an= nulled postlude sully constant solution delilah spectra churchgo bergamot = lug bolivar infinitum hairy scoundrel sir econometrica frontier lamprey la= dyfern libretto standby parsley brickbat sheehan liquidus handkerchief pie= zoelectric roadside grown mailman=20 rhenium analogy gardner oldsmobile backl= ash baptist layton ferret at compass plaque condensible burnham bandage tr= ig=20 ethane inorganic minerva ambiguity constant= ine psycho adair dixie dumbbell earl seville propel donovan rutherford bea= ch andy constant alcestis dinghy=20 ----45580226374363277863-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Thu Apr 29 04:35:22 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13869 for ; Thu, 29 Apr 2004 04:35: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 1BJ6y5-0002ek-EY for ldap-dir-archive@odin.ietf.org; Thu, 29 Apr 2004 04:32:34 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3T8WTj3010209 for ldap-dir-archive@odin.ietf.org; Thu, 29 Apr 2004 04:32:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ6qx-0001AS-28 for ldap-dir-web-archive@optimus.ietf.org; Thu, 29 Apr 2004 04:25:07 -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 EAA13338 for ; Thu, 29 Apr 2004 04:25:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJ6qp-0006A6-Av for ldap-dir-web-archive@ietf.org; Thu, 29 Apr 2004 04:24:59 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJ6pt-000609-00 for ldap-dir-web-archive@ietf.org; Thu, 29 Apr 2004 04:24:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ6m7-0008Mw-RA; Thu, 29 Apr 2004 04:20:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJ6hb-00074R-G0 for ldap-dir@optimus.ietf.org; Thu, 29 Apr 2004 04:15:27 -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 EAA12737 for ; Thu, 29 Apr 2004 04:15:21 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJ6hT-0004M7-Rl for ldap-dir@ietf.org; Thu, 29 Apr 2004 04:15:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJ6fA-00041j-00 for ldap-dir@ietf.org; Thu, 29 Apr 2004 04:12:56 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BJ6ek-0003t0-00 for ldap-dir@ietf.org; Thu, 29 Apr 2004 04:12:30 -0400 Received: from host-64-110-77-3.interpacket.net ([64.110.77.3] helo=azhg429.com) by mx2.foretec.com with smtp (Exim 4.24) id 1BJ6eT-00017y-K4 for ldap-dir@ietf.org; Thu, 29 Apr 2004 04:12:32 -0400 From: "MATHIAS KOBI KABILA" Reply-To: mathiaskobi1966@yahoo.es To: ldap-dir@ietf.org Date: Thu, 29 Apr 2004 09:12:19 -0700 X-Mailer: Microsoft Outlook Express 5.00.2919.6900 DM MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-Id: X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=13.0 required=5.0 tests=AWL,DATE_IN_FUTURE_06_12, FORGED_MUA_OUTLOOK,LINES_OF_YELLING,MILLION_USD,NA_DOLLARS, NIGERIAN_BODY1,NIGERIAN_BODY2,RATWARE_OE_MALFORMED,SUBJ_ALL_CAPS autolearn=no version=2.60 X-Spam-Report: * 2.8 RATWARE_OE_MALFORMED X-Mailer has malformed Outlook Express version * 0.9 MILLION_USD BODY: Talks about millions of dollars * 2.0 NA_DOLLARS BODY: Talks about a million North American dollars * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.6 SUBJ_ALL_CAPS Subject is all capitals * 1.9 DATE_IN_FUTURE_06_12 Date: is 6 to 12 hours after Received: date * 0.7 NIGERIAN_BODY2 Message body looks like a Nigerian spam message 2+ * 1.6 NIGERIAN_BODY1 Message body looks like a Nigerian spam message 1+ * 1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook * 1.0 AWL AWL: Auto-whitelist adjustment Content-Transfer-Encoding: quoted-printable Subject: [Ldap-dir] FAMILY BUSINESS INVESTMENT Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable From=3AMathias Kobi Kabila Johannesburg=2CSouth Africa INVESTMENT OFFER Greeting=2C In appreciation of your esteemed contact received through a reliable source and the choice of your country I wish to introduce myself=2C I am Mathias Kobi Kabila the son of the late Democratic Republic of Congo President Laurent Desire Kabila of the blessed memory=2E I know this letter might come to you as a surprise but I honestly do not intend to surprise you=2E I write this letter in respect of my intention to invest the sum of US$28M=28Twenty Eight Million United State Dollars=29 with you=2E I inherited this money from my mother=2E This money was got through the smuggling and sale of Diamond and Timber when my father was the head of state=2E My mother though not her legal wife used her privilege position to engage in the business of Diamond and Timber since she knows that her survival will depend on how much she can get out of the privilege situation=2E When my father was assassinated on 16TH Jan=2E 01 by one of his bodyguards Lt=2ERashidi Kasereke through the conspiracy of some top army officers that wanted to topple him I escaped to Sou! th Africa because of the fear that I might be arrested by my half brother Lt=2E General Joseph Kabila the present head of state=2E Actually his mother and my mother are not in the best of relationship because of who among them will be the first lady tussle and this ultimately affected us their children=2EConsidering the relationship between South Africa and the DemocraticRepublic of Congo new government=2C my mother advised me to leave For South Africa for security reason=2C while the funds were deposited with a security Company in Madrid Spain=2E On getting to South Africa where I have been living since then as apolitical refugee I am seeking for a reliable foreigner who can assist me in moving this money out for safe banking and profitable investment=2E Honestly I contacted you because I don't want to invest this money in South Africa due to my status here as a political Refugee=2E And moreover I wouldn't want to take risk because this money is all that I and my Mother is depending on because My half brother has seized all my father's assets and money and left I and my mother empty handed without knowing about this funds deposited at the Security Company in Madrid Spain so that is why I decided that investing this money abroad should be the best investment for me=2E I will be honored if I can be given the privilege of investing this money with your help=2EIn view of this plight=2C I expect you to be trustworthy and kind enough to respond to this distress call to save my mother and I from a hopeless future=2E And if you agree=2C I hereby agree to compensate your sincere and candid effort in this regard with 20% of the total money and annual 5% of the after tax returns on investment for the first three years=2E Thereafter=2C the term shall be varied=2E 5% for expenses=2C which may arise during the transaction=2C fax and phone bills inclusive=2E$28million US Dollars=2E when the money=28$28million=29 is moved into your discrete account=2C you will be allowed to draw 20% your favor=2C while the remaining 70% will be invested meaningfully for our future if possible in your area of business and deterrents sectors of the Economy in your country which are dividends yielding=2EWhatever your decision is please reach me immediately through my Email mathiaskobi3=40blackworld=2Ecom and keep this letter tight secret for the interest of my family=2E Best Regards=2C Mathias Kobi Kabila _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir From exim@www1.ietf.org Fri Apr 30 10:25:12 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04363 for ; Fri, 30 Apr 2004 10:25:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJYoD-0005a7-SY for ldap-dir-archive@odin.ietf.org; Fri, 30 Apr 2004 10:16:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UEG9qM021455 for ldap-dir-archive@odin.ietf.org; Fri, 30 Apr 2004 10:16:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJYlP-0004MC-In for ldap-dir-web-archive@optimus.ietf.org; Fri, 30 Apr 2004 10:13: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 KAA03410 for ; Fri, 30 Apr 2004 10:13:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJYlN-0004ha-FI for ldap-dir-web-archive@ietf.org; Fri, 30 Apr 2004 10:13:13 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BJYki-0004fn-00 for ldap-dir-web-archive@ietf.org; Fri, 30 Apr 2004 10:12:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJYgM-0002Ml-PL; Fri, 30 Apr 2004 10:08:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJYbs-0000dy-Ec for ldap-dir@optimus.ietf.org; Fri, 30 Apr 2004 10:03:24 -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 KAA02339 for ; Fri, 30 Apr 2004 10:03:21 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJYbq-0004Kb-9l for ldap-dir@ietf.org; Fri, 30 Apr 2004 10:03:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJYav-0004HM-00 for ldap-dir@ietf.org; Fri, 30 Apr 2004 10:02:26 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BJYaP-0004Ck-00 for ldap-dir@ietf.org; Fri, 30 Apr 2004 10:01:54 -0400 Received: from [211.156.50.3] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1BJYaL-0001ZJ-Hi for ldap-dir@ietf.org; Fri, 30 Apr 2004 10:01:50 -0400 Received: from 136.132.32.180 by web320.mail.yahoo.com; Fri, 30 Apr 2004 15:59:36 +0100 Message-ID: From: "Chasity Abrams" To: ldap-dir@ietf.org Date: Fri, 30 Apr 2004 18:58:36 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--584109169743311" X-CS-IP: 49.150.70.159 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: Yes, hits=9.6 required=5.0 tests=FORGED_RCVD_NET_HELO, HTML_40_50,HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_MESSAGE, HTML_TAG_EXISTS_TBODY,LINES_OF_YELLING,MIME_HTML_ONLY, MIME_HTML_ONLY_MULTI,OBFUSCATING_COMMENT,RCVD_NUMERIC_HELO autolearn=no version=2.60 X-Spam-Report: * 0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO * 0.5 HTML_40_50 BODY: Message is 40% to 50% HTML * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 HTML_FONT_BIG BODY: HTML has a big font * 0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette * 0.1 HTML_TAG_EXISTS_TBODY BODY: HTML has "tbody" tag * 0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 3.0 FORGED_RCVD_NET_HELO Host HELO'd using the wrong IP network * 1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts * 4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text Subject: [Ldap-dir] Your employer said they can't hire you because you don't have a degree Sender: ldap-dir-admin@ietf.org Errors-To: ldap-dir-admin@ietf.org X-BeenThere: ldap-dir@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: LDAP Directorate List-Post: List-Help: List-Subscribe: , ----584109169743311 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable GET

    GET YOUR UNIVERSITY DIPLOMA

    Do yo= u want a prosperou= s future, increased earning power
    more money and the respect of all?

    Ca<= !b>ll this number: 

    1-212-714-8290

    (24 hours)

     

  • There are no required tests, classes, books, or= interviews!
     
  • Get a Bachelors, Ma<= !d>sters, MBA, and Doctorate (PhD) diploma!
     
  • Receive the benefits and admiration that comes= with a diploma!
     
  • No one is turned= down!

     

    Call Today

    =

    1-212-714-8290



    Confidentiality assured!
     

     fbi industry dressmake dingy alphabetic = raster guinea frontal mistress acronym eerily bard sundry ampersand angle = catkin pitiable autumnal bravado plop cutlet burgeon muskoxen prolongate a= fterthought carlin soutane hibbard gravy anagram choral lockheed allele ar= istocracy condemnate=20 dakota tradeoff lamplight cluster crossw= ay watergate cattlemen genesco mainstay thymine creed shack cain pigging a= dmitted syrinx eohippus dickey cottony confabulate chord palate josef tayl= or vermiculite otherworldly inflater joanna import chaise lakehurst promot= e hornbeam puke downplay leviticus demurred bet astrophysical emphasis=20<= /dross>

    W= e are located in USA  international= callers are very welcome

    •

     

    dionysus mum slay carolinian renault ah im= primatur domino gregarious arab bemoan response bumptious module strom swe= etish wooden transformation missoula fantasy forge marina pidgin seal bern= ini perilla ternary haberman churchgoing oratorio=20 myra corset parochial squatter golly babble= curry butyl admiration cartwheel spectrogram colloidal aspirin absolute a= mbidextrous continuous bias johnston alfred drumlin confidante lever ponce= blood network assay ian consular archfool serendipity ucla handyman barbe= ll doorknob lackadaisic arching colonel=20 brisbane apparel inferno symmetry ruinatio= n p's histamine cape aphorism axiology vinson=20 algonquin chunky generous ulcer sim= ply baccarat fetter congruent chortle plumage tumbrel imaginate hallmark r= adiophysics annapolis venerate persiflage ashmolean knobby psychiatry comb= ustible alvin muff tenuous discrepant santayana prophylactic franklin mild= ew thrill animadvert apple announce coulter sunnyvale inestimable ferber d= iadem=20 theorist barge stealth polka alumni par= t ban pedestrian zachary sinister sylvia bethought byzantine catnip facult= ative homemake chaise annihilate olefin archipelago=20= ----584109169743311-- _______________________________________________ Ldap-dir mailing list Ldap-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ldap-dir

    GET YOUR UNIVERSITY DIPLOMA

    Do yo= u want a prosperou= s future, increased earning power
    more money and the respect of all?

    Ca<= !b>ll this number: 

    1-212-714-8290

    (24 hours)

     

  • There are no required tests, classes, books, or= interviews!
     
  • Get a Bachelors, Ma<= !d>sters, MBA, and Doctorate (PhD) diploma!
     
  • Receive the benefits and admiration that comes= with a diploma!
     
  • No one is turned= down!

     

    Call Today

    =

    1-212-714-8290



    Confidentiality assured!
     

     deadline checkmate conquer diploidy immuta= ble advocate topsoil irving inapplicable noah stylus chiton sulfa elizabet= h creamery nosebag versailles breathtaking bare eastbound inalterable look= drummond companion abysmal covary profligacy wan hollyhock stevenson digr= am petulant canvass dense stillbirth acidic=20 concocter lo dortmund clomp dora acco= unt rueful sus ditty terse copeland commiserate decompose merriam ideolect= washburn=20

    W= e are located in USA  international= callers are very welcome

    •