IETF Logo Mail Archive

RE: Issue 226: RFC 3576bis and Renumbering

"David B. Nelson" <d.b.nelson@comcast.net> Wed, 30 May 2007 12:59 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Wed, 30 May 2007 13:00:51 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: radiusext@ops.ietf.org
Subject: RE: Issue 226: RFC 3576bis and Renumbering
Date: Wed, 30 May 2007 08:59:32 -0400
Message-ID: <01bb01c7a2ba$5e16fc90$6401a8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: AceikYw7yAEm4QulTxa71X4R8D9t6QAIWhBwAAGpkIA=

Amending my last post...

> Secret sauce?  That is a very valid question, to which I'm 
> sure there is an answer.  I'm equally sure that it hasn't been 
> provided in this thread.  :-)

Actually, I take that back.  One possible answer has been mentioned briefly
in this thread, Glen's "logoff" draft
http://www.ietf.org/internet-drafts/draft-zorn-radius-logoff-09.txt
which allows a NAS to send messages to the RADIUS Server, and a co-located
Dynamic Authorization Client, indicating the beginning and end of sessions.
We have not discussed this draft in RADEXT because it relies on new RADIUS
command codes, which are currently out of scope.




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

v2.23.0 | Report a Bug | By Email