RE: Guidelines suggested text for checklist:

["David B. Nelson" <dnelson@elbrysnetworks.com>]

Alan DeKok writes...

>   SDO inter-operability is an issue strictly for the SDOs, not 
> for the IETF.

Yes and no.  RADIUS is an IETF protocol.  The IETF has some interest in what
happens to it.  Defining extensions to RADIUS (new attributes) is not
exactly like defining new MIB modules, in that RADIUS has nothing akin to
SMI.  This document is intended to provide guidance for RADIUS attribute
design, much as the MIB design guidelines documents does for new MIB
modules.

I think that the IETF has a role to play in defining such guidelines, and
potentially in providing review of new RADIUS work against these guidelines.
That includes issue of interoperability.  The role of the IETF is therefore
consultative.  That's different from having no role. 

I would call your attention to RFC 4775, BCP 125 "Procedures for Protocol
Extensions and Variations".



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