ITU-T X.501规范：开放系统互连目录模型

X.501

需积分: 31 59 浏览量更新于2024-07-18 收藏 1.01MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"X.501 规范是国际电信联盟(ITU)下属的电信标准化部门(ITU-T)制定的一项标准，它定义了开放系统互连(OSI)模型中的目录结构和模型。此规范在1993年11月更新，已被后来的版本所取代。X.501主要关注数据网络和开放系统的通信，在信息技术领域中，它为开放系统间的互联提供了目录模型。" X.501 规范是信息技术领域的一个关键组成部分，它在开放系统互连参考模型中扮演着重要角色。OSI模型是一个七层架构，用于标准化不同计算机系统之间的通信。X.501特别聚焦于模型的第7层——应用层，这一层涉及到用户和网络服务的接口，以及包括目录服务在内的各种高层应用。目录服务是X.501的核心，它允许网络中的系统和用户查找、访问和管理信息。这些服务基于一个层次化的、可扩展的命名系统，使得任何网络资源（如用户、服务器、打印机等）都可以通过一个唯一的名称来识别和定位。X.501定义了如何组织和表示这些资源，以及如何进行查询和更新操作，确保了跨组织和跨平台的互操作性。 X.501中的模型不仅仅是关于数据存储，还涉及到访问控制、安全性、隐私和管理方面。它定义了一种标准的语言和协议，即 Lightweight Directory Access Protocol (LDAP)，用于与目录服务器进行交互。LDAP允许快速、高效地搜索和管理大量分布式的数据，这对于大型企业或组织的网络管理至关重要。此标准的更新和替代意味着随着技术的发展，对目录服务的需求和实现方式也在不断演变。新的版本可能包含了性能提升、安全增强或新功能的添加，以适应不断变化的网络环境和用户需求。参与制定ITU-T推荐标准的实体广泛，包括来自179个成员国的电信运营实体、科研和工业组织以及38个国际组织。这些推荐标准的批准过程遵循WTSC决议，并且每隔四年，世界电信标准化会议(WTSC)会进行审议和更新，确保全球电信标准的与时俱进。 X.501规范是构建和管理网络目录服务的基础，它的存在促进了信息的共享和通信的效率，为开放系统环境中的协作提供了强大的支持。虽然已经被更新的版本取代，但其在理解和实施现代目录服务时仍然具有重要的历史价值和理论指导意义。

资源详情

资源推荐

Superseded by a more recent version ISO/IEC 9594-2 : 1995 (E)

4 ITU-T Rec. X.501 (1993 E) Superseded by a more recent version

4 Abbreviations

ACDF Access Control Decision Function

ACI Access Control Information

ACIA Access Control Inner Area

ACSA Access Control Specific Area

ADDMD Administration Directory Management Domain

ASN.1 Abstract Syntax Notation 1

AVA attribute value assertion

BER (ASN.1) Basic Encoding Rules

DACD Directory Access Control Domain

DAP Directory Access Protocol

DIB Directory Information Base

DISP Directory Information Shadow Protocol

DIT Directory Information Tree

DMD Directory Management Domain

DMO Domain Management Organization

DOP Directory Operational Binding Management Protocol

DSA Directory System Agent

DSE DSA-Specific Entry

DSP Directory System Protocol

DUA Directory User Agent

HOB Hierarchical Operational Binding

NHOB Non-specific Hierarchical Operational Binding

NSSR Non-Specific Subordinate Reference

PRDMD Private Directory Management Domain

RHOB Relevant Hierarchical Operational Binding (i.e. either a HOB or NHOB, as appropriate)

RDN Relative Distinguished Name

SDSE Shadowed DSE

5 Conventions

With minor exceptions this Directory Specification has been prepared according to the “Presentation of ITU-T/ISO/IEC

common text” guidelines in the Guide for ITU-T and ISO/IEC JTC 1 Cooperation, March 1993.

