[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Alan DeKok <aland@deployingradius.com>, Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Request for Review: "Issues and Fixes" changes
From: Glen Zorn <glen_zorn@yahoo.com>
Date: Wed, 22 Aug 2007 11:31:38 -0700 (PDT)
Cc: dnelson@elbrysnetworks.com, radiusext@ops.ietf.org
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ipawM4PqKzSAcEq5VZbSxszL63aSd3eJ/jUX9y7jCaZC9lPMv6nxytmbOPseiloPnG6W6Sgl4A7qsPtbRnEk4Ng59bGYpUIO9Dx/MFf7lVZ7uyA07T4M1RFKjMtgPoqn0Vm+lwsaj8HNNBBDHVdQpswAr/67F96lYL5RFqx85Uw=;
In-reply-to: <46CC05E6.7040201@deployingradius.com>

...

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?

Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.

Follow-Ups:
- Re: Request for Review: "Issues and Fixes" changes
  - From: Alan DeKok <aland@deployingradius.com>

References:
- Re: Request for Review: "Issues and Fixes" changes
  - From: Alan DeKok <aland@deployingradius.com>

Prev by Date: Re: Reminder: automated key management is often required for new protocols
Next by Date: Re: Request for Review: "Issues and Fixes" changes
Previous by thread: Re: Request for Review: "Issues and Fixes" changes
Next by thread: Re: Request for Review: "Issues and Fixes" changes
Index(es):
- Date
- Thread