Diameter Base Protocol
RFC 3588, “Diameter Base Protocol”, is a Proposed Standard document published in September 2003 by P. Calhoun, J. Loughney, E. Guttman, G. Zorn, J. Arkko. It has since been updated by RFC 5719, RFC 5729, RFC 6408. It has been obsoleted by RFC 6733 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter is also intended to work in both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3588 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3587 IPv6 Global Unicast Address Format
- RFC 3589 Diameter Command Codes for Third Generation Partnership Project Release 5
- RFC 3586 IP Security Policy Requirements
- RFC 3590 Source Address Selection for the Multicast Listener Discovery Protocol
- RFC 3585 IPsec Configuration Policy Information Model
- RFC 3591 Definitions of Managed Objects for the Optical Interface Type
- RFC 3584 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
- RFC 3592 Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy Interface Type