Issue: Vendor Specifc Attribute Values

["Nelson, David" <dnelson@enterasys.com>]

Submitter name: Dave Nelson
Submitter email address: dnelson@enterasys.com
Date first submitted: July 26, 2005
Reference: t.b.s.
Document: RADIUS Design Guidelines
Comment type: 'T'echnical 
Priority: '1' Should fix
Section: (new)
Rationale/Explanation of issue: Discuss the use of Vendor Specific
Atibute Values

Length description of problem

In addition to the well-documented Vendor Specific Attributes (VSA),
implementation practice has extended to Vendor Specific Values (VSV) of
IETF Standard RADIUS Attributes.

A snippet from a RADEXT list thread:

See:

http://www.freeradius.org/cgi-bin/cvsweb.cgi/radiusd/share/dictionary.ba
y?rev=1.5&content-type=text/x-cvsweb-markup

Look for "Service-Type".  Vendor-specific values are of the form
((vendor-id << 16) | num), One of the RFC's refers to this practice, but
I can't recall which right now. 

Requested change:

Describe the practice.  Include recommendations for or against the
practice, and standardize the recommend method of encoding, if the
practice is encouraged.


--
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/>