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

RE: Glen's proposal for Attribute Extension



Bernard Aboba <mailto:bernard_aboba@hotmail.com> scribbled on Tuesday,
August 22, 2006 1:15 PM:

Sorry for the tardy response: my laptop's been in the shop getting
upgraded to WinXP.  Anyway, yes, I think that pretty much covers it.
Thanks for drawing it!

> Is the below a reasonable description of your proposal?
> 
>        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      |  Length       |            Vendor-Id
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> Vendor-Id (cont)           | Extended type |    Length2    |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |  
> Data... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-      
> 
>    Type
> 
>       26 for Vendor-Specific.
> 
>    Length
> 
>       >= 7
> 
>    Vendor-Id
> 
>       0 (for Extended Attributes)
> 
>    Extended Type
> 
>       0:       Reserved
>       1-250:   Allocated by IANA
>       250-255: Reserved
> 
>    Length2
> 
>       >=0
> 
>       Multiple subattributes MAY be encoded within a single Extended
>       Attribute, although they do not have to be.
> 
> 
> For Diameter compatibility, the RADIUS Extended Type attributes would
> need to be allocated within the Diameter AVP space. 

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