Browse Prior Art Database

DHCP Options for Novell Directory Services (RFC2241)

IP.com Disclosure Number: IPCOM000002800D
Original Publication Date: 1997-Nov-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 5 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Provan: AUTHOR

Related Documents

10.17487/RFC2241: DOI

Abstract

This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 41% of the total text.

Network Working Group D. Provan Request for Comments: 2241 Novell, Inc. Category: Standards Track November 1997

DHCP Options for Novell Directory Services

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

Abstract

This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. The first option carries a list of NDS servers. The second option carries the name of the client’s NDS tree. The third carries the initial NDS context. These three options provide an NDS client with enough information to connect to an NDS tree without manual configuration of the client.

1. Introduction

Novell Directory Services is a distributed, replicated, hierarchical database of objects representing network resources such as nodes, services, users, and applications. An NDS client must be able to locate an NDS server in order to authenticate itself to the network and gain access to the database. In addition, the node’s user is better served if the NDS client’s attention is focused on the area of the NDS database likely to be of the most interest to the user. This specification describes DHCP options [1] that carry NDS information to TCP/IP clients of NDS. The first option, the NDS Servers Option, carries a list of NDS servers. The other two options, the NDS Tree Name Option and the NDS Context Option, provide the client with a default context within the NDS database.

Provan Standards Track [Page 1]

RFC 2241 DHCP Options November 1997

The NDS Tree Name Option and the NDS Context Option carry 16-bit Unicode text encoded into an octet stream using UTF-8 [4]. A complete DHCP implementation can represent of the entire Unicode character set supported by NDS. At the same time, 7-bit ASCII text is unchanged by the UTF-8 transformation. In environments where the NDS tree name and context are restricted to the range of 7-bit ASCII characters, ASCII- only DHCP clients and servers can support these options by using the ASCII text as the UTF-8 encoded data.

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 RFC 2119. [2]

2. NDS Servers Option

This option specifies one or more NDS servers for the client to contact for access to the NDS database. Servers SHOULD be listed in order of preference.

The code for this option is 85. The minimum length of this option is 4 octets, and the length MUST be a multiple of 4.

Code Len Address 1 Address 2 +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-- | 85...

Processing...
Loading...