1、CCITT RECHN*F-SOO 92 q8b257L 0575b89 227 INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE DI RECTORY SERVICE OPERATIONS AND DEFINITION OF SERVICE F.500 (08/92) INTERNATIONAL PUBLIC DIRECTORY SERVICES Recommendation F.500 CCITT RECMN*F*SOO 9
2、2 4862593 0575b90 TY9 FOREWOW I The CC (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union 0. CCTT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to
3、 standardiiing telecommunications on a worldwide basis. The Plenary Assembly of CC which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCiT between Plenary Assemblies is covered by
4、 the procedure laid down in CC Resolution No. 2 (Melbome, 1988). Recommendation F.500 was revised by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992. C3T NOTE In this Recommendation, the expression “Adminitration is used for conciseness to indicate both
5、a telecommunication administration and a recognized private operating ageacy. O IT 1993 Au rights reserved. No part of this publication may be reproduced or utilized in any fonn or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing Erom the IT
6、. Recommendation F.500 INTERNATIONAL PUBLIC DIRECTORY SERVICES (revised 1992) Given the rapid multiplication and expansion of CCIT-defined telecommunication services, there is a growing need for subscribers to these telecommunication services to be able to communicate with each other. In order to fa
7、cilitate such intercommunication for the subscribers of the various services, public directory services will be required. The CCIT, considering (a) that the CCITT-defined telecommunication services, including telegraphic, telematic and telephone services, have directory requirements; (b) that such r
8、equirements are being implemented as on-line electronic directories (in addition to traditional hard-copy versions); (c) that national initiatives are being taken to develop electronic integrated directories or service specific directories; (d) that the system definition is being underiaken by the C
9、CIT in the field of electronic directories in the X.500-Series of Recommendations, unanimously declares services. that the specifications of this Recommendation should be applied to the provision of public directory C0“rS 1 Introduction 2 Purpose and scope 3 Organizational provisions 4 Public direct
10、ory services 5 6 Character repertoire and languages 7 Display of a response 8 Operational issues 9 Quality of Service aspects 1 O References Annex A - Abbreviations Annex B - Service error messages Annex C - Selected object classes Annex D - Selected attribute types Annex E - MHS selected object cla
11、sses Names as the key to directory searches Recommendation F.500 (08/92) 1 CCITT RECMN*F*500 92 48b259L 0575b92 811 = Annex F - MHS selected attribute types Annex G - User visibility of the search operation Annex H - Glossary of terms 1 Introduction International public directory services will enabl
12、e subscribers to determine rapidly and easily what services are available and how to access and address their correspondents. Public directories may also be used internally by the various telecommunication services for the proper routing of calls or messages. However, this application of directory s
13、ystems is not covered by this Recommendation. Service specific directories may be implemented as part of a global directory service. Consistent with the need to make directory information as widely available as possible, it is anticipated that Administrations will aim to provide global electronic di
14、rectory services. In order to provide international public directory services, Administrations should mutually cooperate in handling inquiries for information across national boundaries. Public directory services should solve the primary problem of name to address association, e.g. obtaining a compa
15、nys telex number by querying the directory with the name of the company. The reverse question, Le., obtaining the name and other information from the address, may also be applicable in certain services and its provision is at the option of an Administration. Public directory services should include
16、directory information concerning the provision of services, service descriptions, operational instructions, tariff conditions, etc. Public directory services should make provision for accessing information without knowing the wune of the object sought, e.g., designating categories of goods, business
17、 areas or services. Advertising is included in the scope of public directory services, but is left to national implementations. Public directory services can be considered as supplementary to the services for which they provide information or by which they are accessed. Private directory services wh
18、ich are compliant with the public directory services defined in CCITT Recommendations may be permitted to intercommunicate with public directory services under national regulations. 2 Purpose and scope This Recommendation provides for the general framework for the provision of international public d
19、irectory services in accordance with and based on the Recommendations of XSOO-Series. It defines the requirements for and the service features associated with the provision of public directory services. It specifies naming aspects, describes operational issues to be taken into account in providing t
20、he public directory services as well as Quality of Service aspects. 3 Organizational provisions Provision of a public directory service will be done in accordance with the orgmizational model described in Recommendation X.501. An Administration directory management domain (ADDMD) is responsible for
21、the application of the basic service features and the optional user facilities provided in that domain. Directory management domains shall intercommunicate with each other as far as the provision of the public directory services requires it. The protocols to be used for interworking as well as the d
22、irectorys overall concept and behaviour, is described in the XSOO-Series of Recommendations. Note - ADDMDs will typically have (international) connections. 2 Recommendation F.500 (08/92) CCITT RECMN*FD500 92 W 48b259L 0575693 758 Private directory management domains (PRDMDs) may exist and intercommu
23、nicate with ADDMDs, following national regulations. A Directory management domain (DMD) consists of one or more directory system agents (DSAs) and zero or more directory user agents (DUAS). Each directory management domain may act as the naming authority for that domain. Names need to be unambiguous
24、. Note - The system specification assumes only one occurrence of an organization name under the country n is inappropriate. Contact support staff for assistance. Attribute Type is not defined for this . Inappropriate matching for the information type . Attribute Type or Attribute Value is not within
25、 its constraints. or already exists. B.2 Name error This will be displayed with one of tbe following reason values whenever a name provided by the user is detected to have a problem (see Table B-2F.500). I 2 3 The name supplied, , cannot be found. (Nore - Alias names are resolved to the actual named
26、 entry.) is an alias that can not be properly resolved. Part, , of be name used is undefined. Recommendation F.500 (08/92) 19 CCITT RECVN*F=SOO 92 48625?73 0575730 bb7 m B.3 Interconnect error This error will be displayed whenever the operation cannot be carried further at this time. The possible ac
27、cess points for continuing the request are provided in the form: ?name and access point?. B .4 Service error This will be displayed with one of the following reason values whenever the operation requested bas detected a problem that affects the user service (see Table B-3F.500). Reason value 1 2 3 4
28、 5 6 7 8 9 10 11 12 13 TAELE B-3F.500 Meaning The directory system is too busy to perform the request, but may be able to do so after a short while. The directory system is currently unavailable. The directory system is not prepared to execute this request, e.g. because it would lead to excessive co
29、nsumption of resources or violate the administrative authorily involved. The directory system is unable to accomplish the request other than by chaining, however chaining was prohibited by means of service control. The directory system is unable to accomplish the request due to the lack of appropria
30、te administrative authority for name resolution. The directory system is unable to perform the request as directed via OperationProgress by the DUA. The directory system has reached the limit of time set by the user in a service control. The directory system has reached some limit set by an administ
31、rative authority. The directory is unable to accomplish this request due to an internal loop. The directory is unable to satisfy the request because one or more critical extensions are not available. No referrals are available within the requested scope. The directory is unable to accomplish the req
32、uest due to a DIT consistency problem. The parameters of the requested operation are invalid. This problem is reported if the query- reference in paged result request is invalid. B.5 Update error This will be displayed with one of the following reason values whenever the modify (Add, Change, or Dele
33、te) operation(s) requested has detected a problem (see Table B-4F.500). 20 Recommendation F.500 (08192) CCITT RECMNtF-SOO 92 48b2591 0575711 5T3 Reason value 1 2 3 4 5 6 7 TABLE B-4E.500 Meaning The update violates directoiy naming rules. The update violates the directory rules for that class of obj
34、ect. Update not allowed because the object is not the leaf entry. Update not allowed because this affects the RDN. Entry already exists (relevant for add operation only). Update denied, affects multiple directory systems. Update not allowed because this modifies the object class attribute. Reason va
35、lue 1 2 .3 4 5 6 B.6 Securiv error This will be displayed with one of the following reason values whenever the operation requested has detected a problem for security reasons (see Table B-5F.500). Meaning The security level of the requester is inconsistent with the required level. The supplied crede
36、ntial is invalid. le requester does not have the right to cany out the operation. The signature of the requester is invalid. The request is not carried out because the argument is not signed. The request is not carried out by a security error without indicating any information. Reason value 1 2 3 B.
37、7 Abandon error Meaning The directory has no knowledge of the operation to be abandoned. The operation has already responded. The attempt is prohibited or cannot be performed. This will be displayed with one of the foilowing reason values whenever the abandon operation requested has detected a probl
38、em (see Table B.6F.500). Recommendation F.500 (08/92) 21 CCITT RECNN*F*SOO 92 m 48b259L 0575732 43T B.8 Referrul error For further study. ANNEX C (to Recommenation F.500) Selected object classes See Recommendation X.521 (1988). Object identifiers are allocated to object classes. The concept makes us
39、e of the concept of subclasses (see Recommendation X.501) (1988). Selected object classes provided by the directory systems specifications depend on the scope of public directory service chosen by the service provider. It is assumed that the presently defined selected object classes will ailow the p
40、rovision of a useful directory service. - TOP - Alias - Country - Locality - Organization - Organizational unit - Person - Organizational person - Organizational role - Group of names - Residential person - Application entity - Application process - DSA - Device - Strong authentication user - Certif
41、ication authority Note I - A certain object class is used as a classificatory attribute type. Note 2 - The definition of additional selected object classes for public directory service is for further study. Note 3 - Messaging handling, in XA-Series of Recommendations (1988), defined additional objec
42、t classes for message handling system (MHS) specific use (see Anne E). 22 Recommendation F.500 (08/92) CCITT RECHN*F.SOO 92 4862593 0575733 376 ANNEX D (to Recommendation F.500) Selected attribute types It is assumed that the presently defined selected attribute types will provide a useful directory
43、 service. The implementation of the attribute types used in the public directory service are left for the decision of the service provider. Selected attribute types provided by the directory system specification, Recommendation X.520 (1988), are: a) System attribute types - Aliased object name - Kno
44、wledge information - Object class b) Labelling attribute types - Commonname - Serialnumber - Surname c) Geogruphical uttribute types - Countryname - Localityname - State or province name - Street address d) Organizational attribute types - Organization name - Organizational unit name - Title e) Eqla
45、natory attribute types - Business category - Description - Searchguide f) Postal attributes - Physical delivery office name - Post office box - Postal address - Postalcode - Registered address g) Telecommunications addressing attribute types - Destination indicator - Facsimile telephone number - ISD
46、N address - Registered address - Telephone number - Teletex terminai identifier - Telex number - X.121 address Recommendation F.500 (08/92) 23 CCITT RECMN+F.SOO 72 m 4862573 0575734 202 m h) Preferences attribute types - Preferred delivery method i) OSI application attribute types - Presentation add
47、ress - Supported application context j) Relational attribute types - Member - Owner - Role occupant - Seealso k) Security attribute types - User password - User certificate - Authority revocation list - Certificate revocation lise - Certification authority (CA) certificate Note 1 - Other attribute t
48、ypes may be defined for local scope or on bilateral agreement. Note 2 - The definition of additional selected attribute types for public directory services is for further study. Note 3 - Messaging handling, in Recommendation X.402, defined additional attribute types for MHS specific use (see Annex F
49、). ANNEX E (to Recommendation F.500) MHS selected object classes See Recommendation X.402 (1988) for further details. Selected object classes provided by the directory systems for MHS depend on the scope of the public directory service chosen by the service provider. It is assumed that the presently defined selected MHS object classes will allow the provision of a useful directory service that intercommunicates well with MHS as defined in the X.400- Series of Recommendations (1988). MHS object classes - - MHS organizational user - MHS distribution list - MHS messa
