Location draft issues raised today

["Alan DeKok" <aland@ox.org>]

  There were concerns rasied in the meeting today about the encoding
of location data in RADIUS attributes.  I'll expand on my comments here:

 - If the encoding of the location information is taken from a
normitive reference (as suggested in the WG meeting), then the packing
of that information should be outside of the scope of RADEXT.  The
description of the complex encoding in the draft should be replaced by
a normitive reference to another document.

  That would resolve all of the concerns around complex attribute
encodings in RADIUS.

 - If, on the other hand, the encoding is specific to these attributes
and occurs nowhere else, then the packing is within the scope of
RADEXT, and the concerns raised should be addressed by the document
authors.

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