< draft-ietf-asid-ldapv3-protocol-08.txt		draft-ietf-asid-ldapv3-protocol-09.txt >
	Network Working Group M. Wahl		Network Working Group M. Wahl
	INTERNET-DRAFT Critical Angle Inc.		INTERNET-DRAFT Critical Angle Inc.
	Replaces: RFC 1777 T. Howes		Replaces: RFC 1777 T. Howes
	Netscape Communications Corp.		Netscape Communications Corp.
	S. Kille		S. Kille
	Isode Limited		Isode Limited
	Expires in six months from October 1997		Expires in six months from November 1997
	Intended Category: Standards Track		Intended Category: Standards Track
	Lightweight Directory Access Protocol (v3)		Lightweight Directory Access Protocol (v3)
	<draft-ietf-asid-ldapv3-protocol-08.txt>		<draft-ietf-asid-ldapv3-protocol-09.txt>
	Table of Contents - see end of document.		Table of Contents - see end of document.
	1. Status of this Memo		1. Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas, and		documents of the Internet Engineering Task Force (IETF), its areas, and
	its working groups. Note that other groups may also distribute working		its working groups. Note that other groups may also distribute working
	documents as Internet-Drafts.		documents as Internet-Drafts.
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	2. Abstract		2. Abstract
	The protocol described in this document is designed to provide access		The protocol described in this document is designed to provide access
	to directories supporting the X.500 models, while not incurring the		to directories supporting the X.500 models, while not incurring the
	resource requirements of the X.500 Directory Access Protocol (DAP).		resource requirements of the X.500 Directory Access Protocol (DAP).
	This protocol is specifically targeted at management applications and		This protocol is specifically targeted at management applications and
	browser applications that provide read/write interactive access to		browser applications that provide read/write interactive access to
	directories. When used with a directory supporting the X.500		directories. When used with a directory supporting the X.500
	protocols, it is intended to be a complement to the X.500 DAP.		protocols, it is intended to be a complement to the X.500 DAP.
			The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
			"SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document
			are to be interpreted as described in RFC 2119 [10].
	Key aspects of this version of LDAP are:		Key aspects of this version of LDAP are:
	- All protocol elements of LDAPv2 (RFC 1777) are supported. The		- All protocol elements of LDAPv2 (RFC 1777) are supported. The
	protocol is carried directly over TCP or other transport, bypassing		protocol is carried directly over TCP or other transport, bypassing
	much of the session/presentation overhead of X.500 DAP.		much of the session/presentation overhead of X.500 DAP.
	- Most protocol data elements can be encoded as ordinary strings		- Most protocol data elements can be encoded as ordinary strings
	(e.g., Distinguished Names).		(e.g., Distinguished Names).
	- Referrals to other servers may be returned.		- Referrals to other servers may be returned.
	skipping to change at page 34, line 28 ¶		skipping to change at page 34, line 28 ¶
	5.2.1. Transmission Control Protocol (TCP)		5.2.1. Transmission Control Protocol (TCP)
	The LDAPMessage PDUs are mapped directly onto the TCP bytestream.		The LDAPMessage PDUs are mapped directly onto the TCP bytestream.
	It is recommended that server implementations running over the TCP MAY		It is recommended that server implementations running over the TCP MAY
	provide a protocol listener on the assigned port, 389. Servers may		provide a protocol listener on the assigned port, 389. Servers may
	instead provide a listener on a different port number. Clients MUST		instead provide a listener on a different port number. Clients MUST
	support contacting servers on any valid TCP port.		support contacting servers on any valid TCP port.
	6. Implementation Guidelines		6. Implementation Guidelines
	This document describes an Internet protocol. Terms are defined in		This document describes an Internet protocol.
	[10].
	6.1. Server Implementations		6.1. Server Implementations
	The server MUST be capable of recognizing all the mandatory attribute		The server MUST be capable of recognizing all the mandatory attribute
	type names and implement the syntaxes specified in [5]. Servers MAY		type names and implement the syntaxes specified in [5]. Servers MAY
	also recognize additional attribute type names.		also recognize additional attribute type names.
	6.2. Client Implementations		6.2. Client Implementations
	Clients which request referrals MUST ensure that they do not loop		Clients which request referrals MUST ensure that they do not loop
	skipping to change at page 35, line 54 ¶		skipping to change at page 35, line 54 ¶
	[1] ITU-T Rec. X.500, "The Directory: Overview of Concepts, Models and		[1] ITU-T Rec. X.500, "The Directory: Overview of Concepts, Models and
	Service", 1993.		Service", 1993.
	[2] W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access		[2] W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access
	Protocol", RFC 1777, March 1995.		Protocol", RFC 1777, March 1995.
	[3] ITU-T Rec. X.680, "Abstract Syntax Notation One (ASN.1) -		[3] ITU-T Rec. X.680, "Abstract Syntax Notation One (ASN.1) -
	Specification of Basic Notation", 1994.		Specification of Basic Notation", 1994.
	[4] S. Kille, M. Wahl, "A UTF-8 String Representation of Distinguished		[4] S. Kille, M. Wahl, "A UTF-8 String Representation of Distinguished
	Names", INTERNET-DRAFT <draft-ietf-asid-ldapv3-dn-03.txt>.		Names", INTERNET-DRAFT <draft-ietf-asid-ldapv3-dn-04.txt>.
	[5] M. Wahl, A. Coulbeck, T. Howes, S. Kille, W. Yeong, C. Robbins,		[5] M. Wahl, A. Coulbeck, T. Howes, S. Kille, W. Yeong, C. Robbins,
	"Lightweight Directory Access Protocol Attribute Syntax		"Lightweight Directory Access Protocol Attribute Syntax
	Definitions", INTERNET-DRAFT		Definitions", INTERNET-DRAFT
	<draft-ietf-asid-ldapv3-attributes-08.txt>, Oct. 1997.		<draft-ietf-asid-ldapv3-attributes-08.txt>, Oct. 1997.
	[6] ITU-T Rec. X.501, "The Directory: Models", 1993.		[6] ITU-T Rec. X.501, "The Directory: Models", 1993.
	[7] T. Berners-Lee, L. Masinter, M. McCahill, "Uniform Resource		[7] T. Berners-Lee, L. Masinter, M. McCahill, "Uniform Resource
	Locators (URL)", RFC 1738, Dec. 1994.		Locators (URL)", RFC 1738, Dec. 1994.
End of changes. 5 change blocks.
	5 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/