Diameter
Encyclopedia : D : DI : DIA : Diameter
- For the geometric term, see diameter.
| Layer | Protocols |
|---|---|
| Application | DNS, TLS/SSL, TFTP, FTP, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP, SNMP, SSH, TELNET, BitTorrent, RTP, rlogin, … |
| Transport | TCP, UDP, DCCP, SCTP, IL, RUDP, |
| Network | IP (IPv4, IPv6), ICMP, IGMP, ARP, RARP, … |
| Link | Ethernet, Wi-Fi, Token ring, Point-to-Point Protocol>PPP, SLIP, FDDI, ATM, DTM, Frame Relay, SMDS, … |
Contents
Upgrade from RADIUS
The name is a pun on the RADIUS protocol, which is the predecessor (a diameter is twice the radius). Diameter is not directly backwards compatible, but provides an upgrade path for RADIUS. The main differences are :- it uses reliable transport protocols (TCP or SCTP, not UDP)
- it uses transport level security (IPsec or TLS)
- it has transition support for RADIUS
- it has larger address space for AVPs (Attribute Value Pairs) and identifiers (32-bit instead of 8-bit)
- it is a peer-to-peer protocol, not client-server : supports server-initiated messages
- both stateful and stateless models can be used
- it has dynamic discovery of peers (using DNS SRV and NAPTR)
- it has capability negotiation
- it supports application layer acknowledgements, defines failover methods and statemachines (RFC 3539)
- it has error notification
- it has better roaming support
- it is easier extended, new commands and attributes can be defined
- is aligned on 32 bit boundaries
- basic support for user-sessions and accounting is built in
Protocol description
The Diameter Base Protocol is defined by RFC 3588, and defines the minimum requirements for an AAA protocol. Diameter Applications can extend the base protocol, by adding new commands and/or attributes. An application is not a program, but a protocol based on Diameter. Diameter security is provided by IPSEC or TLS, both well-regarded protocols.Packet format
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version | Message Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | command flags | Command-Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Application-ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Hop-by-Hop Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | End-to-End Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AVPs ... +-+-+-+-+-+-+-+-+-+-+-+-+-
Commands
Each command is assigned a command code, which is used for both requests and answers.
