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

RE: no overall type in Extended Attributes



Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Hmm.  I seem to be having some serious problems communicating today,
> > or...anyway, I used the word "group" or its plural 3 times in one
> sentence.
> > How do you get the idea that tags aren't used for grouping?
> 
>   I think they *are* used for grouping.  You said you wanted to name a
> group of TLV's.  

No, I said that I want to name an attribute that consists of a group of
TLVs, not the same thing.  For example: a cryptosuite consists of a an
encryption algorithm identifier and an integrity-protection algorithm
identifier.  Multiple cryptosuite attributes can be in the same message.
Both the integrity-protection and encryption algorithms MUST be present or
the cryptosystem attribute is malformed.  I know how to do this easily & in
a way that comprehensible in Diameter or w/a legacy RADIUS attribute.
Apparently it is not possible to specify such a thing in an easily
comprehensible fashion using Extended Attributes.  I consider this to be a
problem (now -- I didn't before because I hadn't run into this,
short-sighted, I know); I'm not sure why (given your sympathetic concern for
programmers who would separate the word "hello" into 5 different attributes
;-) do not.

...



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