Browse Prior Art Database

Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security (RFC2830)

IP.com Disclosure Number: IPCOM000003429D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 14 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Hodges: AUTHOR [+3]

Abstract

This document defines the "Start Transport Layer Security (TLS) Operation" for LDAP [LDAPv3, TLS]. This operation provides for TLS establishment in an LDAP association and is defined in terms of an LDAP extended request.

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

Network Working Group J. Hodges

Request for Comments: 2830 Oblix Inc.

Category: Standards Track R. Morgan

Univ of Washington

M. Wahl

Sun Microsystems, Inc.

May 2000

Lightweight Directory Access Protocol (v3):

Extension for Transport Layer Security

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 (2000). All Rights Reserved.

Abstract

This document defines the "Start Transport Layer Security (TLS)

Operation" for LDAP [LDAPv3, TLS]. This operation provides for TLS

establishment in an LDAP association and is defined in terms of an

LDAP extended request.

1. Conventions Used in this Document

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

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

document are to be interpreted as described in [ReqsKeywords].

2. The Start TLS Request

This section describes the Start TLS extended request and extended

response themselves: how to form the request, the form of the

response, and enumerates the various result codes the client MUST be

prepared to handle.

The section following this one then describes how to sequence an

overall Start TLS Operation.

2.1. Requesting TLS Establishment

A client may perform a Start TLS operation by transmitting an LDAP

PDU containing an ExtendedRequest [LDAPv3] specifying the OID for the

Start TLS operation:

1.3.6.1.4.1.1466.20037

An LDAP ExtendedRequest is defined as follows:

ExtendedRequest ::= [APPLICATION 23] SEQUENCE {

requestName [0] LDAPOID,

requestValue [1] OCTET STRING OPTIONAL }

A Start TLS extended request is formed by setting the requestName

field to the OID string given above. The requestValue field is

absent. The client MUST NOT send any PDUs on this connection

following this request until it receives a Start TLS extended

response.

When a Start TLS ex...