RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management

This document provides guidance to designers of Authentication, Authorization, and Accounting (AAA) key management protocols. The guidance is also useful to…

Read RFC 4962 on the RFC Editor

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 5247: Extensible Authentication Protocol (EAP) Key Management Framework
Normatively referenced by — RFC 5836: Extensible Authentication Protocol (EAP) Early Authentication Problem Statement
Normatively referenced by — RFC 6421: Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS)
Normatively referenced by — RFC 5030: Mobile IPv4 RADIUS Requirements
Normatively referenced by — RFC 6678: Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method
Informatively referenced by — RFC 6709: Design Considerations for Protocol Extensions
Informatively referenced by — RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
Informatively referenced by — RFC 5296: EAP Extensions for EAP Re-authentication Protocol (ERP)
Informatively referenced by — RFC 6696: EAP Extensions for the EAP Re-authentication Protocol (ERP)
Informatively referenced by — RFC 7298: Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication
Informatively referenced by — RFC 6150: MD4 to Historic Status
Informatively referenced by — RFC 6630: EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK)
Informatively referenced by — RFC 7241: The IEEE 802/IETF Relationship
Informatively referenced by — RFC 5807: Definition of Master Key between PANA Client and Enforcement Point