RE: Sumary of feedback on draft-ietf-dhc-agentopt-radius-07.txt

["Nelson, David" <dnelson@enterasys.com>]

> OK thanks. Having text that suggests a possible solution will
> (I hope/assume) help a lot in trying to come to resolution.

Let me take this one step further, then, and convert the meta-text of my
comment into specific proposed text for inclusion in the draft:

"The scope of applicability of this specification is such that robust
interoperability is only obtained for RADIUS client and server
implementations that exist within the same scope as the DHCP protocol,
i.e. within a single, localized administrative domain.  Global
interoperability of this specification, across administrative domains,
is not required."

And

"The use of the standard keywords MUST, SHOULD, MUST NOT and SHOULD NOT
within this specification are with respect to RADIUS clients and servers
that implement the optional features of this specification, do not
create any normative requirements outside of that scope and do not
modify the base RADIUS specifications, such as RFC2865 or RFC2866."