[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: request to recharter

To: <radiusext@ops.ietf.org>
Subject: RE: request to recharter
From: "David B. Nelson" <d.b.nelson@comcast.net>
Date: Wed, 13 Feb 2008 18:21:33 -0500
In-reply-to: <BLU137-W373C77F8C85B840DB316AE93240@phx.gbl>
References: <200802111126.25340.stefan.winter@restena.lu> <47B3214B.4050407@nitros9.org> <078001c86e67$5fec7d00$011716ac@NEWTON603> <BLU137-W373C77F8C85B840DB316AE93240@phx.gbl>

Bernard Aboba writes...

> There is already a proposed standard for the transport of AAA protocols
> over TCP, "Authentication, Authorization and Accounting (AAA) Transport
> Profile", RFC 3539.

Yes.  Alan pointed that out in a follow up message.  Was that document
created as part of the Diameter requirements work?  Just curious.


--
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/>

References:
- request to recharter
  - From: Stefan Winter <stefan.winter@restena.lu>
- Re: request to recharter
  - From: Alan DeKok <aland@nitros9.org>
- RE: request to recharter
  - From: "David B. Nelson" <d.b.nelson@comcast.net>
- RE: request to recharter
  - From: Bernard Aboba <bernard_aboba@hotmail.com>

Prev by Date: RE: request to recharter
Next by Date: RFC 5090 published as a Proposed Standard
Previous by thread: RE: request to recharter
Next by thread: RE: request to recharter
Index(es):
- Date
- Thread