Re: "Last Look" at the RADIUS Design Guidelines document

[Avi Lior <avi@bridgewatersystems.com>]

Okay then the target is SDOs.

Then fix the messaging...
In essence the document is talking about how bad COmplex Types are.   And that the IETF does not recommend using them and thus we wont recommend your specifications.

The reality is that every SDO uses them and will continue to use them - because they solve real world problems.

Fix this document.


On 11-01-2010, at 22:50 , Alan DeKok wrote:

> Avi Lior wrote:
>> You can talk about the perils of complex types it the document that actually talks about complex types.
> 
>  Many complex types are defined in documents that are SDO and
> vendor-specific.  The IETF cannot influence those documents, other than
> by publishing an IETF BCP.
> 
>  So... we have the "guidelines" document.
> 
>  The "extended attributes" document talks about the "extended
> attributes" complex type.  SDOs and vendors will *still* create complex
> types not matching that document.  There needs to be guidelines to cover
> those situations.
> 
>  So... we have the "guidelines" document.
> 
>  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/>