RE: Questions on modified Extended Attribute format?

[Avi Lior <avi@bridgewatersystems.com>]

You are correct.  In RADIUS definitions we define attributes by specifying the format and meaning.

When we define the meaning typically we say when this attribute "when included in an access accept message it means ...." and "when included in an access request it means ...."

Now if we want to reuse the attribute (because we love the format) in a new container.  We would just have to modify the meaning part of the definition by adding "when the attribute appears as part of this grouping it means ..."

Going forward if you really want to promote reuse when it is possible you would just define the syntax of the attribute and then when you define the container (grouping) which includes that attribute you would define what it means when this attribute is in a particular container/grouping.

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of David B. Nelson
> Sent: Wednesday, January 09, 2008 10:43 AM
> To: radiusext@ops.ietf.org
> Subject: RE: Questions on modified Extended Attribute format?
>
> Avi Lior writes...
>
> > An attribute can appear standalone and also be included in a group
> > (for that matter, in many groups).  The definition of the
> attribute is
> > the same in both cases, but the semantics is different right?
>
> I'm confused by this.  The "definition" of the attribute
> consists of syntax
> (format) and semantics (meaning).  What does it means to say
> that the definition is the same but the semantics (meaning)
> is different?
>
>
>
>
> --
> 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/>
>

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