
	Where results make sense

Topic: RFC 1823

Related Topics

Ettenmoors

QsNet

Kijkduin

Unknot

DESX

Torosaurus

Catal Huyuk

White Day

Apostasy

Menstruation

Pope Leo I

Roman Forum

Right wing

Thimphu

Kagyupa

In the News (Fri 11 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	rfc1823
		They are: Howes and Smith Informational [Page 6] RFC 1823 LDAP API August 1995 ld_sizelimit A limit on the number of entries to return from the search.
		Howes and Smith Informational [Page 8] RFC 1823 LDAP API August 1995 For LDAP_MOD_ADD modifications, the given values are added to the entry, creating the attribute if necessary.
		It can also be used to count the number of entries Howes and Smith Informational [Page 15] RFC 1823 LDAP API August 1995 that remain in a chain if called with an entry returned by ldap_first_entry() or ldap_next_entry().
	ietfreport.isoc.org /idref/rfc1823 (3562 words)

	RFC 1823 (rfc1823) - The LDAP Application Program Interface
		RFC 1823 - The LDAP Application Program Interface
		Network Working Group T. Howes Request for Comments: 1823 M. Smith Category: Informational University of Michigan August 1995 The LDAP Application Program Interface Status of this Memo This memo provides information for the Internet community.
		Previous: RFC 1822 - A Grant of Rights to Use a Specific IBM patent with Photuris
	www.faqs.org /rfcs/rfc1823.html (3531 words)

	Computers Internet RFCs 1801 - 1900 (Site not responding. Last check: 2007-09-10)
		RFC 1822 - A Grant of Rights to Use a Specific IBM Patent with Photuris.
		RFC 1838 - Use of the X.500 Directory to Support Mapping between X.400 and RFC 822 Addresses.
		RFC 1871 - Addendum to RFC 1602 -- Variance Procedure.
	www.iper1.com /iper1-odp/scat/id/Computers/Internet/RFCs/1801_-_1900 (806 words)

	[No title]
		RFC 1823: Application Programming Interface (has become a standard) ¡6YEYEót ¨LDAP Data Representation¨Each record has a unique key called a distinguished name (dn for short).
		A distinguised name (RFC 1779) is meant to be used by humans (not just computers).
		However, to write a client we don't need to know the details of the protocol, there is an API (RFC 1823) and library available!ó¨LDAP API¨ðThere are actually a couple of well-established APIs: the original (RFC 1823) from U. of Michigan.
	www.cs.rpi.edu /~hollingd/netprog99/lectures/ldap.ppt (3997 words)

	LDAP, Lightweight Directory Access Protocol
		[RFC 2164] Use of an X.500/LDAP directory to support MIXER address mapping.
		[RFC 2649] An LDAP Control and Schema for Holding Operation Signatures.
		[RFC 1838] Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses.
	filibusta.crema.unimi.it /docs/rfc/ldap.htm (406 words)

	Common LDAP RFCs
		This document defines the requirements that must be satisfied by encoding rules used to render X.500 directory attribute syntaxes into a form suitable for use in the LDAP, and then goes on to define the encoding rules for the standard set of attribute syntaxes.
		This specification defines a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any distinguished name.
		This document replaces RFC 1960 (http://www.cse.ohio-state.edu/cgi-bin/cis-redirect/htbin/rfc/rfc1960.html), extending the string LDAP filter definition to include support for LDAP version 3 extended match filters, and including support for representing the full range of possible LDAP search filters.
	support.microsoft.com /default.aspx?scid=kb;en-us;221606 (1211 words)

	Managing Enterprise Active Directory With Lightweight Directory Access Protocol (LDAP) > Overview (Site not responding. Last check: 2007-09-10)
		The first specification was submitted as RFC 1487 in 1993 and the most recent, LDAP v3, in 1997 as RFC 2252.
		New controls generally go through the RFC process to gain industry acceptance before implementation, but some vendors, such as Microsoft, have implemented their own controls for use specifically within their directory products.
		It is important to note that RFC 1823 is not a standard or proposed standard, but only informational.
	www.awprofessional.com /articles/article.asp?p=30117 (1045 words)

	Dr. Dobb's \| Examining Microsoft's LDAP API \| July 22, 2001
		The abstract definition of LDAP Version 2 (LDAPv2) was published in 1995 in RFC 1777, and a companion API specification appeared shortly thereafter in RFC 1823.
		In RFC 1823, an API that hides all BER and WinSock minutiae beneath a simple surface is defined.
		The problem with RFC 1823, however, is that it is somewhat outdated.
	www.ddj.com /184410752 (2363 words)

	RFC 1822 (rfc1822) - A Grant of Rights to Use a Specific IBM patent with P (Site not responding. Last check: 2007-09-10)
		RFC 1822 (rfc1822) - A Grant of Rights to Use a Specific IBM patent with P
		The grant is made in this RFC and parties have it even if they do not request a confirmation from IBM.
		This grant of rights will terminate with respect to any party that asserts a patent it owns, directly or indirectly, against IBM for IBM's implementation of and operation in compliance with Photuris or any derivative, as defined above.
	www.faqs.org /rfcs/rfc1822.html (323 words)

	RF from FOLDOC (Site not responding. Last check: 2007-09-10)
		For example, RFC 1123 amends RFC952 to say software MUST handle either a letter or a digit as the first character of a hostname.
		This RFC has been obsoleted by RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049, and BCP0013.
		An RFC defining the Simple Network Paging Protocol (SNPP) which is designed to support Internet access to paging services such as those based on the Telocator Alphanumeric Protocol.
	www.instantweb.com /d/dictionary/foldoc.cgi?query=RF (3285 words)

	[No title]
		This document replaces the previous definition of this API, defined in RFC 1823, updating it to include support for features found in version 3 of the LDAP protocol.
		It is a number that matches that assigned to the C LDAP API extension RFC supported for this extension.
		In RFC 1823 this data type was a structure exposed to the caller, and various fields in the structure could be set to control aspects of the session, such as size and time limits on searches.
	mozilla.org /directory/ietf-docs/draft-ietf-ldapext-ldap-c-api-05.txt (16201 words)

	LDAP SDK Overview (Site not responding. Last check: 2007-09-10)
		It replaces the previous definition of this API, defined in RFC 1823, updating it to include support for features found in version 3 of the LDAP protocol.
		LDAP is the lightweight directory access protocol, described in RFC 2251 and RFC 2252 It can provide a lightweight frontend to the X.500 directory, or a stand-alone service.
		In either mode, LDAP is based on a client-server model in which a client makes a TCP connection to an LDAP server, over which it sends requests and receives responses.
	www.opus1.com /www/iii/sdk/overview.html (843 words)

	RedIRIS - RFCs e Internet-Drafts sobre Directorios LDAP
		RFC 1484 - Using the OSI Directory to Achieve User Friendly Naming - 1781
		RFC 1838 - Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses - 2164
		RFC 2079 - Definition of X.500 Attribute Types and an Object Class to Hold Uniform Resource Identifiers (URIs)
	www.rediris.es /ldap/doc/rfcs.es.html (752 words)

	LDAPman RFC page (Site not responding. Last check: 2007-09-10)
		RFC 1778 -- The String Representation of Standard Attribute Syntaxes
		RFC 2256 -- A Summary of the X.500(96) User Schema for use with LDAPv3
		RFC 2079 -- Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers
	www.ldapman.org /ldap_rfcs.html (242 words)

	Net::LDAP::RFC - List of related RFC's
		This document corrects both situations by explicitly specifying the set of RFCs comprising LDAPv3 and rescinding the ``IESG Note'' due to the specification of mandatory-to-implement authentication mechanisms in RFC 2829.
		This document defines a C language application program interface to LDAP, and replaces the previous definition of this API, defined in RFC 1823, updating it to include support for features found in LDAPv3, as well as other changes to support information hiding and thread safety.
		This document describes LDAP schema features in addition to RFC 2587 that are needed to support a Privilege Management Infrastructure and a Public Key Infrastructure.
	www.ysn.ru /docs/perl-ldap/Net/LDAP/RFC.html (7065 words)

	Appendix C: LDAP RFCs & X.500
		The following RFCs describe LDAP or are relevant to it.
		The main repository for RFCs is maintained by the IETF and there is now a searchable list.
		These RFC deal exclusively with LDAP v.3 (OpenLDAP 2.x series).
	www.zytrax.com /books/ldap/apc (691 words)

	Smith, Mark (Site not responding. Last check: 2007-09-10)
		[RFC 2079] Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs).
		[RFC 2425] A MIME Content-Type for Directory Information.
		[RFC 3829] Lightweight Directory Access Protocol (LDAP) Authorization Identity Request and Response Controls.
	www.networksorcery.com /enp/authors/SmithMark.htm (78 words)

	dictionary r3 (Site not responding. Last check: 2007-09-10)
		RFC 1123 defines the terms "MUST", "SHOULD", "MAY",
		For example, RFC 1123 amends RFC952 to say software MUST
		{RFC 2045}, {RFC 2046}, {RFC 2047}, {RFC 2048}, {RFC 2049},
	www.star-cs.com /peterstar/r3.html (4558 words)

	An enterprise directory solution with DB2 - References
		Howes and M. Smith, The LDAP Application Program Interface, RFC 1823, Internet Engineering Task Force (August 1995); available at http://www.ietf.org/rfc/rfc1823.txt?number=1823.
		Kille, A String Representation of Distinguished Names, RFC 1779, Internet Engineering Task Force (March 1995); available at http://www.ietf.org/rfc/rfc1779.txt?number=1779.
		Howes, A String Representation of LDAP Filters, RFC 1960, Internet Engineering Task Force (June 1996); available at http://www.ietf.org/rfc/rfc1960.txt?number=1960.
	www.research.ibm.com /journal/sj/392/shiref.html (484 words)

	Table of contents for Library of Congress control number 99069872 (Site not responding. Last check: 2007-09-10)
		Bibliographic record and links to related information available from the Library of Congress catalog
		RFC 1798 Connectionless Lightweight X.500 Directory Access Protocol
		RFC 2651 The Architecture of the Common Indexing Protocol (CIP)
	www.loc.gov /catdir/toc/els033/99069872.html (261 words)

	Linux LDAP Tutorial: OpenLDAP Software development C programming SDK man pages, RFC's and Links
		Internet Draft (Obsoletes RFC 1823) - The LDAP Application Program Interface (API) for software developers
		1823 - The LDAP Application Program Interface (API) for software developers.
		Mapping LDAP inetOrgPerson object attributes to Palm Pilot Desktop CSV exchange file
	www.yolinux.com /TUTORIALS/LinuxTutorialLDAP-SoftwareDevelopment.html (1122 words)

	DewN RFC util (Site not responding. Last check: 2007-09-10)
		$ rfc -k ldap The Result: 1558 A String Representation of LDAP Search Filters.
		$ rfc 1823 The Result: 1823 The LDAP Application Program Interface.
		$ rfc 2587 The Result: 2587 Internet X.509 Public Key Infrastructure LDAPv2 Schema.
	www.dewn.com /rfc/example.html (126 words)

	Pangaea (Site not responding. Last check: 2007-09-10)
		RFC 1777 - Lightweight Directory Access Protocal (LDAP)
		RFC 1779 - A String Representation of Distinguished Names
		RFC 1522 - Multipurpose Internet Mail Extensions (MIME)
	www.mebsuta.com /pangaea.htm (90 words)

	Linux.com - RFC's
		Organized by category Full list of HOWTOs Full list of guides
		RFC 1781: Using the OSI Directory to Achieve User Friendly Naming
		RFC 2307: LDAP as a Network Information Service
	www.linux.com /howtos/LDAP-HOWTO/rfcs.shtml (134 words)

	Big Book of Lightweight Directory Access Protocol (LDAP) RFCs:Loshin, Pete:0124558437:eCampus.com
		Big Book of Lightweight Directory Access Protocol (LDAP) RFCs
		RFC 2256 A Summary of the X.500 (96) User Schema for Use with LDAPv3
		The Big Book of Mpls(Multiprotocol Label Switching) Rfcs
	www.ecampus.com /bk_detail.asp?isbn=0124558437&referrer=yah04 (299 words)

	Webmasters Internet Tools and Information Resources : RFCs : 1801 - 1900
		Webmasters Internet Tools and Information Resources : RFCs : 1801 - 1900
		Top : RFCs : 1801 - 1900
		Submit your Web site to the our directory!
	www.pjltechnology.com /links/RFCs/1801_-_1900 (147 words)

	ldap.bib
		@MANUAL{rfc2256, AUTHOR = {M. Wahl}, TITLE = {{A Summary of the X.500(96) User Schema for use with LDAPv3}}, NOTE = {{RFC 2256}}, MONTH = DEC, YEAR = 1997, URL = {ftp://ftp.isi.edu/in-notes/rfc2256.txt} }
		Hedberg}, TITLE = {{LDAPv2 Client vs}}, NOTE = {{RFC 2657}}, MONTH = AUG, YEAR = 1999, URL = {ftp://ftp.isi.edu/in-notes/rfc2657.txt} }
		This file has been generated by bibtex2html 1.69 by gregor@mcs.anl.gov
	www-unix.mcs.anl.gov /~laszewsk/bib/ldap-bib.html (692 words)

Try your search on: Qwika (all wikis)