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

[radext] #41: A1.2

#41: A1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  major                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space via "IETF consensus", and SHOULD
    NOT be allocated from the vendor space.

 [BA] A BCP should not be setting IANA allocation policy.  Recommended
 change:

    Does the data provide authentication and/or security capabilities for
    the RADIUS protocol, as outlined below?  If so, it SHOULD be
    allocated from the standard space.

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