* specificKnowledge
* nonSpecificKnowledge
* supplierKnowledge
* consumerKnowledge
* secondaryShadows
* dITStructureRules
* nameForms
* dITContentRules
* objectClasses
* attributeTypes
* matchingRules
* matchingRuleUse
Conformance is claimed for return of alias names as defined in
7.7.1 of X.511 IS0/IEC 9594-3.
Conformance is claimed for indicating that returned entry
information is complete, as described in 7.7.6 of X.511
ISO/IEC 9594-3.
Conformance is claimed for modifying the object class attribute
to add and/or remove values identifiying auxiliary object
classes, as described in 11.3.2 of X.511 ISO/IEC 9594-3.
Conformance is claimed for Basic Access Control.
Conformance is claimed for Simplified Access Control.
Conformance is claimed for the DSA s ability to administer the
subschema for its portion of the DIT, as defined in X.501
ISO/IEC 9594-2.
Conformance is claimed for all name bindings defined in X.521
ISO/IEC 9594-7.
Conformance is claimed for the DSA s ability to administer
collective attributes, as defined in X.501 ISO/IEC 9594-2.
Static requirements
The DSA supports the application contexts directoryAccessAC and
directorySystemAC.
The DSA conforms to the information framework defined by X.501
ISO/IEC 9594-2.
The DSA conforms to the minimal knowledge requirements defined
in ISO/IEC 959-4.
The DSA operates as a first-level DSA and conforms to the
requirements support of the root context as defined in X.518
ISO/IEC 9594-4.
The DSA supports the attributes for which conformance is
claimed above.
The DSA supports the object classes for which conformance is
claimed above.
The DSA conforms to the following extensions for which
conformance is claimed:
* subentries
* copyShallDo
* extra attributes
* useAliasOnUpdate
* newSuperior
Conformance is claimed for the DSA s ability to administer the
subschema for its portion of the DIT, as defined in X.501
ISO/IEC 9594-2.
Conformance is not claimed for collective attributes, as
defined in X.501 ISO/IEC 9594-3.
Conformance is not claimed for hierarchical attributes, as
defined in X.501 ISO/IEC 9594-3.
The DSA supports the operational attribute types for which
conformance is claimed above.
The DSA supports Basic Access Control and is capable of holding
ACI items that conform to the definitions of Basic Access
Control.
The DSA supports Simplified Access Control and is capable of
holding ACI items that conform to the definitions of Simplified
Access Control.
Dynamic Requirements
The DSA conforms to the mapping onto used services as defined
in clause 8.
The DSA conforms to the procedures for distributed operations
of the Directory related to referrals, as defined in X.518
ISO/IEC 9594-4.
The DSA supports application-context directoryAccessAC and
conforms to the procedures of X.518 ISO/IEC 9594-4 as they
relate to the referral mode of the DAP.
The DSA supports application-context directorySystemAC and
conforms to the referral mode of operation, as defined in
X.518 ISO/IEC 9594-4.
The DSA conforms to the chained mode of interaction as defined
in X.518 ISO/IEC 9594-4.
The DSA conforms to rules of extensibility procedures as
defined in clause 7.5.2 of X.518 ISO/IEC 9594-4.
The DSA supports Basic Access Control and has the capability to
protect information within the DSA in accordance with the
procedures of Basic Access Control.
The DSA supports Simplified Access Control and has the
capability to protect information within the DSA in accordance
with the procedures of Simplified Access Control.
Conformance is not claimed for shadowOperationalBindingID -- as
such, conformance is not claimed for the procedures of X.525
ISO/IEC 9594-9 and X.501 ISO/IEC 9594-2 as they relate to DOP.
Conformance is not claimed for specificHierarchicalBindingID --
as such, conformance is not claimed for the procedures of X.518
ISO/IEC 9594-9 and X.501 ISO/IEC 9594-2 as they relate to
operational bindings.
Conformance is not claimed for non-
specificHierarchicalBindingID -- as such, conformance is not
claimed for the procedures of X.518 ISO/IEC 9594-9 and X.501
ISO/IEC 9594-2 as they relate to operational bindings.
Conformance by a shadow supplier:
Statement Requirements
The DSA supports the application contexts
shadowSupplierInitiatedAC.
Conformance is claimed for the following security-levels:
* None
* Simple
Conformance is claimed for UnitofReplication.
Static Requirements
The DSA supports the application contexts
shadowSupplierInitiatedAC for which conformance is claimed.
Conformance is claimed for the operational attributes
modifyTimestamp and createTimestamp.
Dynamic Requirements
The DSA conforms to the mapping onto used services as defined
in clause 8.
The DSA conforms to the procedures of X.525 ISO/IEC 9594-9 as
they relate to the DISP.
Conformance by a shadow consumer:
Statement Requirements
The DSA supports the application contexts
shadowConsumerInitiatedAC.
Conformance is claimed for the following security-levels:
* None
* Simple
Static Requirements
The DSA supports the application contexts
shadowConsumerInitiatedAC for which conformance is claimed.
The DSA supports operational attributes modifyTimestamp and
createTimestamp.
The DSA supports the copyShallDo service control.
Dynamic Requirements
The DSA conforms to the mapping onto used services as defined
in clause 8.
The DSA conforms to the procedures of X.525 ISO/IEC 9594-9 as
they relate to the DISP.
CONFORMANCE with PROPOSED INTERNET STANDARDS
TransIT 500 supports the following standards: RFC-1777, RFC-1778,
RFC-1779.
CONSISTANCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
RFCs supported include: RFC-1558.
INTEROPERABILITY
Interoperability has been achieved with numerous directory systems.
TransIT 500 has participated in Eurosinet internetworking
demonstrations involving DSAs from:
* AT&T GIS
* Bolden James
* Control Data
* DEC
* ICL
* Nex-tel
* Nexor
* Siemens Nixdorf
PILOT CONNECTIVITY
TransIT 500 is actively involved in pilot projects, including the COS
X.500 Internetworking Project based at The Southern Company in
Atlanta, Georgia, where interoperation was performed with directories
from Digital, Control Data, Hewlett-Packard and Telstra.
BUGS
TransIT 500 products are fully supported category 1 software, which
means:
* These products are periodically updated, revised, and
enhanced.
* Unisys provides software corrections for these products as
necessary.
CAVEATS AND GENERAL LIMITATIONS
[No information provided. -- Ed.]
INTERNETWORKING ENVIRONMENT
[No information provided. -- Ed.]
HARDWARE PLATFORMS
The TransIT 500 software operates on the following hardware
platforms:
* Unisys U6000 Series and Clearpath SMP
* HP 9000 Series
* 386 and above Intel platforms
SOFTWARE PLATFORMS
The DSA is supported on any of the following platforms:
* System V Release 4 (SVR4)
* HP-UX
* Windows NT
The DUA is supported on any of the following platforms:
* Windows 95
* Windows for Workgroups
* Windows NT
Additional software required to run TransIT 500 includes Database
software:
* SQL Server
* Informix
* Oracle
NUMBER OF IMPLEMENTATIONS IN THE FIELD
[No information provided. -- Ed.]
AVAILABILITY
TransIT 500 is commercially available through Unisys Corporation.
For further information, contact the following:
Unisys Corporation
Malvern Building, M.S. B221
2476 Swedesford Road
Paoli, PA 19301, USA
Phone: (800) 874-8647, ext. 584
Fax: (610) 695-5378
e-mail: transit@unisys.com
NAME
waX.500
University of Michigan
ABSTRACT
waX.500 :: Windows Access to X.500
waX.500 is a (currently 16-bit) DUA that run on Microsoft Windows
(3.1, Win95, & WinNT). It uses libldap.dll which uses the winsock
(v1.1) interface. It works on any vendors tcp/ip stack that I've
seen so far (some configuration may be required).
waX.500 was developed by the University of Michigan for use by its
faculty, staff and students. UM's online directory is an X.500
directory containing 50,000+ entries.
I keep the following Web page up to date with respect to latest
release, etc.:
http://www-personal.umich.edu/~rsug/ldap/wax500/
COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)
[No information provided. -- Ed.]
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)
[No information provided. -- Ed.]
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
[No information provided. -- Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided. -- Ed.]
INTEROPERABILITY
[No information provided. -- Ed.]
PILOT CONNECTIVITY
Can see and browse anything in the world as far as I know.
BUGS
report bugs to wax500.bugs@umich.edu
CAVEATS AND GENERAL LIMITATIONS
[No information provided. -- Ed.]
INTERNETWORKING ENVIRONMENT
Microsoft Windows (3.1, 95, & NT) Winsock (v1.1) tcp/ip (any vendor)
HARDWARE PLATFORMS
Any Windows machine with internet connectivity. Both ethernet and
dialup PPP.
SOFTWARE PLATFORMS
Microsoft Windows (3.1, 95, & NT) Winsock (v1.1) tcp/ip (any vendor).
NUMBER OF IMPLEMENTATIONS IN THE FIELD
This implementation is distributed at no cost to the user; accurate
numbers are not available.
AVAILABILITY
http://www-personal.umich.edu/~rsug/ldap/wax500
ftp://terminator.rs.itd.umich.edu/ldap/wax500/wax...
DATE LAST UPDATED or CHECKED
13 Dec 1995
ADDITIONAL INFORMATION and/or COMMENTS
[No information provided. -- Ed.]
NAME
X500-DS
X500-DUA
Bull S.A.
ABSTRACT
X500-DS and X500-DUA are integral part of the large Bull OSI offer.
Although based on the DCE/GDS (Distributed Computing
Environment/Global Directory Service) of OSF, those two products may
be installed and used without the DCE environment. Some enhancements
have been added for the user and the management facilities. X500-DS is
designed to implement both the DUA and the DSA functions, whilst
X500-DUA only provides the DUA functions.
The X500-DUA package contains:
* The standards APIs XOM (X/Open OSI-Abstract-Data Manipulation
API) and XDS (X/Open Directory Service API) for the
development of portable applications,
* A core DUA to translate all user's requests (bind, read,
list, compare, modify, modifyRDN, search, add, remove, unbind
...) into the DAP protocol used for communication with
distant DSAs,
* The OSI standard high layers (ASN.1, ROSE, ACSE, Presentation
and Session) for communication with the distant DSAs. The
interface with the low layers is XTI. [RFC1006] is supported
under XTI or the OSI Session,
* A DUA Cache to improve performances when accessing remote
DSAs,
* A powerful management application facilitating the
configuration of the product and controlling the operations,
logs and traces,
* A user application for the manipulations of the database
entries,
* A generic tool to load and unload ASCII and binary files
in/from distributed DSAs,
* The support of the LDAP [RFC1777] thanks to an LDAP Server,
* A DUA Server that allows to use A-Window-To-Directory (refer
to this DUA product description) on a PC.
The X500-DS package contains:
* All components of the X500-DUA,
* A core DSA to process all requests received from distant DUAs
through DAP protocol or from distant DSAs through DSP
protocol,
* The support of the referral, chained and multi-casting modes
of operation, access control lists and management of
knowledge information (for distribution, shadows and copies
of sub-trees),
* The support of the simple authentication and of the DCE
authentication,
* A management application for managing the schema information
(creation, deletion and modification of object classes and of
attribute types, management of the rules of the DIT).
* A C-ISAM database that is specially designed for high
performances: e.g. less than 10 ms to read an entry on an
Escala at the XOM/XDS interface.
These two products are easely installed, configured and administered
thanks to the System Management Interface Tool (SMIT) screens of AIX.
COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)
Compliant with EWOS and OIW Agreements
Consists of both DUA and DSA implementation according to the '88
CCITT X.500 and ISO 9594 standard. The X/Open standard XDS and XOM
interface libraries are also provided. When the product is installed
with the DCE environment, XDS and XOM interfaces are also used to
access DCE/CDS (Local Cell Directory Service) transparently. A GDA
(Global Directory Agent) serves then as the gateway between the DCE
CDS and GDS.
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)
[New description field -- Ed.]
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
Supports [RFC1277], [RFC1777].
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided--Ed.]
INTEROPERABILITY
This implementation of DAP and DSP can interoperate with other X.500
implementations from other Cebit and EUROSINET demo participants
including IBM, HP, ICL, Siemens-Nixdorf, SUN, Marben, NEXOR, etc. It
also interoperates with ISODE QUIPU.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
Bull S.A. provides complete software maintenance with the products.
CAVEATS AND GENERAL LIMITATIONS
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT
OSI TP4 with CLNP (WAN - LAN)
OSI TP0, 2 & 4 with X.25 (WAN)
[RFC1006] with TCP/IP
Either BSD sockets or XTI can be used to access the transports.
Through XTI, both OSI and TCP/IP protocols are possible on the same
machine, thus permitting to build a Directory Service distributed on
OSI and TCP/IP networks.
HARDWARE PLATFORMS
DPX/20, Escala SMP
SOFTWARE PLATFORMS
AIX 4.1.4
NUMBER OF IMPLEMENTATIONS IN THE FIELD
[No information provided. -- Ed.]
AVAILABILITY
The release 3.1 described here is commercially available since 2 Q 96
Please contact:
Daniel Monges
Tel: + (33) 76 39 79 83
Fax: + (33) 76 39 77 70
e-mail: D.Monges@frec.bull.fr
Note that after October 18th 1996 (23:00), the telephon and fax numbers
will be:
Tel: + (33) 04 76 29 79 83
Fax: + (33) 04 76 29 77 70
DATE LAST UPDATED or CHECKED
April 1996
ADDITIONAL INFORMATION and/or COMMENTS
[No information provided. -- Ed.]
4. References
[CCITT-88] CCITT, "Data Communications Networks Directory",
Recommendations X.500-X.521, Volume VIII Fascicle VIII.8, IXth
Plenary Assembly, Melbourne, November 1988.
[ITU-T-93] ITU-T,"Information Technology - Open Systems
Interconnection - The Directory", Recommendations X.500-X.525, May
1993.
[NIST-88] National Institute of Standards and Technology, "Stable
Implementation Agreements for Open Systems Interconnection
Protocols", Version 2 Edition 1, NIST Special Publication 500-162,
December 1988.
[NIST-94] National Institute of Standards and Technology, "Stable
Implementation Agreements for Open Systems Interconnection
Protocols", Version ? Edition ?, NIST Special Publication ???-???,
December 1994.
[RFC1006] Rose, M., and Cass, D., "ISO Transport Service on top of
the TCP", STD 35, RFC1006, Northrop Research and Technology Center,
May 1987.
[RFC1070] Hagens, R., Hall, N., and Rose, M., "Use of the Internet
as a Subnetwork for Experimentation with the OSI Network Layer", RFC
1070, U of Wisconsin - Madison, The Wollongong Group, February
1993.
[RFC1202] Rose, M., "Directory Assistance Service", RFC1202,
Performance Systems International, Inc., February 1991.
[RFC1249] Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol
Specification", RFC1249, University of Michigan, August 1991.
[RFC1274] Barker, P., and S. Kille, "The COSINE and Internet X.500
Schema", RFC1274, University College, London, England, November
1991.
[RFC1275] Kille, S., "Replication Requirements to provide an
Internet Directory using X.500," RFC1275, University College,
London, England, November 1991.
[RFC1276] Kille, S., "Replication and Distributed Operations
extensions to provide an Internet Directory using X.500", RFC1276,
University College, London, England, November 1991.
[RFC1277] Kille, S., "Encoding Network Addresses to support
operation over non-OSI lower layers", RFC1277, University College,
London, England, November 1991.
[RFC1278] Kille, S., "A string encoding of Presentation Address",
RFC1278, University College, London, England, November 1991.
[RFC1279] Kille, S., "X.500 and Domains", RFC1279, University
College, London, England, November 1991.
[RFC1484] Kille, S., "Using the OSI Directory to achieve User
Friendly Naming", RFC1484, ISODE Consortium, July 1993.
[RFC1485] S. Kille, "A String Representation of Distinguished
Names", RFC1485, ISODE Consortium, July 1993.
[RFC1487] Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight
Directory Access Protocol", RFC1487, Performance Systems
International, University of Michigan, ISODE Consortium, July 1993.
[RFC1488] Howes, T., Kille, S., Yeong, W., and C. Robbins, "The
X.500 String Representation of Standard Attribute Syntaxes", RFC
1488, University of Michigan, ISODE Consortium, Performance Systems
International, NeXor Ltd., July 1993. RFC-1558
[RFC1558] Howes, T., "A String Representation of LDAP Search
Filters", RFC1558, University of Michigan, December 1993.
[RFC1562] Michaelson, G. and Prior, M., "Naming Guidelines for the
AARNet X.500 Directory Service", RFC1562, The University of
Queensland, The University of Adelaide, December 1993.
[RFC1567] Mansfield, G., and Kille, S., "X.500 Directory Monitoring
MIB", RFC1567, AIC Systems Laboratory, ISODE Consortium, January
1994.
[RFC1608] Johannsen, T., Mansfield, G., Kosters, M., and Sataluri,
S., "Representing IP Information in the X.500 Directory", RFC1608,
Dresden University, AIC Systems Laboratory, Network Solutions, Inc.,
AT&T Bell Laboratories, March 1994.
[RFC1609] Mansfield, G., Johannsen, T., and Knopper, M., "Charting
Networks in the X.500 Directory", RFC1609, AIC Systems Laboratory,
Dresden University, Merit Networks, Inc., March 1994.
[RFC1617] Barker, P., Kille, S., and Lenggenhager, T., "Naming and
Structuring Guidelines for X.500 Directory Pilots", RFC1617,
University College London, ISODE Consortium, SWITCH, May 1994.
[RFC1777] Yeong, W., Howes, T., and Kille, S., "Lightweight
Directory Access Protocol", RFC1777, Performance Systems
International, University of Michigan, ISODE Consortium, March 1995.
[RFC1778] Howes, T., Kille, S., Yeong, W., and Robbins, "The String
Representation of Standard Attribute Syntaxes", RFC1778, University
of Michigan, ISODE Consortium, Performance Systems International,
NeXor Ltd., March 1995.
[RFC1779] Kille, S., "A String Representation of Distinguished
Names", RFC1779, ISODE Consortium, March 1995.
[RFC1781] Kille, S., "Using OSI Directory to Achieve User Friendly
Naming", RFC1781, ISODE Consortium, March 1995.
[RFC1798] Young, A., "Connection-less Lightweight Directory Access
Protocol", RFC1798, ISODE Consortium, June 1995.
[RFC1801] Kille, S., "MHS Use of the X.500 Directory to support MHS
Routing", RFC1801, ISODE Consortium, June 1995.
[RFC1803] Wright, R., Getchell, Howes, T., Sataluri, S., Yee, P.,
and Yeong, W., "Recommendations for an X.500 Production Directory
Service", RFC1803, Lawrence Berkeley Laboratory, Lawrence Livermore
National Laboratory, University of Michigan, AT&T Bell Laboratories,
NASA Ames Research Center, Performance Systems International, Inc.,
June 1995.
[RFC1804] Mansfield, G., Rajeev, P., Raghavan, S., and Howes, T.,
"Schema Publishing in X.500 Directory", RFC1804, AIC Laboratories,
Hughes Software Systems, Indian Institute of Technology, Madras,
University of Michigan, June 1995.
[RFC1823] Howes, T. and Smith, M., "The LDAP Application
Programming Interface", RFC1823, University of Michigan, August
1995.
5. Security Considerations
Security issues are not discussed in this memo.
6. Editors' Addresses
Chris Apple
Room 2D-104
AT&T Laboratories
600 Mountain Ave.
Murray Hill, NJ 07974
U.S.A.
e-mail: capple@master.control.att.com
Voice: (908) 582-2409
FAX: (908) 582-6113
Ken Rossen
MCI Systemhouse, Inc.
10 Williamsville Road
Hubbardston Center, MA 01452-1311
U.S.A.
e-mail: kenr@shl.com
Voice: (508) 928-5368
FAX: (508) 928-5399