Diameter CMS Security Application
draft-ietf-aaa-diameter-cms-sec-04
| Document | Type |
Expired Internet-Draft
(aaa WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Pat R. Calhoun , Stephen Farrell , William Bulley | ||
| Last updated | 2015-10-14 (Latest revision 2002-03-05) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Bert Wijnen | ||
| IESG note | |||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Diameter base protocol leverages either IPsec or TLS for integrity and confidentiality between two Diameter peers, and allows the peers to communicate through relay and proxy agents. Relay agents perform message routing, and other than routing AVPs, do not modify Diameter messages. Proxy agents, on the other hand, implement policy enforcement, and actively modify Diameter messages.
Authors
Pat R. Calhoun
Stephen Farrell
William Bulley
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)