My problem with draft-ietf-radext-design

["Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>]

Hi all, 

The document assumes a certain implementation and processing model. This
model is not explicitly documented in the draft and unfortunately has
implications on the design of attributes particularly when it comes to data
types used by RADIUS attributes and for the claimed problems that arise from
adding new code to the RADIUS server. 

In previous mail exchanges on the list I did not agree with certain aspects
of the implicitly assumed progressing model. I am, however, OK with
documenting the model and to thereby make it explicit to the reader. The
understanding of some of the claimed limitations might also be clearer.

Ciao
Hannes

PS: FYI, I stated my concerns previously on the RADEXT list.


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