[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Proposed resolution to Issue 325
For the most part the revision looks OK. I'm OK with recommending to
try to use existing types and resort to complex/new types if there is a
compelling reason not to use the basic types. After seeing all the
discussion on the list, I think there still is some question over when
to use complex/new data types and when not to. I'm not sure this is
easily resolved. The document favors reducing complexity in certain
aspects of server implementation. This may be appropriate for some
cases, but in others it may be appropriate to reduce complexity in
another area, such as on the NAS. The document doesn't seem to be very
clear on this, but perhaps it doesn't intend to or need to be.
Cheers,
Joe
> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org]
> On Behalf Of Bernard Aboba
> Sent: Tuesday, January 19, 2010 9:16 AM
> To: Joseph Salowey (jsalowey)
> Cc: 'radext mailing list'
> Subject: Re: Proposed resolution to Issue 325
>
> Do the changes made below address your issue?
> http://git.freeradius.org/ietf/draft-ietf-radext-design-11.txt
>
>
> -----Original Message-----
> From: Alan DeKok [mailto:aland@deployingradius.com]
> Sent: Tuesday, January 19, 2010 9:12 AM
> To: Bernard Aboba
> Cc: 'radext mailing list'
> Subject: Re: Proposed resolution to guidelines document
>
> Bernard Aboba wrote:
> > Do these changes address Issue #325?
>
> Comments:
>
> (A) addressed by updated text on "new" data types, rather than
> "complex" types
>
> (B) addressed by moving the text to the security section, and
> replacing discussion of "application" with "other systems". Also
> addressed security issues of complex types by noting more clearly that
> *change* has security implications.
>
> (C) previously fixed
>
> (D) Not addressed. We seem to disagree on the utility of the
> recommendations.
>
> (E) previously answered && acknowledged as closed on-list.
>
> 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/>
--
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/>