Re: FW: ISSUE: definition of RADIUS IPv6 "data types" arbitrary and unjustified

[Alan DeKok <aland@deployingradius.com>]

Alan DeKok wrote:
> Glen Zorn wrote:
>> However, simply examining the references shows that none of the RFCs cited
>> define _any_ "data types".

  And to fore-stall any discussion about IPv6... the RFCs referenced
*do* define RADIUS "value" fields that carry IPv6 addresses.

  Since RFC 2865 defines the "value" field of attributes to carry "data
types", and the IPv6 RFC you co-authored lists the "value" field as
carrying an IPv6 address, the only possible conclusion is that you have
personally created and defined the "ipv6 address" data type.

  The alternative is to conclude that the document you wrote specifying
the "value" field as an "IPv6 Address" does not, in fact, specify any
data type for that field.

  i.e. The statement that the field is an "Ipv6 address", and the
definition of it as "Address of 16 octets" should instead be interpreted
to mean "string of undistinguished octets with no obvious meaning".

  The only possible way to conclude that IPv6 data types don't exist in
RADIUS is to disown the documents that you wrote.  I expect that you
will therefore shortly file errata for those RFCs, withdrawing all
statements that the "value" field of IPv6 attributes have any meaning.

  I expect that you will, of course, also re-name the attributes at the
same time.  For example, "NAS-IPv6-Address" should be renamed as
"NAS-String-Of-No-Meaning".

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