As per Relevance of the word university, we have this rfc below:
Network Working Group T.
Request for Comments: 1959 M.
Category: Standards Track University of
June 1996
An LDAP URL
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
1.
LDAP is the Lightweight Directory Access Protocol, defined in [1]
[2]. This document describes a format for an LDAP Uniform
Locator which will allow Internet clients to have direct access
the LDAP protocol. While LDAP currently is used only as a front
to the X.500 directory, the URL format described here is
enough to handle the case of stand-alone LDAP servers (i.e.,
servers not back-ended by X.500).
2. URL
An LDAP URL begins with the protocol prefix "ldap" and is defined
the following grammar
::= "ldap://" [ ] "/" [ "?"
[ "?" "?" ] ]
::= <hostname> [ ":" ]
::= a string as defined in RFC 1485
::= NULL |
::=
| [ "," ]
::= a string as defined in RFC 1777
::= "base" | "one" | "sub
::= a string as defined in RFC 1558
Howes & Smith Standards Track [Page 1]
RFC 1959 An LDAP URL Format June 1996
The ldap prefix indicates an entry or entries residing in the
server running on the given <hostname> at the given .
The default port is TCP port 389. The is an LDAP
Name using the string format described in [1], with any URL-
characters (e.g., spaces) escaped using the % method described in
1738.
The construct is used to indicate which
should be returned from the entry or entries.
names are as defined for AttributeType in RFC 1777.
If the part is omitted, all attributes of the entry
entries should be returned
The construct is used to specify the scope of the search
perform in the given LDAP server. The allowable scopes are "base
for a base object search, "one" for a one-level search, or "sub"
a subtree search. If is omitted, a scope of "base"
assumed
The is used to specify the search filter to apply to
within the specified scope during the search. It has the
specified in [4], with any URL-illegal characters escaped using the %
method described in RFC 1738. If is omitted, a filter
"(objectClass=*)" is assumed
Note that if the entry resides in the X.500 namespace, it should
reachable from any LDAP server that is providing front-end access
the X.500 directory. If the part of the URL is missing
the URL can be resolved by contacting any X.500-back-ended
server
3.
The following are some example LDAP URLs using the format
above. An LDAP URL referring to the University of Michigan entry
available from any X.500-capable LDAP server
ldap:///o=University%20of%20Michigan,c=
An LDAP URL referring to the University of Michigan entry in
particular ldap server
ldap://ldap.itd.umich.edu/o=University%20of%20Michigan,c=
This URL corresponds to a base object search of the "o=University
Michigan, c=US" entry using a filter of (objectclass=*),
all attributes
Howes & Smith Standards Track [Page 2]
RFC 1959 An LDAP URL Format June 1996
An LDAP URL referring to only the postalAddress attribute of
University of Michigan entry
ldap://ldap.itd.umich.edu/o=University%20of%20Michigan,c=US?
The corresponding LDAP search operation is the same as in
previous example, except that only the postalAddress attribute
requested
An LDAP URL referring to the set of entries found by querying
X.500-capable LDAP server and doing a subtree search of
University of Michigan for any entry with a common name of "
Jensen", retrieving all attributes
ldap:///o=University%20of%20Michigan,c=US??sub?(cn=Babs%20Jensen
An LDAP URL referring to all children of the c=GB entry
ldap://ldap.itd.umich.edu/c=GB?objectClass?
The objectClass attribute is requested to be returned along with
entries
4. Security
The LDAP URL format does not provide a way to specify credentials
use when resolving the URL. Therefore, it is expected that
requests will be unauthenticated. The security implications
resolving an LDAP URL are the same as those of resolving any
query. See the RFC 1777 for more details
5. Prototype Implementation
There is a prototype implementation of the specification defined
this document available. It is an extension to the libwww
library, provided in both source and binary forms. Also included
binary versions of the Mosaic WWW client for various platforms.
the following URL for more details
ftp://terminator.rs.itd.umich.edu/ldap/url
Howes & Smith Standards Track [Page 3]
RFC 1959 An LDAP URL Format June 1996
6.
[1] Kille, S., "A String Representation of Distinguished Names",
RFC 1779, March 1995.
[2] Yeong, W., Howes, T., and S. Kille, "
Directory Access Protocol", RFC 1777, March 1995.
[3] Howes, R., Kille, S., Yeong, W., and C. Robbins, "The
Representation of Standard Attribute Syntaxes", RFC 1778,
March 1995.
[4] Howes, T., "A String Representation of LDAP Search Filters",
RFC 1558, December 1993.
[5] Berners-Lee, T., Masinter, L., and M. McCahill, "
Resource Locators (URL)", RFC 1738, December 1994.
7.
This material is based upon work supported by the National
Foundation under Grant No. NCR-9416667.
8. Authors'
Tim
University of
ITD Research
535 W William St
Ann Arbor, MI 48103-4943
Phone: +1 313 747-4454
EMail: tim@umich.
Mark
University of
ITD Research
535 W William St
Ann Arbor, MI 48103-4943
Phone: +1 313 764-2277
EMail: mcs@umich.
Howes & Smith Standards Track [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
