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

[Alan DeKok <aland@deployingradius.com>]

Wojciech Dec (wdec) wrote:
> This would precisely be what one calls an "implementation choice".

  Or "15 years of RADIUS practice".

> I'd
> again suggest that the Radius WG could do much better then trying to
> deal with issues that are actually implementation issues, which does go
> to the heart of a lot of the arguments on this thread.

  Then my position has not been sufficiently clear.

  The issue is whether the document should describe only a subset of
implementations.

  There have been repeated statements that the document describes a
model which does not apply to current implementations.  These statements
are false.

  The follow-on requirement is to remove text which describes the
traditional model, and to insert text which describes a "modern" model.
 The resulting document would describe a significantly reduced subset of
RADIUS implementations.

  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.

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