Standard
Standard
-
Technical committeeTypeAcronymISO 10762CommitteePublished year2015Description
ISO 10762:2015 establishes mounting dimensions for cylinders for use at 10 MPa [100 bar[1]], as required for interchangeability of these cylinders.
NOTE This International Standard allows manufacturers of hydraulic equipment flexibility in the design of 10 MPa (100 bar) cylinders and does not restrict technical development; however, it does provide basic guidelines.
[1] 1 bar = 0,1 MPa = 105 Pa; 1 MPa = 1 N/mm2.
Technology -
Technical committeeTypeAcronymISO 10372CommitteePublished year1992Description
Specifies the dimensions of surfaces on which servovalves are mounted in order to ensure interchangeability. Applies primarily to electrohydraulic flow-control servovalves. In addition, may be used for pressure-control servovalves. If the valve is used in a three-port application, either service port (A and B) may be omitted.
Technology -
Technical committeeTypeAcronymISO 10100CommitteePublished year2020Description
This document specifies acceptance and function tests for hydraulic fluid power cylinders.
Technology -
Technical committeeTypeAcronymIPC-2551Published year2020Description
IPC-2551, 2020 Edition, December 2020 - International Standard for Digital Twins
This standard establishes the IPC Digital Twin, which is comprised of the Digital Twin Product, Digital Twin Manufacturing and Digital Twin Lifecycle frameworks. Within the Digital Twin Architecture, this standard stipulates and defines Digital Twin properties, types, complexities and readiness levels. The IPC Digital Twin includes historical information about a product, including the history of design in terms of revision and engineering changes, and manufacturing information, that many refer to as the Digital Thread.
This standard enables any manufacturer, design organization or solution provider to initiate application interoperability to create smart value chains, as well as the mechanism to assess their current IPC Digital Twin readiness level.
This standard provides the information and guidance necessary to understand a full IPC Digital Twin, Digital Twin Product, Digital Twin Manufacturing and Digital Twin Lifecycle. This standard also provides information and guidance on how organizations benefit from the IPC Digital Twin, how to assess IPC Digital Twin readiness level and how to prepare an organization of any size or production volume to implement a full IPC Digital Twin approach to its organization and/or products.
-
Technical committeeTypeAcronymIETF RFC 6775Published year2012Description
The IETF work in IPv6 over Low-power Wireless Personal Area Network
(6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4. This and other
similar link technologies have limited or no usage of multicast
signaling due to energy conservation. In addition, the wireless
network may not strictly follow the traditional concept of IP subnets
and IP links. IPv6 Neighbor Discovery was not designed for non-
transitive wireless links, as its reliance on the traditional IPv6
link concept and its heavy use of multicast make it inefficient and
sometimes impractical in a low-power and lossy network. This
document describes simple optimizations to IPv6 Neighbor Discovery,
its addressing mechanisms, and duplicate address detection for Low-
power Wireless Personal Area Networks and similar networks. The
document thus updates RFC 4944 to specify the use of the
optimizations defined here. -
Technical committeeTypeAcronymIETF RFC 6347Published year2012Description
This document specifies version 1.2 of the Datagram Transport Layer Security (DTLS) protocol.
The DTLS protocol provides communications privacy for datagram protocols.
The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.
The DTLS protocol is based on the Transport Layer Security (TLS) protocol and provides equivalent security guarantees.
Datagram semantics of the underlying transport are preserved by the DTLS protocol.
This document updates DTLS 1.0 to work with TLS version 1.2
-
Technical committeeTypeAcronymIETF RFC 6272Published year2011Description
This note identifies the key infrastructure protocols of the Internet Protocol Suite for use in the Smart Grid. The target audience is those people seeking guidance on how to construct an appropriate Internet Protocol Suite profile for the Smart Grid. In practice, such a profile would consist of selecting what is needed for Smart Grid deployment from the picture presented here.
-
Technical committeeTypeAcronymIETF RFC 5281Published year2008Description
EAP-TTLS is an EAP (Extensible Authentication Protocol) method that encapsulates a TLS (Transport Layer Security) session, consisting of a handshake phase and a data phase.
During the handshake phase, the server is authenticated to the client (or client and server are mutually authenticated) using standard TLS procedures, and keying material is generated in order to create a cryptographically secure tunnel for information exchange in the subsequent data phase.
During the data phase, the client is authenticated to the server (or client and server are mutually authenticated) using an arbitrary authentication mechanism encapsulated within the secure tunnel.
The encapsulated authentication mechanism may itself be EAP, or it may be another authentication protocol such as PAP, CHAP, MS-CHAP, or MS-CHAP-V2.
Thus, EAP-TTLS allows legacy password-based authentication protocols to be used against existing authentication databases, while protecting the security of these legacy protocols against eavesdropping, man-in-the-middle, and other attacks.
The data phase may also be used for additional, arbitrary data exchange.
-
Technical committeeTypeAcronymIETF RFC 5272Description
This document defines the base syntax for CMC, a Certificate Management protocol using the Cryptographic Message Syntax (CMS). This protocol addresses two immediate needs within the Internet Public Key Infrastructure (PKI) community:
1. The need for an interface to public key certification products and services based on CMS and PKCS #10 (Public Key Cryptography
Standard), and2. The need for a PKI enrollment protocol for encryption only keys due to algorithm or hardware design.
CMC also requires the use of the transport document and the requirements usage document along with this document for a full
definition. -
Technical committeeTypeAcronymIETF RFC 5247Description
The Extensible Authentication Protocol (EAP), defined in RFC 3748, enables extensible network access authentication. This document
specifies the EAP key hierarchy and provides a framework for the transport and usage of keying material and parameters generated by
EAP authentication algorithms, known as "methods". It also provides a detailed system-level security analysis, describing the conditions
under which the key management guidelines described in RFC 4962 can be satisfied.