< draft-zorn-dime-radia-gate-00.txt   draft-zorn-dime-radia-gate-01.txt >
Network Working Group G. Zorn Network Working Group G. Zorn
Internet-Draft Network Zen Internet-Draft Network Zen
Updates: 4005 (if approved) L. Morand Updates: 4005 (if approved) L. Morand
Intended status: Standards Track Orange Labs Intended status: Standards Track Orange Labs
Expires: January 6, 2010 July 5, 2009 Expires: September 8, 2010 T. Hiller
Lucent Technologies
March 7, 2010
The RADIUS-Diameter Gateway (RADIA) Application The RADIUS-Diameter Gateway (RADIA) Application
draft-zorn-dime-radia-gate-00.txt draft-zorn-dime-radia-gate-01.txt
Abstract
This document describes the Diameter RADIUS-Diameter Gateway (RADIA)
Application, which is designed to facillitate the interoperability of
Authentication, Authorization and Accounting (AAA) systems based upon
RADIUS and Diameter.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 6, 2010. This Internet-Draft will expire on September 8, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
This document describes the Diameter RADIUS-Diameter Gateway (RADIA) This document may contain material from IETF Documents or IETF
Application, which is designed to facillitate the interoperability of Contributions published or made publicly available before November
Authentication, Authorization and Accounting (AAA) systems based upon 10, 2008. The person(s) controlling the copyright in some of this
RADIUS and Diameter. material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
3. The RADIUS-Diameter Gateway Application . . . . . . . . . . . . 3 3. The RADIUS-Diameter Gateway Application . . . . . . . . . . . . 3
3.1. Advertising Application Support . . . . . . . . . . . . . . 3 3.1. Advertising Application Support . . . . . . . . . . . . . . 3
3.2. Diameter Session Usage . . . . . . . . . . . . . . . . . . 3 3.2. Diameter Session Usage . . . . . . . . . . . . . . . . . . 3
3.3. Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3.1. The RADIA-Request (RDR) Command . . . . . . . . . . . . 4 3.3.1. The RADIA-Request (RDR) Command . . . . . . . . . . . . 4
3.3.2. The RADIA-Answer (RDA) Command . . . . . . . . . . . . 4 3.3.2. The RADIA-Answer (RDA) Command . . . . . . . . . . . . 4
3.4. Attribute-Value Pairs . . . . . . . . . . . . . . . . . . . 5 3.4. Attribute-Value Pairs . . . . . . . . . . . . . . . . . . . 5
3.4.1. Radius-Message AVP . . . . . . . . . . . . . . . . . . 5 3.4.1. Radius-Message AVP . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Diameter Application Identifier . . . . . . . . . . . . . . 5 5.1. Diameter Application Identifier . . . . . . . . . . . . . . 5
5.2. Diameter Command Codes . . . . . . . . . . . . . . . . . . 5 5.2. Diameter Command Codes . . . . . . . . . . . . . . . . . . 5
5.3. Attribute-Value Pairs . . . . . . . . . . . . . . . . . . . 6 5.3. Attribute-Value Pairs . . . . . . . . . . . . . . . . . . . 5
6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 6. Normative References . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The Diameter Network Access Server (NASREQ) Application [RFC4005] The Diameter Network Access Server (NASREQ) Application [RFC4005]
specifies methods to deal with various interactions between the specifies methods to deal with various interactions between the
RADIUS [RFC2865] and Diameter [RFC3588] protocols. In particular, RADIUS [RFC2865] and Diameter [RFC3588] protocols. In particular,
the translation of RADIUS messages and attributes to and from the translation of RADIUS messages and attributes to and from
Diameter commands and Attribute-Value Pairs (AVPs) is described at Diameter commands and Attribute-Value Pairs (AVPs) is described at
some length. However, there is a fundamental and insurmountable some length. However, there is a fundamental and insurmountable
skipping to change at page 4, line 17 skipping to change at page 5, line 17
The RADIA application defines two new commands: Gateway-Request (RDR) The RADIA application defines two new commands: Gateway-Request (RDR)
and Gateway-Answer (RDA). The following sections describe these and Gateway-Answer (RDA). The following sections describe these
commands. commands.
3.3.1. The RADIA-Request (RDR) Command 3.3.1. The RADIA-Request (RDR) Command
The peer sends the RADIA-Request (RDR) command, indicated by the The peer sends the RADIA-Request (RDR) command, indicated by the
Command-Code field set to <CC1> and the Command Flags' 'R' bit set, Command-Code field set to <CC1> and the Command Flags' 'R' bit set,
in order to transmit a RADIUS message (encapsulated in the Radius- in order to transmit a RADIUS message (encapsulated in the Radius-
Message AVP (Section 3.4.1)) toward its final destination. The Message AVP (Section 3.4.1)) toward its final destination. The
Radius-Message AVP encapsulates a RADIUS request message (e.g., Radius-Message AVP will generally encapsulate a RADIUS request
Access-Request). message (e.g., Access-Request).
Message format: Message format:
<RDR> ::= < Diameter Header: CC1, REQ, PXY > <RDR> ::= < Diameter Header: CC1, REQ, PXY >
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Application-Id } { Auth-Application-Id }
{ Radius-Message} { Radius-Message}
[ User-Name ]
[ Destination-Host ] [ Destination-Host ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
* [ AVP ] * [ AVP ]
3.3.2. The RADIA-Answer (RDA) Command 3.3.2. The RADIA-Answer (RDA) Command
The peer sends the RADIA-Answer (RDA) command, indicated by the The peer sends the RADIA-Answer (RDA) command, indicated by the
Command-Code field set to <CC2> and the Command Flags' 'R' bit set, Command-Code field set to <CC2> and the Command Flags' 'R' bit set,
in order to transmit a RADIUS message (encapsulated in the Radius- in order to transmit a RADIUS message (encapsulated in the Radius-
Message AVP (Section 3.4.1)) toward its final destination. The Message AVP (Section 3.4.1)) toward its final destination. The
Radius-Message AVP encapsulates a RADIUS reply message (e.g., Access- Radius-Message AVP will generally encapsulate a RADIUS reply message
Accept). (e.g., Access-Accept).
Message format: Message format:
<RDA> ::= < Diameter Header: CC2, REQ, PXY > <RDA> ::= < Diameter Header: CC2, REQ, PXY >
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Application-Id } { Auth-Application-Id }
{ Radius-Message} { Radius-Message}
[ User-Name ]
[ Destination-Host ] [ Destination-Host ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
* [ AVP ] * [ AVP ]
3.4. Attribute-Value Pairs 3.4. Attribute-Value Pairs
This section describes the single AVP specific to the RADIUS-Diameter This section describes the single AVP specific to the RADIUS-Diameter
Gateway application. Gateway application.
skipping to change at line 253 skipping to change at page 7, line 34
Email: gwz@net-zen.net Email: gwz@net-zen.net
Lionel Morand Lionel Morand
Orange Labs Orange Labs
38-40 rue du general Leclerc 38-40 rue du general Leclerc
Issy-moulineaux Cedex 9 92794 Issy-moulineaux Cedex 9 92794
France France
Email: Lionel.morand@orange-ftgroup.com Email: Lionel.morand@orange-ftgroup.com
Tom Hiller
Lucent Technologies
1960 Lucent Lane
Naperville, Illinois 60566
USA
Email: tom.hiller@alcatel-lucent.com
 End of changes. 13 change blocks. 
33 lines changed or deleted 39 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/