Information technology — Open Systems Interconnection — The Directory: Authentication framework — Part 8: — Technical Corrigendum 5

Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — L'annuaire: Cadre d'authentification — Partie 8: — Rectificatif technique 5

General Information

Status

Withdrawn

Publication Date

04-Aug-2004

Withdrawal Date

04-Aug-2004

ICS

35.100.70 - Application layer

Technical Committee

ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems

Drafting Committee

ISO/IEC JTC 1/SC 6/WG 7 - Network, transport and future network

Current Stage

9599 - Withdrawal of International Standard

Completion Date

21-May-2007

Ref Project

Relations

Corrects

ISO/IEC 9594-8:1998 - Information technology — Open Systems Interconnection — The Directory: Authentication framework — Part 8:

Effective Date

06-Jun-2022

Child

ISO/IEC 9594-8:1998 - Information technology — Open Systems Interconnection — The Directory: Authentication framework — Part 8:

Effective Date

15-Apr-2008

Buy Standard

Standard

ISO/IEC 9594-8:1998/Cor 5:2004

English language

1 pages

sale 15% off

Preview

sale 15% off

Preview

Standard

ISO/IEC 9594-8:1998/Cor 5:2004

French language

1 pages

sale 15% off

Preview

sale 15% off

Preview

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 9594-8:1998/Cor.5:2004
TECHNICAL CORRIGENDUM 5
Published 2004-08-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE

Information technology — Open Systems Interconnection —
The Directory: Authentication framework
TECHNICAL CORRIGENDUM 5
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — L'annuaire: Cadre
d'authentification
RECTIFICATIF TECHNIQUE 5
Technical Corrigendum 5 to ISO/IEC 9594-8:1998 was prepared by Joint Technical Committee ISO/IEC
JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information exchange between
systems.

ICS 35.100.70 Ref. No. ISO/IEC 9594-8:1998/Cor.5:2004(E)
© ISO/IEC 2004 – All rights reserved
Published in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 9594-8:1998/Cor.5:2004 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
Information technology – Open Systems Interconnection –
The Directory: Authentication framework
Technical Corr
...

NORME INTERNATIONALE ISO/CEI 9594-8:1998
RECTIFICATIF TECHNIQUE 5
Publié 2004-08-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE

Technologies de l'information — Interconnexion de systèmes
ouverts (OSI) — L'annuaire: Cadre d'authentification
RECTIFICATIF TECHNIQUE 5
Information technology — Open Systems Interconnection — The Directory: Authentication framework
TECHNICAL CORRIGENDUM 5
Le Rectificatif technique 5 à l'ISO/CEI 9594-8:1998 a été élaboré par le comité technique mixte
ISO/CEI JTC 1, Technologies de l'information, sous-comité SC 6, Téléinformatique.

o
ICS 35.100.70 Réf. n ISO/CEI 9594-8:1998/Cor.5:2004(F)
© ISO/CEI 2004 – Tous droits réservés
Publié en Suisse

---------------------- Page: 1 ----------------------
ISO/CEI 9594-8:1998/Cor.5:2004 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
Technologies de l'information – Interconnexion
des systèmes ouverts – L'annuaire: cadre d'authentification
Corrigendum technique 5

