Re: Extended-Space attribute draft available

[David Mitton <david@mitton.com>]

On 2/27/2006 09:09 PM, Barney Wolff wrote:
> Greg Weber and I have written a draft defining an Extended-Space
> attribute.  Here's the abstract:
>
>    The RADIUS protocol is being extended beyond the wildest imaginations
>    of its original designers.  These extensions are pushing up against
>    the existing limitations on the numbers, length, base types and
>    grouping of RADIUS attributes.  This document specifies a method of
>    relaxing those limitations.
>
> While it works its way to the IETF draft directory, you're welcome
> to retrieve it here:
>
> http://www.databus.com/.ietf/draft-wolff-radext-ext-attribute-00.txt
> http://www.databus.com/.ietf/draft-wolff-radext-ext-attribute-00.html
>
> This draft is a companion piece the the design guidelines draft, and,
> we hope, will be adopted as a RADEXT work item.
>
> Comments and corrections are welcome, and if necessary I can try to
> get a -01 version in before next week's deadline.
>
> Barney Wolff

An alternative to this format could be a variation on my RADIUS 
Diameter VSA format in
http://www.ietf.org/internet-drafts/draft-mitton-diameter-radius-vsas-01.txt

where we could do something like:
(he says, editing on the fly)....


RADIUS Diameter AVP:

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Type = TBA   |    Length     |r M P r r r r r|    Segment    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 Type (first segment only?)                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                      Attribute-Data ...
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Flags M & P retrain their Diameter values.

      RADIUS Type = TBA
      RADIUS Length (3~255)
      Flags = from Diameter message
      Segment = 0-63, Segment number for data lengths greater than 246,
      Type = 4 bytes from the Diameter Type code
      Data = upto 246 bytes

   For Diameter values with lengths greater than 246, the additional
   data would be put in consecutive attributes, in the same manner as
   EAP [RADIUS-EAP], [RFC3579].

   The Segment field will be zero for the first attribute, and each
   sucessive attribute data segment will increment the Segment field.
   The Vendor-Id and Vendor-Type SHALL not be repeated.

   Note that RADIUS applications that do not understand the
   attribute will not honor the Diameter M and P flags.  These flags
   have no meaning in RADIUS, but are preserved for vendor specific
   meaning and potential transport back to Diameter.


Dave. 


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