Browse Prior Art Database

DIXIE Protocol Specification (RFC1249)

IP.com Disclosure Number: IPCOM000002065D
Original Publication Date: 1991-Aug-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 8 page(s) / 19K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Howes: AUTHOR [+3]

Abstract

OSI Directory Service defines a powerful mechanism for storing and retrieving information about objects, and for arranging those objects in a hierarchical structure. Many types of objects and information can be stored in The Directory, including white pages information, application information, service information, etc. The OSI protocol defined to allow access to this information is the Directory Access Protocol (DAP). The DAP, being an OSI application-layer program, is fairly heavy-weight and requires a substantial amount of computing power and coding investment to implement.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 16% of the total text.

Network Working Group T. Howes

Request for Comments: 1249 M. Smith

B. Beecher

University of Michigan

August 1991

DIXIE Protocol Specification

Status of this Memo

This RFC defines a mechanism by which TCP/UDP based clients can

access OSI Directory Service without the overhead of the ISO

transport and presentation protocols required to implement full-blown

DAP. This memo provides information for the Internet community. It

does not specify any standard. Distribution of this memo is

unlimited.

Table of Contents

1. Introduction .............................................. 2

1.1 History .................................................. 2

2. Protocol .................................................. 2

2.1 Header ................................................... 3

2.2 Operations ............................................... 4

2.2.1 Read ................................................... 4

2.2.1.1 Read Request ......................................... 4

2.2.1.2 Read Reply ........................................... 4

2.2.2 Search ................................................. 5

2.2.2.1 Search Request ....................................... 5

2.2.2.2 Search Reply ......................................... 5

2.2.3 List ................................................... 5

2.2.3.1 List Request ......................................... 5

2.2.3.2 List Reply ........................................... 5

2.2.4 Modify ................................................. 5

2.2.4.1 Modify Request ....................................... 6

2.2.4.2 Modify Reply ......................................... 6

2.2.5 Modify RDN ............................................. 6

2.2.5.1 Modify RDN Request ................................... 6

2.2.5.2 Modify RDN Reply ..................................... 6

2.2.6 Add .................................................... 6

2.2.6.1 Add Request .......................................... 7

2.2.6.2 Add Reply ............................................ 7

2.2.7 Remove ................................................. 7

2.2.7.1 Remove Request ....................................... 7

2.2.7.2 Remove Reply ......................................... 7

2.2.8 Bind ................................................... 7

2.2.8.1 Bind Request ......................................... 7

2.2.8.2 Bind Reply ........................................... 8

2.3 Operation Code Summary ................................... 8

2.4 Return Code Summary ...................................... 8

3. References ................................................ 9

4. Available Implementation...