Issu du projet de Corrigendum technique 12
(correction des erreurs signalées dans les rapports de défaut 291, 297 et 2
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO

ISO/IEC 9594-11:2020(Main)

Information technology — Open systems interconnection directory — Part 11: Protocol specifications for secure operations

The scope of this Recommendation | International Standard is threefold. This Recommendation | International Standard provides guidance on how to prepare new and old protocols for cryptographic algorithm migration, and defines auxiliary cryptographic algorithms to be used for migration purposes. This Recommendation | International Standard specifies a general wrapper protocol that provides authentication, integrity and confidentiality (encryption) protection for other protocols. This wrapper protocol includes a migration path for cryptographic algorithms allowing for smooth migration to stronger cryptographic algorithms as such requirements evolve. This will allow migration to quantum-safe cryptographic algorithms. Protected protocols can then be developed without taking security and cryptographic algorithms into consideration. This Recommendation | International Standard also includes some protocols to be protected by the wrapper protocol primarily for support of public-key infrastructure (PKI). Other specifications, e.g., Recommendations or International Standards, may also develop protocols designed to be protected by the wrapper protocol.

Standard
84 pages
English language
sale 15% off

ISO

ISO/IEC 9594-9:2020(Main)

Information technology — Open systems interconnection — Part 9: The Directory: Replication

This document specifies a shadow service which Directory system agents (DSAs) may use to replicate Directory information. The service allows Directory information to be replicated among DSAs to improve service to Directory users. The shadowed information is updated, using the defined protocol, thereby improving the service provided to users of the Directory.

Standard
38 pages
English language
sale 15% off
Standard
38 pages
English language
sale 15% off

ISO

ISO/IEC 9594-7:2020(Main)

Information technology — Open systems interconnection — Part 7: The Directory: Selected object classes

This document defines a number of object classes and name forms which may be found useful across a range of applications of the Directory. The definition of an object class involves listing a number of attribute types which are relevant to objects of that class. The definition of a name form involves naming the object class to which it applies and listing the attributes to be used in forming names for objects of that class. These definitions are used by the administrative authority which is responsible for the management of the directory information. Any administrative authority can define its own object classes or subclasses and name forms for any purpose. NOTE 1 ? Those definitions may or may not use the notation specified in Rec. ITU-T X.501 | ISO/IEC 9594-2. NOTE 2 ? It is recommended that an object class defined in this Recommendation | International Standard, or a subclass derived from one, or a name form defined in this Recommendation | International Standard, be used in preference to the generation of a new one, whenever the semantics is appropriate for the application. Administrative authorities may support some or all the selected object classes and name forms, and may also add additional ones. All administrative authorities shall support the object classes which the directory uses for its own purpose (the top, alias and Directory system agent (DSA) object classes).

Standard
30 pages
English language
sale 15% off
Standard
30 pages
English language
sale 15% off

ISO

ISO/IEC 9594-8:2020(Main)

Information technology — Open systems interconnection — Part 8: The Directory: Public-key and attribute certificate frameworks

This document addresses some of the security requirements in the areas of authentication and other security services through the provision of a set of frameworks upon which full services can be based. Specifically, this Recommendation | International Standard defines frameworks for: ? public-key certificates; and ? attribute certificates. The public-key certificate framework defined in this Recommendation | International Standard specifies the information objects and data types for a public-key infrastructure (PKI), including public-key certificates, certificate revocation lists (CRLs), trust broker and authorization and validation lists (AVLs). The attribute certificate framework specifies the information objects and data types for a privilege management infrastructure (PMI), including attribute certificates, and attribute certificate revocation lists (ACRLs). This Recommendation | International Standard also provides the framework for issuing, managing, using and revoking certificates. An extensibility mechanism is included in the defined formats for both certificate types and for all revocation list schemes. This Recommendation | International Standard also includes a set of extensions, which is expected to be generally useful across a number of applications of PKI and PMI. The schema components (including object classes, attribute types and matching rules) for storing PKI and PMI information in a directory, are included in this Recommendation | International Standard. This Recommendation | International Standard specifies the framework for strong authentication, involving credentials formed using cryptographic techniques. It is not intended to establish this as a general framework for authentication, but it can be of general use for applications which consider these techniques adequate. Authentication (and other security services) can only be provided within the context of a defined security policy. It is a matter for users of an application to define their own security policy.

Standard
224 pages
English language
sale 15% off
Standard
224 pages
English language
sale 15% off

ISO

ISO/IEC 9594-1:2020(Main)

Information technology — Open systems interconnection — Part 1: The Directory: Overview of concepts, models and services

This document provides the directory capabilities required by many application layer standards and telecommunication services. Among the capabilities which it provides are those of "user-friendly naming", whereby objects can be referred to by names which are suitable for citing by human users (though not all objects need have user-friendly names); and "name-to-address mapping" which allows the binding between objects and their locations to be dynamic. The latter capability allows networks, for example, to be "self-configuring" in the sense that addition, removal and the changes of object location do not affect network operation. The Directory is not intended to be a general-purpose database system, although it may be built on such systems. It is assumed, for instance, that, as is typical with communication directories, there is a considerably higher frequency of "queries" than of updates. The rate of updates is expected to be governed by the dynamics of people and organizations, rather than, for example, the dynamics of networks. There is also no need for instantaneous global commitment of updates; transient conditions, where both old and new versions of the same information are available, are quite acceptable. It is a characteristic of the Directory that, except as a consequence of differing access rights or un-propagated updates, the results of directory queries will not be dependent on the identity or location of the inquirer. This characteristic renders the Directory unsuitable for some telecommunication applications, for example some types of routing. For cases where the results are dependent on the identity of the inquirer, access to directory information and updates of the Directory may be denied.

Standard
22 pages
English language
sale 15% off
Standard
22 pages
English language
sale 15% off

ISO

ISO/IEC 9594-6:2020(Main)

Information technology — Open systems interconnection — Part 6: The Directory: Selected attribute types

This document defines a number of attribute types and matching rules which may be found useful across a range of applications of the Directory. Attribute types and matching rules fall into three categories, as described below. Some attribute types and matching rules are used by a wide variety of applications or are understood and/or used by the Directory itself. NOTE 1 ? It is recommended that an attribute type or matching rule defined in this Recommendation | International Standard be used, in preference to the generation of a new one, whenever it is appropriate for the application. NOTE 2 ? The attribute and context types definitions by this Recommendation | International Standard have some associated semantics. Such specifications should not be used in situations where these semantics do not apply. Some attribute types and matching rules are internationally standardized, but are application‑specific. These are defined in the standards associated with the application concerned. Any administrative authority can define its own attribute types and matching rules for any purpose. These are not internationally standardized, and are available to others beyond the administrative authority which created them only through bilateral agreement.

Standard
122 pages
English language
sale 15% off
Standard
122 pages
English language
sale 15% off

ISO

ISO/IEC 9594-3:2020(Main)

Information technology — Open systems interconnection — Part 3: The Directory: Abstract service definition

This document defines in an abstract way the externally visible service provided by the Directory. This document does not specify individual implementations or products.

Standard
120 pages
English language
sale 15% off
Draft
120 pages
English language
sale 15% off

ISO

ISO/IEC 9594-4:2020(Main)

Information technology — Open systems interconnection — Part 4: The Directory: Procedures for distributed operation

This document specifies the behaviour of DSAs taking part in a distributed directory consisting of multiple Directory systems agents (DSAs) and/or LDAP servers with at least one DSA. The allowed behaviour has been designed to ensure a consistent service given a wide distribution of the DIB across a distributed directory. Only the behaviour of DSAs taking part in a distributed directory is specified. The behaviour of LDAP servers are specified in relevant LDAP specifications. There are no special requirements on an LDAP server beyond those given by the LDAP specifications. The Directory is not intended to be a general purpose database system, although it may be built on such systems. It is assumed that there is a considerably higher frequency of queries than of updates.

Standard
125 pages
English language
sale 15% off
Draft
125 pages
English language
sale 15% off

ISO

ISO/IEC 9594-5:2020(Main)

Information technology — Open systems interconnection — Part 5: The Directory: Protocol specifications

This document specifies the Directory Access Protocol, the Directory System Protocol, the Directory Information Shadowing Protocol, and the Directory Operational Binding Management Protocol which fulfil the abstract services specified in Rec. ITU-T X.511 | ISO/IEC 9594-3, Rec. ITU-T X.518 | ISO/IEC 9594-4, Rec. ITU‑T X.525 | ISO/IEC 9594-9, and Rec. ITU-T X.501 | ISO/IEC 9594-2.

Standard
83 pages
English language
sale 15% off
Standard
83 pages
English language
sale 15% off

ISO

ISO/IEC 9594-2:2020(Main)

Information technology — Open systems interconnection — Part 2: The Directory: Models

This document provides a conceptual and terminological framework for the other ITU-T X.500-series Recommendations | parts of ISO/IEC 9594 which define various aspects of the Directory. The functional and administrative authority models define ways in which the Directory can be distributed, both functionally and administratively. Generic Directory System Agent (DSA) and DSA information models and an Operational Framework are also provided to support Directory distribution. The generic Directory Information Models describe the logical structure of the Directory Information Base (DIB) from the perspective of Directory and Administrative Users. In these models, the fact that the Directory is distributed, rather than centralized, is not visible. This Recommendation | International Standard provides a specialization of the generic Directory Information Models to support Directory Schema administration. The other ITU-T Recommendations in the X.500 series | parts of ISO/IEC 9594 make use of the concepts defined in this Recommendation | International Standard to define specializations of the generic information and DSA models to provide specific information, DSA and operational models supporting particular directory capabilities (e.g., Replication): a) the service provided by the Directory is described (in Rec. ITU-T X.511 | ISO/IEC 9594-3) in terms of the concepts of the information framework: this allows the service provided to be somewhat independent of the physical distribution of the DIB; b) the distributed operation of the Directory is specified (in Rec. ITU-T X.518 | ISO/IEC 9594-4) so as to provide that service, and therefore maintain that logical information structure, given that the DIB is in fact highly distributed; c) replication capabilities offered by the component parts of the Directory to improve overall Directory performance are specified (in Rec. ITU-T X.525 | ISO/IEC 9594-9). The security model establishes a framework for the specification of access control mechanisms. It provides a mechanism for identifying the access control scheme in effect in a particular portion of the Directory Information Tree (DIT), and it defines three flexible, specific access control schemes which are suitable for a wide variety of applications and styles of use. The security model also provides a framework for protecting the confidentiality and integrity of directory operations using mechanisms such as encryption and digital signatures. This makes use of the framework for authentication defined in Rec. ITU-T X.509 | ISO/IEC 9594-8 as well as generic upper layers security tools defined in Rec. ITU-T X.830 | ISO/IEC 11586-1. DSA models establish a framework for the specification of the operation of the components of the Directory. Specifically: a) the Directory functional model describes how the Directory is manifested as a set of one or more components, each being a DSA; b) the Directory distribution model describes the principals according to which the DIB entries and entry‑copies may be distributed among DSAs; c) the DSA information model describes the structure of the Directory user and operational information held in a DSA; d) the DSA operational framework describes the means by which the definition of specific forms of cooperation between DSAs to achieve particular objectives (e.g., shadowing) is structured.

Standard
238 pages
English language
sale 15% off
Standard
238 pages
English language
sale 15% off