[radext] #36: Section 3.2.3

["radext issue tracker" <trac@tools.ietf.org>]

#36: Section 3.2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 We therefore RECOMMEND that the introduction of
    new types and complex data types within RADIUS attribute
    specifications be avoided.  A potential exception to this
    recommendation occurs for attributes that inherently require code
    changes on both the client and server.  For example, as described in
    Appendix B, complex attributes have been used in situations involving
    authentication and security attributes that need to be dynamically
    computed and verified.

 [BA] This advice is not completely consistent with that in Section 2.1.
 Recommended change:

    As described in Section 2.1, the introduction of complex data
    types is discouraged where viable alternatives are available.
    A potential exception is attributes that inherently require code
    changes on both the client and server.  For example, as described in
    Appendix B, complex attributes have been used in situations involving
    authentication and security attributes that need to be dynamically
    computed and verified.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/36>
radext <http://tools.ietf.org/radext/>


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