RE: Issue 290

["Bernard Aboba" <Bernard_Aboba@hotmail.com>]

David Nelson said:

"Would that be a RADEXT or DIME work item?"

It would probably be a DIME WG work item, assuming that they are willing to
take it.
However, before making progress on that we would need a viable proposal (and
a document 
that references it). 

David Nelson also said:

"There is a larger issue here, currently being discussed as part of the
RADIUS Design Guidelines commentary."

Is there an IETF last call comment on the Guidelines document relating to
this? 
I've been trying to keep the tracker up to date on the last call issues, but
I suspect I may be missing some. 

"I think we need to nail down that issue before we can effectively
close on the Design Guidelines and Extended Attributes drafts"

Since Extended Attributes uses Attribute 26, I had assumed that it
inherits all the capabilities of that attribute.  RFC 2865, Section
5.26 says:

      Multiple subattributes MAY be encoded within a single Vendor-
      Specific attribute, although they do not have to be.


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