draft-ietf-svrloc-ldap-scheme-01.txt		draft-ietf-svrloc-ldap-scheme-02.txt
	Service Location Working Group Jonathan Wood		Service Location Working Group Jonathan Wood
	INTERNET DRAFT Roberto Tam		INTERNET DRAFT Roberto Tam
	Sun Microsystems, Inc.		Sun Microsystems, Inc.
	21 February 1998
	The LDAP Service Type		The LDAP Service Type
	draft-ieft-svrloc-ldap-scheme-01.txt		draft-ieft-svrloc-ldap-scheme-02.txt
	Status of This Memo		Status of This Memo
	This document is a submission by the Service Location Working Group		This document is a submission by the Service Location Working Group
	of the Internet Engineering Task Force (IETF). Comments should be		of the Internet Engineering Task Force (IETF). Comments should be
	submitted to the srvloc@srvloc.org mailing list.		submitted to the srvloc@srvloc.org mailing list.
	Distribution of this memo is unlimited.		Distribution of this memo is unlimited.
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	skipping to change at page 3, line 17		skipping to change at page 3, line 17
	attributes are meant to be fluid, following the decisions of their		attributes are meant to be fluid, following the decisions of their
	respective working groups.		respective working groups.
	3. The LDAP Service Type		3. The LDAP Service Type
	Names of submitters: Jonathan Wood <jonathan.wood@eng.sun.com>		Names of submitters: Jonathan Wood <jonathan.wood@eng.sun.com>
	Roberto Tam <roberto.tam@eng.sun.com>		Roberto Tam <roberto.tam@eng.sun.com>
	Language of service template: en		Language of service template: en
	Security Considerations:		Security Considerations:
	This LDAP service type inherits the security considerations from the		This LDAP service type inherits the security considerations from the
	naming-directory service type [4].		naming-directory service type [4], the SLP specification [1].
			Implementors should also be aware of the security considerations
			discussed in [5].
	Template text:		Template text:
	-------------------------template begins here-----------------------		-------------------------template begins here-----------------------
	template-type=naming-directory:ldap		template-type=naming-directory:ldap
	template-version=0.0		template-version=0.0
	template-description=		template-description=
	This is a concrete type; the abstract type for this service		This is a concrete type; the abstract type for this service
	is naming-directory (described in [4]). This type is used		is naming-directory (described in [4]). This type is used
	skipping to change at page 4, line 19		skipping to change at page 4, line 21
	# be guaranteed), and privacy (meaning that the message is		# be guaranteed), and privacy (meaning that the message is
	# encrypted).		# encrypted).
	none,integrity,privacy		none,integrity,privacy
	transport= string		transport= string
	# the transport used to communicate with this server. Possible		# the transport used to communicate with this server. Possible
	# values are connection-oriented (cots) and connectionless		# values are connection-oriented (cots) and connectionless
	# (clts).		# (clts).
	cots,clts		cots,clts
			version= string M
			# Which version(s) of LDAP this server supports. "v3" corresponds to
			# the protocol as defined by RFC 2251, and "v2" corresponds to the
			# protocol as defined by RFC 1777.
			v2,v3
			extensions= string M
			# This is an open-ended attribute intended to contain any standard or
			# non-standard (i.e. vendor-specific) extensions this server supports.
	--------------------------template ends here------------------------		--------------------------template ends here------------------------
	References:		References:
	[1] E. Guttman, C. Perkins, J. Veizades, M. Day. Service Location		[1] E. Guttman, C. Perkins, J. Veizades, M. Day. Service Location
	Protocol. draft-ietf-svrloc-protocol-v2-12.txt, February 1999
	(work in progress)
	[2] E. Guttman, C. Perkins, J. Kempf, Service Templates and service:		[2] E. Guttman, C. Perkins, J. Kempf, Service Templates and service:
	Schemes. draft-ietf-svrloc-service-scheme-14.txt		Schemes. RFC 2609, February 1999
	February 1999 (work in progress)
	[3] W. Yeong, T. Howes, S. Kille, Lightweight Directory Access		[3] W. Yeong, T. Howes, S. Kille, Lightweight Directory Access
	[4] J. Wood, R. Tam, The Naming and Directory Service Abstract Type.		[4] J. Wood, R. Tam, The Naming and Directory Service Abstract Type.
	draft-ietf-svrloc-naming-directory-00.txt, November 1998 (work in		draft-ietf-svrloc-naming-directory-01.txt, June 1999 (work in
	progress)		progress)
	[5] M. Wahl, H. Alvestrand, J. Hodges, RL Morgan. Authentication		[5] M. Wahl, H. Alvestrand, J. Hodges, RL Morgan. Authentication
	Methods for LDAP, draft-ietf-ldapext-authmeth-03.txt, November		Methods for LDAP, draft-ietf-ldapext-authmeth-04.txt, November
	1998 (work in progress)		1998 (work in progress)
	[6] J. Meyers, Simple Authentication and Security Layer (SASL)		[6] J. Meyers, Simple Authentication and Security Layer (SASL)
	RFC 2222 October 1997		RFC 2222 October 1997
	[7] J. Linn, Generic Security Service Application Program Interface,		[7] J. Linn, Generic Security Service Application Program Interface,
	Version 2, RFC 2078 January 1997		Version 2, RFC 2078 January 1997
	[8] E. Baize, D. Pinkas, The Simple and Protected GSS-API Negotiation		[8] E. Baize, D. Pinkas, The Simple and Protected GSS-API Negotiation
	Mechanism, RFC 2478 December 1998		Mechanism, RFC 2478 December 1998
	[9] T. Howes, M. Smith, The LDAP URL Format, RFC 2255 December 1997		[9] T. Howes, M. Smith, The LDAP URL Format, RFC 2255 December 1997
End of changes. 9 change blocks.
	11 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/