|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Last Update: Jul 22, 2008
-- Color Legend: RFC Editor Queue
/ Processed by IESG
/ ID Exists
/ Recently Expired
-- Each I-D name is a link to an I-D description, which points to a text version, a two-page and fit-in-window PDF version, as well as the IETF Tools' HTML version.
|
|
|
|
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
| The charter of the DIME working group
is reported below.
|
|
|
|
The Diameter Maintanence and Extensions WG will focus on maintenance
and extensions to the Diameter protocol required to enable its use
in applications such as IP telephony and Local Area Network
authentication, authorization and accounting.
The IETF has recently completed work on the Diameter Base protocol.
There is on-going work on defining RADIUS extensions. The work done
in the DiME WG will ensure that work done in RADext is also
available for Diameter.
The immediate goals of the DiME working group are to address the
following issues:
|
|
| - |
Maintaining and/or progressing, along the standards track, the
Diameter procotol and Diameter Applications. Every revised
document to be "maintained" requires explicit approval before
it will be accepted as a WG document.
|
| - |
An informational RFC on a Diameter API.
|
| - |
Diameter Application design guidelines. This document will
provide guidelines for design of new Diameter Applications.
It will detail when to consider reusing an existing
application and when to develop a new application. Interaction
between vendor & SDO specific extensions and applications
will be covered.
|
| - |
Diameter QoS application. This document will develop a new
Diameter application for supporting QoS in AAA deployments.
The NSIS WG will be consulted on proper design of QoS attributes.
|
| - |
Diameter URI. RFC 3588 defines an AAA URI which has some known
problems. A document revising the AAA URI as a specific Diameter
URI will be developed.
|
| - |
Diameter extensions for MIPv6. This may include support for
Mobile IP extensions, like FMIP; as well as support for MIP
bootstrapping.
|
|
|
Additionally, AAA systems require interoperability in order to
work. Uncontrolled extensibility is not a mechanism for
interoperability. Therefore, the working group, along with the
AD, will need to evaluate any potential extensions and require
verification that the proposed extension is needed. Coordination
with other IETF working groups and other SDOs will used to
ensure this.
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC5224
03/2008
(5 p.)
[html]
[pdf(2)] |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| -
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
dime-diameter-
api-06
AD Evaluation::
Revised ID Needed
Feb 12, 2008
(48 p.)
[pdf(2)]
[html]
|
P. Calhoun
D. Frascone |
|
The Diameter API |
|
The Diameter authentication, authorization, and accounting (AAA)
protocol provides support for peering AAA transactions across the
Internet. This document describes a standardized API for the
Diameter protocol. The API is defined for the C language. The
intent of the API is to foster source code portability across
multiple programming platforms.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
dime-mip6-
integrated-09
Publication Requested
May 26, 2008
(18 p.)
[pdf(2)]
[html]
|
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 are 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 infrastructure. This document describes
the MIPv6 bootstrapping using the Diameter Network Access Server
(NAS) to home Authentication, Authorization and Accounting server
(HAAA) interface.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
sun-dime-
itu-t-rw-01
In Last Call
Jul 14, 2008
(11 p.)
[pdf(2)]
[html]
|
D. Sun |
|
Diameter ITU-T Rw Policy Enforcement Interface Application |
|
This document describes the need for a new pair of IANA Diameter
Command Codes and a new vendor-specific Application ID 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/responses for controlling the
policy enforcement in a network element, as one of the
recommendations of the International Telecommunication Union -
Telecommunication Standardization Sector (ITU-T).
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
dime-app-
design-guide-07
ID Exists
Jul 13, 2008
(17 p.)
[pdf(2)]
[html]
|
V. Fajardo
T. Asveren
H. Tschofenig
G. McGregor
J. Loughney |
|
Diameter Applications Design Guidelines |
|
The Diameter Base protocol provides updated rules on how to extend
Diameter by modifying and/or deriving from existing applications or
creating entirely new applications. This is a companion document to
the Diameter Base protocol that further explains and clarifies these
rules. It is meant as a guidelines document and therefore it does
not add, remove or change existing rules.
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
| | |
dime-diameter-
qos-06
ID Exists
Jul 13, 2008
(56 p.)
[pdf(2)]
[html]
|
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 -- Pull and Push -- are defined.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
dime-mip6-
split-10
ID Exists
Jul 6, 2008
(36 p.)
[pdf(2)]
[html]
|
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 (MSP). This document
specifies the interaction between a Mobile IP Home Agent and that
Diameter server.
Several different mechanisms for authenticating a Mobile Node are
supported. The usage of the Internet Key Exchange v2 (IKEv2)
protocol allows different mechanisms, such as the Extensible
Authentication Protocol (EAP), certificates and pre-shared secrets to
be used. Furthermore, another method makes use of 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.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
dime-qos-
attributes-07
ID Exists
Jun 26, 2008
(32 p.)
[pdf(2)]
[html]
|
J. Korhonen
H. Tschofenig
M. Arumaithurai
M. Jones
A. Lior |
|
Quality of Service Attributes for Diameter |
|
This document extends the IPFilterRule AVP functionality of the
Diameter Base protocol and the functionality of the QoS-Filter-Rule
AVP defined in RFC 4005. The ability to convey Quality of Service
information using the AVPs defined in this document is available to
existing and future Diameter applications where permitted by the
command ABNF.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
dime-rfc3588bis-11
ID Exists
Jul 9, 2008
(160 p.)
[pdf(2)]
[html]
|
V. Fajardo
J. Arkko
J. Loughney
G. Zorn |
|
Diameter Base Protocol |
|
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.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
| Operations and Management (OPS) area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Informational |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
bodin-dime-
auditing-reqs-03
ID Exists
(Recently Expired)
Aug 30, 2007
(15 p.)
[pdf(2)]
[html]
|
U. Bodin
A. Doria
B. Chatras
S. Norreys |
|
Auditing Functionality in Diameter |
|
Diameter is being increasingly included in the work of other
standards organizations and has become a key protocol in many
architectures. One of the uses of Diameter includes setting and
maintaining hard-state and soft-state during failover and in the
event of delayed refresh messages respectively. Often there is a
need to query for information on active sessions for backup or
synchronization purposes.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
dondeti-dime-
erp-diameter-02
ID Exists
Jul 14, 2008
(11 p.)
[pdf(2)]
[html]
|
L. Dondeti |
|
Diameter Support for EAP Re-authentication Protocol |
|
An EAP extension, called "EAP Re-authentication Protocol (ERP)", has
been specified that supports an EAP method-independent protocol for
efficient re-authentication between the peer and the server through
an authenticator. This document specifies Diameter support for ERP.
The Diameter EAP application is re-used for encapsulating the newly
defined EAP Initiate and EAP Finish messages specified in the ERP
specification. AVPs for request and delivery of Domain Specific Root
Keys from the AAA/EAP server to the ER server are also specified.
Additionally, this document also specifies Diameter processing rules
relevant to ERP.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
korhonen-dime-
nai-routing-00
ID Exists
Jul 3, 2008
(10 p.)
[pdf(2)]
[html]
|
J. Korhonen
M. Jones
L. Morand
T. Tsou |
|
Diameter User-Name and Realm Based Request Routing Clarifications |
|
This specification clarifies the Diameter realm based request
routing. We focus on the case where a Network Access Identifier in
the User-Name AVP is used to populate the Destination-Realm AVP and
the Network Access Identifier contains more than one realm. This
particular case is possible when the Network Access Identifier
decoration is used to force a routing of request messages through a
predefined list of realms. However, this functionality is not
unambiguously specified in the Diameter Base Protocol specification.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
korhonen-dime-
pmip6-03
ID Exists
Feb 25, 2008
(23 p.)
[pdf(2)]
[html]
|
J. Korhonen
J. Bournelle
A. Muhanna
K. Chowdhury
U. Meyer |
|
Diameter Proxy Mobile IPv6: Support For Mobility Access Gateway and
Local Mobility Anchor to Diameter Server Interaction |
|
This specification defines the Diameter support for the Proxy Mobile
IPv6 and the corresponding mobility service session setup. The
policy information needed by the Proxy Mobile IPv6 is defined in
mobile node's policy profile, which could be downloaded from the
Diameter server to the Mobile Access Gateway once the mobile node
roams into a Proxy Mobile IPv6 Domain and performs access
authentication. The access authentication procedure of the Proxy
Mobile IPv6 Domain resembles the Mobile IPv6 integrated scenario
bootstrapping. Rather than defining a completely new set of
attributes or a new Diameter application this specification leverages
the work that has already been done for the Mobile IPv6
bootstrapping.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
mccann-dime-
rfc4004bis-00
ID Exists
(Recently Expired)
Nov 11, 2007
(52 p.)
[pdf(2)]
[html]
|
P. Calhoun
T. Johansson
C. Perkins
T. Hiller
P. McCann |
|
Diameter Mobile IPv4 Application, Revised |
|
This document specifies a Diameter application that allows a Diameter
server to authenticate, authorize and collect accounting information
for Mobile IPv4 services rendered to a mobile node. Combined with
the Inter-Realm capability of the base protocol, this application
allows mobile nodes to receive service from foreign service
providers. Diameter Accounting messages will be used by the foreign
and home agents to transfer usage information to the Diameter
servers.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
morariu-dime-
grid-accounting-00
ID Exists
(Recently Expired)
Oct 5, 2007
(15 p.)
[pdf(2)]
[html]
|
C. Morariu
P. Racz
D. Hausheer
B. Stiller |
|
Diameter Grid Accounting Application |
|
This document specifies a Diameter application in support of
accounting in Grid networks. It defines a way to integrate network-related
and Grid service-related accounting parameters to ensure the
operation of a homogeneous accounting systems based on Diameter. A
new set of AVPs is defined and accounting messages are extended in
order to support accountable and exchangeable Grid services in a
multi provider environment.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
neumann-dime-
webauth-00
ID Exists
Feb 18, 2008
(26 p.)
[pdf(2)]
[html]
|
N. Neumann
X. Fu |
|
Diameter Application for Authentication and Authorization in Web Applications |
|
This document specifies the Diameter Application for Authentication
and Authorization in Web Applications (Diameter WebAuth). This
Diameter application is intended to be used by Diameter clients to
perform authentication and authorization operations with a Diameter
server in web-based environments. It provides facilities to allow
web sites to authenticate their web user clients using a number of
(HTTP) authentication schemes. In addition, it supports user
authorization using dedicated service identifiers. Diameter WebAuth
may also be used by non web-based Diameter clients and servers that
require a lightweight authentication and authorization Diameter
application.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
stupar-dime-
mos-options-00
ID Exists
Feb 18, 2008
(18 p.)
[pdf(2)]
[html]
|
P. Stupar
S. Das
J. Korhonen
T. Melia |
|
Diameter extensions for MoS discovery |
|
IEEE 802.21 standard defines three distinct service types to
facilitate link layer handovers across heterogeneous technologies.
This document focuses on the Diameter Network Access Server (NAS) to
home Authentication, Authorization and Accounting server (HAAA)
interface defining a number of Diameters AVPs containing domain names
or IP addresses. Such information is related to IEEE 802.21 services
assisting a mobile node in handover preparation (network discovery)
and handover decision (network selection).
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
| | |
zorn-dime-
diameter-base-
protocol-mib-03
ID Exists
Feb 10, 2008
(53 p.)
[pdf(2)]
[html]
|
G. Zorn
S. Comerica |
|
Diameter Base Protocol MIB |
Along with providing support for certain basic authentication,
authorization and accounting functions, the Diameter protocol is
designed to provide a framework for AAA applications.
This document defines the Management Information Base (MIB) module
which describes the minimum set of objects needed to manage an
implementation of the Diameter protocol.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
