[radext] #26: Terminology (Section 1.1)

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

#26: Terminology (Section 1.1)
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 standard space
      The 256 possible attributes that follow the format defined in
      [RFC2865] Section 5.

 vendor space
      The contents of the "String" field of a Vendor-Specific Attribute
       (VSA) ([RFC2865] Section 5.26).

 [BA] Given the extended attribute work, we may not want to define the
 standard space a bit more flexibly.  Also, the definition of vendor space
 should take the vendor-type field into account, no?
 Recommend this be changed to:

 standard space
      RADIUS attributes which are allocated by IANA and which follow the
 format defined in RFC 2865 [RFC2865] Section 5.

 vendor space
     The contents of the "String" field of a Vendor-Specific Attribute
 (VSA), as defined in [RFC2865] Section 5.26.  These attributes provide a
 unique attribute space for each vendor (identified by the Vendor-Type
 field) which they can self-allocate."

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