[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RFC3576bis and Session State
Something like this might make sense, but I don't think it's required to be included in RFC 3576bis. What we do need is clear text on the effect of including various session identification attributes in a CoA-Request/Disconnect-Request.
> From: firstname.lastname@example.org
> To: email@example.com
> Subject: RE: RFC3576bis and Session State
> Date: Wed, 30 May 2007 16:45:27 -0400
> All of this discussion leads me to believe we need a document that describes
> the current state of affairs with the creation, naming and modification of
> sessions, sub-sessions, multi-sessions and the like in RADIUS deployments.
> This could be a section of RFC3576bis or it could be stand-alone document.
> Do I recall that someone once attempted to write such a document? Or am I
> just remembering a long thread from the RADEXT list about three or four
> years ago?
> to unsubscribe send a message to firstname.lastname@example.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>