Browse Prior Art Database

Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories (RFC3296)

IP.com Disclosure Number: IPCOM000009216D
Original Publication Date: 2002-Jul-01
Included in the Prior Art Database: 2002-Aug-13
Document File: 15 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Zeilenga: AUTHOR

Abstract

This document details schema and protocol elements for representing and managing named subordinate references in Lightweight Directory Access Protocol (LDAP) Directories.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group                                        K. Zeilenga

Request for Comments: 3296                           OpenLDAP Foundation

Category: Standards Track                                      July 2002

                    Named Subordinate References in

        Lightweight Directory Access Protocol (LDAP) Directories

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document details schema and protocol elements for representing

   and managing named subordinate references in Lightweight Directory

   Access Protocol (LDAP) Directories.

Conventions

   Schema definitions are provided using LDAPv3 description formats

   [RFC2252].  Definitions provided here are formatted (line wrapped)

   for readability.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" used in

   this document are to be interpreted as described in BCP 14 [RFC2119].

1.  Background and Intended Usage

   The broadening of interest in LDAP (Lightweight Directory Access

   Protocol) [RFC2251] directories beyond their use as front ends to

   X.500 [X.500] directories has created a need to represent knowledge

   information in a more general way.  Knowledge information is

   information about one or more servers maintained in another server,

   used to link servers and services together.

   This document details schema and protocol elements for representing

   and manipulating named subordinate references in LDAP directories.  A

   referral object is used to hold subordinate reference information in

Zeilenga                    Standards Track                     [Page 1]

RFC 3296    Named Subordinate References in LDAP Directories   July 2002

   the directory.  These referral objects hold one or more URIs

   [RFC2396] contained in values of the ref attribute type and are used

   to generate protocol referrals and continuations.

   A control, ManageDsaIT, is defined to allow manipulation of referral

   and other special objects as normal objects.  As the name of control

   implies, it is intended to be analogous to the ManageDsaIT service

   option described in X.511(97) [X.511].

   Other forms of knowledge information are not detailed by this

   document.  These forms may be described in subsequent documents.

   This document details subordinate referral processing requireme...