Request for review: Diameter NASREQ specification

Bernard Aboba <aboba@internaut.com> Thu, 11 March 2004 16:15 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 11 Mar 2004 16:06:42 +0000
Date: Thu, 11 Mar 2004 08:15:50 -0800
From: Bernard Aboba <aboba@internaut.com>
To: radiusext@ops.ietf.org
Subject: Request for review: Diameter NASREQ specification
Message-ID: <Pine.LNX.4.56.0403110809460.6128@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-ID: <Pine.LNX.4.56.0403110809462.6128@internaut.com>

The Diameter NASREQ specification is in the last phases of review prior to
publication as an IETF Proposed Standard.  This specification is quite
important to the evolution of both Diameter and RADIUS because it contains
the specification of the RADIUS/Diameter gateway.

The RADIUS/Diameter gateway is designed to translate RADIUS attributes to
Diameter AVPs and vice versa, as well as handling translation between
RADIUS and Diameter commands.

In effect, the RADIUS/Diameter gateway specification defines what it means
for a RADIUS "extension" to be backward compatible with Diameter;  if the
gateway can handle it, it's compatible; if it cannot be handled, that
extension is not compatible.

It is therefore quite important that this specification be carefully
reviewed prior to publication.

The specification is available at:
http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-nasreq-14.txt

Please send comments to the AAA WG mailing list (aaa-wg@merit.edu) using
the Issues format described on the Issues list:

http://www.drizzle.com/~aboba/AAA/issues.html

Please send comments by the Friday, March 19, 2004.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

Request for review: Diameter NASREQ specification Bernard Aboba