[radext] #42: A1.4

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

#42: A1.4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 A.1.4. Pre-existing data types


    There is a trade-off in design between re-using existing formats for
    historical compatibility, or choosing new formats for a "better"
    design.  This trade-off does not always require the "better" design
    to be used.  As a result. pre-existing complex data types described
    in Appendix B MAY be used, though this practice is NOT RECOMMENDED.

 [BA] Mailing list discussion indicates that there is not consensus to
 deprecate existing RADIUS types.  Suggested change:


    There is a trade-off in design between re-using existing formats for
    historical compatibility, or choosing new formats for a "better"
    design.  This trade-off does not always require the "better" design
    to be used.  As a result. pre-existing complex data types described
    in Appendix B MAY be used.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/42>
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/>