< draft-ietf-schema-ldap-00.txt		draft-ietf-schema-ldap-01.txt >
	Network Working Group M. Wahl		Network Working Group M. Wahl
	Request for Comments: DRAFT Critical Angle Inc.		Request for Comments: DRAFT Innosoft International, Inc.
	January 6, 1998		August 1, 1998
	MIME Directory Profile for LDAP Schema		MIME Directory Profile for LDAP Schema
	<draft-ietf-schema-ldap-00.txt>		<draft-ietf-schema-ldap-01.txt>
	1. Status of this Memo		1. Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are working docu-		This document is an Internet-Draft. Internet-Drafts are working docu-
	ments of the Internet Engineering Task Force (IETF), its areas, and its		ments of the Internet Engineering Task Force (IETF), its areas, and its
	working groups. Note that other groups may also distribute working		working groups. Note that other groups may also distribute working
	documents as Internet-Drafts.		documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference material		time. It is inappropriate to use Internet-Drafts as reference material
	or to cite them other than as ``work in progress.''		or to cite them other than as ``work in progress.''
	To learn the current status of any Internet-Draft, please check the		To view the entire list of current Internet-Drafts, please check
	``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow		the "1id-abstracts.txt" listing contained in the Internet-Drafts
	Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),		Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
	munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or		(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au
	ftp.isi.edu (US West Coast).		(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu.
	2. Abstract		2. Abstract
	This document defines a MIME directory profile [1] for holding an		This document defines a MIME directory profile [1] for holding an
	LDAP [2] schema. It is intended for communication with the Internet		LDAP [2] schema. It is intended for communication with the Internet
	schema listing service.		schema listing service.
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
	this document are to be interpreted as described in RFC 2119 [4].		this document are to be interpreted as described in RFC 2119 [4].
	3. Overview		3. Overview
	This document defines how a MIME type may be used to transfer a		This document defines how a MIME type may be used to transfer a
	single LDAPv3 schema definition.		single LDAPv3 schema definition.
	A schema for use with LDAPv3 consists of any number of object class,		A schema for use with LDAPv3 consists of any number of object class,
	attribute type, matching rule and syntax definitions. These concepts		attribute type, matching rule and syntax definitions. These concepts
	are defined in the LDAPv3 protocol definition [2].		are defined in the LDAPv3 protocol definition [2]. The schema MAY
			have a numeric OID assigned to it by a schema listing or registration
	The schema may have a numeric OID assigned to it by a schema listing		service.
	or registration service.
	A schema may import definitions from another schema. Schema imports		A schema may import definitions from another schema. Schema imports
	are not, however, transitive.		are not, however, transitive.
	For example, a schema contains a definition for a "modem" object		For example, a schema contains a definition for a "modem" object
	class, which is to be defined as a subclass of the X.521 "device"		class, which is to be defined as a subclass of the X.521 "device"
	object class. In this case, the schema MUST import the definitions		object class. In this case, the schema MUST import the definitions
	of X.521.		of X.521.
	4. The "schema-ldap-0" MIME Directory Profile Registration		4. The "schema-ldap-0" MIME Directory Profile Registration
	skipping to change at page 6, line 41 ¶		skipping to change at page 6, line 41 ¶
	[3] "Lightweight Directory Access Protocol (v3): Attribute Syntax		[3] "Lightweight Directory Access Protocol (v3): Attribute Syntax
	Definitions", Dec. 1997, RFC 2252.		Definitions", Dec. 1997, RFC 2252.
	[4] S. Bradner, "Key words for use in RFCs to Indicate Requirement		[4] S. Bradner, "Key words for use in RFCs to Indicate Requirement
	Levels", RFC 2119.		Levels", RFC 2119.
	9. Authors Address		9. Authors Address
	Mark Wahl		Mark Wahl
	Critical Angle Inc.		Innosoft International, Inc.
	4815 West Braker Lane #502-385		8911 Capital of Texas Hwy Suite 4140
	Austin, TX 78759		Austin, TX 78759
	USA		USA
	Phone: +1 512 372-3160		EMail: M.Wahl@innosoft.com
	EMail: M.Wahl@critical-angle.com
	Appendix A		Appendix A
	This appendix defines two new attributes which could be present in		This appendix defines two new attributes which could be present in
	an subschema entry. These attributes could be added to a future		an subschema entry. These attributes could be added to a future
	revision of the LDAP attribute definition [3].		revision of the LDAP attribute definition [3].
	A.1. ldapSchemas attribute type definition		A.1. ldapSchemas attribute type definition
	( 1.3.6.1.4.1.1466.101.120.17 NAME 'ldapSchemas'		( 1.3.6.1.4.1.1466.101.120.17 NAME 'ldapSchemas'
End of changes. 7 change blocks.
	17 lines changed or deleted		14 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/