The term “Directory Specification” (as in “this Directory Specification”) shall be taken to mean ITU-T Rec. X.501 |

ISO/IEC 9594-2. The term “Directory Specifications” shall be taken to mean the X.500-Series Recommendations and all

parts of ISO/IEC 9594.

This Directory Specification uses the term “1988 edition systems” to refer to systems conforming to the previous (1988)

edition of the Directory Specifications, i.e. the 1988 edition of the series of ITU-T X.500 Recommendations and the

ISO/IEC 9594:1990 edition. Systems conforming to the current Directory Specifications are referred to as “1993 edition

systems”.

Superseded by a more recent version ISO/IEC 9594-2 : 1995 (E)

Recommendation X.501 (11/93) Superseded by a more recent version 5

SECTION 2 – OVERVIEW OF THE DIRECTORY MODELS

6 Directory Models

6.1 Definitions

For the purposes of this Directory Specification, the following definitions apply:

6.1.1 administrative authority: An agent of the Domain Management Organization concerned with various aspects

of Directory administration. The term administrative authority (in lower case) refers to the power vested in an

Administrative Authority by the Domain Management Organization to execute policy.

6.1.2 administration directory management domain (ADDMD): A DMD which is managed by an

Administration.

NOTE 1 – The term Administration denotes a public telecommunications administration or other organization offering

public telecommunications services.

6.1.3 directory administrative and operational information: Information used by the Directory for administrative

and operational purposes.

6.1.4 DIT domain: That part of the global DIT held by the DSAs- forming a DMD.

6.1.5 directory management domain (DMD): A set of one or more DSAs and zero or more DUAs managed by a

single organization.

6.1.6 domain management organization: An organization that manages a DMD (and the associated DIT Domain).

6.1.7 directory user information: Information of interest to users and their applications.

6.1.8 directory system agent (DSA): An OSI application process which is part of the Directory.

6.1.9 (directory) user: The end user of the Directory, i.e. the entity or person which accesses the Directory.

6.1.10 directory user agent (DUA): An OSI application process which represents a user in accessing the Directory.

NOTE 2 – DUAs may also provide a range of local facilities to assist users compose queries and interpret the responses.

6.1.11 private directory management domain (PRDMD): A DMD which is managed by an organization other than

an Administration.

6.2 The Directory and its Users

The Directory is a repository of information. This repository is known as the Directory Information Base (DIB).

Directory services provided to users are concerned with various kinds of access to this information.

The services provided by the Directory are defined in ITU-T Rec. X.511 | ISO/IEC 9594-3.

A Directory user (e.g. a person or an application-process) obtains Directory services by accessing the Directory. More

precisely, a Directory User Agent (DUA) actually accesses the Directory and interacts with it to obtain the service on

behalf of a particular user. The Directory provides one or more access points at which such accesses can take place.

These concepts are illustrated in Figure 1.

A DUA is manifested as an application-process. In any instance of communication each DUA represents precisely one

directory user.

The Directory is manifested as a set of one or more application-processes known as Directory System Agents (DSAs),

each of which provides one or more of the access points. For a more detailed description of DSAs see 17.2.

NOTES

1 Some open systems may provide a centralized DUA function retrieving information for the actual users (application-

processes, persons, etc.). This is transparent to the Directory.

2 The DUA functions and a DSA can be within the same open system, and it is an implementation choice whether to

make one or more DUAs visible within the OSI Environment as application-entities.

DUA may exhibit local behavior and structure which is outside the scope of envisaged Directory Specifications For

example, a DUA which represents a human directory user may provide a range of local facilities to assist its user to compose queries

and interpret the responses.

Superseded by a more recent version ISO/IEC 9594-2 : 1995 (E)

6 ITU-T Rec. X.501 (1993 E) Superseded by a more recent version

TISO3220-94/d01

Directory

user

DUA

Access Point

The Directory

Figure 1 – Access to the Directory

FIGURE 1/X.501...[D01] = 7 CM

