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

Re: Attribute Design Guidelines and RADIUS layering (was:[RADIUS FIXES] Authorize Only / RADIUS layering criteria)



"Nelson, David" <dnelson@enterasys.com> wrote:
> I would like to reiterate that I think re-definition, over-loading or
> private agreements to modify the semantics of any IETF standard RADIUS
> attribute is harmful to the integrity and multi-vendor interoperability
> of the protocol.

  Let's add that text to the "issues & fixes" draft.

> It *is* important that vendors be able to use VSAs for proprietary
> features that do not have wider applicability.  It is also important
> that vendors, other WGs, or other SDOs be able to create and properly
> document fully interoperable IETF standard attributes, when appropriate.

  Agreed.  Let's re-iteratite again in the draft.

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