[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: FW: Review of Radius Guidelines 11
In terms of process, my suggestion is to discuss proposed changes to the
text on the list, and incorporate them within a -12 version to be submitted
by the deadline. At IETF 77, we can then go over what additional changes
(if any) are necessary.
-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Alan DeKok
Sent: Wednesday, February 24, 2010 8:12 AM
To: Bernard Aboba
Cc: radiusext@ops.ietf.org
Subject: Re: FW: Review of Radius Guidelines 11
Alan DeKok wrote:
To summarize: the comments can be divided into a few rough areas:
- minor fixes
- these should be addressed
- requests to define *new* methods/architectures in the document
- these should be rejected
- requests to change the document or add explanations
- I would appreciate suggested text.
As editor, I welcome suggestions from the WG on how to improve the
document. I have offered many suggestions in the past, and given the
volume of requested changes, ask for guidance from the WG on what to do
next.
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/>