6.3 Directory and DSA Information Models

6.3.1 Generic Models

Directory information may be classified as either:

– user information, placed in the Directory by, or on behalf of, users; and subsequently administered by, or

on behalf of, users. Section 3 provides a model of this information, or;

– administrative and operational information, held by the Directory to meet various administrative and

operational requirements. Section 5 provides a model of this information. Also provided in Section 5 is a

specification of the relationship between the user, administrative and operational information models.

These models, presenting views of the DIB from different perspectives, are referred to as the generic Directory

Information Models.

Directory information models describe how the Directory as a whole represents information. The composition of the

Directory as a set of potentially cooperating DSAs is abstracted from the model. The DSA information model, on the

other hand, is especially concerned with DSAs and the information that must be held by DSAs in order that the set of

DSAs comprising the Directory may together realize the Directory information model. The DSA Information Model is

provided in clauses 18 through 20.

The DSA information model is a generic model describing the information held by DSAs and the relationship between

this information and the DIB and DIT.

Some, but not all, of the information represented by the DSA information model is accessible via the Directory abstract

service. Therefore, administration of all of the information described in these Directory Specifications is not possible via

the Directory abstract service. It is envisioned that administration of DSA information will initially be a local matter, but

that eventually some generic system management service will be employed to provide access to all of the information

described in the DSA information model.

6.3.2 Specific Information Models

Subsequent to the development of generic models for the Directory as a whole and for its components, specific

information models are required for the standardisation of particular aspects of the operation of the Directory and its

components.

The generic Directory Information Models establish a framework for the following specific information models:

– an access control information model;

– a subschema information model;

– a collective attribute information model.

The generic DSA Information Model in turn establishes a framework for the following specific information models:

– a model for a DSA’s distribution knowledge;

– a model for a DSA’s replication knowledge.

Superseded by a more recent version ISO/IEC 9594-2 : 1995 (E)

Recommendation X.501 (11/93) Superseded by a more recent version 7

6.4 Directory Administrative Authority Model

A Directory Management Domain (DMD) is a set of one or more DSAs and zero or more DUAs managed by a single

organization.

That part of the global DIT held by (the DSAs forming) a DMD is referred to as a DIT Domain. There is a one to one

correspondence between DMDs and DIT Domains. The term DMD is used when referring to the management of the

functional components of the Directory. The term DIT Domain is used when referring to the management of Directory

Information. Two important points regarding this terminology are:

– A DIT Domain consists of one or more disjoint subtrees of the DIT (see 10.5). A DIT Domain shall not

contain the root of the global DIT.

– The term DMD may also be used as a general term when both aspects of management are considered

together.

An organization that manages a DMD (and the associated DIT Domain) is referred to as a Domain Management

Organization (DMO).

NOTE – A DMO may be an Administration (i.e. a public telecommunications administration or other organization offering

public telecommunications services) in which case the managed DMD is said to be an Administration DMD (ADDMD); otherwise it

is a Private DMD (PRDMD). It should be recognized that the provision of support for private directory systems by ITU-T members

falls within the framework of national regulations. Thus, the technical possibilities described may or may not be offered by an

Administration which provides directory services. The internal operation and configuration of private DMDs is not within the scope of

envisaged Directory Specifications.

Figure 2 illustrates the relationship between a DMO, DMD and DIT Domain.

TISO3230-94/d02

Domain Management Organization

Manages

DIT Domain

DMD

DUA

DSA

DUA

Figure 2 – Directory Management

FIGURE 2/X.501...[D02] = 9 CM

Management of a DUA by a DMO implies an ongoing responsibility for service to that DUA, e.g. maintenance, or in

some cases ownership, by the DMO. The DMO may or may not elect to make use of the Directory Specifications to

govern any interactions among DUAs and DSAs which are wholly within the DMD.

An agent of a DMO concerned with various aspects of Directory administration is referred to as an Administrative

