[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RADEXT WG last call on RADIUS Design Guidelines Document
I went through the current RADIUS Guidelines doc and do not have anytechnical comments -one question and a couple minor editorial comments
below. I think the doc can be passed to IESG.
Question: In the description of polymorphic attributes (sec 3.2), what
does this mean: "...the meaning of an attribute may depend on earlier
packets in a sequence." ? Is that referring to a request/challenge sequence?
Minor Editorial changes:
Sec 1.1: "it's usage" -> "its usage"
Sec 2.1.3: "to introduced" -> "to be introduced"
Sec 2.1.3: "This issues" -> "These issues"
Sec 2.1.3: "attributes involve authentication" -> "attributes involving authentication"
Sec 2.1.3: I'd remove the "(e.g., IPv6 address)" from the last paragraph. That's not
a good example anymore as we've earlier called IPv6 a basic data type in Sec 2.1.1.
Sec 2.2: Last paragraph has the wrong indentation
Sec 3.1.1: "vendors and SDOs they SHOULD" -> "vendors and SDOs SHOULD"
Sec 3.1.3: Expand PEC acronym at first use?
Sec
A.1.2: "not included nested groups" -> "not include nested groups"
Greg
On Dec 26, 2007 12:53 PM, <
Bernard_Aboba@hotmail.com> wrote:
This is an announcement of RADEXT WG last call on
the
"RADIUS Design Guidelines" document, prior
to sending
it to the IESG for publication as a Proposed
to this solicitation if you have read the
document, regardless of whether you
have comments to provide or not. In your
email, please state whether you
believe that the document is ready for
publication.
If you have comments to provide, please send them
to the