RE: Rationalizing the RADIUS data model

[Avi Lior <avi@bridgewatersystems.com>]

John,

See inline.

> Barney,  write:
> 
> > I would strongly protest any move to make arbitrarily-formatted 
> > vendor- specific attributes retroactively prohibited.  There is 
> > absolutely no justification for any such move.  If you wish to 
> > contrain future vendor-specific attributes, you MUST define 
> a new Type 
> > code for that and confine the restriction to users of the new code.
> 
John responds:

> Knowing the enforcemant part of the IETF is rather weak, I 
> don't think you need to worry about this.  If the IETF 
> defines a standard content, and insists upon its use for 
> standard / interoperable usage, would this be a problem?  
>
The answer is yes!!!!!

Then what is the point of doing this?  This is going to generate more heat
then light.  It will be a pointless exercise. 

Surely we got better things to do then argue about something that wont  be
used or that is too little too late.

Avi

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