Proposal: Capabilities Attribute

[Bernard Aboba <aboba@internaut.com>]

Farid mentioned in his last message that we might want to move ahead on
defining a general Capabilities attribute.  Here is a strawman proposal:

Capabilities

   Description

      This Attribute includes a list of attribute types supported by
      the client.  One or more Capabilities attributes MAY be sent
      within an Access-Request packet.

   A summary of the Capabilities Attribute format is shown below.  The
   fields are transmitted from left to right.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |      Value    |    String..
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Type

      TBD for Capabilities.

   Length

      >= 3

   Value

      The Value field is one octet, falling in the range between 1
      and 253.

   String

      The String field is one or more octets.

      Where the Value field is not equal to 26, the String field
      contains a list of Type values, 1 octet per Type; up to
      253 Type values may be included within each Capabilities
      attribute.

      Where the Value field is equal to 26, the format of the String
      field is as follows:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Vendor-Id                    |   String2...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Id

      The Vendor-Id field is 3 octets, containing the SMI
      Management Private Enterprise Code of the Vendor in
      network byte order, as defined by [IANA].

   String2

      The String2 field is one or more octets.  The actual format of the
      information is site or application specific as described in
      [RFC2865] Section 5.26.

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