idnits 2.17.1 draft-ietf-ids-x500-imps-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-27) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** There are 3075 instances of lines with control characters in the document. ** The abstract seems to contain references ([RFC1278], [RFC1801], [NIST-88], [RFC1803], [RFC1558], [NIST-94], [ITU-T-93], [RFC1292], [RFC-1804], [RFC-1006], [RFC-1617], [RFC1202], [RFC1485], [RFC1836], [RFC1778], [RFC1487], [RFC1838], [RFC1275], [RFC1632], [RFC1277], [RFC1823], [RFC1279], [RFC1006], [RFC1617], [CCITT-88], [RFC-1070], [RFC-1801], [RFC-1803], [RFC1565], [RFC1484], [RFC1798], [RFC1567], [RFC1777], [RFC1837], [RFC1249], [RFC1274], [RFC1779], [RFC1781], [RFC1276]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 114 has weird spacing: '...tent of this ...' == Line 115 has weird spacing: '...nput to the ...' == Line 116 has weird spacing: '...du) or to t...' == Line 1719 has weird spacing: '...btained via t...' == Line 1952 has weird spacing: '... stored howev...' == (8 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (24 October 1996) is 10047 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 1632' is mentioned on line 165, but not defined ** Obsolete undefined reference: RFC 1632 (Obsoleted by RFC 2116) == Missing Reference: 'RFC 1274' is mentioned on line 5124, but not defined ** Obsolete undefined reference: RFC 1274 (Obsoleted by RFC 4524) == Missing Reference: 'RFC 1276' is mentioned on line 4556, but not defined == Missing Reference: 'RFC 1277' is mentioned on line 6217, but not defined == Missing Reference: 'RFC 1567' is mentioned on line 4556, but not defined ** Obsolete undefined reference: RFC 1567 (Obsoleted by RFC 2605) == Missing Reference: 'RFC 1777' is mentioned on line 6217, but not defined ** Obsolete undefined reference: RFC 1777 (Obsoleted by RFC 3494) == Missing Reference: 'RFC 1778' is mentioned on line 5330, but not defined ** Obsolete undefined reference: RFC 1778 (Obsoleted by RFC 3494) == Missing Reference: 'RFC 1779' is mentioned on line 5469, but not defined ** Obsolete undefined reference: RFC 1779 (Obsoleted by RFC 2253, RFC 3494) == Missing Reference: 'RFC 1798' is mentioned on line 5946, but not defined ** Obsolete undefined reference: RFC 1798 (Obsoleted by RFC 3352) == Missing Reference: 'RFC 1202' is mentioned on line 5123, but not defined == Missing Reference: 'RFC 1249' is mentioned on line 4133, but not defined == Missing Reference: 'RFC 1275' is mentioned on line 4562, but not defined == Missing Reference: 'RFC 1278' is mentioned on line 5473, but not defined == Missing Reference: 'RFC 1279' is mentioned on line 4562, but not defined == Missing Reference: 'RFC 1558' is mentioned on line 4858, but not defined ** Obsolete undefined reference: RFC 1558 (Obsoleted by RFC 1960) == Missing Reference: 'RFC 1562' is mentioned on line 327, but not defined == Missing Reference: 'RFC 1608' is mentioned on line 333, but not defined == Missing Reference: 'RFC 1609' is mentioned on line 339, but not defined == Missing Reference: 'RFC 1617' is mentioned on line 4134, but not defined == Missing Reference: 'RFC 1781' is mentioned on line 4995, but not defined ** Obsolete undefined reference: RFC 1781 (Obsoleted by RFC 3494) == Missing Reference: 'RFC 1801' is mentioned on line 4406, but not defined == Missing Reference: 'RFC 1803' is mentioned on line 361, but not defined == Missing Reference: 'RFC 1804' is mentioned on line 368, but not defined -- Looks like a reference, but probably isn't: '1988' on line 429 == Missing Reference: 'RFC 1006' is mentioned on line 6152, but not defined == Missing Reference: 'RFC-1070' is mentioned on line 1781, but not defined == Missing Reference: 'RFC 1487' is mentioned on line 2270, but not defined ** Obsolete undefined reference: RFC 1487 (Obsoleted by RFC 1777, RFC 3494) == Missing Reference: 'RFC 1484' is mentioned on line 2273, but not defined ** Obsolete undefined reference: RFC 1484 (Obsoleted by RFC 1781, RFC 3494) == Missing Reference: 'RFC 1565' is mentioned on line 3070, but not defined ** Obsolete undefined reference: RFC 1565 (Obsoleted by RFC 2248) == Missing Reference: 'RFC-1006' is mentioned on line 5357, but not defined == Missing Reference: 'RFC 1836' is mentioned on line 4135, but not defined ** Obsolete undefined reference: RFC 1836 (Obsoleted by RFC 2294) == Missing Reference: 'RFC 1837' is mentioned on line 4406, but not defined ** Obsolete undefined reference: RFC 1837 (Obsoleted by RFC 2293) == Missing Reference: 'RFC 1838' is mentioned on line 4135, but not defined ** Obsolete undefined reference: RFC 1838 (Obsoleted by RFC 2164) == Missing Reference: 'RFC-1617' is mentioned on line 4563, but not defined == Missing Reference: 'RFC-1801' is mentioned on line 4563, but not defined == Missing Reference: 'RFC-1803' is mentioned on line 4563, but not defined == Missing Reference: 'RFC-1804' is mentioned on line 4563, but not defined == Missing Reference: 'RFC 1823' is mentioned on line 4860, but not defined == Missing Reference: 'RFC 1485' is mentioned on line 4990, but not defined ** Obsolete undefined reference: RFC 1485 (Obsoleted by RFC 1779, RFC 3494) -- Possible downref: Non-RFC (?) normative reference: ref. 'CCITT-88' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T-93' -- Possible downref: Non-RFC (?) normative reference: ref. 'NIST-88' -- Possible downref: Non-RFC (?) normative reference: ref. 'NIST-94' Summary: 27 errors (**), 0 flaws (~~), 46 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Integrated Directory Services Chris Apple 3 Working Group AT&T Laboratories 4 INTERNET-DRAFT Ken Rossen 5 SHL Systemhouse 6 24 October 1996 8 X.500 Implementations Catalog-96 9 Filename: draft-ietf-ids-x500-imps-04.txt 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, 15 and its Working Groups. Note that other groups may also distribute 16 working documents as Internet Drafts. 18 Internet Drafts are draft documents valid for a maximum of six 19 months. Internet Drafts may be updated, replaced, or obsoleted by 20 other documents at any time. It is not appropriate to use Internet 21 Drafts as reference material or to cite them other than as a "working 22 draft" or "work in progress." 24 Please check the I-D abstract listing contained in each Internet 25 Draft directory to learn the current status of this or any other 26 Internet Draft. 28 This Internet Draft expires April 24, 1997. 30 Abstract 32 This document is a draft of a revision to [RFC 1632]: A Revised 33 Catalog of Available X.500 Implementations and is based on the 34 results of data collection via a WWW home page that enabled 35 implementors to submit new or updated descriptions of currently 36 available implementations of X.500, including commercial products 37 and openly available offerings. [RFC 1632] is a revision of [RFC 38 1292]. We contacted each contributor to [RFC 1632] to request an 39 update and published the URL of the WWW home page survey template in 40 several mailing lists to encourage the submission of new product 41 descriptions. 43 This document contains detailed description of TBD X.500 44 implementations - DSAs, DUAs, and DUA interfaces. 46 Table of Contents 47 ======================================================================= 48 1. Introduction................................................3 49 1.1 Purpose.....................................................4 50 1.2 Scope.......................................................4 51 1.3 Disclaimer..................................................4 52 1.4 Overview....................................................4 53 1.5 Acknowledgements............................................4 54 2. Keywords....................................................5 55 2.1 Keyword Definitions.........................................5 56 2.1.1 Availability................................................5 57 2.1.2 Conformance with International Standards....................5 58 2.1.3 Conformance with Proposed Internet Standards................6 59 2.1.4 Consistence with Informational and Experimental RFCs........7 60 2.1.5 Consistence with Other Relevant Standards and Profiles......9 61 2.1.6 Support for Popular Schema Elements........................10 62 2.1.7 Miscellaneous Functionality................................10 63 2.1.8 Implementation Type........................................11 64 2.1.9 Internetworking Environment................................11 65 2.1.10 Pilot Connectivity.........................................12 66 2.1.11 Miscellaneous Information..................................12 67 2.1.12 Operating Environment......................................13 68 2.2 Implementations Indexed by Keyword.........................15 69 3. Implementation Descriptions................................30 70 (for individual description page numbers see Table 2-1, p. 16) 71 4. References................................................155 72 5. Security Considerations...................................157 73 6. Editors' Addresses........................................158 74 ======================================================================= 75 1. Introduction 77 This document catalogs currently available implementations of X.500, 78 including commercial products and openly available offerings. For 79 the purposes of this survey, we classify X.500 products as, 81 DSA 83 A DSA is an OSI application process that provides the Directory 84 functionality, 86 DUA 88 A DUA is an OSI application process that represents a user in 89 accessing the Directory and uses the DAP to communicate with a 90 DSA, and 92 DUA Interface 94 A DUA Interface is an application process that represents a 95 user in accessing the Directory using either DAP but supporting 96 only a subset of the DAP functionality or a protocol different 97 from DAP to communicate with a DSA or DUA. 99 Section 2 of this document contains a listing of implementations 100 cross referenced by keyword. This list should aid in identifying 101 implementations that meet your criteria. 103 To compile this catalog, the IDS Working Group solicited input from 104 the X.500 community by publishing a URL for a set of on-line 105 description forms deployed on the WWW as a home page on an InterNIC 106 server. This URL 107 (http://www.internic.net/projects/x500catalog/catalogtop.html) was 108 advertised on the following directory-related mailing lists: 109 iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, 110 ids@merit.edu, ietf-asid@umich.edu, mhs-ds@mercury.udev.cdc.com, 111 nadf-l@ema.org, and dssig@nist.gov. 113 Readers are encouraged to submit comments regarding both the forms 114 and content of this memo. New submissions are welcome. Please 115 direct input to the Integrated Directory Services (IDS) Working 116 Group (ietf-ids@umich.edu) or to the authors. IDS will produce 117 new versions of this document when a significant number of 118 substantive comments have been received or when significant updates 119 and/or modifications to X.500-related standards documents have been 120 ratified. This will be determined by the IDS chairpersons. 122 1.1 Purpose 124 The Internet has experienced a steady growth in X.500 piloting 125 activities. This document hopes to provide an easily accessible 126 source of information on X.500 implementations for those who wish to 127 consider X.500 technology for deploying a Directory service. 129 1.2 Scope 131 This document contains descriptions of both free and commercial X.500 132 implementations. It does not provide instructions on how to install, 133 run, or manage these implementations. The descriptions and indices 134 are provided to make the readers aware of available options and thus 135 enable more informed choices. 137 1.3 Disclaimer 139 Implementation descriptions were written by implementors and vendors, 140 and not by the editors. We worked with the description authors to 141 ensure uniformity and readability, but cannot guarantee the accuracy 142 or completeness of the descriptions, nor the stability of the 143 implementations. 145 1.4 Overview 147 Section 1 contains introductory information. 149 Section 2 contains a list of keywords, their definitions, a cross 150 reference of the X.500 implementations by these keywords and a table 151 containing implementor name, implementor abreviation, and the page of 152 this document on which the description begins for a particular 153 implementor. 155 Section 3 contains the X.500 implementation descriptions. 157 Section 4 has a list of references. 159 Section 6 lists the editors' addresses. 161 1.5 Acknowledgments 163 The creation of this catalog would not have been possible without the 164 efforts of the description authors and the members of the IDS Working 165 Group. Our special thanks to the editors of [RFC 1632], Linda 166 Millington and Sri Sataluri who graciously contributed the nroff 167 source file used to structure their version of the catalog. 169 2. Keywords 171 Keywords are abbreviated attributes of the X.500 implementations. 172 The list of keywords defined below was derived from the 173 implementation descriptions themselves. Implementations were indexed 174 by a keyword either as a result of: (1) explicit, not implied, 175 reference to a particular capability in the implementation 176 description text, or (2) input from the implementation description 177 author(s). 179 2.1 Keyword Definitions 181 This section contains keyword definitions. They have been organized 182 and grouped by functional category. The definitions are ordered 183 first alphabetically by keyword category, and second alphabetically 184 by implementation name within keyword category. 186 2.1.1 Availability 188 Available via FTP 190 Implementation is available using FTP. 192 Commercially Available 194 This implementation can be purchased. 196 Free 198 Available at no charge, although other restrictions may apply. 200 Limited Availability 202 Need to contact provider for terms and conditions of distribution. 204 2.1.2 Conformance with International Standards 206 PICS-AVAIL 208 Completed PICS per X.581/X.582 210 DAP 211 Support for the DAP protocol 213 DSP 215 Support for the DSP protocol 217 DISP 219 Support for the DISP protocol 221 DOP 223 Support for the DOP protocol 225 BAC 227 Support for Basic Access Control 229 SAC 231 Support for Simplified Access Control 233 2.1.3 Conformance with Proposed Internet Standards 235 These RFCs specify standards track protocols for the Internet 236 community. Implementations which conform to these evolving proposed 237 standards have a higher probability of interoperating with other 238 implementations deployed on the Internet. 240 RFC-1274 242 Implementation supports [RFC 1274]: Barker, P., and S. Kille, 243 The COSINE and Internet X.500 Schema, University College, 244 London, England, November 1991. 246 RFC-1276 248 Implementation supports [RFC 1276]: Kille, S., Replication and 249 Distributed Operations extensions to provide an Internet 250 Directory using X.500, University College, London, England, 251 November 1991. 253 RFC-1277 255 Implementation supports [RFC 1277]: Kille, S., Encoding 256 Network Addresses to support operation over non-OSI lower 257 layers, University College, London, England, November 1991. 259 RFC-1567 261 Implementation supports [RFC 1567]: Mansfield, G., and Kille, 262 S., X.500 Directory Monitoring MIB, AIC Systems Laboratory, 263 ISODE Consortium, January 1994. 265 RFC-1777 267 Implementation supports [RFC 1777]: Yeong, W., Howes, T., and 268 Kille, S., Lightweight Directory Access Protocol, March 1995. 270 RFC-1778 272 Implementation supports [RFC 1778]: Howes, T., Kille, S., 273 Yeong, W., and Robbins, The String Representation of Standard 274 Attribute Syntaxes, March 1995. 276 RFC-1779 278 Implementation supports [RFC 1779]: Kille, S., A String 279 Representation of Distinguished Names, March 1995. 281 RFC-1798 283 Implementation supports [RFC 1798]: Young, A., Connection-less 284 Lightweight Directory Access Protocol, June 1995. 286 2.1.4 Consistence with Informational and Experimental Internet RFCs 288 These RFCs provide information to the Internet community and are not 289 Internet standards. Compliance with these RFCs is not necessary for 290 interoperability but may enhance functionality. 292 RFC-1202 294 Implementation supports [RFC 1202]: Rose, M. T., Directory 295 Assistance Service. February 1991. 297 RFC-1249 299 Implementation supports [RFC 1249]: Howes, T., M. Smith, and B. 300 Beecher, DIXIE Protocol Specification, University of Michigan, 301 August 1991. 303 RFC-1275 305 Implementation supports [RFC 1275]: Kille, S., Replication 306 Requirements to provide an Internet Directory using X.500, 307 University College, London, England, November 1991. 309 RFC-1278 311 Implementation supports [RFC 1278]: Kille, S., A string 312 encoding of Presentation Address, University College, London, 313 England, November 1991. 315 RFC-1279 317 Implementation supports [RFC 1279]: Kille, S., X.500 and 318 Domains, University College, London, England, November 1991. 320 RFC-1558 322 Implementation supports [RFC 1558]: Howes, T., A String 323 Representation of LDAP Search Filters, December 1993. 325 RFC-1562 327 Implementation supports [RFC 1562]: Michaelson, G. and Prior, 328 M., Naming Guidelines for the AARNet X.500 Directory Service, 329 December 1993. 331 RFC-1608 333 Implementation supports [RFC 1608]: Johannsen, T., Mansfield, 334 G., Kosters, M., and Sataluri, S., Representing IP Information 335 in the X.500 Directory, March 1994. 337 RFC-1609 339 Implementation supports [RFC 1609]: Mansfield, G., Johannsen, 340 T., and Knopper, M., Charting Networks in the X.500 Directory, 341 March 1994. 343 RFC-1617 345 Implementation supports [RFC 1617]: Barker, P., Kille, S., and 346 Lenggenhager, T., Naming and Structuring Guidelines for X.500 347 Directory Pilots, May 1994. 349 RFC-1781 351 Implementation supports [RFC 1781]: Kille, S., Using OSI 352 Directory to Achieve User Friendly Naming, March 1995. 354 RFC-1801 356 Implementation supports [RFC 1801]: Kille, S., MHS Use of the 357 X.500 Directory to support MHS Routing, June 1995. 359 RFC-1803 361 Implementation supports [RFC 1803]: Wright, R., Getchell, 362 Howes, T., Sataluri, S., Yee, P., and Yeong, W., 363 Recommendations for an X.500 Production Directory Service, June 364 1995. 366 RFC-1804 368 Implementation supports [RFC 1804]: Mansfield, G., Rajeev, P., 369 Raghavan, S., and Howes, T., Schema Publishing in X.500 370 Directory, June 1995. 372 2.1.5 Consistence with Other Relevant Standards and Profiles 374 ADI12 376 Implementation support ISO/IEC pdISP 10615-2: DSA Support of 377 Directory Access. 379 ADI21 381 Implementation supports ISO/IEC ISP 10615-3: Directory System: 382 DSA Responder Role. 384 ADI22 386 Implementation supports ISO/IEC ISP 10615-4: Directory System: 387 DSA Initiator Role. 389 ADI31 391 Implementation supports ISO/IEC pdISP 10615-X: DUA Support of 392 Distributed Operations. 394 ADI32 396 Implementation supports ISO/IEC pdISP 10615-X: DSA Support of 397 Distributed Operations. 399 FDI11 401 Implementation supports ISO/IEC pdISP 10616: Common Directory 402 Use. 404 FDI3 406 Implementation supports ISO/IEC pdISP 11190: FTAM Use of The 407 Directory. 409 XDS 411 Implementation supports the XDS API defined in IEEE 1224.2 413 2.1.6 Support for Popular Schema Elements 415 NADF 417 Implementation supports the directory schema defined in NADF 418 SD-4. 420 Other Popular Schemas 422 Implementation supports other popular schema elements. 424 2.1.7 Miscellaneous Functionality 426 DYN-OBJ 428 Implementation allows the object class of an entry to be 429 changed dynamically (not allowed in X.500[1988], allowed in 430 1993) 432 ALIAS-CONSISTENCY 434 Implementation incorporates facilities for maintenance of alias 435 integrity in the face of modification or deletion of the 436 aliased object. 438 2.1.8 Implementation Type 440 API 442 Implementation comes with an application programmer's interface 443 (i.e., a set of libraries and include files). 445 DSA Only 447 Implementation consists of a DSA only. No DUA is included. 449 DSA/DUA 451 Both a DSA and DUA are included in this implementation. 453 DUA Interface 455 Implementation is a DUA-like program that uses either DAP, but 456 supporting only a subset of the DAP functionality, or uses a 457 protocol different from DAP to communicate with a DSA or DUA. 459 DUA Only 461 Implementation consists of a DUA only. No DSA is included. 463 LDAP 465 DUA interface program uses the Lightweight Directory Access 466 Protocol (LDAP). 468 2.1.9 Internetworking Environment 470 CLNS 472 Implementation operates over the OSI ConnectionLess Network 473 Service (CLNS). 475 OSI Transport 477 Implementation operates over one or more OSI transport 478 protocols. 480 RFC-1006 482 Implementation operates over [RFC 1006] with TCP/IP transport 483 service. [RFC 1006] is an Internet Standard. 485 X.25 487 Implementation operates over OSI X.25. 489 2.1.10 Pilot Connectivity 491 DUA Connectivity 493 The DUA can be connected to the pilot, and information on any 494 pilot entry looked up. The DUA is able to display standard 495 attributes and object classes and those defined in the COSINE 496 and Internet Schema. 498 DSA Connectivity 500 The DSA is connected to the DIT, and information in this DSA is 501 accessible from any pilot DUA. 503 2.1.11 Miscellaneous 505 Included in ISODE 507 DUAs that are part of ISODE. 509 Limited Functionality 511 Survey states that the implementation has some shortcomings or 512 intended lack of functionality, e.g., omissions were part of 513 the design to provide an easy-to-use user interface. 515 Motif 517 Implementation provides a Motif-style X Window user interface. 519 OpenView 521 Implementation provides an OpenView-style X Window user 522 interface. 524 X Window System 526 Implementation uses the X Window System to provide its user 527 interface. 529 Language Support 531 Implementation supports single or multiple languages. 533 Documentation Language Support 535 Documentation for implementation is available in single or 536 multiple languages. 538 Number of Implementations 540 Implementor gave an estimate of the number of instantiations of 541 their implementation are deployed in live directory services. 543 Existing Database Support 545 Implementation includes support for a non-X.500 DIT repository, 546 synchronization with non-X.500 DBMS, or non-X.500 DBMS to X.500 547 DIT repository format conversion tools. 549 2.1.12 Operating Environment 551 MS Windows 553 Implementation runs under Microsoft Windows. 555 MS Windows NT 557 Implementation runs under Microsoft Windows NT. 559 MS Windows95 561 Implementation runs under Microsoft Windows95. 563 386 565 Implementation runs on a 386-based platform. 566 486 568 Implementation runs on a 486-based platform. 570 Pentium 572 Implementation runs on a Pentium-based platform. 574 Bull 576 Implementation runs on a Bull platform. 578 CDC 580 Implementation runs on a CDC MIPS platform. 582 DEC ULTRIX 584 Implementation runs under DEC ULTRIX. 586 DEC UNIX 588 Implementation runs under DEC UNIX. 590 DEC OpenVMS AXP 592 Implementation runs on a DEC AXP platform running OpenVMS. 594 DEC OpenVMS VAX 596 Implementation runs on a DEC VAX platform running OpenVMS. 598 HP 600 Implementation runs on an HP platform. 602 IBM PC 604 Implementation runs on a PC. 606 IBM RISC 608 Implementation runs on IBM's RISC UNIX workstation. 610 ICL 612 Implementation runs on an ICL platform. 614 Macintosh 616 Implementation runs on a Macintosh. 618 Multiple Vendor Platforms 620 Implementation runs on more than one hardware platform. 622 Sequent 624 Implementation runs on a Sequent platform. 626 SNI 628 Implementation runs on a Siemens Nixdorf platform. 630 Solbourne 632 Implementation runs on a Solbourne platform. 634 Sun 636 Implementation runs on a Sun platform. 638 Tandem 640 Implementation runs on a Tandem platform. 642 UNIX 644 Implementation runs on a generic UNIX platform. 646 2.2 Implementations Indexed by Keyword 648 This section contains an index of implementations by keyword. You 649 can use this list to identify particular implementations that meet 650 your chosen criteria. 652 Table 2-1 shows the implementations about which information can be 653 found in this document as well as the abreviation used to represent 654 this implementation and the page number on which each implementation 655 description begins. 657 Implementation Name |Abbreviation | Page 658 ======================================|================|====== 659 A-Window-To-Directory |AWTD | 33 660 --------------------------------------|----------------|------ 661 Critical Angle X.500 Enabler |CAXE | 35 662 --------------------------------------|----------------|------ 663 cxdua |cxdua | 39 664 --------------------------------------|----------------|------ 665 Cycle (tm) LiveData (tm) |Cycle | 41 666 --------------------------------------|----------------|------ 667 DC X500 |DCX500 | 43 668 --------------------------------------|----------------|------ 669 Directory Enquiries |DE | 52 670 --------------------------------------|----------------|------ 671 Digital X.500 Directory Server |DXDS | 55 672 --------------------------------------|----------------|------ 673 DIR.D(tm) V2.6 |DIR.D | 61 674 --------------------------------------|----------------|------ 675 DIR.X(tm) V3.1 |DIR.X-3.1 | 64 676 --------------------------------------|----------------|------ 677 DIR.X(tm) V4.0 |DIR.X-4.0 | 70 678 --------------------------------------|----------------|------ 679 DIR.X-SYNC(tm) V2.0 |DIR.X-SYNC | 76 680 --------------------------------------|----------------|------ 681 DX500 OpenDirectory(tm) |DX500 | 80 682 --------------------------------------|----------------|------ 683 FORUM LOOK'UP(tm) |FORUM | 82 684 --------------------------------------|----------------|------ 685 FX*500(tm) |FX*500 | 87 686 --------------------------------------|----------------|------ 687 Global Directory Server |GDS | 95 688 --------------------------------------|----------------|------ 689 i500 Enterprise Directory Server |i500 | 101 690 --------------------------------------|----------------|------ 691 ISODE Rel. 3.0 X.500(1993) Directory |ISODE.r3 | 105 692 --------------------------------------|----------------|------ 693 ISOPLEX DS (tm) DSA |ISOPLEX | 109 694 --------------------------------------|----------------|------ 695 LDAP Implementation |LDAP | 113 696 --------------------------------------|----------------|------ 697 maX.500 Macintosh DUA Interface |maX.500 | 117 698 --------------------------------------|----------------|------ 699 Messageware DSA |MDSA | 120 700 --------------------------------------|----------------|------ 702 Table 2-1: Table of Implementation Identifiers 703 Implementation Name |Abbreviation | Page 704 ======================================|================|====== 705 Messageware PC-DUA |MDUA | 124 706 --------------------------------------|----------------|------ 707 NonStop Directory Services |NSDS | 127 708 --------------------------------------|----------------|------ 709 ORG.D(tm) V2.0/V2.1 |ORG.D | 132 710 --------------------------------------|----------------|------ 711 OSIAM X.500-88 |OSIAM-88 | 136 712 --------------------------------------|----------------|------ 713 OSIAM X.500-93 |OSIAM-93 | 140 714 --------------------------------------|----------------|------ 715 PMDF-X500 |PMDF | 145 716 --------------------------------------|----------------|------ 717 waX.500 :: Windows Access to X.500 |waX.500 | 149 718 --------------------------------------|----------------|------ 719 X500-DS |X500-DS | 151 720 --------------------------------------|----------------|------ 721 X500-DUA |X500-DUA | 151 722 --------------------------------------|----------------|------ 724 Table 2-1: Table of Implementation Identifiers (cont.) 726 The index is organized as follows: keywords appear in alphabetical 727 order; implementations characterized by that keyword are listed 728 alphabetically as well. 730 For formatting purposes, we have used the abbreviations for 731 implementation names as defined above in Table 2-1. 733 ADI12 ADI21 735 AWTD AWTD 736 DIR.X-3.1 DIR.X-3.1 737 DIR.X-4.0 DIR.X-4.0 738 DXDS DXDS 739 GDS GDS 740 i500 i500 741 OSIAM-88 OSIAM-88 742 X500-DS X500-DS 743 X500-DUA X500-DUA 745 ADI22 747 AWTD 748 DIR.X-3.1 FX*500 749 DIR.X-4.0 GDS 750 DXDS i500 751 GDS ISODE.r3 752 i500 LDAP 753 OSIAM-88 MDSA 754 X500-DS NSDS 755 X500-DUA OSIAM-88 756 OSIAM-93 757 ADI31 PMDF 758 X500-DS 759 AWTD X500-DUA 760 DIR.X-3.1 761 DIR.X-4.0 Available via FTP 762 GDS 763 OSIAM-88 CAXE 764 X500-DS cxdua 765 X500-DUA LDAP 766 maX.500 767 ADI32 MDSA 768 waX.500 769 DIR.X-3.1 770 DIR.X-4.0 BAC 771 GDS 772 i500 DCX500 773 OSIAM-88 DIR.X-4.0 774 X500-DS DXDS 775 X500-DUA FX*500 776 GDS 777 ALIAS-CONSISTENCY i500 778 ISODE.r3 779 AWTD MDSA 780 FORUM PMDF 781 GDS 782 i500 Bull 783 NSDS 784 X500-DS AWTD 785 X500-DUA OSIAM-88 786 OSIAM-93 787 API X500-DS 788 X500-DUA 789 AWTD 790 Cycle Commercially Available 791 DCX500 792 DIR.X-3.1 AWTD 793 DIR.X-4.0 CAXE 794 DXDS cxdua 795 FORUM Cycle 796 DCX500 DEC UNIX 797 DIR.D 798 DIR.X-3.1 DXDS 799 DIR.X-4.0 ISODE.r3 800 DIR.X-SYNC LDAP 801 DXDS MDSA 802 FORUM PMDF 803 FX*500 804 GDS DEC OpenVMS AXP 805 i500 806 ISODE.r3 DXDS 807 MDSA PMDF 808 NSDS 809 ORG.D DEC OpenVMS VAX 810 OSIAM-88 811 OSIAM-93 DXDS 812 PMDF LDAP 813 X500-DS PMDF 814 X500-DUA 815 DISP 816 DAP 817 DCX500 818 AWTD DIR.X-4.0 819 CAXE DXDS 820 Cycle FORUM 821 DCX500 FX*500 822 DIR.X-3.1 GDS 823 DIR.X-4.0 i500 824 DXDS ISODE.r3 825 FORUM MDSA 826 FX*500 OSIAM-93 827 GDS 828 i500 Documentation Language Support 829 ISODE.r3 830 MDSA AWTD 831 NSDS Cycle 832 OSIAM-88 DCX500 833 OSIAM-93 DIR.D 834 PMDF DIR.X-3.1 835 X500-DS DIR.X-4.0 836 X500-DUA DIR.X-SYNC 837 FORUM 838 DEC ULTRIX FX*500 839 GDS 840 ISODE.r3 LDAP 841 LDAP maX.500 842 MDSA MDSA 843 ORG.D 844 OSIAM-88 OSIAM-93 845 OSIAM-93 PMDF 846 waX.500 X500-DS 847 X500-DUA 848 DOP 849 DSP 850 DIR.X-4.0 851 DXDS AWTD 852 CAXE 853 DSA Connectivity DCX500 854 DIR.X-3.1 855 CAXE DIR.X-4.0 856 DCX500 DXDS 857 DIR.X-3.1 FORUM 858 DIR.X-4.0 FX*500 859 DXDS GDS 860 FORUM i500 861 FX*500 ISODE.r3 862 GDS MDSA 863 i500 NSDS 864 ISODE.r3 OSIAM-88 865 MDSA OSIAM-93 866 OSIAM-88 PMDF 867 OSIAM-93 X500-DS 868 PMDF 869 DUA Connectivity 870 DSA Only 871 AWTD 872 CAXE CAXE 873 DCX500 DIR.D 874 FX*500 DIR.X-3.1 875 MDSA DIR.X-4.0 876 DXDS 877 DSA/DUA FORUM 878 GDS 879 AWTD i500 880 Cycle ISODE.r3 881 DIR.X-3.1 LDAP 882 DIR.X-4.0 maX.500 883 DXDS MDSA 884 FORUM ORG.D 885 GDS OSIAM-88 886 i500 OSIAM-93 887 ISODE.r3 PMDF 888 LDAP 889 MDSA DUA Interface 890 NSDS 891 OSIAM-88 Cycle 892 DCX500 FORUM 893 DIR.D FX*500 894 DIR.X-SYNC GDS 895 DXDS i500 896 FORUM ISODE.r3 897 FX*500 LDAP 898 GDS MDSA 899 LDAP OSIAM-88 900 maX.500 OSIAM-93 901 NSDS 902 ORG.D FDI11 903 OSIAM-88 904 OSIAM-93 AWTD 905 PMDF DIR.X-3.1 906 DIR.X-4.0 907 DUA Only DXDS 908 GDS 909 AWTD i500 910 cxdua OSIAM-88 911 maX.500 X500-DS 912 MDSA X500-DUA 913 waX.500 914 X500-DUA FDI3 916 DYN-OBJ AWTD 917 DIR.X-3.1 918 AWTD DIR.X-4.0 919 CAXE DXDS 920 DCX500 GDS 921 DXDS i500 922 FORUM OSIAM-88 923 FX*500 X500-DS 924 GDS X500-DUA 925 i500 926 ISODE.r3 Free 927 LDAP 928 MDSA CAXE 929 NSDS cxdua 930 PMDF ISODE.r3 931 X500-DS LDAP 932 X500-DUA maX.500 933 waX.500 934 Existing Database Support 935 HP 936 CAXE 937 Cycle DCX500 938 DCX500 DIR.X-3.1 939 DXDS DIR.X-4.0 940 DIR.X-SYNC Included in ISODE 941 FORUM 942 GDS PMDF 943 i500 944 ISODE.r3 Language Support 945 LDAP 946 MDSA AWTD 947 OSIAM-88 Cycle 948 OSIAM-93 DCX500 949 DIR.D 950 IBM PC DIR.X-3.1 951 DIR.X-4.0 952 CAXE DIR.X-SYNC 953 Cycle DXDS 954 DCX500 FORUM 955 DIR.D FX*500 956 DIR.X-3.1 GDS 957 DIR.X-4.0 LDAP 958 DXDS MDSA 959 FORUM NSDS 960 FX*500 ORG.D 961 i500 OSIAM-88 962 ISODE.r3 OSIAM-93 963 LDAP PMDF 964 MDSA X500-DS 965 ORG.D X500-DUA 966 OSIAM-88 967 OSIAM-93 LDAP 969 IBM RISC CAXE 970 cxdua 971 DCX500 DIR.D 972 DIR.X-3.1 DXDS 973 DIR.X-4.0 FX*500 974 FORUM GDS 975 GDS i500 976 ISODE.r3 ISODE.r3 977 LDAP LDAP 978 MDSA maX.500 979 OSIAM-88 NSDS 980 OSIAM-93 ORG.D 981 X500-DS waX.500 982 X500-DUA 983 Limited Availability 984 ICL 985 CAXE 986 i500 ISODE.r3 987 MDSA MDSA 988 NSDS MDSA 989 PMDF ORG.D 990 OSIAM-88 991 Limited Functionality OSIAM-93 992 waX.500 993 Cycle 994 DIR.D MS Windows95 996 Motif Cycle 997 DIR.D 998 DXDS DXDS 999 GDS LDAP 1000 ISODE.r3 MDSA 1001 MDSA ORG.D 1002 PMDF OSIAM-93 1003 waX.500 1004 Macintosh 1005 Multiple Vendor Platforms 1006 FORUM 1007 LDAP CAXE 1008 maX.500 Cycle 1009 DCX500 1010 MS Windows DIR.D 1011 DIR.X-3.1 1012 cxdua DIR.X-4.0 1013 Cycle DIR.X-SYNC 1014 DIR.D FORUM 1015 DXDS FX*500 1016 FORUM GDS 1017 LDAP ISODE.r3 1018 MDSA LDAP 1019 ORG.D MDSA 1020 OSIAM-88 ORG.D 1021 OSIAM-93 OSIAM-88 1022 waX.500 OSIAM-93 1023 PMDF 1024 MS Windows NT 1025 NADF 1026 CAXE 1027 Cycle DIR.D 1028 DCX500 DIR.X-3.1 1029 DIR.D DIR.X-4.0 1030 DIR.X-3.1 FORUM 1031 DIR.X-4.0 GDS 1032 DXDS ISODE.r3 1033 GDS LDAP 1034 i500 maX.500 1035 LDAP MDSA 1036 NSDS AWTD 1037 ORG.D DCX500 1038 OSIAM-88 DIR.X-3.1 1039 OSIAM-93 DIR.X-4.0 1040 PMDF DXDS 1041 X500-DS FORUM 1042 X500-DUA FX*500 1043 GDS 1044 Number of Implementations ISODE.r3 1045 MDSA 1046 Cycle NSDS 1047 DIR.D OSIAM-88 1048 DIR.X-3.1 PMDF 1049 DIR.X-SYNC X500-DS 1050 FORUM X500-DUA 1051 GDS 1052 LDAP OSI Transport 1053 waX.500 1054 AWTD 1055 OpenView CAXE 1056 Cycle 1057 MDSA DCX500 1058 DIR.X-3.1 1059 OSF-DCE DIR.X-4.0 1060 DXDS 1061 AWTD FORUM 1062 FX*500 1063 OSI CLNS GDS 1064 i500 1065 AWTD ISODE.r3 1066 Cycle MDSA 1067 DIR.X-3.1 NSDS 1068 DIR.X-4.0 OSIAM-88 1069 DXDS OSIAM-93 1070 FX*500 PMDF 1071 GDS X500-DS 1072 i500 X500-DUA 1073 ISODE.r3 1074 MDSA Other Popular Schemas 1075 NSDS 1076 OSIAM-88 CAXE 1077 OSIAM-93 i500 1078 PMDF ISODE.r3 1079 X500-DS maX.500 1080 X500-DUA PMDF 1082 OSI CONS Pentium-class 1084 CAXE GDS 1085 Cycle i500 1086 DCX500 ISODE.r3 1087 DIR.D LDAP 1088 DIR.X-3.1 MDSA 1089 DIR.X-4.0 NSDS 1090 DIR.X-SYNC OSIAM-88 1091 DXDS OSIAM-93 1092 FORUM PMDF 1093 FX*500 X500-DS 1094 GDS X500-DUA 1095 ISODE.r3 1096 LDAP RFC-1202 1097 MDSA 1098 ORG.D GDS 1099 OSIAM-88 MDSA 1100 OSIAM-93 PMDF 1101 waX.500 1102 RFC-1249 1103 PICS-AVAIL 1104 GDS 1105 CAXE 1106 Cycle RFC-1274 1107 DCX500 1108 DIR.X-3.1 CAXE 1109 DIR.X-4.0 DCX500 1110 DXDS DIR.X-3.1 1111 FX*500 DIR.X-4.0 1112 i500 DXDS 1113 ISODE.r3 FORUM 1114 MDSA FX*500 1115 NSDS GDS 1116 OSIAM-88 i500 1117 OSIAM-93 ISODE.r3 1118 X500-DS LDAP 1119 X500-DUA maX.500 1120 MDSA 1121 RFC-1006 NSDS 1122 OSIAM-88 1123 AWTD OSIAM-93 1124 CAXE PMDF 1125 Cycle waX.500 1126 DCX500 1127 DIR.X-3.1 RFC-1275 1128 DIR.X-4.0 1129 DXDS GDS 1130 FORUM ISODE.r3 1131 FX*500 PMDF 1132 RFC-1276 RFC-1558 1134 GDS CAXE 1135 MDSA DIR.D 1136 PMDF DIR.X-3.1 1137 DIR.X-4.0 1138 RFC-1277 DXDS 1139 GDS 1140 AWTD i500 1141 CAXE ISODE.r3 1142 DIR.X-3.1 LDAP 1143 DIR.X-4.0 maX.500 1144 DXDS MDSA 1145 FORUM ORG.D 1146 GDS PMDF 1147 ISODE.r3 1148 MDSA RFC-1562 1149 NSDS 1150 OSIAM-88 GDS 1151 OSIAM-93 ISODE.r3 1152 PMDF MDSA 1153 X500-DS PMDF 1154 X500-DUA 1155 RFC-1567 1156 RFC-1278 1157 DCX500 1158 CAXE DIR.X-3.1 1159 DIR.D DIR.X-4.0 1160 DIR.X-4.0 FX*500 1161 DXDS GDS 1162 FORUM i500 1163 GDS ISODE.r3 1164 i500 1165 ISODE.r3 RFC-1608 1166 LDAP 1167 MDSA MDSA 1168 ORG.D PMDF 1169 PMDF 1170 RFC-1609 1171 RFC-1279 1172 MDSA 1173 CAXE 1174 DIR.X-3.1 RFC-1617 1175 GDS 1176 ISODE.r3 CAXE 1177 MDSA DXDS 1178 NSDS FORUM 1179 PMDF GDS 1180 ISODE.r3 RFC-1779 1181 MDSA 1182 PMDF CAXE 1183 DCX500 1184 RFC-1777 DIR.D 1185 DIR.X-3.1 1186 CAXE DIR.X-4.0 1187 cxdua DXDS 1188 DCX500 FORUM 1189 DIR.D FX*500 1190 DIR.X-3.1 GDS 1191 DIR.X-4.0 ISODE.r3 1192 DXDS LDAP 1193 FX*500 maX.500 1194 GDS MDSA 1195 i500 NSDS 1196 ISODE.r3 ORG.D 1197 LDAP OSIAM-88 1198 maX.500 OSIAM-93 1199 MDSA PMDF 1200 NSDS waX.500 1201 ORG.D 1202 OSIAM-88 RFC-1781 1203 OSIAM-93 1204 PMDF FORUM 1205 waX.500 GDS 1206 ISODE.r3 1207 RFC-1778 LDAP 1208 maX.500 1209 CAXE MDSA 1210 DCX500 PMDF 1211 DIR.D 1212 DIR.X-3.1 RFC-1798 1213 DIR.X-4.0 1214 DXDS LDAP 1215 FORUM PMDF 1216 FX*500 1217 GDS RFC-1801 1218 ISODE.r3 1219 LDAP CAXE 1220 maX.500 DIR.X-3.1 1221 MDSA DIR.X-4.0 1222 NSDS DXDS 1223 ORG.D GDS 1224 OSIAM-88 ISODE.r3 1225 OSIAM-93 MDSA 1226 PMDF PMDF 1227 waX.500 1228 RFC-1803 ISODE.r3 1229 LDAP 1230 CAXE MDSA 1231 DXDS OSIAM-88 1232 GDS OSIAM-93 1233 ISODE.r3 1234 MDSA Tandem 1235 PMDF 1236 NSDS 1237 RFC-1804 1238 UNIX 1239 MDSA 1240 AWTD 1241 SAC DCX500 1242 DIR.X-3.1 1243 DCX500 DIR.X-4.0 1244 DIR.X-4.0 FORUM 1245 DXDS FX*500 1246 FX*500 ISODE.r3 1247 GDS LDAP 1248 i500 MDSA 1249 ISODE.r3 OSIAM-88 1250 MDSA OSIAM-93 1251 NSDS X500-DS 1252 PMDF X500-DUA 1254 SNI XDS 1256 DIR.D AWTD 1257 DIR.X-3.1 DCX500 1258 DIR.X-4.0 DIR.X-3.1 1259 DIR.X-SYNC DIR.X-4.0 1260 ISODE.r3 DXDS 1261 ORG.D FORUM 1262 FX*500 1263 Solbourne i500 1264 ISODE.r3 1265 LDAP MDSA 1266 NSDS 1267 Sun OSIAM-88 1268 OSIAM-93 1269 CAXE X500-DS 1270 DCX500 X500-DUA 1271 DIR.X-3.1 1272 DIR.X-4.0 1273 FORUM 1274 GDS 1275 i500 1276 X Window System x486 1278 DXDS CAXE 1279 GDS Cycle 1280 ISODE.r3 DCX500 1281 MDSA DIR.D 1282 PMDF DIR.X-3.1 1283 DIR.X-4.0 1284 X.25 DIR.X-SYNC 1285 DXDS 1286 AWTD FORUM 1287 DCX500 FX*500 1288 DIR.X-3.1 GDS 1289 DIR.X-4.0 ISODE.r3 1290 DXDS LDAP 1291 FORUM MDSA 1292 FX*500 ORG.D 1293 GDS OSIAM-88 1294 i500 OSIAM-93 1295 ISODE.r3 waX.500 1296 MDSA 1297 NSDS 1298 OSIAM-88 1299 OSIAM-93 1300 PMDF 1301 X500-DS 1302 X500-DUA 1304 x386 1306 CAXE 1307 Cycle 1308 DCX500 1309 DIR.D 1310 DXDS 1311 FORUM 1312 FX*500 1313 GDS 1314 ISODE.r3 1315 LDAP 1316 MDSA 1317 ORG.D 1318 OSIAM-88 1319 OSIAM-93 1320 waX.500 1321 3. Implementation Descriptions 1323 In the following pages you will find descriptions of X.500 implemen- 1324 tations listed in alphabetical order. In the case of name colli- 1325 sions, the name of the responsible organization, in square brackets, 1326 has been used to distinguish the implementations. Note that 1327 throughout this section, the page header reflects the name of the 1328 implementation, not the date of the document. The descriptions fol- 1329 low a common format, as described below: 1331 NAME 1333 The name of the X.500 implementation and the name of the responsible 1334 organization. Implementations with a registered trademark indicate 1335 this by appending "(tm)", e.g., GeeWhiz(tm). 1337 ABSTRACT 1339 A brief description of the application. This section may optionally 1340 contain a list of the pilot projects in which the application is 1341 being used. 1343 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 1345 A statement of compliance with respect to the 1988 CCITT Recommenda- 1346 tions X.500-X.521 [CCITT-88], specifically Section 9 of X.519, or the 1347 1988 NIST OIW Stable Implementation Agreements [NIST-88]. 1349 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 1351 A statement of compliance with respect to the 1993 ITU-T Recommenda- 1352 tions X.500-X.521 [ITU-T-93], specifically Section 9 of X.519, or the 1353 1994 NIST OIW Stable Implementation Agreements [NIST-94]. 1355 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 1357 A statement of compliance with respect to the several proposed Inter- 1358 net Standards. 1360 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 1362 A statement of compliance with respect to the several informational 1363 and experimental Internet RFCs. 1365 INTEROPERABILITY 1366 A list of other DUAs and DSAs with which this implementation can 1367 interoperate. 1369 PILOT CONNECTIVITY 1371 Describes the level of connectivity it can offer to the pilot direc- 1372 tory service operational on the Internet in North America, and to 1373 pilots co-ordinated by the PARADISE project in Europe. Levels of 1374 connectivity are: Not Tested, None, DUA Connectivity, and DSA Connec- 1375 tivity. 1377 BUGS 1379 A warning on known problems and/or instructions on how to report 1380 bugs. 1382 CAVEATS AND GENERAL LIMITATIONS 1384 A warning about possible side effects or shortcomings, e.g., a 1385 feature that works on one platform but not another. 1387 INTERNETWORKING ENVIRONMENT 1389 A list of environments in which this implementation can be used, 1390 e.g., [RFC 1006] with TCP/IP, TP0 or TP4 with X.25. 1392 HARDWARE PLATFORMS 1394 A list of hardware platforms on which this application runs, any 1395 additional boards or processors required, and any special suggested 1396 or required configuration options. 1398 SOFTWARE PLATFORMS 1400 A list of operating systems, window systems, databases, or unbundled 1401 software packages required to run this application. 1403 NUMBER OF IMPLEMENTATIONS IN THE FIELD 1405 A statement regarding the number of implementations deployed in the 1406 field. 1408 AVAILABILITY 1410 A statement regarding the availability of the software (free or com- 1411 mercially available), a description of how to obtain the software, 1412 and (optionally) a statement regarding distribution conditions and 1413 restrictions. 1415 DATE LAST UPDATED or CHECKED 1417 The month and year within which this implementation description was 1418 last modified. 1420 NAME 1422 A-Window-To-Directory (AWTD) 1424 ABSTRACT 1426 A-Window-To-Directory is a simple-to-use DUA interface available on 1427 PC that provides access to the X.500 Directory Services. The 1428 available operations are: bind (authenticated or anonymous), read, 1429 list, compare, modify, modifyRDN, search, add, remove and unbind. It 1430 is designed to be used with the Bull X500-DUA product and for that 1431 reason is able to handle any of the defined schema. The new acronyms, 1432 objects and attributes are automatically loaded without any 1433 customisation. The interface of the application may be personalized 1434 in several ways, through Local Preferences stored on the PC and 1435 through User Settings stored on the UNIX machine that runs the Bull 1436 X500-DUA product. 1438 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 1440 A-Window-To-Directory offers all the services described in the 88 1441 CCITT X.500 standard. 1443 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 1445 No 1447 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 1449 No 1451 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 1453 No 1455 INTEROPERABILITY 1457 Is designed to interoperate with Bull X500-DUA and X500-DS products 1459 PILOT CONNECTIVITY 1461 [No information provided. -- Ed.] 1463 BUGS 1465 Bull S.A. provides complete software maintenance with the products. 1467 CAVEATS AND GENERAL LIMITATIONS 1469 [No information provided. -- Ed.] 1471 INTERNETWORKING ENVIRONMENT 1473 Proprietary protocol to access the Bull X500-DUA through TCP/IP 1474 sockets. The product may be used on LAN (Ethernet) or WAN (X.25). 1476 HARDWARE PLATFORMS 1478 386SX/DX, 486SX/DX PC Ethernet board/connection 4 MBytes RAM 3 Mbytes 1479 on disk 1481 SOFTWARE PLATFORMS 1483 MS-DOS 5.0 Microsoft Windows 3.1 Microsoft TCP/IP stack installed, 1484 version 1.0 1486 NUMBER OF IMPLEMENTATIONS IN THE FIELD 1488 [No information provided. -- Ed.] 1490 AVAILABILITY 1492 The product is commercially available since February 1995. 1494 DATE LAST UPDATED or CHECKED 1496 November 1995 1498 ADDITIONAL INFORMATION and/or COMMENTS 1500 [No information provided. -- Ed.] 1502 NAME 1504 Critical Angle X.500 Enabler 1506 (CAIx500e) 1508 ABSTRACT 1510 The X.500 Enabler product allows an LDAP-only directory server to be 1511 integrated into X.500 environments, by transparently converting X.500 1512 DAP and DSP requests into LDAP requests. 1514 The initial release scheduled for 4Q96 will allow for connections 1515 from X.500-capable clients and servers to an LDAP-capable server, and 1516 will support the following features: 1518 * LDAP version 2, as defined in RFC 1777, 1520 * all attributes defined for LDAPv2, with the exception of 1521 certificates and revocation lists, 1523 * X.500(1988) DAP and DSP protocols over TCP/IP (using RFC 1524 1006), 1526 * the following operations: Bind (with none or simple 1527 credentials), Read, Compare, List, Search, Abandon, AddEntry, 1528 ModifyEntry, RemoveEntry and ModifyRDN, 1530 * the X.500(1993) critical extensions field, to aid in 1531 deployments incorporating 1993 DSAs. 1533 This release will be available for Solaris 2.5 (SPARC and Intel) and 1534 Windows NT 4.0 Server (Intel). 1536 The product is expected to enter a public beta test period in 1537 September 1996. Beta test evaluation copies will be free (limited to 1538 two copies per site) but will be set to expire in December 1996. 1540 Released versions of X.500 Enabler will be licensed per server, and 1541 will be distributed over the Internet. 1543 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 1545 The X.500 enabler accepts DAP and DSP connections. 1547 It supports Bind (with none or simple credentials), Read, Compare, 1548 List, Search, Abandon, AddEntry, ModifyEntry, RemoveEntry and 1549 ModifyRDN. 1551 It supports the attributes and object classes defined in X.520 and 1552 X.521. 1554 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 1556 The X.500 Enabler will accept connections from X.500(1993) DUAs and 1557 DSAs. 1559 It supports the X.511(1993) critical extension mechanism. 1561 Non-critical protocol fields which do not map onto LDAPv2 are 1562 ignored. 1564 Attribute and object classes from X.520(1993) and X.521(1993) are 1565 supported, including collective. Operational attributes from X.501 1566 are supported, with the exception of subschema. 1568 As LDAPv3-based servers become available, it is expected that the 1569 X.500 Enabler will be upgraded to map more of the X.500(1993) 1570 protocol onto LDAPv3. 1572 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 1574 [RFC 1006] is the supported transport service. 1576 The product supports the object classes and attributes defined in RFC 1577 1274. 1579 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 1581 [No information provided. -- Ed.] 1583 INTEROPERABILITY 1585 The X.500 Enabler is being tested with public-domain X.500 and LDAP 1586 clients and servers, and with the various X.500 clients and servers 1587 connected to the PARADISE project, such as from the ISODE Consortium. 1589 Critical Angle intends to do interoperability testing with commercial 1590 LDAP-only servers as they become available. 1592 PILOT CONNECTIVITY 1594 This product will be used to connect LDAP-only servers, such as 1595 University of Michigan's slapd, and many vendor's forthcoming 1596 commercial LDAP server products, into the PARADISE project directory, 1597 so that they can be accessed by LDAP and X.500 DUAs throughout the 1598 project. 1600 BUGS 1602 Bugs reports may be sent to . 1604 CAVEATS AND GENERAL LIMITATIONS 1606 X.509 certificates and revocation lists are not supported due to 1607 limitations in the LDAP version 2 protocol. This restriction will be 1608 removed once LDAP version 3 servers become generally available. 1610 Under Windows NT there are limitations on the number of simultaneous 1611 incoming connections. 1613 INTERNETWORKING ENVIRONMENT 1615 This product supports RFC 1006 for DAP and DSP, and LDAP over TCP. 1617 HARDWARE PLATFORMS 1619 This product will initially be available for Sun Solaris 2.5 SPARC 1620 and Intel, and Windows NT Server 4.0 Intel. 1622 Subsequent versions may be available on additional platforms. 1624 SOFTWARE PLATFORMS 1626 An LDAP-based server, such as the freely-available slapd, is 1627 required. It does not need to run on the same host as the X.500 1628 Enabler. 1630 AVAILABILITY 1632 This product is licensed per-host server, and is distributed over the 1633 Internet. 1635 In addition to discounts for large deployment orders, subscription 1636 programs permit customers to obtain subsequent update releases at a 1637 substantial discount. 1639 Beta test evaluations are free (limited to two copies per site), and 1640 will expire 90 days after the start of the beta period. 1642 DATE LAST UPDATED or CHECKED 1644 September 1996 1646 ADDITIONAL INFORMATION and/or COMMENTS 1648 [No information provided. -- Ed.] 1650 NAME 1652 cxdua 1654 Chromatix, Inc. 10451 Twin Rivers Rd, Suite 265 Columbia, MD 21044 1656 ABSTRACT 1658 The CXDUA is a Windows 3.1 DUA that has been derrived from a highly 1659 portable and flexible Unix based Administrative Directory User Agent. 1660 The goal of the original design was to support features to assist a 1661 directory administrator in managing the directory. These features 1662 include a highly portable GUI, Entry Templates, Entry Lists, Batch 1663 Operations and Directory Control Functions. 1665 Both the Windows and the Unix versions support strong authentication. 1667 The Unix DUA has been used in various DMS and NSA pilot projects. 1669 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 1671 [No information provided. -- Ed.] 1673 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 1675 [No information provided. -- Ed.] 1677 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 1679 [No information provided. -- Ed.] 1681 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 1683 [No information provided. -- Ed.] 1685 INTEROPERABILITY 1687 [No information provided. -- Ed.] 1689 PILOT CONNECTIVITY 1691 [No information provided. -- Ed.] 1692 BUGS 1694 [No information provided. -- Ed.] 1696 CAVEATS AND GENERAL LIMITATIONS 1698 [No information provided. -- Ed.] 1700 INTERNETWORKING ENVIRONMENT 1702 [No information provided. -- Ed.] 1704 HARDWARE PLATFORMS 1706 Windows 3.1 1708 SOFTWARE PLATFORMS 1710 [No information provided. -- Ed.] 1712 NUMBER OF IMPLEMENTATIONS IN THE FIELD 1714 [No information provided. -- Ed.] 1716 AVAILABILITY 1718 The software is freely available via anonymous ftp from 1719 ftp.chromatix.com or can be obtained via the WEB at 1720 http://www.chromatix.com. Commercial versions will be available in the 1721 near future. 1723 DATE LAST UPDATED or CHECKED 1725 0496 1727 ADDITIONAL INFORMATION and/or COMMENTS 1729 [No information provided. -- Ed.] 1730 NAME 1732 Cycle (tm) LiveData (tm) (Cycle) 1734 Cycle Software,Inc. 1736 ABSTRACT 1738 A component of the Cycle Virtual Data Highway. 1740 Network software product used to break down barriers between isolated 1741 systems. Available separatly as Cycle LiveNet (DUA) and Cycle 1742 LiveNet Directory (DUA & DSA) 1744 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 1746 Cycle LiveData is compliant with the 1988 NIST OIW Stable Agreements 1747 to the extent that implementations based on the more recent stable 1748 agreements are compliant. 1750 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 1752 Cycle LiveData is compliant with the 1993 NIST OIW Stable Agreements. 1754 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 1756 Unknown 1758 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 1760 Unknown 1762 INTEROPERABILITY 1764 Not tested 1766 PILOT CONNECTIVITY 1768 Not tested 1770 BUGS 1772 No known bugs 1774 CAVEATS AND GENERAL LIMITATIONS 1776 Current release supports objects of the Application Entity Object 1777 Class only. This limitation is being relaxed in the next release. 1779 INTERNETWORKING ENVIRONMENT 1781 [RFC 1006] with TCP/IP,TP4, [RFC-1070] with IP,IPX, and NetBEUI. 1783 HARDWARE PLATFORMS 1785 Runs on Microsoft Windows hardware platforms. 1787 SOFTWARE PLATFORMS 1789 Windows 95, Windows NT, Windows for Workgroups 1791 NUMBER OF IMPLEMENTATIONS IN THE FIELD 1793 > 1,000 1795 AVAILABILITY 1797 Commercially Available. 1799 Contact: 1801 Cycle Software,Inc. 1802 1212 Hancock St. 1803 Quincy, MA 02169 1805 Voice- 617-770-9594 1806 Fax- 617-770-9903 1807 E-mail cycle@livedata.com. 1809 DATE LAST UPDATED or CHECKED 1811 1/96 1813 ADDITIONAL INFORMATION and/or COMMENTS 1815 [No information provided. -- Ed.] 1817 NAME 1819 DC X500 1821 Data Connection Ltd 1822 100 Church Street 1823 Enfield 1824 Middlesex 1825 EN2 6BQ 1826 UK 1828 ABSTRACT 1830 DC X500 provides a truly scalable X.500 based enterprise directory 1831 server with the necessary architectural flexibility to enable 1832 integration with existing database and directory technologies. 1834 From a pure X.500 standpoint, DC X500 provides a full function 1835 state-of-the-art DSA implementation. 1837 * Architected from scratch according to the 1993 X.500 1838 standards (i.e. not a 1988 DSA with 1993 features grafted on) 1840 * Support for all the key X.500 OSI protocols: 1842 * Directory Access Protocol (DAP) for user access 1844 * Directory System Protocol (DSP) for distributed DSA 1845 comunications 1847 * Directory Information Shadowing Protocol (DISP) to support 1848 replication between servers to give improved performance 1849 in a distributed network 1851 * Support of the 1993 Basic Access Control and Simplified 1852 Access Control models 1854 * Support for the key Internet X.500 related standards: 1856 * integrated Lightweight DAP (LDAP)for DUA access 1858 * Madman MIBs for easy integration with SNMP 1860 The DC X500 architecture is based on Data Connection's underlying 1861 product architecture which has evolved since 1987 and includes: 1863 * genuine multi-threaded implementation 1865 * true portability (the product is available on a range of 1866 operating systems e.g Windows NT, AIX, HP-UX. OS/2 etc and it 1867 is possible to port the core technology to any 1868 hardware/software platform) 1870 * secure service recording for operation tracking and billing 1872 * support for system monitoring (both alarms and statistics) 1873 Key product features include: 1875 * Name resolution and integrated use of Search Indices based on 1876 2-3 trees leads to high performance operation evaluation 1877 (subsecond response times on million entry DSAs) 1879 * Generic schema support based on 1993 concepts that allows 1880 customers to tailor the schema to meet their precise data 1881 structuing requirements 1883 * System recycle time is minimised (e.g. DC X500 can be backed 1884 up while running and search indices are dynamically updated), 1885 helping achieve the goal of continuous (24x7) availability 1886 and high reliability. 1888 * No artificial software constraints are imposed resulting in a 1889 truly scalable product - assuming the availability of the 1890 necessary hardware DC X500 can be configured to support 1891 millions of entries in a single DSA. 1893 DC X500 is certified for used within the Paradise Pilot project. The 1894 product has also undergone interoperability testing at the EuroSInet 1895 interoperability workshops in Europe. 1897 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 1899 From 1988 X.519 1901 9.2 Conformance by DSAs 1903 9.2.1 Statement Requirements 1905 a) directoryAccessAC and directorySystemAC are both supported 1907 b) the DSA can act as a first level DSA 1908 c) the chained mode of ooperation is supported. 1910 d) security levels none and simple as supported with the 1911 delivered product. However, the product is architectured 1912 to interface to an external security module to support 1913 strong authentication. 1915 e) DC X500 supports the selected attribute types defined 1916 in X.520. 1918 f) DC X500 supports the selected object classes defined in X.521. 1920 9.2.2 Static Requirements 1922 DC X500 supports the static requirements implied by the above 1923 statement. 1925 9.2.3 Dynamic Requirements 1927 DC X500 supports the dynamic requirements implied by the above 1928 statement. 1930 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 1932 From 1993 X.519 1934 9.2 Conformance by DSAs 1936 9.2.1 Statement Requirements 1938 a) directoryAccessAC and directorySystemAC are both supported 1940 b) n/a 1942 c) the DSA can act as a first level DSA 1944 d) the chained mode of ooperation is supported. 1946 e) security levels none and simple as supported with the delivered 1947 product. However, the product is architectured to interface to 1948 an external security module to support strong authentication. 1950 f) DC X500 supports the selected attribute types defined in X.520. 1951 Attributes based on the syntax DirectoryString using the 1952 UNIVERSAL STRING choice can be stored however the UNIVERSAL 1953 STRING choice cannot be used for matching rules. 1955 g) DC X500 supports the selected object classes defined in X.521. 1957 h) DC X500 supports the following extensions 1959 subentries Y 1960 copyShallDo Y 1961 attributeSizeLimit Y 1962 extraAttributes Y 1963 modifyRightsRequest N 1964 pagedResultsRequest N 1965 matchedValuesOnly N 1966 extendedFilter N 1967 targetSystem N 1968 useAliasOnUpdate Y 1969 newSuperior Y 1971 i) DC X500 does not support collective attributes 1973 j) DC X500 does not support hierarchical attributes 1975 k) DC X500 supports the following operational attributes 1977 Directory Operational Attributes: 1979 structural object class 1980 governing structural rule 1981 create timestamp 1982 modify timestamp 1983 creators name 1984 modifiers name 1986 prescriptive ACI 1987 entry ACI 1988 subentry ACI 1990 DSA Operational Attributes: 1992 myAccessPoint 1993 superiorKnowledge 1994 supplierKnowledge (*) 1995 consumerKnowledge(*) 1996 secondaryShadows (*) 1998 * - supported using local proprietary extension 2000 Distributed Operation Attributes (dsa-shared): 2002 specificKnowledge 2003 nonSpecificKnowledge 2005 l) DC X500 supports return of alias names 2007 m) DC X500 supports indicating that returned entry information is 2008 complete 2010 n) DC X500 supports modifying the object class attribute to add 2011 and/or remove values identifying auxiliary object classes 2013 o) DC X500 supports Basic Access Control 2015 p) DC X500 supports Simplified Access Control 2017 q) DC X500 does not support subschema administration as defined 2018 in X.501. 2020 r) DC X500 supports the name binding defined in X.521 2022 s) DC X500 cannot administer collective attributes. 2024 9.2.2 Static Requirements 2026 DC X500 supports the static requirements implied by the above 2027 statement. 2029 9.2.3 Dynamic Requirements 2031 DC X500 supports the dynamic requirements implied by the above 2032 statement. 2034 9.3 Conformance By Shadow Supplier 2036 9.3.1 Statement Requirements 2038 a) shadowSupplierInitiatedAC and shadowConsumerInitiatedAC 2039 are supported. 2041 b) security levels none and simple as supported with the delivered 2042 product. However, the product is architectured to interface to 2043 an external security module to support strong authentication. 2045 c) DC X500 supports the following UnitOfReplication: 2047 * Entry filtering on object class is supported 2049 * Selection/Exclusion of attributes via a AttributeSelection 2050 is not supported 2052 * Inclusion of subordinate knowledge in the replicated area is 2053 supported 2055 * Inclusion of extended knowledge in addition to subordinate 2056 knowledge is supported 2058 9.3.2 Static Requirements 2060 a) DC X500 supports the shadowSupplierInitiatedAC and 2061 shadowConsumerInitiatedAC 2063 b) DC X500 provides support for modifyTimestamp and createTimestamp 2064 operational attributes 2066 9.3.3 Dynamic Requirements 2068 a) DC X500 conforms to the mapping onto used services defined 2069 in clause 8 2071 b) DC X500 conforms to the procedures of X.525 as they relate 2072 to DISP. 2074 9.4 Conformance by a Shadow Consumer 2076 9.4.1 Statement Requirements 2078 a) shadowSupplierInitiatedAC and shadowConsumerInitiatedAC 2079 are supported. 2081 b) security levels none and simple as supported with the delivered 2082 product. However, the product is architectured to interface to 2083 an external security module to support strong authentication. 2085 c) DC X500 can act as a secondary supplier. 2087 d) DC X500 does not support shadowing o overlapping units 2088 of replication. (Overlapping Administration Points 2089 are supported though). 2091 9.4.2 Static Requirements 2092 a) DC X500 supports both shadowSupplierInitiatedAC and 2093 shadowConsumerInitiatedAC. 2095 b) DC X500 supports the modifyTimestamp and createTimestamp 2096 operational attributes. 2098 c) DC X500 supports the copyShallDo service element 2100 9.4.3 Dynamic Requirements 2102 a) DC X500 conforms to the mapping onto used services defined 2103 in clause 8 2105 b) DC X500 conforms to the procedures of X.525 as they relate 2106 to DISP. 2108 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 2110 [No information provided. -- Ed.] 2112 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 2114 [No information provided. -- Ed.] 2116 INTEROPERABILITY 2118 DC X500 has interoperated with the following implementations: 2120 DUAs: 2122 ICL 2123 SNI 2124 Net-tel 2125 Bull 2126 AT&T 2127 CDC 2128 Digital 2129 ICL 2130 Nexor 2132 DSAs: 2134 SNI 2135 ICL 2136 AT&T 2137 CDC 2138 Digital 2139 ICL 2140 Net-tel 2141 Nexor 2143 PILOT CONNECTIVITY 2145 DC X500 has been tested and approved for connectivity to the PARADISE 2146 pilot project. 2148 BUGS 2150 [No information provided. -- Ed.] 2152 CAVEATS AND GENERAL LIMITATIONS 2154 [No information provided. -- Ed.] 2156 INTERNETWORKING ENVIRONMENT 2158 DC X500 supports the following network connectivity: 2160 * [RFC 1006] with TCP/IP 2162 * TP0 with X.25 2164 HARDWARE PLATFORMS 2166 DC X500 is a portable product 2168 SOFTWARE PLATFORMS 2170 DC X500 is a portable product. It is available on the following 2171 plaforms: 2173 * UNIX, including 2175 * IBM AIX 2177 * HP UX 2179 * Sun Solaris 2180 * Windows NT 2182 * OS/2. 2184 Porting to further UNIX platforms is very straightforward, in 2185 particular where existing transport services are available. Other 2186 proprietary systems (such as Novell's Netware, Digital's VMS or fault 2187 tolerant or mainframe environments) can also be supported if 2188 required. 2190 NUMBER OF IMPLEMENTATIONS IN THE FIELD 2192 [No information provided. -- Ed.] 2194 AVAILABILITY 2196 DC X500 is commercially available. 2198 For further details, please contact: 2200 Nigel Ratcliffe 2201 Data Connection Ltd 2202 100 Church Street 2203 Enfield 2204 Middlesex 2205 EN2 6BQ 2206 UK 2208 Tel: +44 181 366 1177 2210 E-mail: nr@datcon.co.uk 2212 DATE LAST UPDATED or CHECKED 2214 February 1996 2216 ADDITIONAL INFORMATION and/or COMMENTS 2218 Data Connection provides a whole series of directory applications, 2219 including a corporate telephone directory, e-mail synchronisation, 2220 security services, groupware directory integration and a directory 2221 publishing application. These can be accessed by Windows 2222 applications or standard web browsers. 2224 Further information can be found at http://www.datcon.co.uk. 2226 NAME 2228 DE 2230 ABSTRACT 2232 DE (Directory Enquiries) is intended to be a simple-to-use DUA 2233 interface, suitable for the naive user, and suitable for running as a 2234 public access dua. it will work on any terminal. The user is presented 2235 with a series of (verbose) prompts asking for person's name department 2236 organization country. There is extensive on-line help. The matching 2237 algorithms are such that near matches are presented to the user before 2238 less good matches. 2240 There have been a few minor enhancements since the description in [RFC 2241 1632]. The power searching feature still sets DE apart from most other 2242 DUAs - this allows a user to search for an entry even when they do not 2243 know the name of the organisation in which the person works - you still 2244 have to specify the country. DE also allows UFN style searching. DE 2245 uses slightly different search algorithms depending on whether it is 2246 accessing part of the Directory mastered by a Quipu DSA - Quipu DSAs 2247 tend to use lots of replication and so encourage searching. DE 2248 incorporates a QOS feature where it maintains a database of past 2249 information availability and DSA responsiveness. Translations exist 2250 into at least 4 different languages. 2252 DE runs over ISODE DAP and University of Michigan LDAP. There is a 2253 version of DE, called DOS-DE, which has been ported to DOS, and this 2254 uses LDAP. 2256 DE was funded by the COSINE PARADISE project, and DE is used as the 2257 PARADISE public access dua. You can test the software by telnet to 2258 directory.ja.net and logging in as dua -- no password required. 2260 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 2262 N/A 2264 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 2266 [No information provided -- Ed.] 2268 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 2270 [RFC 1274] and [RFC 1487] Yes and yes 2271 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 2273 [RFC 1484]. yes 2275 INTEROPERABILITY 2277 N/A 2279 PILOT CONNECTIVITY 2281 The interface is widely used in the publicly accessible PARADISE 2282 directory. 2284 BUGS 2286 Doesn't handle aliases well when power searching. 2288 Send bug reports to: 2290 p.barker@cs.ucl.ac.uk 2292 CAVEATS AND GENERAL LIMITATIONS 2294 DE tries to cater well for the general case, at the expense of not 2295 dealing with the less typical. The main manifestation of this is that 2296 the current version does not handle searching under localities very 2297 well. 2299 It can handle photographs and reproduce sound attributes if these are 2300 dealt with by ancillary programs. 2302 INTERNETWORKING ENVIRONMENT 2304 [RFC 1006] with TCP/IP, TP0 or TP4 with X.25, and LDAP. 2306 HARDWARE PLATFORMS 2308 UNIX + DOS platforms 2310 SOFTWARE PLATFORMS 2312 UNIX + DOS 2313 NUMBER OF IMPLEMENTATIONS IN THE FIELD 2315 [No information provided. -- Ed.] 2317 AVAILABILITY 2319 The software is freely available from 2321 ftp://cs.ucl.ac.uk/dirpilot/de-7.0.tar.Z 2323 The DOS version is freely available. Look in the following directory: 2325 ftp://ftp.bath.ac.uk/pub/x500/dosde7/ 2327 DATE LAST UPDATED or CHECKED 2329 March 96 2331 ADDITIONAL INFORMATION and/or COMMENTS [No Information Provided -- Ed.] 2332 NAME 2334 Digital X.500 Directory Server 2335 Digital Equipment Corporation 2337 This single entry covers a number of different products 2339 ABSTRACT 2341 The Digital X.500 Directory Services product set includes a directory 2342 server product and a variety directory user agents, as well as a 2343 directory synchronizer utility. 2345 The Digital X.500 Directory Server product provides a high 2346 performance DSA implemented according to the 1993 edition of the 2347 standard. The InfoBroker Server product extends this to provide the 2348 server component for LDAP and WWW user agents. Features of these 2349 servers include: 2351 * Integrated multi-protocol support allowing concurrent DAP, 2352 DSP, DISP and DOP access over OSI and TCP/IP (using [RFC 2353 1006]) protocols. 2355 * Indexed database (DIB) to support high-performance searching 2356 and sophisticated matching including approximate match. 2358 * A DIB based on the 1993 edition Extended Information Models. 2360 * Support for chaining and referrals in support of a 2361 distributed DIB 2363 * Support for the 1993 edition Basic Access Control scheme. 2365 * Configurable schema based on the 1993 edition (including 2366 attributes, object classes, structure rules, name forms). 2368 * Support for 1993 edition Shadowing using the DISP and DOP 2369 protocol, including both incremental and on-change features 2370 for high performance. 2372 * Remote management to control DSAs and log significant events. 2374 * Support for the LDAP protocols using the InfoBroker Server 2375 product across either TCP/IP or DECnet transport protocols. 2377 * A Look-up Daemon that accepts requests from Web Browsers, 2378 allowing access to the directory from any web browser. 2380 * Both X/OPEN XDS/XOM and LDAP APIs. 2382 * An award winning documentation set. 2384 The Digital X.500 Administration Facility, X.500 Information Manager 2385 and InfoBroker Client products provide MS-Windows, Motif and command 2386 line interfaces to access and manage the information stored in the 2387 X.500 directory, including: 2389 * Support for different ways of accessing the directory, either 2390 by browsing or searching based on an extensible set of 2391 filters. 2393 * Support for bulk load, unload and reload of entries. 2395 * Driven off the same configurable schema information as the 2396 DSA allowing extensibility of window layouts and text to 2397 support customer-defined object classes and attributes. 2399 The Synchronizer-500 is an X.500 DUA which: 2401 * Enables bi-directional synchronization between X.500 and 2402 virtually ANY other non-X.500 directory facilitating common 2403 management. 2405 * Maps incoming data into X.500 using flexible configuration 2406 files 2408 * Facilitates creation of a multivendor electronic mail 2409 database, creating addresses in the appropriate syntax for 2410 any mail system. 2412 * Provides uniqueness checking on mnemonic O/R addresses, 2413 preventing address duplication 2415 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 2417 The Digital X.500 Directory Services products are based on the 1993 2418 edition standard. They are compatible with, and interwork with, 1988 2419 edition DUAs and DSAs, and are implemented to conform to relevant 2420 NIST OIW and EWOS agreements and the X.500 Implementors Guide. 2422 OSTC conformance testing (1988 DUA/DAP, DSA/DAP) has been completed 2423 and registered successfully. 2425 The X.500 Directory Server is registered as conformant to US-GOSIP. 2427 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 2429 Conformance with respect to clause 9.2 of ISO/IEC 9594-5:1993: 2431 * Supports the directoryAccessAC (DAP) and directorySystemAC 2432 (DSP) application contexts. 2434 * The DSA is capable of acting as a first-level DSA. 2436 * Chaining is supported. 2438 * Bind security levels of simple (unprotected password) and 2439 none are supported. 2441 * Supports the shadowSupplierInitiatedAC and 2442 shadowConsumerInitiatedAC in both synchronous and 2443 asynchronous variants (DISP protocol) and the 2444 directoryOperationalBindingManagementAC (DOP protocol) for 2445 shadowing 2447 * All attribute types defined in ISO/IEC 9594-6:1993 are 2448 supported except for 1993 edition supertypes and collective 2449 attributes and EnhancedSearchGuide. Customers can define new 2450 attribute types. UNIVERSAL STRING is not supported for 2451 attributes based on DirectoryString. 2453 * All object classes defined in ISO/IEC 9594-7:1993 are 2454 supported. Customers can define new object classes. 2456 * The following operational attributes are supported: 2458 governingStructureRule myAccessPoint 2459 modifyTimestamp supplierKnowledge 2460 superiorKnowledge specificKnowledge 2461 consumerKnowledge prescriptiveACI 2462 dseType entryACI 2463 createTimestamp 2464 * Dynamic modification of object class is permitted 2466 * Basic Access Control is supported with some restrictions. 2468 * All name forms defined in ISO/IEC 9594-7:1993 are supported. 2469 Customers can defined new name forms and structure rules. 2471 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 2473 The InfoBroker products support the V1 and V2 LDAP protocols for easy 2474 integration into LDAP-compliant client and server environments. 2476 Standards supported include [RFC 1006], [RFC 1274], [RFC 1277], [RFC 2477 1777], [RFC 1779]. 2479 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 2481 RFCs supported include [RFC 1278], [RFC 1558] 2483 INTEROPERABILITY 2485 Digital has performed X.500 interoperability testing at various 2486 Eurosinet and OSInet events, during the COS Pilot activity and in- 2487 house. In addition, Digital's products were part of the EEMA 2488 Interoperability Demonstration in Amsterdam 1995. 2490 Digital has achieved successful DAP and DSP interworking with a 2491 number of vendors. In the a recent Eurosinet Interoperability event, 2492 tests were performed against: 2494 AT&T ISOCOR 2495 Control Data Systems NET-TEL Computer Systems Ltd 2496 DCL (Data Connection Ltd) NEXOR 2497 ICL SNI (Siemens Nixdorf) 2499 In addition, previous interoperability tests have been performed 2500 against: 2502 Hewlett Packard Telstra 2503 ISODE Consortium UNISYS 2504 QUIPU 2505 Digital has performed limited successful 1993 DISP (Replication) 2506 interworking with two vendors at a Eurosinet Interoperability event. 2507 These were: 2509 ICL NEXOR 2511 All interoperability test results will be available on request from 2512 Digital. 2514 PILOT CONNECTIVITY 2516 Digital is actively involved in both public and private pilots of 2517 X.500. 2519 BUGS 2521 Digital provides complete software maintenance services with products 2522 on a worldwide basis. 2524 CAVEATS AND GENERAL LIMITATIONS 2526 None 2528 INTERNETWORKING ENVIRONMENT 2530 The Digital X.500 Services products operate over: 2532 * [RFC 1006] over TCP/IP 2534 * OSI TP0, TP2 and TP4 over CLNS and CONS as appropriate 2536 * TCP/IP or DECnet transport protocols to communicate with an 2537 LDAP server. 2539 HARDWARE PLATFORMS 2541 The Digital X.500 Directory Service products run on: 2543 * Alpha processors supported by Digital UNIX 2545 * Alpha and VAX processors supported by OpenVMS 2546 SOFTWARE PLATFORMS 2548 The Digital X.500 Directory Service products currently run on: 2550 * Digital UNIX running DECnet/OSI 2552 * OpenVMS/AXP running DECnet/OSI 2554 * OpenVMS/VAX running DECnet/OSI 2556 For the latest availability on these and other other hardware and 2557 software platforms please contact Digital. 2559 NUMBER OF IMPLEMENTATIONS IN THE FIELD 2561 [No information provided. -- Ed.] 2563 AVAILABILITY 2565 The Digital X.500 Directory Service products are commercially 2566 available from Digital Equipment Corporation. For further 2567 information please contact your local Digital office and quote SPD 2568 numbers 40.77.XX, 53.32.XX, 53.33.XX and 60.43.XX, or contact one of: 2570 Ian Gunn, Product Manager: Nick Tatham, Engineering 2571 Manager: 2572 Tel: +1 603 881 0762 Tel: +44 1734 203635 2573 Email: ian.gunn@zko.mts.dec.com Email: 2574 nick.tatham@reo.mts.dec.com 2575 Digital Equipment Corporation Digital Equipment Co. Ltd 2576 Corporate Software Engineering Corporate Software 2577 Engineering 2578 110 Spit Brook Road PO Box 121 2579 Nashua, NH. 03062-2698 Reading, RG2 0TU 2580 USA UK 2582 DATE LAST UPDATED or CHECKED 2584 13th November 1995 2586 ADDITIONAL INFORMATION and/or COMMENTS 2588 None 2590 NAME 2592 DIR.D(tm) V2.6 2593 Siemens Nixdorf Informationssysteme AG 2595 ABSTRACT 2597 DIR.D V2.6 is Siemens Nixdorf's directory browser product. Through 2598 its file manager like user interface only retrieval operations are 2599 supported. The DDE interface also allows for modification operations. 2600 DIR.D is an MS-Windows application acting as an LDAP client. 2602 Among others, DIR.D has the following features: 2604 * Graphical representation of the DIT 2606 * Tree browsing 2608 * Simple and complex searches, including approximate search 2610 * Adaptable to any directory schema 2612 * Configurable user interface 2614 * Automatic unbind after idle time 2616 * Anonymous and simple unprotected bind 2618 * Tight integration with SNI's X.400 user agent MAIL.D and CIT 2619 product ComfoPhone 2621 * Data transfer to Windows applications via clipboard, file, 2622 Drag&Drop, and DDE 2624 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 2626 DIR.D V2.6 is an LDAP client. 2628 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 2630 DIR.D V2.6 is an LDAP client. 2632 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 2634 DIR.D V2.6 is compliant with the following RFCs: [RFC 1777], [RFC 2635 1778], [RFC 1779]. 2637 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 2639 DIR.D V2.6 is compliant with the following RFCs: [RFC 1278], [RFC 2640 1558]. 2642 INTEROPERABILITY 2644 DIR.D V2.6 is based on University of Michigan's LDAP implementation 2645 V3.0. It can interoperate with any LDAP server. 2647 PILOT CONNECTIVITY 2649 DIR.D V2.6 is used to browse in the European NameFLOW-PARADISE pilot 2650 network. 2652 BUGS 2654 To report bugs and/or to retrieve additional information on SNI's 2655 directory products please send mail to infoline- 2656 com@s41.mch1.x400scn.sni.de. 2658 CAVEATS AND GENERAL LIMITATIONS 2660 DIR.D V2.6 was designed for information retrieval. 2662 INTERNETWORKING ENVIRONMENT 2664 LDAP with TCP/IP 2666 HARDWARE PLATFORMS 2668 PC (Intel) 2670 SOFTWARE PLATFORMS 2672 Windows 3.1 + Winsockets 2673 Windows for Workgroups 3.11 + Winsockets 2674 Windows 95 2675 Windows NT 3.5 2676 OS/2 3.0 + Windows for OS/2 + Winsockets 2678 NUMBER OF IMPLEMENTATIONS IN THE FIELD 2680 > 10,000 2682 AVAILABILITY 2684 DIR.D V2.6 can be delivered as a binary product. It is commercially 2685 available from: 2687 Siemens Nixdorf Informationssysteme AG 2688 ASW BA COM 1 2689 D-81730 Munich 2690 Germany 2692 Please contact 2694 Giovanni Rabaioli 2695 Voice: +49/89-636-41095 2696 Fax: +49/89-636-42552 2697 Mail: Giovanni.Rabaioli@mch.sni.de 2699 DATE LAST UPDATED or CHECKED 2701 April 1996 2703 ADDITIONAL INFORMATION and/or COMMENTS 2705 The following X.500 products are also part of SNI's X.500 product 2706 family: 2708 DIR.X V4.0 1993 X.500 Directory Service 2709 DIR.X V3.1 1988 X.500 Directory Service 2710 ORG.D V2.1 Full administrative LDAP browser 2711 DIR.X-SYNC V2.0 Directory synchronization 2712 NAME 2714 DIR.X (tm) V3.1 2715 Siemens Nixdorf Informationssysteme AG 2717 ABSTRACT 2719 DIR.X V3.1 is Siemens Nixdorf's Directory Service product compliant 2720 with the 1988 ITU-T X.500 recommendations. Siemens Nixdorf has 2721 supplied its Directory Service product as the GDS (Global Directory 2722 Service) component to OSF DCE. However, DIR.X V3.1 has a number of 2723 features and enhancements which are not available in the GDS 2724 component of OSF DCE. 2726 DIR.X V3.1 is a distributed, replicated Directory Service. It 2727 consists of DSA, DUA and a tools package including comfortable 2728 administration and management utilities. DIR.X implements the 2729 protocol stack ranging from LDAP, DAP, DSP over ACSE, ROSE, 2730 Presentation, Session down to [RFC 1006]. On transport layer it 2731 supports TCP/IP and OSI LAN/WAN protocols. 2733 Data stored by DIR.X can be accessed via 2735 * the MS-Windows user interfaces DIR.D/ORG.D which are 2736 available as separate products from Siemens Nixdorf 2738 * any third-party LDAP or DAP browser 2740 * directory applications using the standardized X/Open XDS/XOM 2741 APIs (Directory Service / OSI Abstract Data Manipulation). 2742 The Siemens Nixdorf implementation was the first to gain 2743 XPG4-certification. 2745 * a command-line administration program 2747 * a menu-driven administration program 2749 * WWW 2751 * a shell interface 2753 * the Query-by-mail interface of SNI's directory 2754 synchronization product DIR.X-SYNC 2756 DIR.X enables 2758 * The storage of globally-unique, tree-like name structures 2759 which can be mapped onto organizations. 2761 * The use of several alternative names (aliases) for one and 2762 the same directory entry. 2764 * Search queries that allow the user to select objects on the 2765 basis of specific attributes and their values, as with a 2766 "Yellow Pages" telephone directory 2768 * Tree management functions which can cover entire subtrees. 2770 * The creation and automatic updating of copies ("shadows") 2771 from remote computers. 2773 * Access protection at attribute level, which regulates access 2774 on an object-specific basis. 2776 * The storage of unstructured attributes (graphics, pixels). 2778 The tools package of DIR.X V3.1 includes: 2780 * gdssetup: A simple-to-use tool for the generation and 2781 initialization of a directory configuration. 2783 * gdshdsch: Enables the directory administrator to modify the 2784 directory schema off-line. 2786 * X.500 MIB access via SNMP 2788 * gdscp: A TCL based administration tool for UNIX clients with 2789 full XDS functionality 2791 * gdshd: A powerful import/export tool 2793 Additional features include: 2795 * support for ISO 8859-1 characters 2797 * dynamic schema modifications 2799 * caching. 2801 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 2803 DIR.X V3.1 fully complies with the following ITU-T recommendations 2804 and ISO/IEC standards: 2806 ITU-T ISO/IEC Title 2807 X.500 9594-1 Overview of Concepts, Models, and Services 2808 X.501 9594-2 Models 2809 X.511 9594-3 Abstract Service Definition 2810 X.518 9594-4 Procedures for Distributed Operations 2811 X.519 9594-5 Protocol Specifications 2812 X.520 9594-6 Selected Attribute Types 2813 X.521 9594-7 Selected Object Classes 2814 X.509 9594-8 Authentication Framework 2816 DIR.X V3.1 was successfully conformance tested by the OSI Test 2817 Laboratory of Siemens Nixdorf. The OSI Test Laboratory is accredited 2818 by BAPT/DEKITZ (registration number TTI-P-G055/92-40). Test reports, 2819 PICS per X.581/X.582 and PIXITs are available for all tested 2820 protocols: DSA/DAP, DUA/DAP, Presentation, ACSE, and Session embedded 2821 in X.500. 2823 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 2825 DIR.X V3.1 is not compliant with the 1993 ITU-T recommendations. 2826 Please refer to the DIR.X V4.0 implementation description. 2828 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 2830 DIR.X V3.1 is compliant with the following RFCs: [RFC 1274], [RFC 2831 1277], [RFC 1565], [RFC 1567], [RFC 1777], [RFC 1778], [RFC 1779]. 2833 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 2835 DIR.X V3.1 is compliant with the following RFCs: [RFC 1278], [RFC 2836 1558], [RFC 1801]. 2838 INTEROPERABILITY 2840 DIR.X V3.1 can interoperate with: 2842 * OSF DCE Global Directory Service (GDS) 2843 * ISODE Consortium Quipu V8.0 2845 * ISODE Consortium 93 DSA R3.0 2847 * AT&T OpenDirectory 2.0.1 2849 * Bull X.500-DS and X.500-DUA 2851 * Control Data MailHub 2.4 2853 * Data Connection DC X500 V1 2855 * Digital DEC X.500 Directory Services V2.0 2857 * ICL I500 DSA V5.2 2859 * ISOCOR ISOPLEX DS V1.00 2861 * NET-TEL RouteFinder 500 DSA 1.0 2863 * NEXOR Messageware Directory Server V0.9 2865 * Olivetti UX_X500 V1.1 2867 * Unisys TransIT X.500 V7.1 2869 PILOT CONNECTIVITY 2871 Several DIR.X V3.1 DSAs and DUAs are connected to the European 2872 NameFLOW- PARADISE pilot network. 2874 BUGS 2876 To report bugs and/or to retrieve additional information on SNI's 2877 directory products please send mail to infoline- 2878 com@s41.mch1.x400scn.sni.de. 2880 CAVEATS AND GENERAL LIMITATIONS 2882 DIR.X V3.1 is highly portable and without any general limitation. 2883 SNMP support is available for SNI platforms only. 2885 INTERNETWORKING ENVIRONMENT 2887 [RFC 1006] with TCP/IP 2888 OSI TP0, TP2 with X.25 2889 OSI TP4 with CLNP 2890 OSI TP4 with CONS (LAN) 2892 HARDWARE PLATFORMS 2894 SNI platforms (RM200/300/400/600, Pyramid Nile 100/150, MX300i/500i) 2895 for X.25: X.25 board needed 2897 IBM RS/6000 2898 for X.25: X.25 board needed 2900 HP 9000 2901 for X.25: X.25 board needed 2903 Sun Sparc 2904 no X.25 board needed (X.25 can use the serial line) 2906 PC (Intel) 2907 for X.25: X.25 board needed 2909 SOFTWARE PLATFORMS 2911 SINIX 5.42 + CMX + XTI 2912 for X.25: WAN-CCP needed 2914 Pyramid Nile 100/150 DC/OSx1.1 2916 Unixware 2918 AIX 3.2 2919 for X.25: OSI/6000 needed 2921 HP-UX 9.01 2922 for X.25: OTS 9000 needed 2924 Solaris 2.3 2925 for X.25: SunLink X.25 and SunLink OSI needed 2927 NUMBER OF IMPLEMENTATIONS IN THE FIELD 2929 100 and growing 2931 AVAILABILITY 2933 DIR.X V3.1 can be delivered as a binary product or as source to OEM 2934 customers. It is commercially available from: 2936 Siemens Nixdorf Informationssysteme AG 2937 ASW BA COM 1 2938 D-81730 Munich 2939 Germany 2941 Please contact 2943 Giovanni Rabaioli 2944 Voice: +49/89-636-41095 2945 Fax: +49/89-636-42552 2946 Mail: Giovanni.Rabaioli@mch.sni.de 2948 DATE LAST UPDATED or CHECKED 2950 April 1996 2952 ADDITIONAL INFORMATION and/or COMMENTS 2954 The following X.500 products are also part of SNI's X.500 product 2955 family: 2957 DIR.X V4.0 1993 X.500 Directory Service 2958 DIR.D V2.6 LDAP browser for information retrieval 2959 ORG.D V2.1 Full administrative LDAP browser 2960 DIR.X-SYNC V2.0 Directory synchronization 2961 NAME 2963 DIR.X (tm) V4.0 2964 Siemens Nixdorf Informationssysteme AG 2966 ABSTRACT 2968 DIR.X V4.0 is Siemens Nixdorf's Directory Service product compliant 2969 with the 1993 ITU-T X.500 recommendations. The implementation 2970 incorporates SNI's experience of 10 years development, support and 2971 maintenance of the DIR.X products conformant to the 1988 Directory 2972 Standards, and has the following main features: 2974 * It conforms to the 1993 Directory standards, with particular 2975 emphasis on the requirements for interoperability with other 2976 X.500 implementations 2978 * The implementation is scaleable: it handles small-scale 2979 workgroup directories as well as very large directories for 2980 backbone solutions in large organisations 2982 * The implementation is extensible: new functionality can 2983 easily be incorporated 2985 * Existing databases and proprietary directory services can be 2986 accessed or integrated with the implementation. 2988 * Particular emphasis is placed on ease of administration of 2989 the Directory Service a service based on DIR.X V4.0 can be 2990 administered effectively from a central site, including the 2991 management of configuration and monitoring options 2993 * The implementation has a high throughput performing well not 2994 only on small systems, but also on high-performance backend 2995 servers, handling hundreds of requests in parallel on a 2996 multiprocessor machine. 2998 DIR.X V4.0 is a distributed, replicated Directory Service. It 2999 consists of: 3001 * DSA 3003 * DUA 3004 * Command-line DUA using a TCL (Tool Control Language) shell 3005 interface (dirxcp) 3007 * Management centre (dirxadm) 3009 * Toolkit for application development 3011 Data stored by DIR.X can be accessed via 3013 * the MS-Windows user interfaces DIR.D/ORG.D which are 3014 available as separate products from Siemens Nixdorf 3016 * any third-party LDAP or DAP browser 3018 * directory applications using the standardized X/Open XDS/XOM 3019 APIs (Directory Service / OSI Abstract Data Manipulation). 3020 The Siemens Nixdorf implementation was the first to gain 3021 XPG4-certification. 3023 * a command-line administration program 3025 * a menu-driven administration program 3027 * WWW 3029 * a shell interface 3031 * the Query-by-mail interface of SNI's directory 3032 synchronization product DIR.X-SYNC 3034 DIR.X V4.0 is fully backwards compatible with 1988 DSAs and DUAs. 3036 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 3038 DIR.X V4.0 is fully backwards compatible with the following ITU-T 3039 recommendations and ISO/IEC standards: 3041 ITU-T ISO/IEC Title 3042 X.500 9594-1 Overview of Concepts, Models, and Services 3043 X.501 9594-2 Models 3044 X.511 9594-3 Abstract Service Definition 3045 X.518 9594-4 Procedures for Distributed Operations 3046 X.519 9594-5 Protocol Specifications 3047 X.520 9594-6 Selected Attribute Types 3048 X.521 9594-7 Selected Object Classes 3049 X.509 9594-8 Authentication Framework 3051 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 3053 DIR.X V4.0 fully complies with the following ITU-T recommendations 3054 and ISO/IEC standards: 3056 ITU-T ISO/IEC Title 3057 X.500 9594-1 Overview of Concepts, Models, and Services 3058 X.501 9594-2 Models 3059 X.511 9594-3 Abstract Service Definition 3060 X.518 9594-4 Procedures for Distributed Operations 3061 X.519 9594-5 Protocol Specifications 3062 X.520 9594-6 Selected Attribute Types 3063 X.521 9594-7 Selected Object Classes 3064 X.509 9594-8 Authentication Framework 3065 X.525 9594-9 Replication 3067 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 3069 DIR.X V4.0 is compliant with the following RFCs: [RFC 1274], [RFC 3070 1277], [RFC 1565], [RFC 1567], [RFC 1777], [RFC 1778], [RFC 1779]. 3072 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 3074 DIR.X V4.0 is compliant with the following RFCs: [RFC 1278], [RFC 3075 1558], [RFC 1801]. 3077 INTEROPERABILITY 3079 Interoperability tests have not been completed yet. 3081 PILOT CONNECTIVITY 3083 [No information provided. -- Ed.] 3085 BUGS 3087 To report bugs and/or to retrieve additional information on SNI's 3088 directory products please send mail to infoline- 3089 com@s41.mch1.x400scn.sni.de. 3091 CAVEATS AND GENERAL LIMITATIONS 3093 DIR.X V4.0 is highly portable and without any general limitation. 3095 INTERNETWORKING ENVIRONMENT 3097 [RFC-1006] with TCP/IP 3098 OSI TP0, TP2 with X.25 3099 OSI TP4 with CLNP 3100 OSI TP4 with CONS (LAN) 3102 HARDWARE PLATFORMS 3104 SNI platforms (RM200/300/400/600, Pyramid Nile 100/150) 3105 for X.25: X.25 board needed 3107 IBM RS/6000 3108 for X.25: X.25 board needed 3110 HP 9000 3111 for X.25: X.25 board needed 3113 Sun Sparc 3114 no X.25 board needed (X.25 can use the serial line) 3116 PC (Intel) 3117 for X.25: X.25 board needed 3119 SOFTWARE PLATFORMS 3120 SINIX 5.42 + CMX + XTI 3121 for X.25: WAN-CCP needed 3123 Pyramid Nile 100/150 DC/OSx1.1 3125 Windows NT 3.51 3127 AIX 4.1 3128 for X.25: OSI/6000 needed 3130 HP-UX 10.0 3131 for X.25: OTS 9000 needed 3133 Solaris 2.5 3134 for X.25: SunLink X.25 and SunLink OSI needed 3136 NUMBER OF IMPLEMENTATIONS IN THE FIELD 3138 Field testing to be started in Summer 1996. 3140 AVAILABILITY 3142 DIR.X V4.0 can be delivered as a binary product or as source to OEM 3143 customers. It is commercially available from: 3145 Siemens Nixdorf Informationssysteme AG 3146 ASW BA COM 1 3147 D-81730 Munich 3148 Germany 3150 Please contact 3152 Giovanni Rabaioli 3153 Voice: +49/89-636-41095 3154 Fax: +49/89-636-42552 3155 Mail: Giovanni.Rabaioli@mch.sni.de 3156 DATE LAST UPDATED or CHECKED 3158 April 1996 3160 ADDITIONAL INFORMATION and/or COMMENTS 3162 The following X.500 products are also part of SNI's X.500 product 3163 family: 3165 DIR.X V3.1 1988 X.500 Directory Service 3166 DIR.D V2.6 LDAP browser for information retrieval 3167 ORG.D V2.1 Full administrative LDAP browser 3168 DIR.X-SYNC V2.0 Directory synchronization 3169 NAME 3171 DIR.X-SYNC (tm) V2.0 Siemens Nixdorf Informationssysteme AG 3173 ABSTRACT 3175 DIR.X-SYNC V2.0 enables the synchronization of existing e-mail 3176 address directories in the X.500-based DIR.X directory service. The 3177 standard DIR.X, DIR.X-SYNC and DIR.D (all available from Siemens 3178 Nixdorf) products are the foundations on which the corporate 3179 directory solutions can be tailored to meet the customer's needs. The 3180 corporate directory then becomes the universal information system 3181 within the company. 3183 The user can access corporate directory information in different 3184 ways: 3186 * Using DIR.D, SNI's Windows client for the X.500 service, PC 3187 users can gain easy access to the DIR.X server containing the 3188 corporate directory data. The data found can be transferred 3189 to other applications by means of DDE, drag and drop or cut 3190 and paste. (See DIR.D V2.6 for further information). 3192 * Query by mail: Authorized users can access data stored in the 3193 central or distributed directory system over their own mail 3194 system. DIR.X-SYNC retrieves the inquiry transmitted by mail 3195 and directs it on to the X.500 service. The search results 3196 are then delivered back to the user by mail. Using a WWW 3197 interface based on TCL scripts 3199 Query by mail does not require additional software on the end system. 3200 Each mail system connected to the X.400 backbone (e.g. MS-Mail, 3201 cc:Mail etc.) can use this function. DIR.X-SYNC currently supports 3202 the address formats of the following e-mail systems: 3204 * MAIL.X-OD V2.3 3206 * MAIL.2000 V1.2, AKOM 3208 * MS-Mail 3210 * cc:Mail 3211 * Intelligent Messaging Mail (Banyan) 3213 The standardized ISO-10021 interface for X.400 addresses is 3214 supported, enabling need for extension. This means that any type of 3215 system capable of generating this format (e.g. WordPerfect, Lotus 3216 Notes) can be connected. Address acknowledgment is carried out in ISO 3217 format. 3219 Functions for the administrator: 3221 * Export: Addresses can be exported from local directories. 3222 They are delivered as mail messages in ASCII format to the 3223 DIR.X-SYNC server. 3225 * Upload: The upload server stores the exported local addresses 3226 in DIR.X as globally valid X.400 addresses. 3228 * Query by Mail: DIR.X-SYNC enables mail members to send a 3229 search to the DIR.X-SYNC server by e-mail. Using this 3230 function, authorized administrators of the synchronized 3231 directories can acquire copies of the corporate directory 3232 data. 3234 * Administration of the DIR.X-SYNC server with an 3235 administration tool which can be used via command line or a 3236 command file. 3238 Other features include: 3240 * Replication and distribution: In addition to the central 3241 solution with a single corporate directory server, DIR.X-SYNC 3242 also supports replicated or distributed data storage in 3243 DIR.X-SYNC server. 3245 * Authentication/Authorization: To prevent unauthorized use of 3246 the corporate directory system, the O/R addresses of the 3247 authorized administrators and users are configured by the 3248 DIR.X-SYNC administrator. When a query by mail or an update 3249 arrives, the sender address is compared with this address. 3251 * Logging: In the case of error, e.g. incorrect file format, 3252 the sender (and the administrator configurable) are informed 3253 of the fault by mail. At the same time, the error message is 3254 saved in a log file for the DIR.X-SYNC administrator. In 3255 addition, a "history file" enables the monitoring of the 3256 uploads that have run or are currently running 3258 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 3260 DIR.X-SYNC is a directory application. 3262 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 3264 DIR.X-SYNC is a directory application. 3266 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 3268 [No information provided. -- Ed.] 3270 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 3272 [No information provided. -- Ed.] 3274 INTEROPERABILITY 3276 [No information provided. -- Ed.] 3278 PILOT CONNECTIVITY 3280 [No information provided. -- Ed.] 3282 BUGS 3284 To report bugs and/or to retrieve additional information on SNI's 3285 directory products please send mail to infoline- 3286 com@s41.mch1.x400scn.sni.de. 3288 CAVEATS AND GENERAL LIMITATIONS 3290 The DIR.X-SYNC server runs with SNI's mail service products MAIL.X 3291 V2.3 or MAIL.X V3.0. 3293 INTERNETWORKING ENVIRONMENT 3295 [No information provided. -- Ed.] 3297 HARDWARE PLATFORMS 3299 SNI platforms (RM200/300/400/600, MX300i/500i) 3300 HP 9000 3302 SOFTWARE PLATFORMS 3304 SINIX 5.42 3306 HP-UX 10.0 3308 NUMBER OF IMPLEMENTATIONS IN THE FIELD 3310 100 3312 AVAILABILITY 3314 DIR.X-SYNC V2.0 can be delivered as a binary product. It is 3315 commercially available from: 3317 Siemens Nixdorf Informationssysteme AG 3318 ASW BA COM 1 3319 D-81730 Munich 3320 Germany 3322 Please contact 3324 Giovanni Rabaioli 3325 Voice: +49/89-636-41095 3326 Fax: +49/89-636-42552 3327 Mail: Giovanni.Rabaioli@mch.sni.de 3329 DATE LAST UPDATED or CHECKED 3331 April 1996 3333 ADDITIONAL INFORMATION and/or COMMENTS 3335 The following X.500 products are also part of SNI's X.500 product 3336 family: 3338 DIR.X V4.0 1993 X.500 Directory Service 3339 DIR.X V3.1 1988 X.500 Directory Service 3340 DIR.D V2.6 LDAP browser for information retrieval 3341 ORG.D V2.1 Full administrative LDAP browser 3342 NAME 3344 DX500 OpenDirectory(tm) 3346 Datacraft Australia Pty Ltd 3348 ABSTRACT 3350 DX500 OpenDirectory is a family of carrier grade, version 1993 X.500 3351 conformant products 3353 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 3355 [No information provided. -- Ed.] 3357 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 3359 See WEB page: http://www.datacraft.com.au/dx500ovr.html for up to 3360 date details. 3362 PICS are available upon request. 3364 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 3366 [No information provided. -- Ed.] 3368 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 3370 [No information provided. -- Ed.] 3372 INTEROPERABILITY 3374 OpenDirectory DSA supports: 3376 * DX-plorer, 93 full DAP stack, [RFC 1006] client over Winsock 3378 * ISOPRO 1.5+ messaging clients 3379 * ISOPRO for MAPI messaging clients 3380 * ISOPLEX Navigator 3381 * ISOPLEX Management Centre 3382 * ISOPLEX DS 3383 * ISOPLEX Web Gateway 3385 * Uni of Mich. - WAX500 3387 * Quipu emulation mode 3389 PILOT CONNECTIVITY 3391 [No information provided. -- Ed.] 3393 BUGS 3395 [No information provided. -- Ed.] 3397 CAVEATS AND GENERAL LIMITATIONS 3399 [No information provided. -- Ed.] 3401 INTERNETWORKING ENVIRONMENT 3403 [No information provided. -- Ed.] 3405 HARDWARE PLATFORMS 3407 [No information provided. -- Ed.] 3409 SOFTWARE PLATFORMS 3411 [No information provided. -- Ed.] 3413 NUMBER OF IMPLEMENTATIONS IN THE FIELD 3415 [No information provided. -- Ed.] 3417 AVAILABILITY 3419 The software is commercially available from Datacraft, or its 3420 distributors. 3422 DATE LAST UPDATED or CHECKED 3424 March, 96 3426 ADDITIONAL INFORMATION and/or COMMENTS 3428 Capable of supporting a million entries, with subsecond response 3429 time, on small Unix, with 32 mgbytes of ram, due to a unique patented 3430 meta-data design. 3432 NAME 3434 Forum LOOK'UP (tm) 3436 Telis Systemes & Communications 3438 ABSTRACT 3440 Forum LOOK'UP (tm) is a Corporate directory solution based on the 3441 X.500 recommendations. It includes: 3443 * a Directory System Agent (DSA), 3445 * Directory User Agents (DUAs). 3447 * local network connections 3449 * remote workstation access 3451 * a WEB and videotex access 3453 * data updating tools 3455 * a directory editing tool 3457 Forum LOOK'UP is a product based on PIZARRO, the research prototype 3458 developed at INRIA by Christian Huitema's team, and commercialized by 3459 Telis, a member of the France Telecom group. 3461 Characteristics of the DSA are: 3463 * The DAP and DSP protocols are provided conformant with X.500 3464 (88). 3466 * The DIB is maintained in ASN.1 encoded format in the Unix 3467 file system. 3469 * Utilities are provided to load and dump the DIB from and to 3470 ASCII text files. 3472 * As an option, an ORACLE V7 database can also be used. 3474 * The DIT structure is held in main memory. Frequently used 3475 attributes may be held in inverted tables in memory to speed 3476 up searches. 3478 * Knowledge management: knowledge on managed domains is stored 3479 in Forum LOOK'UP specific attributes of the DSA entries. 3481 * Schema: The X.500 (88), X.400 (88) and most of the Cosine and 3482 Internet Schema are supported. Object class and attribute 3483 definitions are enforced. Users may define their own. 3485 * Simple authentication is provided strong authentication and 3486 signed operations have been tested operationally through 3487 Telis's participation in PASSWORD, a VALUE project with aim 3488 to pilot a European security infrastructure for network 3489 applications. 3491 * Access control : the DSA offers a mechanism defined by Telis 3492 that is functionally equivalent to a profile of the X500 '93 3493 access control mechanism. The mechanism is based on the 3494 notion of administrative domains (autonomous and semi- 3495 autonomous). A domain defines the user groups (categories) 3496 and their access rights (consult, modify) to specified 3497 attribute types. The access rights are defined in 3498 prescriptive and entry ACI attributes. 3500 * Phonetic searches : administrators may specify a language 3501 (English, French, ...) for a subtree of the DIT. Approximate 3502 (phonetic) searches will then be carried out in the given 3503 language. The software loads a rule database to which new 3504 languages and new rules may be added easily. 3506 * Management: a Forum LOOK'UP DSA object has been defined to 3507 allow operational parameters of the DSA to be managed via 3508 DAP. Forum LOOK'UP conforms to X.500 (88) as specified in 3509 poaragraph 9 of X.519 Administration tools are provided : 3511 * to generate usage statistics automatically and distribute 3512 these by mail to administrators 3514 * to replicate subtrees of the DIT to other FORUM LOOK'UP 3515 DSAs and automatically update shadow copies, 3517 * to extract hardcopy listings from the database in an Excel 3518 compatible format for "paper" directories, all the 3519 management tasks are performed through a GUI (X/Motif). 3521 * The GUI includes a "dashboard" for monitoring of servers and 3522 the hardware they are installed on. 3524 * The DUAs include a graphical directory browser with powerful 3525 search functionality for PCs and Macintosh. 3527 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 3529 Forum LOOK'UP conforms to X.500 (88) as specified in paragraph 9 of 3530 X.519 3532 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 3534 [No information provided. -- Ed.] 3536 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 3538 [RFC 1274], [RFC 1277], [RFC 1778], [RFC 1779] are supported 3540 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 3542 [RFC 1278], [RFC 1279] are supported 3544 INTEROPERABILITY 3546 Through the use of Forum LOOK'UP in the French Paradise pilot, 3547 interoperability has been informally but extensively tested with 3548 Quipu, Marben, SNI DIR/X. 3550 PILOT CONNECTIVITY 3552 DSA connectivity to the PARADISE pilot. 3554 BUGS 3556 Forum LOOK'UP is a commercial product. As such, it is supported and 3557 bugs are fixed when detected. 3559 Bug reports can be sent to our support team via electronic mail. 3561 CAVEATS AND GENERAL LIMITATIONS 3563 * The DIT structure and inverted attribute tables are stored in 3564 main memory. 3566 * The recommended main memory size for a DSA is 1 kb per node, 3567 i.e., 10 Mb for a database of 10,000 objects. 3569 * The current recommended maximum for the proprietary database 3570 (based on the Unix file system) is a database size of the order 3571 of 100,000 objects. 3573 * For a larger database one unique server (up to 300,000 objects), 3574 the use of the Oracle database is recommended 3576 * Of the selected attribute types defined in X.500 (88), the 3577 searchGuide attribute is not supported 3579 * neither are the following attributes from the Cosine and 3580 Internet Schema [RFC 1274]: OtherMailbox, MailPreferenceOption 3581 and the various quality attributes. 3583 INTERNETWORKING ENVIRONMENT 3585 Forum LOOK'UP includes a transport stack for TP0 with TCP/IP [RFC 3586 1006] and X.25. The stack has been ported to SunNet OSI for TP4 with 3587 CLNP. 3589 DUAs on a LAN (Novell Netware, Microsoft Lan Manager, IBM Lan Server) 3590 can access the DSA without the need for IP on every Workstation. A 3591 module (called SOLO server) available on Novell, OS/2 and UNIX allows 3592 to have an IP or X.25 stack only on the file server. It is in charge 3593 of forwarding the request to a DSA. 3595 A direct access (DUA / DSA) through IP, X.25, PSTN or ISDN is also 3596 available. 3598 HARDWARE PLATFORMS 3600 Forum LOOK'UP can easily be ported to any UNIX machine. 3602 It currently runs on: Sun Solaris and Hewlett Packard. 3604 A port on IBM AIX is to be completed. 3606 SOFTWARE PLATFORMS 3608 The Forum LOOK'UP server is portable to any UNIX-like operating 3609 system. X/Motif is the interface used for management. 3611 The DUAs are available on Windows and Macintosh. 3613 ORACLE V7 can be used as a database (option). 3615 NUMBER OF IMPLEMENTATIONS IN THE FIELD 3617 30 servers 3619 AVAILABILITY 3621 Forum LOOK'UP is commercially available. For further information 3622 contact: 3624 Laurence Puvilland, Product manager 3625 Email: C=fr A=atlas P=telis-sc O=telis-sc OU1=paris S=puvilland 3626 laurence.puvilland@paris.telis-sc.fr 3628 or: 3630 Ascan Woermann, X.500 development manager 3631 Email: C=fr A=atlas P=telis-sc O=telis-sc OU1=sophia S=Woermann 3632 ascan.woermann@sophia.telis-sc.fr 3634 DATE LAST UPDATED or CHECKED 3636 April 1996 3638 ADDITIONAL INFORMATION and/or COMMENTS 3640 [No information provided. -- Ed.] 3642 NAME 3644 FX*500 3646 Firefox International Limited 3648 ABSTRACT 3650 FX*500 is a core component of Firefoxs product suite for mail, 3651 messaging and directories. 3653 FX*500 provides a Directory System Agent (DSA) which adheres to the 3654 latest 1993 X.500 standards. 3656 FX*500 may be used in conjunction with the Firefox FX*400 messaging 3657 products or may be combined with a range of Directory User Agent and 3658 Gateway products in order to satisfy a broad range of directory 3659 requirements. 3661 FX*500 affords unique integration opportunities with Novell's NetWare 3662 Directory Service (NDS) by offering the option of true dynamic 3663 directory integration between NDS and X.500. 3665 FX*500 provides support for key features of the X.500 1993 standard 3666 while continuing to support interworking with 1988 based directory 3667 user agents and system agents. The main 1993 features of X.500 3668 supported by FX*500 are: 3670 * Basic Access Control 3672 * The 1993 DSA Information Model 3674 * Replication and Shadowing 3676 In summary, FX*500 supports: 3678 * 1988 and 1993 X.500 Directory Access Protocol (DAP) 3680 * 1988 and 1993 X.500 Directory System Protocol (DSP) 3682 * 1993 X.500 Directory Information Shadowing Protocol (DISP) 3684 * 1993 Basic (or Simplified) Access Control 3685 * the Lightweight Directory Access Protocol (LDAP), as defined 3686 by [RFC 1777] 3688 * configuration of knowledge information for distributed 3689 operation using 1993 operational attributes 3691 * local management services, including a knowledge 3692 configuration application and extensive diagnostic facilities 3694 * an extended set of management applications 3696 * operation in a wide variety of network environments including 3697 connectivity over X.25, TCP/IP [RFC 1006] and OSI LANs. 3699 * an application developer's toolkit 3701 The optional application developer's toolkit includes: 3703 * the X/Open Directory Services (XDS) API to support directory 3704 user agent applications 3706 * a Gateway (G-XDS) API which is based on a simplified version 3707 of the XDS API syntax and allows developers to implement 3708 gateways to existing/ proprietary directory databases 3710 * a Network Management Interface (NMI) to support management 3711 applications and integration with management services. 3713 FX*500 is delivered with a schema defined to support the Common Use 3714 and MHS (X.402) Schemas defined by UK GOSIP V4. The subschema for 3715 FX*500 can be modified by the customer and updated dynamically. 3717 FX*500 provides for search optimisation by supporting keyed search 3718 whereby specific attributes can be identified as 'keyed' through 3719 local configuration data. This optimisation avoids the need to do a 3720 "brute force" search which requires a traversal of all the nodes of a 3721 subtree. Approximate match search filters are also supported by using 3722 a phonetic search based on the "Soundex" algorithm. 3724 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 3726 FX*500 meets both the static and dynamic requirements implied by 3727 section 9.2 of X.519 1988. 3729 From section 9.2 of X.519 1988 regarding DSA conformance: 3731 * FX*500 supports both the directoryAccessAC and 3732 directorySystemAC application contexts. 3734 * The FX*500 DSA can act as a first level DSA 3736 * The chained mode of operation is supported. 3738 * The security levels "none" and "simple" are supported, the 3739 "strong" security level can be supported with the addition of 3740 an appropriate security module. 3742 * The attribute types defined in X.520 and the object classes 3743 defined in X.521 are supported. 3745 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 3747 FX*500 meets both the static and dynamic requirements implied by 3748 sections 9.2, 9.3 and 9.4 of X.519 1993 regarding the conformance of 3749 DSA, Shadow Supplier and Shadow Consumer. 3751 From section 9.2 of X.519 1993 regarding DSA conformance: 3753 * FX*500 supports both the directoryAccessAC and 3754 directorySystemAC application contexts 3756 * the FX*500 DSA can act as a first level DSA 3758 * the chained mode of operation is supported. 3760 * the security levels "none" and "simple" are supported, the 3761 "strong" security level can be supported with the addition of 3762 an appropriate security module. 3764 * the selected attribute types defined in X.520 are supported. 3765 The UNIVERSAL STRING choice for DirectoryString is supported 3766 but cannot be used for matching rules. 3768 * the selected object classes defined in X.521 are supported. 3770 * FX*500 supports the following 1993 extensions to the DAP and 3771 DSP protocols: 3773 * subentries 3774 * copyShallDo 3776 * attributeSizeLimit 3778 * extraAttributes 3780 * useAliasOnUpdate 3782 * newSuperior 3784 * FX*500 supports the following operational attributes: 3786 * structural object class 3788 * governing structural rule 3790 * create timestamp 3792 * modify timestamp 3794 * creators name 3796 * modifiers name 3798 * prescriptive ACI 3800 * entry ACI 3802 * subentry ACI 3804 * myAccessPoint 3806 * superiorKnowledge 3808 * supplierKnowledge (supported by local mechanism) 3810 * consumerKnowledge (supported by local mechanism) 3812 * secondaryShadows (supported by local mechanism) 3814 * specificKnowledge 3816 * nonSpecificKnowledge 3817 * FX*500 supports return of alias names and indication that 3818 returned entry information is complete 3820 * support is given to modifying the object class attribute to 3821 add and/or remove values identifying auxiliary object classes 3823 * FX*500 supports both Basic Access Control and Simplified 3824 Access Control 3826 * FX*500 supports the name bindings defined in X.521 3828 From section 9.3 and 9.4 of X.519 1993 regarding conformance of a 3829 Shadow Supplier and Shadow Consumer respectively: 3831 * FX*500 supports the shadowSupplierInitiatedAC and 3832 shadowConsumerInitiatedAC application contexts 3834 * the security levels "none" and "simple" are supported, the 3835 "strong" security level can be supported with the addition of 3836 an appropriate security module. 3838 * FX*500 supports the following UnitOfReplication: 3840 * Entry filtering on object class 3842 * Inclusion of subordinate knowledge in the replicated area 3844 * Inclusion of extended knowledge in addition to subordinate 3845 knowledge 3847 * FX*500 can act as a secondary shadow supplier. 3849 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 3851 Supports [RFC 1274], [RFC 1567],[RFC 1777],[RFC 1778],[RFC 1779] 3853 FX*500 maintains statistics that are a superset of those defined by 3854 [RFC 1567] "X.500 Directory Monitoring MIB". 3856 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 3858 [No information provided. -- Ed.] 3860 INTEROPERABILITY 3862 Firefox are members of EurOSInet and test FX*500 by direct links with 3863 other members and at interoperability workshops. 3865 PILOT CONNECTIVITY 3867 Firefox are participating in the NameFLOW-Paradise project, which is 3868 the successor to the Paradise European X.500 directory pilot. 3870 BUGS 3872 [No information provided. -- Ed.] 3874 CAVEATS AND GENERAL LIMITATIONS 3876 [No information provided. -- Ed.] 3878 INTERNETWORKING ENVIRONMENT 3880 FX*500 utilises the Firefox FX*STACK product to provide an OSI stack 3881 for use over local or wide-area networks. This enables the X.500 3882 DAP, DSP and DISP protocols operate over a range of different network 3883 types. The current network options are: 3885 * OSI LANs are supported by Transport Class 4 over CLNP (ISO 3886 8473), including the ES-IS routing protocol. 3888 * X.25 networks are supported in either a Connection-Oriented 3889 Network Service (CONS) or a Connection-Less Network Service 3890 (CLNS) environment. 3892 * For CONS, Transport Classes 0, 2 and 4 are supported over 3893 X.25(1984). 3895 * For CLNS, Transport Class 4 is supported over CLNP (ISO 3896 8473) utilising X.25 as a subnetwork. 3898 * TCP/IP networks are supported by an implementation of [RFC 3899 1006], which supports Transport Class 0 over TCP/IP. 3901 HARDWARE PLATFORMS 3903 Intel 386, 486, Pentium 3905 SOFTWARE PLATFORMS 3907 FX*500 is available on NetWare 3.12 and 4.1, UnixWare 1.1. 3909 NUMBER OF IMPLEMENTATIONS IN THE FIELD 3911 [No information provided. -- Ed.] 3913 AVAILABILITY 3915 FX*500 is commercially available. 3917 For further details please contact: 3919 Keith Vallance 3920 Product Manager 3921 Firefox International Limited 3922 668 Hitchin Road 3923 Stopsley 3924 Bedfordshire LU2 7UH 3925 UK 3927 Tel: +44 (0)1582 29007 3928 Fax: +44 (0)1582 29107 3929 email: keithv@firefox.co.uk 3931 Ken Sanofsky 3932 Firefox (U.S.) Inc. 3933 Seventh Floor 3934 2099 Gateway Place 3935 San Jose 3936 CA 95110-1017 3938 Tel: +1 408 321 8344 3939 Fax: +1 408 321 8311 3940 email: kens@firefox.com 3941 DATE LAST UPDATED or CHECKED 3943 April 1996 3945 ADDITIONAL INFORMATION and/or COMMENTS 3947 [No information provided. -- Ed.] 3949 NAME 3950 Global Directory Server 3952 Control Data Systems, Inc. 3954 ABSTRACT 3956 Control Data's X.500 implementation, called the Global Directory 3957 Server, is compliant with the 1993 ITU-T Recommendations X.500-X.521, 3958 except for DOP, schema publication, and non-specific subordinate 3959 references. Features include: 3961 * 1993 administrative framework 3963 * 1993 operational attributes 3965 * 1993 reference structure 3967 * 1993 distributed operations 3969 * 1993 incremental and full replication including: 3971 * Supplier or consumer initiated 3973 * Periodic (by update interval) or onchange replication 3975 * Complete subtree specification to select replicated 3976 area 3978 * Reference replication 3980 * 1993 basic access control including: 3982 * Prescriptive, entry and subentry ACI supported 3984 * Item first and user first specification 3986 * All user classes supported including users by subtree 3987 specification 3989 * Access control by entry, attribute, and attribute value 3991 * All priority levels supported 3992 * 1993 collective attributes 3994 * 1993 hierarchical attributes 3996 * 1993 operational extensions 3998 * 1993 modifyDN operation 4000 * Full interoperability with "quipu" implementations including: 4002 * quipu replication for designated portions of DIT 4004 * quipu reference model for designated portions of DIT 4006 * enhanced quipu access controls (ACLs) 4008 * quipu operational attributes for designated portions of 4009 DIT 4011 * Can "automatically" migrate quipu DIT to 1993 DIT: 4013 * Migration process is dynamic, can occur while DSA is 4014 operating 4016 * Process preserves quipu attributes if desired 4017 Also: 4019 * Directory API based on the X.400 API 4021 * Support for X.400 objects including those to support MHS use 4022 of directory to support MHS routing 4024 * Integration with Control Data's Mail*Hub standards-based E- 4025 mail and directory integration products 4027 * DUA interfaces that support the full set of directory 4028 operations 4030 * A DUA daemon that provides directory access for applications 4032 * Directory synchronization tools for synchronizing 4033 PC/Mac/DEC/IBM mail directories and other sources of 4034 information, such as human resources databases, with X.500 4036 * Hash indexing for fast string search 4037 * dixie, dad, finger, whois, and ph.x500 support 4039 * SNMP based monitoring and management of DSAs 4041 * Support for DAP, LDAP, DSP, and DISP 4043 * Can be browsed via standard World Wide Web browsers 4045 Control Data Systems offers complete integration services to design, 4046 plan, install, configure, tailor and maintain X.500 services. These 4047 services may include the preparation of customer unique DUAs and 4048 tools for X.500 integration, synchronization, operational control and 4049 management. 4051 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 4053 The Global Directory Server complies with the 1988 CCITT 4054 Recommendations X.500-X.521 [CCITT-88] and the 1988 NIST OIW Stable 4055 Implementation Agreements [NIST-88]. It also complies with all 4056 static and dynamic requirements of X.519. 4058 The Global Directory Server also provides: 4060 * Full interoperability with "quipu" implementations including: 4062 * quipu replication for designated portions of DIT 4064 * quipu reference model for designated portions of DIT 4066 * enhanced quipu access controls (ACLs) 4068 * quipu operational attributes for designated portions of 4069 DIT 4071 * Can "automatically" migrate quipu DIT to 1993 DIT: 4073 * Migration process is dynamic, can occur while DSA is 4074 operating 4076 * Process preserves quipu attributes if desired 4078 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 4080 The Global Directory Server complies with the 1993 ITU-T 4081 Recommendations X.500-X.521, except for DOP, schema publication, and 4082 non-specific subordinate references. It also complies with the 1994 4083 NIST OIW Stable Implementation Agreements. And it complies with all 4084 static and dynamic requirements of X.519. Compliance features: 4086 * 1993 administrative framework 4088 * 1993 operational attributes 4090 * 1993 reference structure 4092 * 1993 distributed operations 4094 * 1993 incremental and full replication including: 4096 * Supplier or consumer initiated 4098 * Periodic (by update interval) or onchange replication 4100 * Complete subtree specification to select replicated area 4102 * Reference replication 4104 * 1993 basic access control including: 4106 * Prescriptive, entry and subentry ACI supported 4108 * Item first and user first specification 4110 * All user classes supported including users by subtree 4111 specification 4113 * Access control by entry, attribute and attribute value 4115 * All priority levels supported 4117 * 1993 collective attributes 4119 * 1993 hierarchical attributes 4121 * 1993 operational extensions 4123 * 1993 modifyDN operation 4124 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4126 Global Directory Server is compliant with the following RFCs: [RFC 4127 1274], [RFC 1276], [RFC 1277], [RFC 1567], [RFC 1778], [RFC 1777], 4128 [RFC 1779] 4130 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4132 Global Directory Server is compliant with the following RFCs: [RFC 4133 1202], [RFC 1249], [RFC 1275], [RFC 1278], [RFC 1279], [RFC 1558], 4134 [RFC 1562], [RFC 1617], [RFC 1781], [RFC 1801], [RFC 1802], [RFC 4135 1803], [RFC 1836], [RFC 1837], [RFC 1838] 4137 INTEROPERABILITY 4139 Control Data X.500 has successfully interoperated with other X.500 4140 implementations including those from HP, DEC, ESL, ISODE Consortium, 4141 Telstra, ICL, Marben (HP), Nexor, Unisys, and Siemens. 4143 PILOT CONNECTIVITY 4145 Control Data's X,500 implementation interoperates with other 4146 implementations in the Internet X.500 pilots. It also provides the 4147 base routing tree for the MHS Use of the Directory pilot (Longbud) on 4148 the Internet. 4150 BUGS 4152 Control Data provides complete software maintenance services with 4153 products. 4155 CAVEATS AND GENERAL LIMITATIONS 4157 None. 4159 INTERNETWORKING ENVIRONMENT 4161 [RFC 1006] with TCP/IP, TP4 with CLNS, TP0 with X.25. 4163 HARDWARE PLATFORMS 4165 Global Directory Server is supported on UNIX for SUN SPARC, HP 9000, 4166 and IBM RS/6000 platforms, and on Windows NT for Intel platforms. 4167 Other platforms are pending. 4169 SOFTWARE PLATFORMS 4171 Distributed and supported for SUN Solaris 2.x, HP-UX 10.x, IBM AIX 4172 4.x, and Windows NT. 4174 NUMBER OF IMPLEMENTATIONS IN THE FIELD 4176 Product was introduced in December 1995. 5 implementations in the 4177 field to date. 4179 AVAILABILITY 4181 Commercially available from: 4183 Control Data Systems Inc. 4184 Electronic Commerce Solutions, ARH290 4185 4201 Lexington Avenue North 4186 Arden Hills, MN 55126-6198 U.S.A. 4188 1-800-257-OPEN (U.S. and Canada) 4189 1-612-482-6736 (worldwide) 4190 FAX: 1-612-482-2000 (worldwide) 4191 EMAIL: info@cdc.com 4192 or 4193 s=info p=cdc a=attmail c=us 4195 DATE LAST UPDATED or CHECKED 4197 July 1996 4199 ADDITIONAL INFORMATION and/or COMMENTS 4201 [No information provided. -- Ed.] 4203 NAME 4205 i500 Enterprise Directory Server 4207 ICL 4209 ABSTRACT 4211 ICL's i500 Enterprise Directory Server (simply termed "i500") is a 4212 high performance X.500 distributed Directory system providing 4213 features such as: 4215 * multi-protocol support covering 1993-edition DAP, DSP and 4216 DISP plus LDAP and WWW client access 4218 * dynamically configurable schema (object classes, attributes, 4219 structure rules etc.) including support for user-defined 4220 schema items and auxiliary object classes 4222 * a scalable, disk-based database incorporating configurable 4223 indexing facilities to enable rapid, large-scale searching, 4224 including approximate matching 4226 * storage of a variety of information types including text, 4227 image and sound 4229 * the capabaility to operate as a "first-level" DSA 4231 * 1993-edition replication of information (both primary and 4232 secondary shadowing using DISP and supporting total refresh, 4233 incremental or on-change updates) 4235 * information security, using X.509 authentication techniques 4236 together with either 1993-edition Basic or Simplified Access 4237 Controls 4239 * gateway facilities to enable X.500, LDAP and WWW client 4240 access to non-X.500 based information 4242 * a variety of APIs and associated development toolkits 4243 including LDAP and X/Open XDS/XOM Directory access APIs 4245 * support of the [RFC 1567] "MADMAN" systems management MIB 4246 * a Windows (3.11, 95 or NT) based management station 4248 COMPLIANCE withX.500-1988 (applicable only forDSAs and DUAs) 4250 i500 is compliant with the 1993-edition of X.500 and interoperates 4251 with 1988-edition DUAs and DSAs. 4253 COMPLIANCE withX.500-1993 (applicable only forDSAs and DUAs) 4255 i500 is compliant with the 1993-edition of X.500 and is implemented 4256 in-line with the ISO/ITU-T Directory Implementor's Guide and the 4257 emerging 1993 International Standardized Profiles (ISPs) being 4258 produced by the NIST OIW, EWOS and AOW workshops. 4260 Full Protocol Implementation Conformance Statements (PICS) are 4261 available on request to either: 4263 i500@reston.icl.com or k.richardson@man0523.wins.icl.co.uk 4265 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4267 i500 supports a variety of proposed Internet standards and in 4268 particular, [RFC 1274] (schema), [RFC 1567] (MIB) and [RFC 1777] 4269 (LDAP). 4271 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4273 i500 is developed in-line with any necessary informational and 4274 experimental RFCs, e.g.[RFC 1278] and [RFC 1558] are supported. 4276 INTEROPERABILITY 4278 ICL are members of EuroSInet and EEMA. As such, i500 is regularly 4279 tested for interoperability at EuroSInet workshops and has also been 4280 included in public demonstrations of X.500 interoperability at EEMA 4281 annual exhibitions. Other X.500 products with which i500 has been 4282 proven to interoperate include those from the following vendors: 4284 * Boldon-James 4286 * Control Data 4288 * DCL 4289 * Digital 4291 * ISOCOR 4293 * ISODE 4295 * Net-Tel 4297 * NeXor 4299 * SNI 4301 * Unisys 4303 * WorldTalk 4305 PILOT CONNECTIVITY 4307 i500 operates within the Internet PARADISE network controlled by 4308 DANTE. 4310 BUGS 4312 No known bugs. World-wide software maintenance services are provided 4313 with primary support desks based in North America and Europe. 4315 CAVEATSAND GENERAL LIMITATIONS 4317 None. 4319 INTERNETWORKING ENVIRONMENT 4321 TCP/IP for LDAP and WWW client (HTTP) access 4322 TCP/IP with [RFC 1006] 4323 OSI TP0, TP2, TP3, (X.25, CONS) and TP4 (CLNP) 4325 HARDWARE PLATFORMS 4327 HP, Intel PC, ICL, SUN, Pyramid and platforms which support UNIXWARE 4328 2.0 4330 SOFTWARE PLATFORMS 4332 HP UX-9.04 and 10.0, Windows NT 3.51, ICL DRS/NX 7, SUN Solaris 2.4 4333 and 2.5, Pyramid OSx, UNIXWARE 2.0 4335 NUMBER OF IMPLEMENTATIONS IN THE FIELD 4337 [No information provided. -- Ed.] 4339 AVAILABILITY 4341 i500 is commercially available from ICL High Performance Systems. 4342 For further information please contact either: 4344 i500 Marketing Manager, or David Longley (i500 Business Manager), 4345 ICL Inc., ICL, 4346 11490 Commerce Park Drive, Wenlock Way, 4347 Suite 500, West Gorton, 4348 Reston, Manchester, 4349 VA 22091-1532 USA M12 5DR, UK 4351 Tel. +1 703 648 3300 Tel. +44 (0)161 223 1301 ext.2832 4352 Fax. +1 703 648 3350 Fax. +44 (0)161 223 0482 4353 I/net. i500@reston.icl.com I/net. d.c.longley@man0505.wins.icl.co.uk 4355 Information on i500 is also provided at 4356 http://www.icl.com/hps/i500.html. 4358 DATE LAST UPDATED or CHECKED 4360 July 29, 1996 4362 ADDITIONAL INFORMATION and/or COMMENTS 4364 None. 4366 NAME 4368 ISODE Consortium Release 3.0 X.500(1993) Directory 4369 ISODE Consortium Ltd. 4371 ABSTRACT 4373 This implementation is a source release of an X.500(1993) Directory 4374 System Agent (DSA). It has been designed an implemented as an X.500 4375 1993 DSA not as a 1988 DSA with '93 extensions. Emphasis has been 4376 placed on providing support for a flexible information model, access 4377 control, X.509 security features, and standard replication. 4379 The 1993 DSA offers a strong technical foundation on which to build 4380 an information and messaging infrastructure that relies on robust and 4381 scalable directory services. The implementation of this DSA 4382 incorporates the experience gained through the development, support, 4383 and maintenance of the earlier QUIPU, as well as operational 4384 experience and standards support. 4386 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 4388 The DSA is aligned to the 1988 ISO IS and the NIST OIW Directory 4389 Implementors Guide Version 1. X.500(1993) features such as 4390 replication, access control, as well as X.509 certification are also 4391 available. Interoperability testing with other DSAs has been 4392 performed. 4394 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 4396 Please contact the ISODE Consortium if you wish to obtain our 4397 protocol information conformance statements. PICS may also be 4398 available from member organizations for their binary products. 4400 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4402 [RFC 1781],[RFC 1779],[RFC 1778],[RFC 1777], [RFC 1274], [RFC 1277]. 4404 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4406 [RFC 1838], [RFC 1837], [RFC 1836],[RFC 1801], [RFC 1275], [RFC 4407 1278], [RFC 1279]. 4409 INTEROPERABILITY 4411 Interoperability with several other DSAs has been demonstrated in 4412 pilot operation and at Eurosinet in October 1995. 4414 At Eurosinet, X.500 interoperability testing used the X.500 DAP 4415 (Directory Access) and DSP (Directory System) protocols. Successful 4416 testing was done between the ISODE Consortium X.500(1993) DSA and 4417 DSAs from four other vendors including Siemens-Nixdorf and Bull. The 4418 ISODE Consortium was the only vendor to bring an X.500(93) compliant 4419 DSA to the workshop for the scheduled X.500(93) testing. 4421 PILOT CONNECTIVITY 4423 Connectivity to the global research pilots (PARADISE etc.) has been 4424 demonstrated. It is expected that this system will be used 4425 extensively in a wide range of pilot activities. DUA Connectivity, 4426 and DSA Connectivity. 4428 BUGS 4430 Bugs should be reported to the ISODE Consortium via email. 4432 CAVEATS AND GENERAL LIMITATIONS 4434 None 4436 INTERNETWORKING ENVIRONMENT 4438 The IC R3.0 release is application level code, and assumes vendor 4439 provided lower layers. It provides the following modules with support 4440 for a range of APIs to handle associated lower layers: 4442 * [RFC 1006] (vendor supplied TCP/IP using sockets or TLI) 4444 * Transport service (vendor supplied transport, which may be 4445 any class and use any network service. TLI, XTI and various 4446 vendor-specific APIs). 4448 * TP0 (Vendor supplied X.25 or CONS using NTI and various 4449 vendor specific APIs). 4451 HARDWARE PLATFORMS 4453 Reference platform is SUN SPARC Solaris 2. The software has been 4454 ported to various other platforms by the IC and by member 4455 organizations. Contact the ISODE Consortium for a complete member 4456 product list. 4458 SOFTWARE PLATFORMS 4460 Reference OS is Solaris 2.3/2.4. It is also known to run on various 4461 other UNIX platforms. Contact the ISODE Consortium for a complete 4462 member product list. 4464 NUMBER OF IMPLEMENTATIONS IN THE FIELD 4466 [No information provided. -- Ed.] 4468 AVAILABILITY 4470 Available to members of the ISODE Consortium. Membership is open to 4471 any organisation. An earlier version of the source release is 4472 available under licence (zero cost) to universities and equivalent 4473 educational institutions. 4475 Contact: 4477 ISODE Consortium 4478 The Dome, The Square 4479 Richmond 4480 TW9 1DT 4481 UK 4483 Phone: +44-181-332-9091 4484 Fax: +44-181-332-9019 4486 Email: 4488 DATE LAST UPDATED or CHECKED 4490 January 1996 4492 ADDITIONAL INFORMATION and/or COMMENTS 4494 More information may be obtained by contacting the ISODE Consortium, 4495 or by visiting our WWW site, http://www.isode.com/ 4497 Our X.400 address is s=ic-info; o=ISODE Consortium; p=ISODE; 4498 a=MAILNET; c=FI 4500 NAME 4502 ISOPLEX DS (tm) DSA 4504 ISOCOR 4506 ABSTRACT 4508 ISOCOR's ISOPLEX DS Directory Services Product Family also includes: 4510 ISOPLEX DS Import/Export Utility for Windows 4511 ISOPLEX DS Navigator 4512 ISOPLEX DS Directory Access XDS/XOM APIs 4513 ISOGATE DS (tm) Oracle 4515 The ISOPLEX DS provides a 1988 X.500 conformant Directory System 4516 Agent (DSA), a Lightweight Directory Access Protocol (LDAP) daemon to 4517 service Directory requests via LDAP, a UNIX Directory shell user 4518 agent (DISH), a Motif Directory Administrator interface to configure 4519 the first level and subordinate DSAs, and supporting utilities to 4520 handle bulk loading of the Directory, maintain statistics, and 4521 provide logging information. 4523 In addition to supporting memory-based Directory Information Bases 4524 (DIBs), the ISOPLEX DS includes the optional configuration of 4525 delegate DSA processes for storing selected subtrees of the Directory 4526 Information Tree (DIT) in disk-based index and data files. 4528 The ISOPLEX DS includes a set of utilities integrating it with key 4529 technology. The most important of these tools is the World Wide Web 4530 to X.500 gateway, which supports Hyper-Text Markup Language (HTML)- 4531 based DUA bindings to the ISOPLEX DS DSA via the ISOPLEX DS LDAP 4532 daemon process. 4534 The ISOPLEX DS additionally provides Simple Network Management 4535 Protocol (SNMP) functionality that works in conjunction with an 4536 existing SNMP environment. The ISOPLEX DS functionality is 4537 specifically designed to monitor a DSA's DSP and DAP connections from 4538 a network managment system and uses the X.500 Directory monitoring 4539 Management Information Base (MIB), which is based on [RFC 1567]. 4541 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 4543 The ISOPLEX DS conforms to the 1988 CCITT Recommendations X.500-X.521 4544 as detailed in the Protocol Implementation Conformance Statements 4545 X.581 (1988) and X.582 (1988). It conforms in part to Version 7 of 4546 the NIST OIW Stable Implementation Agreements. 4548 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 4550 The ISOPLEX DS does not conform to the 1993 ITU-T Recommendations 4551 X.500-X.521. 4553 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4555 The ISOPLEX DS conforms with the following proposed Internet Standard 4556 RFCs: [RFC 1274], [RFC 1276], [RFC 1277], [RFC 1567], [RFC 1777], 4557 [RFC 1778], [RFC 1779], and [RFC 1798]. 4559 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4561 The ISOPLEX DS is consistent with the following informational and 4562 experimental RFCs: [RFC 1275], [RFC 1278], [RFC 1279], [RFC 1558], 4563 [RFC-1617], [RFC 1781], [RFC-1801], [RFC-1803], and [RFC-1804]. 4565 INTEROPERABILITY 4567 The ISOPLEX DS interoperates with the following systems: Control 4568 Data, Digital Equipment, Hewlett Packard, Marben, Nexor, The 4569 Wollongong Group, and Unisys. 4571 PILOT CONNECTIVITY 4573 The ISOPLEX DS provides DUA Connectivity and DSA Connectivity via the 4574 PARADISE project in Europe and via the Internet in North America. 4576 BUGS 4578 If problems arise with the ISOPLEX DS, the customer can report these 4579 to the relevant ISOCOR reseller or contact ISOCOR Technical Support 4580 directly. ISOCOR Technical Support staffs are available in two 4581 locations: one in the US at +1 (310) 581-8100 (phone), +1 (310) 4582 581-8111 (fax), and helpdesk@isocor.com; the other in Ireland at +353 4583 (1) 284-3802 (phone), +353 (1) 280-0365, and helpdesk.isocor.ie. 4585 CAVEATS AND GENERAL LIMITATIONS 4587 Not applicable. 4589 INTERNETWORKING ENVIRONMENT 4591 Though the internetworking capability of the product depends on the 4592 specific hardware/software platform, the ISOPLEX DS in general 4593 supports the following environments: 4595 [RFC 1006] with TCP/IP 4597 TP2 over X.25, CONS (ISO 8878), APS on Async 4599 TP4 over CLNS, PAD (X.29) Server 4601 HARDWARE PLATFORMS 4603 Hewlett Packard 4605 Intel 486/Pentium 4607 Sun 4609 Stratus 4611 SOFTWARE PLATFORMS 4613 Hewlett Packard HP-UX v9.x/v10.x, HP OSI Transport Services 9000 4615 SCO v3.2.4, v3.2.5, SCO OpenDesktop, TCP/IP, IEEE 802.3, Eicon R3.1 4616 for X.25 networking software and hardware 4618 Solaris v2.4, Sunlink OSI 8.0.2, Sunlink X.25 8.0.2 4620 Stratus ftx v2.2, OSI Open Networking Platform (ONP), Stratus Window 4621 Manager 1.2 End User System, MIT X11R5 Graphics End User System, MIT 4622 X11R5 Graphics Fonts package, MIT X11R5 Graphics Openlook Software 4623 package 4625 Motif/X11R5 runtime support 4627 NUMBER OF IMPLEMENTATIONS IN THE FIELD 4629 [No information provided. -- Ed.] 4631 AVAILABILITY 4633 The ISOPLEX DS is commercially available either directly from ISOCOR 4634 or from a licensed ISOCOR reseller. 4636 DATE LAST UPDATED or CHECKED 4638 December 31, 1995. 4640 ADDITIONAL INFORMATION and/or COMMENTS 4642 Not applicable. 4644 NAME 4646 LDAP 4648 University of Michigan 4650 ABSTRACT 4652 UM-LDAP is an implementation of the Lightweight Directory Access 4653 Protocol. LDAP is a draft Internet standard directory service 4654 protocol that runs over TCP/IP. It can be used to provide a stand- 4655 alone directory service, or to provide lightweight access to the 4656 X.500 directory. LDAP is defined by [RFC 1777] and [RFC 1778]. 4658 The UM-LDAP package includes the following components: 4660 * slapd - a stand-alone LDAP directory server 4662 * slurpd - a stand-alone LDAP replication server 4664 * ldapd - an LDAP-to-X.500 gateway server 4666 * centipede - an LDAP centroid generation and maintenance 4667 program 4669 * libldap - an LDAP client library 4671 * liblber - a lightweight BER/DER encoding/decoding library 4673 * ldif tools - data conversion tools for use with slapd 4675 * in.xfingerd - a finger-to-LDAP gateway server 4677 * go500 - a gopher-to-LDAP gateway server for searching 4679 * go500gw - a gopher-to-LDAP gateway server for searching and 4680 browsing 4682 * rcpt500 - an email-to-LDAP query responder 4684 * mail500 - an LDAP-capable mailer 4686 * fax500 - an LDAP-capable mailer that supports remote printing 4688 * LDAP tools - A collection of shell-based LDAP utility 4689 programs 4690 In addition, there are some contributed components: 4692 * web500 - an HTTP-to-LDAP gateway 4694 * whois++d - a WHOIS++-to-LDAP gateway 4696 * saucer - a simple command-line oriented client program 4698 The latest information about LDAP can always be found on the LDAP 4699 Home Page at this URL: 4701 http://www.umich.edu/~rsug/ldap/ 4703 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 4705 The U-M LDAP distribution is a complete implementation of the LDAP 4706 protocol. The LDAP protocol does not support access to all X.500 4707 features and operations. The operations supported are bind, search, 4708 compare, add, delete, modify, modify RDN, and abandon. Note that 4709 read and list operations can be emulated using the search operation. 4710 Size and time limits may be specified, as may alias dereferencing and 4711 searching, but all X.500 service controls are not supported. 4713 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 4715 Since the LDAP protocol itself has not yet been updated to support 4716 any 1993-specific X.500 features, this implementation does support 4717 any 1993 features yet either. 4719 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4721 Believed to be compliant with: 4723 [RFC 1274], [RFC 1777], [RFC 1778], [RFC 1779], [RFC 1781] 4725 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4727 Includes an implementation of the LDAP API, as defined in [RFC 1823]. 4728 Search filters used within UM-LDAP comply with [RFC 1558]. 4730 INTEROPERABILITY 4732 The current implementation of the X.500-backended LDAP server (ldapd) 4733 is known to work with ISODE-based DAP libraries and the QUIPU DSA. 4735 PILOT CONNECTIVITY 4737 DUA connectivity should be possible to all pilots. 4739 BUGS 4741 Bug reports should be sent to bug-ldap@umich.edu. 4743 CAVEATS AND GENERAL LIMITATIONS 4745 None, aside from those mentioned above under completeness. 4747 INTERNETWORKING ENVIRONMENT 4749 LDAP clients use TCP to communicate with the LDAP server. The LDAP 4750 server normally uses [RFC 1006] with TCP/IP to communicate with the 4751 DSA, though any other transport mechanism for DSA communication 4752 supported by ISODE should be possible. 4754 HARDWARE PLATFORMS 4756 The complete UM-LDAP package has been ported to a wide variety of 4757 UNIX systems, including: Sun3 and SPARCs running SunOS 4.1.x or 4758 Solaris 2.x, DECStations running Ultrix 4.3, HP 9000 series running 4759 HP-UX 9.05, IBM RS6000 running AIX 3.2.5, PCs running SCO, FreeBSD, 4760 NetBSD, or LINUX, DEC Alphas ruuning OSF/1, and NeXTStatios running 4761 NeXTSTEP 3.2. The complete package has also been ported to VMS. In 4762 addition, the LDAP client libraries and some client programs have 4763 been ported to Apple Macintosh and PCs running MSDOS or Windows. 4765 SOFTWARE PLATFORMS 4767 The complete UM-LDAP package has been ported to a wide variety of 4768 UNIX systems, including: SunOS 4.1.x, Solaris 2.x, Ultrix 4.3, HP-UX 4769 9.05, AIX 3.2.5, SCO, FreeBSD, NetBSD, LINUX, OSF/1, and NeXTSTEP 4770 3.2. It has also been ported to VMS. In addition, the LDAP client 4771 libraries and some clients have been ported to Macintosh (System 7), 4772 MSDOS (some TCP/IP stacks), and Microsoft Windows 3.1, 95, and NT. 4774 NUMBER OF IMPLEMENTATIONS IN THE FIELD 4776 Unknown; used by almost all Internet X.500 sites. 4778 AVAILABILITY 4780 This software is openly available for all to use. It may be obtained 4781 by anonymous FTP from terminator.rs.itd.umich.edu in the /ldap/ 4782 directory (URL: ftp://terminator.rs.itd.umich.edu/ldap/). The 4783 latest information about LDAP can always be found on the LDAP Home 4784 Page at this URL: 4786 http://www.umich.edu/~rsug/ldap/ 4788 Send e-mail to ldap-support@umich.edu for additional assistance. 4790 This software was developed at the University of Michigan by Tim 4791 Howes with help from Mark Smith, Bryan Beecher, Gordon Good, Steve 4792 Rothwell, Lance Sloan as well as many others around the Internet. It 4793 is subject to the following copyright: 4795 Copyright (c) 1992-1996 Regents of the University of Michigan. 4796 All rights reserved. Redistribution and use in source and binary 4797 forms are permitted provided that this notice is preserved and 4798 that due credit is given to the University of Michigan at Ann 4799 Arbor. The name of the University may not be used to endorse or 4800 promote products derived from this software without specific prior 4801 written permission. This software is provided ``as is'' without 4802 express or implied warranty. 4804 DATE LAST UPDATED or CHECKED 4806 December 1995 4808 ADDITIONAL INFORMATION and/or COMMENTS 4810 [No Information Provided -- Ed.] 4812 NAME 4814 maX.500 :: Macintosh DUA Interface 4816 University of Michigan 4818 ABSTRACT 4820 maX.500 is a Directory User Agent (client) for Apple Macintosh. It 4821 is widely used within Paradise and other Internet X.500 pilots. 4822 maX.500 supports searching, browsing, and modifying directory 4823 entries. Display of textual information, playing of audio, and 4824 viewing of both black-and-white (fax) and color (JPEG) images are 4825 supported. Communication with directory servers is via the 4826 Lightweight Directory Access Protocol (LDAP) over TCP/IP. maX.500 4827 works both with standalone LDAP directory servers (such as slapd) and 4828 with X.500-backended LDAP servers (such as ldapd). 4830 maX.500 is a native Macintosh application, and has a friendly 4831 interface. It requires System Software version 6.0.5 or later and 4832 Apple's MacTCP or Open Transport TCP/IP networking. The current 4833 version of maX.500 is 2.0.2, although version 2.1 is in beta test. 4835 The latest information about maX.500 can always be found on the 4836 maX.500 Home Page at this URL: 4837 http://www.umich.edu/~rsug/ldap/max500/ 4839 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 4841 maX.500 works over LDAP, and is subject to LDAP's limitations. The 4842 bind, search, compare, add, delete, abandon, modify, and modifyrdn 4843 operations are all used by maX.500. Size and time limits may be 4844 specified, as may alias dereferencing control. 4846 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 4848 maX.500 currently uses LDAP as defined in [RFC 1777], which does not 4849 support any 1993-specific X.500 features. 4851 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4853 Believed to be compliant with: 4855 [RFC 1274], [RFC 1777], [RFC 1778], [RFC 1779], [RFC 1781] 4856 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4858 Search filters comply with [RFC 1558]. 4860 Uses the LDAP API, as defined in [RFC 1823]. 4862 INTEROPERABILITY 4864 maX.500 is known to work with the U-M LDAP servers (ldapd and slapd). 4865 It has also been tested with other commerical LDAP servers, such as 4866 Control Data's server. maX.500 has been used with a wide variety of 4867 DSAs (always through an LDAP server). 4869 PILOT CONNECTIVITY 4871 DUA connectivity should be possible to all pilots. 4873 BUGS 4875 Bug reports should be sent to max500-bugs@umich.edu. 4877 CAVEATS AND GENERAL LIMITATIONS 4879 maX.500 does not support modification of "photo" (fax), "jpegPhoto", 4880 or "audio" attributes. Versions of maX.500 before 2.1 did not 4881 support a fully functional browse facility. 4883 INTERNETWORKING ENVIRONMENT 4885 maX.500 is an LDAP client, and as such is uses TCP to communicate 4886 with the LDAP server. Apple's MacTCP control panel or Open 4887 Transport TCP/IP networking is required. 4889 HARDWARE PLATFORMS 4891 maX.500 runs on Apple Macintosh Plus or later Macintosh computers, 4892 including PowerMacs. It requires 600K of free RAM. 4894 SOFTWARE PLATFORMS 4896 maX.500 requires Apple System Software 6.0.5 or later (System 7 4897 preferred) and MacTCP 1.1 or later (2.0.6 preferred). maX.500 2.1, 4898 which is currently in beta test, will run natively on the PowerMac 4899 and use the native Open Transport networking interface if it is 4900 installed. 4902 NUMBER OF IMPLEMENTATIONS IN THE FIELD 4904 [No information provided. -- Ed.] 4906 AVAILABILITY 4908 This software is openly available for all to use. It may be obtained 4909 by anonymous FTP from terminator.rs.itd.umich.edu in the /ldap/max500 4910 directory (URL: ftp://terminator.rs.itd.umich.edu/ldap/max500). The 4911 latest information about maX.500 can always be found on the maX.500 4912 Home Page at this URL: 4914 http://www.umich.edu/~rsug/ldap/max500/ 4916 Send e-mail to max500@umich.edu for additional assistance. 4918 This software was developed at the University of Michigan by Mark 4919 Smith with help from Tim Howes and many others around the Internet. 4920 It is subject to the following copyright: 4922 Copyright (c) 1995 Regents of the University of Michigan. All 4923 rights reserved. Redistribution and use in binary forms is 4924 permitted provided that this notice is preserved and that due 4925 credit is given to the University of Michigan at Ann Arbor. The 4926 name of the University may not be used to endorse or promote 4927 products derived from this software without specific prior written 4928 permission. This software is provided ``as is'' without express or 4929 implied warranty. 4931 DATE LAST UPDATED or CHECKED 4933 December 1995 4935 ADDITIONAL INFORMATION and/or COMMENTS 4937 [No Information Provided -- Ed.] 4939 NAME 4941 Messageware DSA 4943 NEXOR 4945 ABSTRACT 4947 Messageware DSA is a high performance X.500(93) DSA. Characteristics 4948 of the DSA are: 4950 * DAP access 4952 * DISP for replication and shadowing information 4954 * DSP access 4956 * LDAP 4958 * Full 1993 Basic and Simple Access Control 4960 * Support for X.400, X.500, and [RFC 1274] attributes and 4961 object classes 4963 * Approximate match based on Soundex. 4965 * Flexible schema management 4967 * Anti-trawling access control 4969 * Knowledge management mapped onto DIT 4971 * Attribute inheritance 4973 * Remote management 4975 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 4977 Messageware DSA is an X.500 1993 compliant DSA 4979 XT-QUIPU is a X.500 1988 compliant DSA conforming to NIST SIA version 4980 2. 4982 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 4984 Messageware DSA isn X.500 1993 compliant DSA implementing standard 4985 access control, replication and shadowing, X.509, for a full 4986 conformance statement see the NEXOR web site(http://www.nexor.com). 4988 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 4990 The following are supported: String DN format [RFC 1485], [RFC 1274], 4991 [RFC 1276], and [RFC 1277]. 4993 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 4995 The following are supported: UFN [RFC 1781], [RFC 1278], and [RFC 4996 1279]. 4998 INTEROPERABILITY 5000 Messagware DSA has been extensively interoperability tested at 5001 Eurosinet workshops and at the EEMA X.500 demonstration. Other 5002 vendors DSAs/DUAs interoperated with include: 5004 ICL, Control Data, Unisys, Digital, Isocor, DCL, SNI, Boldon James 5006 It is also in operation with DSAs used in the PARADISE and other 5007 pilot projects. 5009 PILOT CONNECTIVITY 5011 Messageware DSA is fully connected to the PARADISE and PSI White 5012 Pages X.500 Pilots. 5014 BUGS 5016 No known bugs. Support is given via phone or email to 5017 "support@nexor.co.uk" 5019 CAVEATS AND GENERAL LIMITATIONS 5021 None. 5023 INTERNETWORKING ENVIRONMENT 5025 OSI TP4 wtih CLNP 5026 OSI TP0 with X.25 or CONS 5027 [RFC 1006] with TCP/IP 5029 HARDWARE PLATFORMS 5031 Sun: SunOS 5032 Solaris 5033 X86 5034 IBM RS/6000: AIX 5035 HP 9000 5037 It is available on a number of other UNIX platforms 5039 SOFTWARE PLATFORMS 5041 SunOs 4.1.3 Solaris 2.4 AIX 3.2 DRS/NX 6000 HP-UX 9.01 5043 Other software platforms are available. 5045 NUMBER OF IMPLEMENTATIONS IN THE FIELD 5047 [No information provided. -- Ed.] 5049 AVAILABILITY 5051 Messageware DSA is available from NEXOR and NEXOR partners. For more 5052 details contact: 5054 NEXOR 5055 PO Box 132 5056 Nottingham 5057 NG7 2UU 5058 UK 5060 DN: c=GB@o=NEXOR Ltd 5061 Telephone: +44 115 952 0510 5062 Fax: +44 115 952 0519 5063 E-Mail: info@nexor.co.uk 5065 DATE LAST UPDATED or CHECKED 5067 Dec 95 5069 ADDITIONAL INFORMATION and/or COMMENTS 5071 [No Information Provided--Ed.] 5073 NAME 5075 MESSAGEWARE PC-DUA 5077 NEXOR 5079 ABSTRACT 5081 PC-DUA provides a MS Windows based user interface to the X.500 5082 Directory. 5084 Features include: 5086 o Modify - allows users and administrators alike to add, change or 5087 delete directory entries 5089 o Searching - powerful searching tool so specific information can 5090 be quickly located. Also lists close matches 5092 o Highly flexible - can be customised to suit an organisations 5093 particular requirements 5095 o Directory Browser - to enable user to identify directory entries 5097 o History - allowing quick access to previously referenced parts 5098 of the DIT. 5100 o User Friendly Name (UFN) based searching 5102 o Hypertext-like navigation. 5104 o Friendly names for attribute labels. 5106 o Intelligent choice of entries to display when moving to a new 5107 location in the DIT. 5109 o On-line hypertext help. 5111 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 5113 Compliant with LDAP 3. 5115 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 5117 Compliant with 1993 versions of ITU X.500/ISO 9594 services and 5118 protocols 5120 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 5122 The following are supported: [RFC 1006] 5123 [RFC 1202] 5124 [RFC 1274] 5125 [RFC 1277] 5126 [RFC 1777] 5128 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 5130 [No information provided--Ed.] 5132 INTEROPERABILITY 5134 PC-DUA has interoperated with LDAP 2.0 and 3.0 distributions. 5136 Eurosinet Workshop: 5138 SNI, CDS, AT&T, ICL, Digital, ISOCOR, UNISYS and QUIPU. 5140 PILOT CONNECTIVITY 5142 Full DUA connectivity to the NADF, PARADISE and PSI White Pages X.500 5143 Pilots. 5145 BUGS 5147 No known bugs. Support is given via phone or email to 5148 "support@nexor.co.uk" 5150 CAVEATS AND GENERAL LIMITATIONS 5152 None. 5154 INTERNETWORKING ENVIRONMENT 5156 WinSock based TCP/IP stacks 5158 HARDWARE PLATFORMS 5160 386 PC or greater WITH 4MGBYTES RAM 5161 SOFTWARE PLATFORMS 5163 MS WINDOWS 3.1 5164 Windows NT 5165 Windows95 5167 NUMBER OF IMPLEMENTATIONS IN THE FIELD 5169 [No information provided. -- Ed.] 5171 AVAILABILITY 5173 PC-DUA is commercial software. For more details contact: 5175 NEXOR 5176 PO Box 132 5177 Nottingham 5178 NG7 2UU 5179 UK 5181 DN: c=GB@o=NEXOR Ltd 5182 Telephone: +44 (0) 115 952 0510 5183 Fax: +44 (0) 115 952 0519 5184 E-Mail: info@nexor.co.uk 5186 DATE LAST UPDATED or CHECKED 5188 Dec 95 5190 ADDITIONAL INFORMATION and/or COMMENTS 5192 [No Information Provided--Ed.] 5194 NAME 5196 NonStop Directory Services (NSDS) 5197 Tandem Computers, Inc. 5199 ABSTRACT 5201 The Tandem NonStop Directory Services (NSDS) product provides a 5202 distributed open directory service on Tandem platforms. It is an 5203 industrial strength implementation incorporating the Tandem product 5204 fundementals of resilience, linear extensibility, fault-tolerance, 5205 and continuous availability. NSDS runs on the NonStop Kernel 5206 Guardian Personality which includes support for Tandem system 5207 characteristics such as data integrity, process persistence, and 5208 server classes. NSDS supports access over X.25 WAN, LAN and TCP/IP 5209 networks. 5211 NSDS is a port of OSF's DCE GDS Reference Implementation, with Tandem 5212 enhancements including 1993 X.500 Simplified Access Control. Tandem 5213 server class management provides fault events, tracing, accounting 5214 and configuration services for NSDS. TM/MP (Transaction Management) 5215 is used to protect all file operations that affect the integrity of 5216 the directory entries in the DIB. 5218 Major Features Include: 5220 * X/Open Directory Services (XDS) API and X/Open Object 5221 Management (XOM) interface in conformance with X/Open CAE 5222 Specifications, and an additional Tandem extension package 5224 * 1988 Edition X.500 Conformant DAP and DSP, capable of inter- 5225 operating with 1993 Edition DUA or DSA implementations 5227 * Simplified Access Control as specified in the 1993 edition of 5228 the X.500 standard. 5230 * Unprotected Simple Authentication (name and password in 5231 clear) 5233 * Character set support for T61 Printables, IA5 and Teletex 5234 Strings 5236 * The DSA-SC server class performs the functions of a DSA. 5237 Multiple processes are used for fault tolerance and load 5238 balancing. 5240 * The DUA-ACCESS server class handles communications between 5241 local applications and remote DSA's using DAP across an OSI 5242 stack. 5244 * The DSA-ACCESS server class handles communications from 5245 remote DUAs or DSAs to the DSA-SC server class using the 5246 Tandem OSI stack implementation which includes [RFC 1006] 5247 support for TCP/IP networks. 5249 * The DSA-CHAIN server class handles chaining communications 5250 between the DSA-SC server class and remote DSAs. 5252 * NSDS GUI Viewer supports administration/management of an NSDS 5253 DIB on a PC Windows workstation. The NSDS GUI Viewer is 5254 supported by a persistent server process on the Tandem 5255 NonStop Kernel. The GUI Viewer allows a directory entry and 5256 a complete set of attributes and values to be inserted 5257 anywhere in the directory tree (DIT), to be deleted or 5258 changed, read or searched based on distinguished name 5259 components, with or without wild-card. 5261 * NSDS SCRIPTOR allows customers to explore features of the XDS 5262 programmatic interface in advance of writing their XOM/XDS 5263 application. NSDS SCRIPTOR is a menu-driven batch interface 5264 to XDS functions. 5266 * A BulkUnload/BulkLoad utility allows a branch of the DIB to 5267 be dumped to an editable flat file and restored from that 5268 file. The flat file can be modified before being bulk-loaded 5269 into a DIB which may conform to a different schema 5270 definition. 5272 * Support for the LDAP protocol. 5274 * Messaging-Based Directory Query (MDQ) provides a text-based 5275 query interface to the directory from an X.400 messaging 5276 system, such as Tandem OSI/MHS, via the XAPIA compliant GPI 5277 interface. 5279 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 5281 NSDS complies with the '88 CCITT X.500 and ISO 9594 standard, and 5282 part of '93 X.500 standard. 5284 NSDS DSA and DUA are compliant with OIW Agreements, with the 5285 following features yet to be implemented: 5287 * Strong Authentication (Sections 6.6.2 and 8.4e) 5289 * Priority Service Control (Section 7.4) 5291 * Digital Signature, Replication and Shadowing (Sections 8.8- 5292 8.12) 5294 * Authentication (Sections 9.1.7 and 14.1- 5295 14.2) 5297 * Directory Trace Information (Section 9.2.2) 5299 * Abandon and ROSE operation class 2 (Section 10.1) 5301 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 5303 * NSDS supports the directoryAccessAC (DAP) and directorySystemAC 5304 (DSP) application contexts. 5306 * The DSA is capable of acting as a first-level DSA. 5308 * Chaining is supported. 5310 * security levels of simple unprotected password and none are 5311 supported. 5313 * All attribute types defined in ISO/IEC 9594-6:1993 are supported 5314 except for collective attributes and enhancedSearchGuide. 5315 Customer defined attributes can also be added. UNIVERSAL STRING 5316 is not supported. 5318 * All object classes defined in ISO/IEC 9594-7:1993 are supported. 5319 Customer defined object classes can be also be added. 5321 * Name forms defined in ISO/IEC 9594-7:1993 are all supported. 5322 Customer defined name forms can also be added. 5324 * Simplified Access Control is supported. 5326 * Support for collective attributes is not provided. 5328 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 5330 [RFC 1277], [RFC 1777], [RFC 1779], [RFC 1778] 5332 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 5334 [RFC 1279] 5336 INTEROPERABILITY 5338 NSDS DSAs interoperate with various 1988 X.500 and 1993 X.500 5339 conformant DUAs with unrecognized features of the incoming 1993-based 5340 request ignored. 5342 PILOT CONNECTIVITY None at the present time. 5344 BUGS 5346 Information is provided with the production installation guide. 5348 CAVEATS AND GENERAL LIMITATIONS 5350 The OSF/DCE "GDS Extension Package" is not supported by NSDS. A 5351 Tandem "NDS Extension Package" is provided to support 1993 Simplified 5352 Access Control. 5354 INTERNETWORKING ENVIRONMENT 5356 The underlying protocols carrying DAP and DSP protocols are provided 5357 by OSI higher layer stack over X.25, LAN and/or TCP/IP via [RFC- 5358 1006]. 5360 HARDWARE PLATFORMS 5362 Tandem NonStop Himalaya Systems 5364 SOFTWARE PLATFORMS 5366 D30.02 NonStop Kernel. The operator's GUI runs under Microsoft 5367 Windows 3.1 or later. 5369 NUMBER OF IMPLEMENTATIONS IN THE FIELD 5371 [No information provided. -- Ed.] 5373 AVAILABILITY 5375 The NSDS Rev 1.0 production version has been available since October 5376 1995. 5378 For more details, please contact: 5380 Don S. Jones 5381 NSDS Product Manager 5382 Phone: (408) 285-6480 5383 Fax: (408) 285-6004 5384 e-mail: JONES_S_DON@TANDEM.COM 5386 DATE LAST UPDATE or CHECKED 5388 July 1996. 5390 ADDITIONAL INFORMATION and/or COMMENTS 5392 None. 5394 NAME 5396 ORG.D (tm) V2.0 / V2.1 5398 Siemens Nixdorf Informationssysteme AG 5400 ABSTRACT 5402 ORG.D V2.0 is Siemens Nixdorf's administrative directory client 5403 product. Through its file manager like user interface retrieval and 5404 DIT administration operations are supported. ORG.D offers a DDE 5405 interface and with ORG.D V2.1 additionally OLE / OCX / MAPI 5406 interfaces are supported. ORG.D V2.1 is an MS-Windows application 5407 acting as an LDAP client. 5409 Among others, ORG.D has the following features: 5411 * Comprehensive, simple-to-use search and positioning options 5413 * complex searches, including approximate search 5415 * Several databases visible at the same time in an interface 5417 * Private address books: available on every desktop 5419 * Optional use of distribution lists and private address book 5421 * Support for MS-Word mail merge by means of special export 5422 format 5424 * adaptable print listings and comfortable list&label 5425 functionality 5427 * customizing tool in order to adapt to any directory schema 5429 * Configurable user interface 5431 * Automatic unbind after idle time 5433 * Anonymous and simple unprotected bind 5435 * Data transfer to Windows applications via file, Drag&Drop, 5436 and DDE 5437 * Central administration of distribution lists/groups 5439 * "Domain administrators" with limited rights defined only for 5440 home site/department 5442 * Direct modification / creation of DIT entries from the user 5443 interface 5445 * Choice of a proposal list when new employee data is added 5447 Tight integration in SNI4s X.400/SMTP-MIME mail service and CIT 5448 products 5450 * DDE connection and drag&drop data transfer to SNI's X.400 5451 user agent MAIL.D and SNI4s CIT product ComfoPhone 5453 * Setting up and administering mailboxes on remote mailbox 5454 servers 5456 * Central administration of server addresses and logon data 5458 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 5460 ORG.D V2.1 is an LDAP client. 5462 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 5464 ORG.D V2.1 is an LDAP client. 5466 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 5468 ORG.D V2.1 is compliant with the following RFCs: [RFC 1777], [RFC 5469 1778], [RFC 1779]. 5471 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 5473 ORG.D V2.1 is compliant with the following RFCs: [RFC 1278], [RFC 5474 1558]. 5476 INTEROPERABILITY 5478 ORG.D V2.1 is based on University of Michigan's LDAP implementation 5479 V3.0. It can interoperate with any LDAP server. 5481 PILOT CONNECTIVITY 5482 In future ORG.D will be used to browse in the European NameFLOW- 5483 PARADISE pilot network. Currently SNI's directory client product 5484 DIR.D V2.6 is used to browse in the European NameFLOW-PARADISE pilot 5485 network. 5487 BUGS 5489 To report bugs and/or to retrieve additional information on SNI's 5490 directory products please send mail to infoline- 5491 com@s41.mch1.x400scn.sni.de. 5493 CAVEATS AND GENERAL LIMITATIONS 5495 [No information provided. -- Ed.] 5497 INTERNETWORKING ENVIRONMENT 5499 LDAP with TCP/IP 5501 HARDWARE PLATFORMS 5503 PC (Intel) 5505 SOFTWARE PLATFORMS 5507 Windows 3.1 + Winsockets 5508 Windows for Workgroups 3.11 + Winsockets 5509 Windows 95 5510 Windows NT 3.5 5511 OS/2 3.0 + Windows for OS/2 + Winsockets 5513 NUMBER OF IMPLEMENTATIONS IN THE FIELD 5515 Field testing is to be started in Spring 1996. 5517 AVAILABILITY 5519 ORG.D V2.0 / V2.1 can be delivered as a binary product. It is 5520 commercially available from: 5522 Siemens Nixdorf Informationssysteme AG 5523 ASW BA COM 1 5524 D-81730 Munich 5525 Germany 5526 Please contact 5528 Giovanni Rabaioli 5529 Voice: +49/89-636-41095 5530 Fax: +49/89-636-42552 5531 Mail: Giovanni.Rabaioli@mch.sni.de 5533 DATE LAST UPDATED or CHECKED 5535 April 1996 5537 ADDITIONAL INFORMATION and/or COMMENTS 5539 DIR.X V4.0 1993 X.500 Directory Service 5540 DIR.X V3.1 1988 X.500 Directory Service 5541 DIR.D V2.6 LDAP browser for information retrieval 5542 DIR.X-SYNC V2.0 Directory synchronization 5543 NAME 5545 OSIAM X.500-88 5547 MARBEN 5549 ABSTRACT 5551 OSIAM X.500-88 is Marben's 1988 compliant directory product. It 5552 provides: 5554 * DUA, offering X/Open XOM and XDS APIs 5556 * Pocket DUA, providing Microsoft MAPI(tm) 5558 * DSA and C-ISAM based DIB 5560 * LDAP Server 5561 OSIAM DUA is a portable Directory User Agent implement, which 5562 implements DAP engine. It provides X/Open XOM and XDS APIs. It works 5563 on multiple lower layer stacks (OSI Transport or TCP/IP). An LDAP 5564 Server may be provided with the DUA. 5566 Pocket DUA is a light DUA implement which offers full DAP access, but 5567 light in terms of code size and memory occupation, and is mainly 5568 designed for PC environments. It provides MAPI(tm) interface, as an 5569 address book provider. It provides multiple network connectivities: 5570 X.25, [RFC 1006] over TCP/IP, and APS. 5572 OSIAM X.500 DSA provides full X.500 1988 functionality. Main features 5573 include: chaining/multicasting, extensible schema, proprietary access 5574 control list, comprehensive administration facilities. 5576 MARBEN is currently developing a new generation of directory product, 5577 providing X.500 1993 functionality. Main targets are: 5579 * high performance 5581 * robustness and administration facility with DIB on commercial 5582 RDBMS 5584 * replication 5585 * access control 5587 * extended information models 5589 Please contact MARBEN for more information on '93 product. 5591 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 5593 OSIAM X.500-88 DUA and DSA implement CCITT X.500 (1988) an ISO 9594 5594 standards. 5596 Compliant with EWOS and NIST OIW Stable Implementor's Agreement. 5598 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 5600 1993 product is under development. 5602 Please contact MARBEN for more information on '93 product. 5604 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 5606 Compliant with the following Internet Standards: 5608 * [RFC 1274]: the COSINE and Internet X.500 Schema (partially 5609 supported) 5611 * [RFC 1277]: encoding of network addresses 5613 * [RFC 1778], [RFC 1777], [RFC 1779]: LDAP and related 5614 standards 5616 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 5618 None is supported at the present time. 5620 INTEROPERABILITY 5622 Have successfully interoperated, both on DAP and DSP, with QUIPU, E3X 5623 and other implementations involved in Paradise pilot project. 5625 PILOT CONNECTIVITY 5627 Connected to Paradise pilot project. 5629 BUGS 5631 [No Information Provided--Ed.] 5633 CAVEATS AND GENERAL LIMITATIONS 5635 [No Information Provided--Ed.] 5637 INTERNETWORKING ENVIRONMENT 5639 [RFC 1006] with TCP/IP, TP0 with X.25, TP4 with CLNS 5641 HARDWARE PLATFORMS 5643 OSIAM X.500-88 is highly portable, and has been ported to a wide 5644 range of platforms, including: 5646 * HP9000 series 5648 * SUN SPARC Stations 5650 * SCO UNIX 5652 * Tandem 5654 * MARK III, etc. 5656 MARBEN Pocket DUA runs on PC/Windows and NT. 5658 SOFTWARE PLATFORMS 5660 See HARDWARE PLATFORMS. 5662 NUMBER OF IMPLEMENTATIONS IN THE FIELD 5664 [No information provided. -- Ed.] 5666 AVAILABILITY 5668 Commercially available from: 5670 MARBEN 5671 11 Rue Curie 5672 92150 Suresnes, France 5674 Contact Person: Karim Jammal or Shaofeng Li 5675 Phone: (33 - 1) 41 38 10 00 5676 Fax: (33 - 1) 41 38 10 01 5677 X.400: C=FR;A=Atlas;P=Marben;O=Suresnes;OU1=MxMs;S=KJammal 5678 E-Mail:sli@wtk.suresnes.marben.fr 5680 Also available from: 5682 MARBEN Products Inc. 5683 2105 Hamilton Avenue, Suite 320 5684 San Jose, CA95125, USA 5686 Contact Person: Jean-Francois Chapuis 5687 Phone: (408) 879 4000 5688 Fax: (408) 879 4001 5689 E-Mail: jfchapuis@marben.com 5691 DATE LAST UPDATED or CHECKED 5693 October 1995 5695 ADDITIONAL INFORMATION and/or COMMENTS 5697 [No Information Provided--Ed.] 5699 NAME 5701 OSIAM X.500-93 5703 MARBEN 5705 ABSTRACT 5707 OSIAM X.500-93 is Marben's 1993 compliant directory product. 5709 Open Directory 5711 * OSIAM X.500-93 provides both DAP and LDAP access 5713 * Support for distribution using the DSP protocol 5715 * Support for replication using the DISP protocol 5717 * Pocket DUA, providing Microsoft MAPI0(tm) and MAPI1(tm) 5718 interface to MS-Mail(tm) or Exchange(tm) 5720 * WEB gateway to access Directory information from WEB browsers 5722 * X/Open XOM/XDS API 5724 * High performance direct API 5726 High Capacity 5728 * Mapped on a RDBMS 5730 * Over 1.000.000 entries 5732 * Use of transaction, to ensure robustness 5734 * Can run on high-available hardware systems 5736 * Isolated interface, to be customized for various RDBMS 5738 High Performance 5740 * Use of cache at DUA level 5741 * Use of cache at DSA level 5743 * Use of replication. Can act as shadow supplier, shadow 5744 consumer or secondary shadow supplier. Support for total or 5745 incremental refresh. Support for both scheduled update and 5746 "on change" update. 5748 * Based on an indexed database, to ensure high-performance 5749 elaborated search. 5751 Security 5753 * Anonymous bind, simple and simple protected authentication 5755 * X.509 certificates storage 5757 * Access control 5759 Ease of administration 5761 * Extensible schema 5763 * Backup-recovery 5765 * Event logging 5767 * Statistics information about Directory use 5769 * Billing dockets generation 5771 Ease of integration 5773 * Provided as binary product or as portable source code 5775 * MARBEN services: training, consulting, system integration, 5776 hot-line support, maintenance. 5778 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 5780 OSIAM X.500-93 DUA and DSA implement CCITT X.500 (1988) and ISO 9594 5781 standards. 5783 Compliant with EWOS and NIST OIW Stable Implementor's Agreement. 5785 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 5787 OSIAM X.500-93 DUA and DSA implement CCITT X.500 (1993) and ISO 9594 5788 standards. 5790 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 5792 Compliant with the following Internet Standards: 5794 * [RFC 1274]: the COSINE and Internet X.500 Schema (partially 5795 supported) 5797 * [RFC 1277]: encoding of network addresses 5799 * [RFC 1778], [RFC 1777], [RFC 1779]: LDAP and related 5800 standards 5802 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 5804 None is supported at the present time. 5806 INTEROPERABILITY 5808 Have successfully interoperated, both on DAP and DSP, with QUIPU, E3X 5809 and other implementations involved in Paradise pilot project. 5811 PILOT CONNECTIVITY 5813 Connected to Paradise pilot project. 5815 BUGS 5817 [No Information Provided--Ed.] 5819 CAVEATS AND GENERAL LIMITATIONS 5821 [No Information Provided--Ed.] 5823 INTERNETWORKING ENVIRONMENT 5825 [RFC 1006] with TCP/IP, TP0 with X.25, TP4 with CLNS 5827 HARDWARE PLATFORMS 5829 OSIAM X.500-93 is highly portable, and has been ported to a wide 5830 range of platforms, including: 5832 * Windows NT 5834 * HP-UX 5836 * IBM AIX 5838 * SUN Solaris 5840 * SCO UNIX 5842 * IBM MVS 5844 MARBEN Pocket DUA runs on PC/Windows and NT. 5846 SOFTWARE PLATFORMS 5848 See HARDWARE PLATFORMS. 5850 NUMBER OF IMPLEMENTATIONS IN THE FIELD 5852 [No information provided. -- Ed.] 5854 AVAILABILITY 5856 Commercially available from: 5858 MARBEN 5859 11 Rue Curie 5860 92150 Suresnes, France 5862 Contact Person: Marc Chauvin or Olivier Gatine 5863 Phone: (33 - 1) 41 38 10 00 5864 Fax: (33 - 1) 41 38 10 01 5865 E-Mail:sales@suresnes.marben.fr 5867 Also available from: 5869 MARBEN Products Inc. 5870 2105 Hamilton Avenue, Suite 320 5871 San Jose, CA95125, USA 5873 Contact Person: Jean-Francois Chapuis 5874 Phone: (408) 879 4000 5875 Fax: (408) 879 4001 5876 E-Mail: jfchapuis@marben.com 5878 DATE LAST UPDATED or CHECKED 5880 July 1996 5882 ADDITIONAL INFORMATION and/or COMMENTS 5884 [No Information Provided--Ed.] 5886 NAME 5888 PMDF-X500 5890 from: 5892 Innosoft International, Inc. 1050 East Garvey Ave. South West 5893 Covina, California 91790 5895 Phone: +1 818-919-3600 email: sales@innosoft.com 5897 ABSTRACT 5899 PMDF-X500 is Innosoft's implementation of the X.500 standards for 5900 Directory Services. PMDF-X500 is based upon the ISODE Consortium 5901 code-base. The core of PMDF-X500 is the Directory System Agent (DSA) 5902 server. This server provides directory information to Directory User 5903 Agents (DUA) using either OSI or TCP/IP networking protocols. Since 5904 PMDF-X500 is based on a widely used implementation, it interoperates 5905 particularly well with a whole host of X.500-based products from 5906 other sources. 5908 In order to facilitate initial loading of directory data as well as 5909 ongoing coordination with other directory services, PMDF-X500 5910 includes tools to import from and export directory information to 5911 Entry Description File (EDF) files. EDF files are flat text files. 5912 PMDF-X500 provides directory coordination functions using EDF files 5913 for the following directories: 5915 * X.500 DSAs supporting LDAP access 5917 * cc:Mail 5919 * Digital's DDS 5921 * GroupWise 5923 * Microsoft Mail 5925 * PMDF generic databases 5927 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 5929 OSI directory services as specified in CCITT X.500 Recommendations 5930 and ISO 9594 use the Directory Access Protocol (DAP) and the 5931 Directory System Protocol (DSP). 5933 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 5935 PMDF-X500 does not yet support the 1993 changes to the X.500 5936 standard. Support for the 1993 X.500 recommendations is planned for 5937 a future release of PMDF-X500. 5939 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 5941 PMDF-X500 supports DAP and DSP accesses using Internet protocols as 5942 specified in [RFC 1006]. In addition, the Internet community has 5943 proposed two lightweight alternatives to DAP called Lightweight 5944 Directory Access Protocol (LDAP), which is specified in [RFC 1777], 5945 and Connectionless Lightweight Directory Access Protocol (CLDAP), 5946 which is specified in [RFC 1798]. LDAP and CLDAP, which are currently 5947 specified to run over TCP/IP, are much simpler protocols than DAP and 5948 were designed to reduce the cost of entry associated with using X.500 5949 protocols in client applications. PMDF-X500 includes both LDAP and 5950 CLDAP servers. 5952 The LDAP server accesses X.500 directory information using DAP to 5953 communicate with X.500 DSAs. PMDF-X500 provides an LDAP server which 5954 translates LDAP requests into DAP requests to communicate with X.500 5955 DSAs. CLDAP defines a very low overhead method for accessing X.500 5956 directory information. CLDAP is suitable for providing access to 5957 information that does not require access controls. 5959 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 5961 [No information provided. -- Ed.] 5963 INTEROPERABILITY 5965 PMDF-X500 interoperates with a large number of DUAs and DSAs. This is 5966 demonstated by the fact that PMDF-X500 is DSA used by several 5967 Internet White Pages Project participants. PMDF-X500 DSA 5968 interoperability includes at least all of the DSA that are used in 5969 the White Pages Project. 5971 PMDF-X500 is delivered with several DUAs and in addition is know to 5972 support the DUAs from Unisys and Digital Equipment Corporation as 5973 well as the publically available DUAs MaX500, Cello, Swix, and the 5974 NASA DUA. 5976 PILOT CONNECTIVITY 5978 PMDF-X500 is used by several sites that are participants of the 5979 Internet White Pages Project include the Innosoft DSA. 5981 BUGS 5983 [No information provided. -- Ed.] 5985 CAVEATS AND GENERAL LIMITATIONS 5987 [No information provided. -- Ed.] 5989 INTERNETWORKING ENVIRONMENT 5991 DAP and DSP are layered on top of the OSI protocol suite. PMDF-X500 5992 supports this protocol suite over multiple network transports. For a 5993 pure OSI protocol stack, DECnet/OSI can be used to provide the lower 5994 layers of the stack. In addition, PMDF-X500 supports running OSI 5995 upper layer protocols over a TCP/IP transport in accordance with [RFC 5996 1006]. It is important to note that while [RFC 1006] specifies TCP/IP 5997 as a transport, all of the OSI upper layer protocols are always used 5998 with DAP and DSP. 6000 HARDWARE PLATFORMS 6002 Digital VAX systems 6003 Digital Alpha/AXP systems 6005 SOFTWARE PLATFORMS 6007 OpenVMS/VAX 6008 OpenVMS/AXP 6009 Digital UNIX 6011 NUMBER OF IMPLEMENTATIONS IN THE FIELD 6013 [No information provided. -- Ed.] 6015 AVAILABILITY 6017 PMDF-X500 is a commerical product that is part of the PMDF family of 6018 eMail Interconnect products. PMDF-X500 requires the presence of 6019 PMDF-MTA, Innosoft's SMTP/MIME mailer. PMDF-X500 and PMDF-MTA can be 6020 obtained from: 6022 Innosoft International, Inc. 6023 1050 East Garvey Ave. South 6024 West Covina, California 91790 6026 Phone: +1 818-919-3600 6027 FAX: +1 818-919-3614 6028 email: sales@innosoft.com 6030 DATE LAST UPDATED or CHECKED 6032 December 1995 6034 ADDITIONAL INFORMATION and/or COMMENTS 6035 NAME 6037 waX.500 6039 University of Michigan 6041 ABSTRACT 6043 waX.500 :: Windows Access to X.500 6045 waX.500 is a (currently 16-bit) DUA that run on Microsoft Windows 6046 (3.1, Win95, & WinNT). It uses libldap.dll which uses the winsock 6047 (v1.1) interface. It works on any vendors tcp/ip stack that I've 6048 seen so far (some configuration may be required). 6050 waX.500 was developed by the University of Michigan for use by its 6051 faculty, staff and students. UM's online directory is an X.500 6052 directory containing 50,000+ entries. 6054 I keep the following Web page up to date with respect to latest 6055 release, etc.: 6056 http://www-personal.umich.edu/~rsug/ldap/wax500/ 6058 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 6060 [No information provided. -- Ed.] 6062 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 6064 [No information provided. -- Ed.] 6066 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 6068 [No information provided. -- Ed.] 6070 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 6072 [No information provided. -- Ed.] 6074 INTEROPERABILITY 6076 [No information provided. -- Ed.] 6078 PILOT CONNECTIVITY 6080 Can see and browse anything in the world as far as I know. 6082 BUGS 6084 report bugs to wax500.bugs@umich.edu 6086 CAVEATS AND GENERAL LIMITATIONS 6088 [No information provided. -- Ed.] 6090 INTERNETWORKING ENVIRONMENT 6092 Microsoft Windows (3.1, 95, & NT) Winsock (v1.1) tcp/ip (any vendor) 6094 HARDWARE PLATFORMS 6096 Any Windows machine with internet connectivity. Both ethernet and 6097 dialup PPP. 6099 SOFTWARE PLATFORMS 6101 Microsoft Windows (3.1, 95, & NT) Winsock (v1.1) tcp/ip (any vendor). 6103 NUMBER OF IMPLEMENTATIONS IN THE FIELD 6105 This implementation is distributed at no cost to the user; accurate 6106 numbers are not available. 6108 AVAILABILITY 6110 http://www-personal.umich.edu/~rsug/ldap/wax500 6111 ftp://terminator.rs.itd.umich.edu/ldap/wax500/wax... 6113 DATE LAST UPDATED or CHECKED 6115 13 Dec 1995 6117 ADDITIONAL INFORMATION and/or COMMENTS 6119 [No information provided. -- Ed.] 6121 NAME 6123 X500-DS 6125 X500-DUA 6127 Bull S.A. 6129 ABSTRACT 6131 X500-DS and X500-DUA are integral part of the large Bull OSI offer. 6132 Although based on the DCE/GDS (Distributed Computing 6133 Environment/Global Directory Service) of OSF, those two products may 6134 be installed and used without the DCE environment. Some enhancements 6135 have been added for the user and the management facilities. X500-DS 6136 is designed to implement both the DUA and the DSA functions, whilst 6137 X500-DUA only provides the DUA functions. 6139 The X500-DUA package contains: 6141 * The standards APIs XOM (X/Open OSI-Abstract-Data Manipulation 6142 API) and XDS (X/Open Directory Service API) for the 6143 development of portable applications, 6145 * A core DUA to translate all user's requests (bind, read, 6146 list, compare, modify, modifyRDN, search, add, remove, unbind 6147 ...) into the DAP protocol used for communication with 6148 distant DSAs, 6150 * The OSI standard high layers (ASN.1, ROSE, ACSE, Presentation 6151 and Session) for communication with the distant DSAs. The 6152 interface with the low layers is XTI. [RFC 1006] is supported 6153 under XTI or the OSI Session, 6155 * A DUA Cache to improve performances when accessing remote 6156 DSAs, 6158 * A powerful management application facilitating the 6159 configuration of the product and controlling the operations, 6160 logs and traces, 6162 * A user application for the manipulations of the database 6163 entries, 6164 * A generic tool to load and unload ASCII and binary files 6165 in/from distributed DSAs, 6167 * The support of the LDAP [RFC 1777] thanks to an LDAP Server, 6169 * A DUA Server that allows to use A-Window-To-Directory (refer 6170 to this DUA product description) on a PC. 6172 The X500-DS package contains: 6174 * All components of the X500-DUA, 6176 * A core DSA to process all requests received from distant DUAs 6177 through DAP protocol or from distant DSAs through DSP 6178 protocol, 6180 * The support of the referral, chained and multi-casting modes 6181 of operation, access control lists and management of 6182 knowledge information (for distribution, shadows and copies 6183 of sub-trees), 6185 * The support of the simple authentication and of the DCE 6186 authentication, 6188 * A management application for managing the schema information 6189 (creation, deletion and modification of object classes and of 6190 attribute types, management of the rules of the DIT). 6192 * A C-ISAM database that is specially designed for high 6193 performances: e.g. less than 10 ms to read an entry on an 6194 Escala at the XOM/XDS interface. 6196 These two products are easely installed, configured and administered 6197 thanks to the System Management Interface Tool (SMIT) screens of AIX. 6199 COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs) 6201 Compliant with EWOS and OIW Agreements 6203 Consists of both DUA and DSA implementation according to the '88 6204 CCITT X.500 and ISO 9594 standard. The X/Open standard XDS and XOM 6205 interface libraries are also provided. When the product is installed 6206 with the DCE environment, XDS and XOM interfaces are also used to 6207 access DCE/CDS (Local Cell Directory Service) transparently. A GDA 6208 (Global Directory Agent) serves then as the gateway between the DCE 6209 CDS and GDS. 6211 COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs) 6213 [New description field -- Ed.] 6215 CONFORMANCE WITH PROPOSED INTERNET STANDARDS 6217 Supports [RFC 1277], [RFC 1777]. 6219 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 6221 [No information provided--Ed.] 6223 INTEROPERABILITY 6225 This implementation of DAP and DSP can interoperate with other X.500 6226 implementations from other Cebit and EUROSINET demo participants 6227 including IBM, HP, ICL, Siemens-Nixdorf, SUN, Marben, NEXOR, etc. It 6228 also interoperates with ISODE QUIPU. 6230 PILOT CONNECTIVITY 6232 [No information provided--Ed.] 6234 BUGS 6236 Bull S.A. provides complete software maintenance with the products. 6238 CAVEATS AND GENERAL LIMITATIONS 6240 [No information provided--Ed.] 6242 INTERNETWORKING ENVIRONMENT 6244 OSI TP4 with CLNP (WAN - LAN) 6246 OSI TP0, 2 & 4 with X.25 (WAN) 6248 [RFC 1006] with TCP/IP 6250 Either BSD sockets or XTI can be used to access the transports. 6252 Through XTI, both OSI and TCP/IP protocols are possible on the same 6253 machine, thus permitting to build a Directory Service distributed on 6254 OSI and TCP/IP networks. 6256 HARDWARE PLATFORMS 6258 DPX/20, Escala SMP 6260 SOFTWARE PLATFORMS 6262 AIX 4.1.4 6264 NUMBER OF IMPLEMENTATIONS IN THE FIELD 6266 [No information provided. -- Ed.] 6268 AVAILABILITY 6270 The release 3.1 described here is commercially available since 2 Q 96 6272 Please contact: 6274 Daniel Monges 6275 Tel: + (33) 76 39 79 83 6276 Fax: + (33) 76 39 77 70 6277 e-mail: D.Monges@frec.bull.fr 6279 Note that after October 18th 1996 (23:00), the telephon and fax numbers 6280 will be: 6281 Tel: + (33) 04 76 29 79 83 6282 Fax: + (33) 04 76 29 77 70 6284 DATE LAST UPDATED or CHECKED 6286 April 1996 6288 ADDITIONAL INFORMATION and/or COMMENTS 6290 [No information provided. -- Ed.] 6292 4. References 6294 [CCITT-88] CCITT, "Data Communications Networks Directory", 6295 Recommendations X.500-X.521, Volume VIII Fascicle VIII.8, IXth 6296 Plenary Assembly, Melbourne, November 1988. 6298 [ITU-T-93] ITU-T,"Information Technology - Open Systems 6299 Interconnection - The Directory", Recommendations X.500-X.525, May 6300 1993. 6302 [NIST-88] National Institute of Standards and Technology, "Stable 6303 Implementation Agreements for Open Systems Interconnection 6304 Protocols", Version 2 Edition 1, NIST Special Publication 500-162, 6305 December 1988. 6307 [NIST-94] National Institute of Standards and Technology, "Stable 6308 Implementation Agreements for Open Systems Interconnection 6309 Protocols", Version ? Edition ?, NIST Special Publication ???-???, 6310 December 1994. 6312 [RFC 1006] Rose, M., and Cass, D., "ISO Transport Service on top of 6313 the TCP", RFC 1006, Northrop Research and Technology Center, May 6314 1987. 6316 [RFC 1070] Hagens, R., Hall, N., and Rose, M., "Use of the Internet 6317 as a Subnetwork for Experimentation with the OSI Network Layer", RFC 6318 1070, U of Wisconsin - Madison, The Wollongong Group, February 1993. 6320 [RFC 1202] Rose, M., "Directory Assistance Service", RFC 1202, 6321 Performance Systems International, Inc., February 1991. 6323 [RFC 1249] Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol 6324 Specification", RFC 1249, University of Michigan, August 1991. 6326 [RFC 1274] Barker, P., and S. Kille, "The COSINE and Internet X.500 6327 Schema", RFC 1274, University College, London, England, November 6328 1991. 6330 [RFC 1275] Kille, S., "Replication Requirements to provide an 6331 Internet Directory using X.500," RFC 1275, University College, 6332 London, England, November 1991. 6334 [RFC 1276] Kille, S., "Replication and Distributed Operations 6335 extensions to provide an Internet Directory using X.500", RFC 1276, 6336 University College, London, England, November 1991. 6338 [RFC 1277] Kille, S., "Encoding Network Addresses to support 6339 operation over non-OSI lower layers", RFC 1277, University College, 6340 London, England, November 1991. 6342 [RFC 1278] Kille, S., "A string encoding of Presentation Address", 6343 RFC 1278, University College, London, England, November 1991. 6345 [RFC 1279] Kille, S., "X.500 and Domains", RFC 1279, University 6346 College, London, England, November 1991. 6348 [RFC 1484] Kille, S., "Using the OSI Directory to achieve User 6349 Friendly Naming", RFC 1484, ISODE Consortium, July 1993. 6351 [RFC 1485] S. Kille, "A String Representation of Distinguished 6352 Names", RFC 1485, ISODE Consortium, July 1993. 6354 [RFC 1487] Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight 6355 Directory Access Protocol", RFC 1487, Performance Systems 6356 International, University of Michigan, ISODE Consortium, July 1993. 6358 [RFC 1488] Howes, T., Kille, S., Yeong, W., and C. Robbins, "The 6359 X.500 String Representation of Standard Attribute Syntaxes", RFC 6360 1488, University of Michigan, ISODE Consortium, Performance Systems 6361 International, NeXor Ltd., July 1993. RFC-1558 6363 [RFC 1558]: Howes, T., "A String Representation of LDAP Search 6364 Filters", RFC 1558, University of Michigan, December 1993. 6366 [RFC 1562]: Michaelson, G. and Prior, M., "Naming Guidelines for the 6367 AARNet X.500 Directory Service", RFC 1562, The University of 6368 Queensland, The University of Adelaide, December 1993. 6370 [RFC 1567]: Mansfield, G., and Kille, S., "X.500 Directory Monitoring 6371 MIB", RFC 1567, AIC Systems Laboratory, ISODE Consortium, January 6372 1994. 6374 [RFC 1608]: Johannsen, T., Mansfield, G., Kosters, M., and Sataluri, 6375 S., "Representing IP Information in the X.500 Directory", RFC 1608, 6376 Dresden University, AIC Systems Laboratory, Network Solutions, Inc., 6377 AT&T Bell Laboratories, March 1994. 6379 [RFC 1609]: Mansfield, G., Johannsen, T., and Knopper, M., "Charting 6380 Networks in the X.500 Directory", RFC 1609, AIC Systems Laboratory, 6381 Dresden University, Merit Networks, Inc., March 1994. 6383 [RFC 1617]: Barker, P., Kille, S., and Lenggenhager, T., "Naming and 6384 Structuring Guidelines for X.500 Directory Pilots", RFC 1617, 6385 University College London, ISODE Consortium, SWITCH, May 1994. 6387 [RFC 1777]: Yeong, W., Howes, T., and Kille, S., "Lightweight 6388 Directory Access Protocol", RFC 1777, Performance Systems 6389 International, University of Michigan, ISODE Consortium, March 1995. 6391 [RFC 1778]: Howes, T., Kille, S., Yeong, W., and Robbins, "The String 6392 Representation of Standard Attribute Syntaxes", RFC 1778, University 6393 of Michigan, ISODE Consortium, Performance Systems International, 6394 NeXor Ltd., March 1995. 6396 [RFC 1779]: Kille, S., "A String Representation of Distinguished 6397 Names", RFC 1779, ISODE Consortium, March 1995. 6399 [RFC 1781]: Kille, S., "Using OSI Directory to Achieve User Friendly 6400 Naming", RFC 1781, ISODE Consortium, March 1995. 6402 [RFC 1798]: Young, A., "Connection-less Lightweight Directory Access 6403 Protocol", RFC 1798, ISODE Consortium, June 1995. 6405 [RFC 1801]: Kille, S., "MHS Use of the X.500 Directory to support MHS 6406 Routing", RFC 1801, ISODE Consortium, June 1995. 6408 [RFC 1803]: Wright, R., Getchell, Howes, T., Sataluri, S., Yee, P., 6409 and Yeong, W., "Recommendations for an X.500 Production Directory 6410 Service", RFC 1803, Lawrence Berkeley Laboratory, Lawrence Livermore 6411 National Laboratory, University of Michigan, AT&T Bell Laboratories, 6412 NASA Ames Research Center, Performance Systems International, Inc., 6413 June 1995. 6415 [RFC 1804]: Mansfield, G., Rajeev, P., Raghavan, S., and Howes, T., 6416 "Schema Publishing in X.500 Directory", RFC 1804, AIC Laboratories, 6417 Hughes Software Systems, Indian Institute of Technology, Madras, 6418 University of Michigan, June 1995. 6420 [RFC 1823]: Howes, T. and Smith, M., "The LDAP Application 6421 Programming Interface", RFC 1823, University of Michigan, August 6422 1995. 6424 5. Security Considerations 6426 Security issues are not discussed in this memo. 6428 6. Editors' Addresses 6430 Chris Apple 6431 Room 2D-104 6432 AT&T Laboratories 6433 600 Mountain Ave. 6434 Murray Hill, NJ 07974 6435 U.S.A. 6436 e-mail: capple@master.control.att.com 6437 Voice: (908) 582-2409 6438 FAX: (908) 582-6113 6440 Ken Rossen 6441 SHL Systemhouse, Inc. 6442 10 Williamsville Road 6443 Hubbardston Center, MA 01452-1311 6444 U.S.A. 6445 e-mail: kenr@shl.com 6446 Voice: (508) 928-5368 6447 FAX: (508) 928-5399