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

Re: Review of draft-ietf-radext-status-server

To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Review of draft-ietf-radext-status-server
From: Alan DeKok <aland@deployingradius.com>
Date: Fri, 22 Jan 2010 07:53:02 +0100
Cc: 'Ignacio Goyret' <igoyret@alcatel-lucent.com>, igoyret@lucent.com, radiusext@ops.ietf.org
In-reply-to: <BLU137-DS1CD0967AB65A86C97329493620@phx.gbl>
References: <BLU137-DS7CC96B2843AF5673A1BD5936D0@phx.gbl> <201001212330.o0LNUoX4003769@cliff.eng.ascend.com> <BLU137-DS1CD0967AB65A86C97329493620@phx.gbl>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)

Bernard Aboba wrote:
> It had been my assumption that these codes had been implemented at the time
> that RFC 2865 was published (June 2000), but perhaps that was not the case. 

  IIRC, the Cistron RADIUS server had support for Status-Server in 1998
or 1999.  I believe the idea had originated from elsewhere, but I can't
find any reference for that right now.

  In any case, there are a number of implementations using it now.

  Alan DeKok.

--
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:
- RE: Review of draft-ietf-radext-status-server
  - From: "Bernard Aboba" <bernard_aboba@hotmail.com>

Prev by Date: RE: Proposed resolution to guidelines document
Next by Date: Re: "Last Look" at the RADIUS Design Guidelines document
Previous by thread: RE: Review of draft-ietf-radext-status-server
Index(es):
- Date
- Thread