Approach for identifying different schemas in effect across a Directory Name-space
draft-hahn-schemapart-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Timothy Hahn | ||
| Last updated | 2001-07-10 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-hahn-schemapart-00.txt
Abstract
IETF RFC 2251 [RFC2251] provides a mechanism for indicating, given any particular entry in the directory tree, what entry in the directory tree holds the directory schema information for that particular entry. RFC 2251 does not, however, provide guidance on how different directory servers, each of which might have their own active directory schema, should “publicize” this directory schema such that the different active schemas are distinct from one another when viewing the entire directory name-space. This document describes a way to name sub-schema sub-entry entries such that different active schemas can be distinguished from one another across the entire directory name-space.
Authors
Timothy Hahn (hahnt@us.ibm.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)