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

[radext] #33: Section 2.3

#33: Section 2.3
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  blocker                    |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 New commands (i.e., the Code field in the packet header) and new
    attributes in the standard space are allocated only through "IETF
    Consensus" as noted in [RFC3575] Section 2.1.

 [BA] The rules described in RFC 3575 are more complex than this.  In fact,
 some parameters require standards track. Recommended change:

    Requirements for allocation of new commands (i.e. the Code field in the
 packet header) and new attributes within the standards space are described
 in [RFC3575] Section 2.1.

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