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

RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"



Alan DeKok <mailto://aland@deployingradius.com> writes:

> 
> Glen Zorn wrote:
> > OK, are you saying that the existing text isn't clear?  It seems
> pretty
> > precise to me, should it be more vague (e.g., "long" & "short")?
> 
>   I just wanted to be sure I understood it.

OK.

> 
> >>       Two (2) octets.  Up-to-date values of the Ext-Type field are
> >>       specified in the most recent "Assigned Numbers" [IANA].
> Values
> >>       XXXX-YYYY are reserved.
> >>
> >>   I would suggest reserving the top 1K: 64512-65535
> >
> > Rationale?
> 
>   Numbers are better than XXXX-YYYY. :)  As for using the top 1K rather
> than 256, or 32, or 4.... it's small enough that we likely won't need
> the attribute numbers later, and large enough it gives a lot of room to
> work with.
> 
>   I'd say 32 may be too small, and anything over 1K is likely too
> large.

OK.  Any other opinions?

> 
> > Actually, I'd just as soon discard the examples: this draft has way
> too much
> > flavor of a tutorial for my taste...
> 
>   Sure.

Great!  Anybody married to section 6?  If not, it's gone...


> 
> >>   The examples could also given broken-out hex encoding of the
> >> attributes, which may be clearer than the ASCII art diagrams.  e.g.
> >>
> >>   1a 0f 00 00 00 00 00 01 01 08 48 65 6c 6c 6f
> >
> > You're joking, right?
> 
>   Other RFC's have hex examples...

Sure, but I thought that we were writing not with any expectation of a
reasonable level of shared knowledge but for the LCD...

> 
> >>   I suggest leaving the first 0..255 attributes as unallocated, in
> >> order
> >> to avoid confusion with legacy RADIUS attributes.
> >
> > Presumably the people who would get confused are those who have to be
> told
> > to protect against buffer overflows (& send "hello" as five separate
> > attributes), right?
> 
>   Yes.
> 
>   I should put up a web page listing all of the "creative"
> interpretation of the RFC's.  Some people have put a lot of effort into
> doing the most inventive things.

"There is no end to the folly of men..."

> 
>   Alan DeKok.



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