Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Connection-less Lightweight X.500 Directory Access Protocol (RFC1798)

IP.com Disclosure Number: IPCOM000004052D
Original Publication Date: 1995-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 7 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Young: AUTHOR

Abstract

The Directory can be used as a repository for many kinds of information. The full power of DAP is unnecessary for applications that require simple read access to a few attribute values. Applications addressing is a good example of this type of use where an application entity needs to determine the Presentation Address (PA) of a peer entity given that peer's Application Entity Title (AET). If the AET is a Directory Name (DN) then the required result can be obtained from the PA attribute of the Directory entry identified by the AET. This is very similar to DNS.

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

Network Working Group A. Young

Request for Comments: 1798 ISODE Consortium

Category: Standards Track June 1995

Connection-less Lightweight X.500 Directory Access Protocol

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.

X.500

The protocol described in this document is designed to provide access

to the Directory while not incurring the resource requirements of the

Directory Access Protocol (DAP) [3]. In particular, it is aimed at

avoiding the elapsed time that is associated with connection-oriented

communication and it facilitates use of the Directory in a manner

analagous to the DNS [5,6]. It is specifically targeted at simple

lookup applications that require to read a small number of attribute

values from a single entry. It is intended to be a complement to DAP

and LDAP [4]. The protocol specification draws heavily on that of

LDAP.

1. Background

The Directory can be used as a repository for many kinds of

information. The full power of DAP is unnecessary for applications

that require simple read access to a few attribute values.

Applications addressing is a good example of this type of use where

an application entity needs to determine the Presentation Address

(PA) of a peer entity given that peer's Application Entity Title

(AET). If the AET is a Directory Name (DN) then the required result

can be obtained from the PA attribute of the Directory entry

identified by the AET. This is very similar to DNS.

Use of DAP to achieve this functionality involves a significant

number of network exchanges:

___________________________________________________________

|_#_|______Client_(DUA)________DAP________Server_(DSA)_____|

| 1| N-Connect.request -> |

| 2| <- N-Connect.response |

| 3| T-Connect.request -> |

| 4| <- T-Connect.response |

| | S-Connect.request, |

| | P-Connect.request, |

| | A-Associate.request, |

| 5| DAP-Bind.request -> |

| | ...