|
|
|
|
|
|
|
|
|
|
| Last Update: May 26, 2010
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC5224
03/2008
(5 p.)
pdf(2p)
|
M. Brenner |
|
Diameter Policy Processing Application |
|
This document describes the need for a new IANA Diameter Command Code
to be used in a vendor-specific new application for invocation of
Policy Processing (Policy Evaluation, or Evaluation and Enforcement).
This application is needed as one of the implementations of the Open
Mobile Alliance (OMA) Policy Evaluation, Enforcement and Management
(PEEM) enabler, namely for the PEM-1 interface used to send a
request/response for Policy Processing.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
| | |
RFC5431
03/2009
(5 p.)
pdf(2p)
|
D. Sun |
|
Diameter ITU-T Rw Policy Enforcement Interface Application |
|
This document describes the need for a new pair of IANA Diameter
Command Codes to be used in a vendor-specific new application, namely
for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/
response for authorizing network Quality of Service (QoS) resources
and policy enforcement in a network element, as one of the
recommendations of the International Telecommunication Union -
Telecommunication Standardization Sector (ITU-T).
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
| | |
RFC5447
02/2009
(17 p.)
pdf(2p)
|
J. Korhonen
J. Bournelle
H. Tschofenig
C. Perkins
K. Chowdhury |
|
Diameter Mobile IPv6:
Support for Network Access Server to Diameter Server Interaction |
|
A Mobile IPv6 node requires a home agent address, a home address, and
a security association with its home agent before it can start
utilizing Mobile IPv6. RFC 3775 requires that some or all of these
parameters be statically configured. Mobile IPv6 bootstrapping work
aims to make this information dynamically available to the mobile
node. An important aspect of the Mobile IPv6 bootstrapping solution
is to support interworking with existing Authentication,
Authorization, and Accounting (AAA) infrastructures. This document
describes MIPv6 bootstrapping using the Diameter Network Access
Server to home AAA server interface.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5516
04/2009
(5 p.)
pdf(2p)
|
M. Jones
L. Morand |
|
Diameter Command Code Registration for the 3GPP Evolved Packet System (EPS) |
|
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).
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
| | |
RFC5624
08/2009
(12 p.)
pdf(2p)
|
J. Korhonen
H. Tschofenig
E. Davies |
|
Quality of Service Parameters for Usage with Diameter |
This document defines a number of Quality of Service (QoS) parameters
that can be reused for conveying QoS information within Diameter.
The defined QoS information includes data traffic parameters for
describing a token bucket filter, a bandwidth parameter, and a per-hop
behavior class object.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5719
01/2010
(5 p.)
pdf(2p)
|
D. Romascanu
H. Tschofenig |
|
Updated IANA Considerations for Diameter Command Code Allocations |
|
The Diameter base specification, described in RFC 3588, provides a
number of ways to extend Diameter, with new Diameter commands (i.e.,
messages used by Diameter applications) and applications as the most
extensive enhancements. RFC 3588 illustrates the conditions that
lead to the need to define a new Diameter application or a new
command code. Depending on the scope of the Diameter extension, IETF
actions are necessary. Although defining new Diameter applications
does not require IETF consensus, defining new Diameter commands
requires IETF consensus per RFC 3588. This has led to questionable
design decisions by other Standards Development Organizations, which
chose to define new applications on existing commands -- rather than
asking for assignment of new command codes -- for the pure purpose of
avoiding bringing their specifications to the IETF. In some cases,
interoperability problems were an effect of the poor design caused by
overloading existing commands.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5729
12/2009
(11 p.)
pdf(2p)
|
J. Korhonen
M. Jones
L. Morand
T. Tsou |
|
Clarifications on the Routing of Diameter Requests Based on the Username and the Realm |
|
This specification defines the behavior required of Diameter agents
to route requests when the User-Name Attribute Value Pair contains a
Network Access Identifier formatted with multiple realms. These
multi-realm, or "Decorated", Network Access Identifiers are used in
order to force the routing of request messages through a predefined
list of mediating realms.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5777
02/2010
(43 p.)
pdf(2p)
|
J. Korhonen
H. Tschofenig
M. Arumaithurai
M. Jones
A. Lior |
|
Traffic Classification and Quality of Service (QoS) Attributes for Diameter |
|
This document defines a number of Diameter attribute-value pairs
(AVPs) for traffic classification with actions for filtering and
Quality of Service (QoS) treatment. These AVPs can be used in
existing and future Diameter applications where permitted by the
Augmented Backus-Naur Form (ABNF) specification of the respective
Diameter command extension policy.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5778
02/2010
(34 p.)
pdf(2p)
|
J. Korhonen
H. Tschofenig
J. Bournelle
G. Giaretta
M. Nakhjiri |
|
Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction |
Mobile IPv6 deployments may want to bootstrap their operations
dynamically based on an interaction between the home agent and the
Diameter server of the Mobile Service Provider. This document
specifies the interaction between a Mobile IP home agent and a
Diameter server.
This document defines the home agent to the Diameter server
communication when the mobile node authenticates using the Internet
Key Exchange v2 protocol with the Extensible Authentication Protocol
or using the Mobile IPv6 Authentication Protocol. In addition to
authentication and authorization, the configuration of Mobile IPv6-specific
parameters and accounting is specified in this document.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5779
02/2010
(20 p.)
pdf(2p)
|
J. Korhonen
J. Bournelle
K. Chowdhury
A. Muhanna
U. Meyer |
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
| | |
RFC5866
05/2010
(51 p.)
pdf(2p)
|
D. Sun
P. McCann
H. Tschofenig
T. Tsou
A. Doria
G. Zorn |
|
Diameter Quality-of-Service Application |
|
This document describes the framework, messages, and procedures for
the Diameter Quality-of-Service (QoS) application. The Diameter QoS
application allows network elements to interact with Diameter servers
when allocating QoS resources in the network. In particular, two
modes of operation, namely "Pull" and "Push", are defined.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
