[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[radext] #38: Section 3.3.2

#38: Section 3.3.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Nevertheless, following the guidelines outlined within this document
    has many advantages.  Following these guidelines means that RADIUS
    servers can be updated to support the vendor's equipment by editing a
    RADIUS dictionary.  It is therefore RECOMMENDED that vendors follow
    the guidelines outlined here, which are intended to enable maximum
    interoperability with minimal changes to existing systems.  If these
    guidelines are not followed, then the vendor's equipment can only be
    supported via code changes in RADIUS server implementations.  Such
    code changes add complexity and delay to implementations.

 [BA] This advice is repeated elsewhere so it can be deleted here.

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