RFC 5516: Diameter Command Code Registration for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)
In plain English — editorial summary, not part of the RFC
This document registers a set of IANA Diameter Command Codes to be used in new vendor-specific Diameter applications defined for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS). These new Diameter applications are defined for Mobile Management Entity (MME)- and Serving GPRS (General Packet Radio Service) Support Node (SGSN)-related interfaces in the architecture for the Evolved 3GPP Packet Switched Domain, which is also known as the Evolved Packet System (EPS). This memo provides information for the Internet community.
Document record
- Document ID
- RFC5516
- Published
- April 2009
- Authors
- M. Jones; L. Morand
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5448Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')Updated
May 2009
- RFC 5447Diameter Mobile IPv6: Support for Network Access Server to Diameter Server InteractionCurrent
February 2009
- RFC 5624Quality of Service Parameters for Usage with DiameterCurrent
August 2009
- RFC 5279A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)Current
July 2008
- RFC 5777Traffic Classification and Quality of Service (QoS) Attributes for DiameterCurrent
February 2010
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 5002The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)Updated
August 2007
- RFC 6064SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Multimedia Broadcast/Multicast ServiceCurrent
January 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?