IETF Logo Mail Archive

Re: Request for Review: "Issues and Fixes" changes

Alan DeKok <aland@deployingradius.com> Thu, 23 August 2007 08:53 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Thu, 23 Aug 2007 08:54:42 +0000
Message-ID: <46CD4B26.8030201@deployingradius.com>
Date: Thu, 23 Aug 2007 10:53:58 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Glen Zorn <glen_zorn@yahoo.com>
CC: Bernard Aboba <bernard_aboba@hotmail.com>, dnelson@elbrysnetworks.com, radiusext@ops.ietf.org
Subject: Re: Request for Review: "Issues and Fixes" changes
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

Glen Zorn wrote:
>>     ...
>>     Yes. RFC 2865 mentions only User-Password and CHAP-Password, and
>>     refers to other "authentication information". We could extend the list
>>     to include currently known authentication attributes. But I think it's
>>     better to give directions for future efforts.
>      
>     Speaking of which, shouldn't this be in the design guidelines,
>     rather than issues & fixes?

  Perhaps.  It's in the context of "clarifying how to use state", which
belongs in issues & fixes, because many people got it wrong.  How to use
State in the future is just another sentence here.  The text can be
re-iterated, and expanded in the "guidelines" document.

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

v2.23.0 | Report a Bug | By Email