RE: "Last Look" at the RADIUS Design Guidelines document

["Dave Nelson" <d.b.nelson@comcast.net>]

>   The document would cease to be a RADIUS BCP.  It would become an SDO
> BCP, and would describe practices that are SDO specific.
> 
>   If you want such a document, go write it in an SDO.

I'm not sure that's the best possible advice, either.  The "preferred future
state" is a more unified RADIUS data model, not a more fragment one.

While SDOs are certainly free to follow specific guidelines for RADIUS work
that is SDO-specific, I'm not aware that we have SDO-specific RADIUS server
implementations.  Or at the very least, we would likely run into the same
set of issues when attempting to deploy these new attributes on legacy
RADIUS servers.  For that reason, I'm not sure such a "walled garden"
approach would really work.


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