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

Re: IPv6

Wojciech Dec (wdec) wrote:
> That same RFC 2865, in section 5, states:
> 
>       string    1-253 octets containing binary data (values 0 through
>                 255 decimal, inclusive).  Strings of length zero (0)
>                 MUST NOT be sent; omit the entire attribute instead.
> 
> With that, Ipv6 Prefix, Route options, Auth-IPv6-Prefix-User-ID, etc
> would be pretty much covered by using the string term.

  The document says that attributes are of type "string", and not IPv6
prefix or integer.  Re-defining "32-bit integer" to mean "string" is an
argument from absurdity.

>> 3.3 IPv6-Prefix
>>   Defines an 8-bit tag followed by a 64-bit integer.  There 
>> are NO existing attributes that are tagged 64-bit integers.  
>> This data type is new.
> 
> Are unsigned 64-bit integers really a new thing to Radius? 

  You missed the word "tagged" in the sentence above.  That makes my
comment meaningful, instead of nonsensical.

> That would
> seemingly contradict what's presented as de facto in
> http://tools.ietf.org/html/draft-ietf-radext-design-08#section-2.1.1

  Only if you take a discussion about "tagged" attributes, and ignore
key words like "tagged".

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