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 resp...view more

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

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.

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

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...view more

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

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 e...view more

    • sale 15% off
    • Standard
      22 pages
      English language
    • sale 15% off
    • Standard
      22 pages
      English language
    • sale 15% off
    • Draft
      24 pages
      English language

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.

    • sale 15% off
    • Standard
      83 pages
      English language
    • sale 15% off
    • Standard
      83 pages
      English language
    • sale 15% off
    • Draft
      85 pages
      English language

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

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

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 ...view more

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

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 ...view more

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

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 I...view more

    • sale 15% off
    • Standard
      238 pages
      English language
    • sale 15% off
    • Standard
      238 pages
      English language
    • sale 15% off
    • Draft
      240 pages
      English language

IEC 62264-6:2020(E) defines a technology independent model for a set of abstract services that is located above the application layer of the OSI model, and that is used for exchanging transaction messages based on the transaction models defined in IEC 62264-5. The model, which is called the Messaging Service Model (MSM), is intended for interoperability between manufacturing operations domain applications and applications in other domains.

    • sale 15% off
    • Standard
      50 pages
      English language

This document is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the three-layer fieldbus reference model described in IEC 61158-1. This International Standard contains material specific to the Type 21 communication protocol.

    • sale 10% off
    • Standard
      58 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 19 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications request...view more

    • sale 10% off
    • Standard
      26 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-timecritical messaging communications between application programs in an automation environment and material specific to Type 25 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesti...view more

    • sale 10% off
    • Standard
      127 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 23 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications request...view more

    • sale 10% off
    • Standard
      228 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 3 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesti...view more

    • sale 10% off
    • Standard
      381 pages
      English language
    • e-Library read for
      1 day

This document provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.” This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 10 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within...view more

    • sale 10% off
    • Standard
      634 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 4 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesti...view more

    • sale 10% off
    • Standard
      43 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 10 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications request...view more

    • sale 10% off
    • Standard
      899 pages
      English language
    • e-Library read for
      1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 12 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications request...view more

    • sale 10% off
    • Standard
      146 pages
      English language
    • e-Library read for
      1 day