Authority. The term administrative authority (in lower case) refers to the power vested in an Administrative Authority by

a DMO to execute policy.

NOTE – A Directory Administrative Authority Model is specified in Section 4.

Superseded by a more recent version ISO/IEC 9594-2 : 1995 (E)

8 ITU-T Rec. X.501 (1993 E) Superseded by a more recent version

SECTION 3 – MODEL OF DIRECTORY USER INFORMATION

7 Directory Information Base

7.1 Definitions

For the purposes of this Directory Specification, the following definitions apply:

7.1.1 alias entry: An entry of the class “alias” containing information used to provide an alternative name for an

object or alias entry.

7.1.2 direct superclass: Relative to a subclass – an object class from which the subclass is directly derived.

7.1.3 directory information base (DIB): The complete set of information to which the Directory provides access,

and which includes all of the pieces of information which can be read or manipulated using the operations of the

Directory.

7.1.4 directory information tree (DIT): The DIB considered as a tree, whose vertices (other than the root) are the

Directory entries.

NOTE – The term DIT is used instead of DIB only in contexts where the tree structure of the information is relevant.

7.1.5 (directory) entry: A named collection of information within the DIB. The DIB is composed of entries.

7.1.6 immediate superior (noun): Relative to a particular entry or object (it shall be clear from the context which is

intended), the immediately superior entry or object.

7.1.7 immediately superior

7.1.8 (entry): Relative to a particular entry – an entry which is at the initial vertex of an arc in the DIT whose final

vertex is that of the particular entry.

7.1.9 (object): Relative to a particular object – an object whose object entry is the immediate superior of any of the

entries (object or alias) for the second object.

7.1.10 object (of interest): Anything in some ‘world’, generally the world of telecommunications and information

processing or some part thereof, which is identifiable (can be named), and which it is of interest to hold information on

in the DIB.

7.1.11 object class: An identified family of objects (or conceivable objects) which share certain characteristics.

7.1.12 object entry: An entry which is the primary collection of information in the DIB about an object, and which

can therefore be said to represent that object in the DIB.

7.1.13 subclass: Relative to one or more superclasses – an object class derived from one or more superclasses. The

members of the subclass share all the characteristics of the super classes and additional characteristics possessed by none

of the members of those superclasses.

7.1.14 subordinate: The converse of superior.

7.1.15 superclass: Relative to a subclass – a direct superclass, or superclass to an object class that is a direct

superclass (recursively).

7.1.16 superior: (Applying to entry or object) immediately superior, or superior to one which is immediately superior

(recursively).

7.2 Objects

The purpose of the Directory is to hold, and provide access to, information about objects of interest (objects) which exist

in some ‘world’. An object can be anything in that world which is identifiable (can be named).

NOTES

1 The ‘world’ is generally that of telecommunications and information processing or some part thereof.

2 The objects known to the Directory may not correspond exactly with the set of ‘real’ things in the world. For

example, a real-world person may be regarded as two different objects, a business person and a residential person, as far as the

Directory is concerned. The mapping is not defined in this Directory Specification, but is a matter for the users and providers of the

Directory in the context of their applications.

剩余164页未读，继续阅读

ccjingbao2008

粉丝: 4
资源: 9

ITU-T X.501规范：开放系统互连目录模型

R15 33501中文版 5G 系统安全架构和过程.pdf

无线局域网设备名称规范.doc

select x from JadGovunitauditEntity x where x.agrunit.id = ? and x.gstype = ? and x.deleted = 0 and x.task.deleted = 0 order by x.id desc

分别以255.255.255.192 和255.255.255.240 为掩码时，以下IP 地址 X.Y.Z.0，X.Y.Z.8，X.Y.Z.15，X.Y.Z.31，X.Y.Z.96 哪些是子网地址？哪些是子网广播地址？哪些是主机地址？

python中'x.sbp','x.tobacco','x.ldl','x.adiposity','x.famhist','x.typea','x.obesity','x.alcohol','x.age'决策树特征重要性怎么判断

