ISO/IEC 9595:1991/Cor 2:1992
(Corrigendum)Information technology — Open systems Interconnection — Common management information service definition — Technical Corrigendum 2
- BACK
- 01-Jul-1992
- 01-Jul-1992
- 35.100.70
- ISO/IEC JTC 1
Information technology — Open systems Interconnection — Common management information service definition — Technical Corrigendum 2
Technologies de l'information — Interconnexion de systèmes ouverts — Définition du service commun d'informations de gestion — Rectificatif technique 2
General Information
Relations
This May Also Interest You
ISO/IEC 20802-1:2016 defines the core semantics and facilities of the Open Data Protocol (OData). This enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Locators (URLs) and defined in an Entity Data Model (EDM), to be published and edited by Web clients using simple HTTP messages.
- Standard203 pagesEnglish language
- 14-Dec-2016
- 35.100.70
- ISO/IEC JTC 1
ISO/IEC 20802-2:2016 extends ISO/IEC 20802-1, the core specification of the Open Data Protocol (OData) for representing and interacting with structured content, by defining representations for Odata requests and responses using a JSON format.
- Standard43 pagesEnglish language
- 14-Dec-2016
- 35.100.70
- ISO/IEC JTC 1
ISO/IEC 20922:2016 is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium. The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include: Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications. A messaging transport that is agnostic to the content of the payload. Three qualities of service for message delivery: "At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after. "At least once", where messages are assured to arrive but duplicates can occur. "Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
- Standard73 pagesEnglish language
- Standard73 pagesEnglish language
- 07-Jun-2016
- 35.100.70
- ISO/IEC JTC 1
ISO/IEC 16512-2:2016 specifies the relayed multicast protocol part 2 (RMCP-2), an application‑layer protocol that constructs a multicast tree for data delivery from one sender to multiple receivers over an IP-based network, where IP multicast is not fully deployed. RMCP-2 defines relayed multicast data transport capabilities over IP‑based networks for simplex group applications. This Recommendation | International Standard specifies the following: a) descriptions of the entities, control and data delivery models of RMCP-2; b) description of the functions and procedures of multicast agents (MAs) to construct a one-to-many relayed data path and to relay data for simplex communication; c) description of the security features of the basic RMCP-2; and d) definitions of messages and parameters of the basic RMCP-2 and secure RMCP-2. Annex A defines a membership authentication procedure for use with the secure RMCP-2. Annex B provides a method for sharing information among session managers (SMs) when multiple SMs are used. Annexes C‑G provide informative material related to RMCP-2. Annex H contains an informative bibliography.
- Standard119 pagesEnglish language
- 20-Mar-2016
- 35.100.70
- ISO/IEC JTC 1
Relayed multicast protocol (RMCP) is a protocol which is used to realize a relayed multicast data transport scheme. Different from the conventional IP multicast, RMCP can configure a relayed multicast path that multicast traffic flows by using intermediate end-hosts. RMCP can be applied to the current unicast based IP network where IP multicast is not fully deployed. ISO/IEC 16512-1:2016 addresses the basic concepts needed to specify RMCP for relayed multicast. It defines the related terminology and proposes a framework for the future development of subsequent protocols. The framework covers network topology including network entities and the relationship among them, service scenarios, basic operations, and message format.
- Standard15 pagesEnglish language
- 20-Mar-2016
- 35.100.70
- ISO/IEC JTC 1
ISO/IEC 19464:2014 defines the Advanced Message Queuing Protocol (AMQP), an open internet protocol for business messaging. It defines a binary wire-level protocol that allows for the reliable exchange of business messages between two parties. AMQP has a layered architecture and the specification is organized as a set of parts that reflects that architecture. Part 1 defines the AMQP type system and encoding. Part 2 defines the AMQP transport layer, an efficient, binary, peer-to-peer protocol for transporting messages between two processes over a network. Part 3 defines the AMQP message format, with a concrete encoding. Part 4 defines how interactions can be grouped within atomic transactions. Part 5 defines the AMQP security layers.
- Standard124 pagesEnglish language
- Standard124 pagesEnglish language
- 28-Apr-2014
- 35.100.70
- ISO/IEC JTC 1
This Recommendation | International Standard defines the scheduling function. The scheduling function is a systems management function which may be used by an application process in a centralized or decentralized management environment to exchange information and commands for the purpose of systems management, as defined by CCITT Rec. X.700 | ISO/IEC 7498-4. This Recommendation | International Standard is positioned in the application layer of ITU-T Rec. X.200 | ISO/IEC 7498-1 and is defined according to the model provided by ISO/IEC 9545. The role of systems management functions is described by CCITT Rec. X.701 | ISO/IEC 10040. This Recommendation | International Standard: ? identifies a set of requirements satisfied by the function; ? provides a model for scheduling; ? specifies the management requirements of the function and how these are realized by specification of managed objects and their behaviour; ? defines the conformance requirements to be met by implementations of this Recommendation | International Standard; ? defines managed objects. This Recommendation | International Standard does not define: ? the manner in which management is to be accomplished by the user of the scheduling function; ? the nature of any implementation intended to provide the scheduling function; ? the nature of any interactions which result in the use of the scheduling function; ? the interactions which result by the simultaneous use of several management functions; ? the occasions where the use of the scheduling function is appropriate; ? the services necessary for the establishment, normal and abnormal release of a management association.
- Standard40 pagesEnglish language
- Standard44 pagesFrench language
- 10-Dec-2002
- 35.100.70
- ISO/IEC JTC 1
- Standard3 pagesEnglish language
- Standard3 pagesFrench language
- 10-Apr-2002
- 35.100.70
- ISO/IEC JTC 1
- Standard31 pagesEnglish language
- Standard32 pagesFrench language
- 01-Nov-2000
- 35.100.70
- ISO/IEC JTC 1
This Recommendation | International Standard defines systems management protocol machine managed objects, thus allowing the use of the Common Management Information Protocol (CMIP), as defined in ITU-T Rec. X.711 | ISO/IEC 9596-1, to manage CMISE and SMASE application service elements and invocations. This Recommendation | International Standard: ? establishes a model for supporting systems management application service elements; ? provides generic and formal definitions for supporting systems management application service element managed objects. This Recommendation | International Standard does not: ? define new management functions; ? specify a framework or methodology for conformance tests. In the context of this Recommendation | International Standard, the term systems management is used to refer to SMASE, CMISE, and ROSE.
- Standard11 pagesEnglish language
- Standard12 pagesFrench language
- 25-Oct-2000
- 35.100.70
- ISO/IEC JTC 1
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.