Re: RADIUS Design Guidelines

[Barney Wolff <barney@databus.com>]

On Mon, Aug 28, 2006 at 10:50:02AM -0700, Glen Zorn (gwz) wrote:
> Nelson, David <> scribbled on Monday, August 28, 2006 10:28 AM:
> > 
> > If this is a serious problem, could we simply use two tag fields, one
> > to mark grouping for "data structuring" and another to mark grouping
> > for "continuation"?  
> 
> That's certainly one way to do it, & simple.  Another (more compact but
> less simple) way would be to give away the high-order bit of the tag to
> an "Attribute start flag"; this only allows 128 frags/attr (around 32K
> max attribute length) however.

Let me try it again:  What's wrong with using the special value of 0 for
extended-type to indicate that this extended attribute is a continuation
of the previous one?  That way, extra logic is only exercised when needed.

Pardon me for grumbling, but it was specifically to avoid this sort of
debate that some of us suggested we adopt the Diameter attribute header.
Oh well, never mind.

-- 
Barney Wolff         I never met a computer I didn't like.

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