fbgrab-x.x.x.tar.gz

python编写一个计算器计算网段如输入x.x.x.x/x输出为x.x.x.x-x.x.x.x输的形式,x为0-255

x = x.view(x.shape[0], x.shape[1], x.shape[2] * x.shape[3])

x = x.reshape(x.shape[0], x.shape[1], x.shape[2] * x.shape[3]).permute(2, 0, 1)

public Key getparent(Node x, Key key){ if (x==null){ return null; } if (x.left.key==key || x.right.key==key){ return x.key; } else if(x.key.compareTo(key)<0){ return getparent(x.left,key); } else if(x.key.compareTo(key)>0){ return getparent(x.right,key); } return null; }

# 输入特征值 x = np.array(['x.sbq':0 , 'x.tobacco':2.3 , 'x.ldl':3 , 'x.adiposity':0 , 'x.famhist':0 , 'x.typea':0 ,'x.obesity':0 ,'x.alcohol':0 ,'x.age':45]) # 使用随机森林分类器预测 pred = dec_rf.predict_proba(x)

ModiDruPra = @(x, y) sqrt(x.^2 - x.y + y.^2).... (1+(-0.2).*(6.sqrt(3).(x.^3+y.^3-6.*x.^2.*y-6.*x.y.^2))/(2.((x.^2+y.^2-x.*y)/3)^(3/2)))-5;旨在这段代码基础上增加容差

data.InWarehouseTasks = list.Select( x => new BigInOutScreenWarehouseTaskData("入库", GetWarehouseTaskTypeDisplayName(x.State), x.StartLocation, x.DestinationLocation,x.TraySerialNumber,x.CreationTime) ).ToList();请您为我修改成倒叙查询的方式

(1) 最小的子网掩码是多少？ (2) 分别以255.255.255.192 和255.255.255.240 为掩码时，以下IP 地址中 哪些是子网地址？哪些是子网广播地址？哪些是主机地址？ [ X.Y.Z.0，X.Y.Z.8，X.Y.Z.15，X.Y.Z.31，X.Y.Z.96 ]

bool cmp(node x, node y){ return x.x!=y.x? x.x<y.x : x.y<y.y; }这一句中的返回值x.x<y.x和x.y<y.y是数字还是别的什么

bool cmp(node x, node y){ return x.x!=y.x? x.x<y.x : x.y<y.y; }详细解释这一句

this.list.forEach((x)=> { if(this.map.has(x.regionName)){ const value = this.map.get(x.regionName) this.map.set(x.regionName,value,x.finalTotalAmount) }else{ this.map.set(x.regionName,x.finalTotalAmount) }是什么意思

[x, y] = meshgrid(-2:0.2:2); z = x .* exp(-x.^2 - y.^2);其中， x .* exp(-x.^2 - y.^2)的计算方法是设么

解决Duplicate class androidx.arch.core.executor.ArchTaskExecutor found in modules core-runtime-2.0.0-runtime.jar (androidx.arch.core:core-runtime:2.0.0) and jetified-androidx.arch.core.core-runtime-2.0.0-runtime.jar (:androidx.arch.core.core-runtime-2.0.0:)

最新资源

ModiDruPra = @(x, y) sqrt(x.^2 - x.y + y.^2).... (1+(-0.2).(6.sqrt(3).(x.^3+y.^3-6.x.^2.y-6.x.y.^2))/(2.((x.^2+y.^2-x.*y)/3)^(3/2)))-5;旨在这段代码基础上增加容差

(1) 最小的子网掩码是多少？ (2) 分别以255.255.255.192 和255.255.255.240 为掩码时，以下IP 地址中哪些是子网地址？哪些是子网广播地址？哪些是主机地址？ [ X.Y.Z.0，X.Y.Z.8，X.Y.Z.15，X.Y.Z.31，X.Y.Z.96 ]