Standard
Standard
-
Technical committeeTypeAcronymIETF RFC 5246Published year2008Description
This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.
-
Technical committeeTypeAcronymIETF RFC 4962Published year2007Description
This document provides guidance to designers of Authentication, Authorization, and Accounting (AAA) key management protocols. The
guidance is also useful to designers of systems and solutions that include AAA key management protocols. Given the complexity and
difficulty in designing secure, long-lasting key management algorithms and protocols by experts in the field, it is almost certainly inappropriate for IETF working groups without deep expertise in the area to be designing their own key management algorithms and protocols based on Authentication, Authorization, and Accounting (AAA) protocols. The guidelines in this document apply to documents requesting publication as IETF RFCs. Further, these guidelines will be useful to other standards development organizations (SDOs) that specify AAA key management. -
Technical committeeTypeAcronymIETF RFC 4422Published year2006Description
The Simple Authentication and Security Layer (SASL) is a framework for providing authentication and data security services in connection-oriented protocols via replaceable mechanisms. It provides a structured interface between protocols and mechanisms. The resulting framework allows new protocols to reuse existing mechanisms and allows old protocols to make use of new mechanisms. The framework also provides a protocol for securing subsequent protocol exchanges within a data security layer. This document describes how a SASL mechanism is structured, describes how protocols include support for SASL, and defines the protocol for carrying a data security layer over a connection. In addition, this document defines one SASL mechanism, the EXTERNAL mechanism.
-
Technical committeeTypeAcronymIETF RFC 4303Published year2005Description
This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. ESP is used to provide
confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document obsoletes RFC 2406 (November 1998). -
Technical committeeTypeAcronymIETF RFC 4210Published year2005Description
This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP). Protocol messages are defined for X.509v3 certificate creation and management. CMP
provides on-line interactions between PKI components, including an exchange between a Certification Authority (CA) and a client system. -
Technical committeeTypeAcronymIEEE P2030CommitteePublished year2011KeywordsDescription
A worldwide standard for narrowband power line communications (PLC) via alternating current, direct current, and nonenergized electric power lines using frequencies below 500 kHz. Data rates of up to 500 kb/s are supported. The field of use includes Smart Grid applications. Coexistence mechanisms that can be used by other PLC technologies operating below 500 kHz are also included. These coexistence mechanisms may be used separately from the rest of the standard
-
Technical committeeTypeAcronymIEEE P1901.2CommitteePublished year2013Description
A worldwide standard for narrowband power line communications (PLC) via alternating current, direct current, and nonenergized electric power lines using frequencies below 500 kHz. Data rates of up to 500 kb/s are supported. The field of use includes Smart Grid applications. Coexistence mechanisms that can be used by other PLC technologies operating below 500 kHz are also included. These coexistence mechanisms may be used separately from the rest of the standard
-
Technical committeeTypeAcronymIEEE C50.12CommitteePublished year2005Description
The requirements in this standard apply to all types of 50 Hz and 60 Hz salient-pole synchronous generators and generator/motors rated 5 MVA and above to be used for hydraulic turbine or hydraulic pump/turbine applications.
Technology -
Technical committeeTypeAcronymIEEE C37.118.2CommitteePublished year2011Description
A method for real-time exchange of synchronized phasor measurement data between power system equipment is defined. This standard specifies messaging that can be used with any suitable communication protocol for real-time communication between phasor measurement units (PMU), phasor data concentrators (PDC), and other applications. It defines message types, contents, and use. Data types and formats are specified. A typical measurement system is described. Communication options and requirements are described in annexes.
-
Technical committeeTypeAcronymIEEE C37.118.1aCommitteePublished year2014Description
Modifications in this amendment include some performance requirements with related text updates to correct inconsistencies and remove limitations introduced by IEEE Std C37.118.1(TM)-2011. It was discovered that a few requirements were not achievable with the published models as was intended and others were extremely difficult to meet with available hardware. This amendment modifies requirements in Table 4 through Table 10. Text was modified to support the requirement modification. Testing described in 5.5.9 was clarified, and Table 11 (formerly Table 12) was modified to match. Annex C was modified to keep it consistent with the rest of the document.